POST
|
To clarify: I notice this behavior when the line is composed of only 2 vertices such that one WSE point covers the start (FROM) vertex and another WSE point covers the end (TO) vertex. The corresponding line in the Output Line 3D has Shape_Length = 0 and the TOZ = FROMZ such that the FROMZ = the value of the WSE point that covers the start (FROM) vertex.
... View more
09-08-2016
03:49 PM
|
0
|
0
|
250
|
POST
|
I notice this behavior when the line is composed of only 2 vertices.
... View more
09-08-2016
01:34 PM
|
0
|
1
|
250
|
POST
|
How to disable Attribute Table editing for a specific layer - or all layers? I have editable feature service layer, but I do not want user to be able to edit this layer through the Viewer's Attribute Table. Edits will be done only in the popup or a custom dialog. I'm developing with the API. Seems there should be a setting in the Viewer's config files, in the xaml resource styles, or a way to programmatically disable editing in the underlying FeatureDataGrid.
... View more
03-17-2015
07:47 AM
|
0
|
0
|
3761
|
POST
|
Did you find the solution? There is barely any mention of this issue in the forums. In Flex API forum is a post of the same problem. ESRI response says it will be fixed in the next release(?) and mentions a workaround of setting the value to Number.NaN. I don't know to what that translates in the JSON update string. It would be odd for the Server REST API to know how to handle "VALUE":NaN (???), but not know how to handle the typical "VALUE":null.
... View more
01-28-2015
09:11 AM
|
1
|
1
|
563
|
POST
|
I'm surprised how little discussion there is of this issue in the forums and the docs. At which release is this fixed? I'm at 10.1 with the problem. What value does Number.NaN translate to in the JSON request? Does this workaround work for a nullable attribute of any GDB data type? What is the workaround from Silverlight?
... View more
01-28-2015
08:42 AM
|
0
|
0
|
344
|
POST
|
This tweak works as expected when run from my dev machine. But when I deploy the app to the production server, the popup reverts to its original out-of-the-box appearance, i.e. displays the PopupItem.Title. When I delete Config\Layouts\ResourceDictionaries\Common\OnClickPopupContainerStyle.xaml from both my dev and production server, and the popups on both show only the original out-of-the-box appearance, i.e. display the PopupItem.Title. This indicates the popup has a default template that is defined elsewhere, but more importantly, this means my production server is unable to override the default template by applying the OnClickPopupContainerStyle.xaml. Any ideas why the production version will not apply OnClickPopupContainerStyle.xaml? I wonder if it is a file/folder permission issue with Config\Layouts\ResourceDictionaries\Common\OnClickPopupContainerStyle.xaml on the production server.
... View more
01-07-2015
04:20 PM
|
0
|
0
|
608
|
POST
|
Show Related Records appears at the bottom of the popup window when you click a feature. On click Show Related Records the related records are displayed in a table.
... View more
08-21-2014
01:25 PM
|
1
|
0
|
828
|
POST
|
It is odd the WAB popup doesn't even have the Show Related Records tool already built into the AGO Javascript Map Viewer.
... View more
08-21-2014
01:16 PM
|
0
|
3
|
828
|
POST
|
Filter widget/functionality like that already built into the AGO Javascript map viewer: where in the latter you go Content->click the drop down arrow next to the layer->context menu opens with Filter option->Filter dialog opens and enables end user to create|execute|edit their own query on a series of expressions. The WAB Query widget looks similar to the AGO Filter tool, but former doesn't allow end user to build their own query (as far as I can tell). Moreover, the WAB Query widget at beta 2 is so buggy and unusable, I'm not able to make sense of it. At WAB beta 2, seems ESRI could just take the AGO Filter tool and add it to WAB (and even replace most of the Query widget code with AGO Filter code).
... View more
08-21-2014
12:57 PM
|
0
|
0
|
828
|
POST
|
A good idea is to make a new control inherits from Attachment Editor control then override onApplytemplate method to get the ItemsControl object. After that you can listen on ItemsSource property changed via DependencyProperty.RegisterAttached Method. Check this post for more information. ItemsControl attachmentListControl = null;
public override void OnApplyTemplate()
{
base.OnApplyTemplate();
attachmentListControl = GetTemplateChild("AttachmentList") as ItemsControl;
RegisterForNotification("ItemsSource", this.attachmentListControl, new PropertyChangedCallback(ItemsSourceChanged));
}
public void ItemsSourceChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
{
System.Collections.ObjectModel.ObservableCollection<AttachmentInfo> attachmentInfoList = e.NewValue as System.Collections.ObjectModel.ObservableCollection<AttachmentInfo>;
attachmentListControl.ItemsSource = attachmentInfoList.Where(x => x.Name.Contains(".pdf")); //or better check content type
}
public void RegisterForNotification(string propertyName, FrameworkElement element, PropertyChangedCallback callback)
{
Binding b = new Binding(propertyName) { Source = element };
var prop = System.Windows.DependencyProperty.RegisterAttached("ListenAttached" + propertyName, typeof(object), typeof(UserControl), new System.Windows.PropertyMetadata(callback));
element.SetBinding(prop, b);
} you can also add another property for your filter to be more dynamic. Hope this helps. Regards, From what I can understand this approach would work, too. How do you know the ESRI AttachmentEditor contains an ItemsControl named "AttachmentList" (and that it is an ItemsControl)?
... View more
06-26-2014
11:04 AM
|
0
|
0
|
442
|
POST
|
Brilliant. Thank you. I implemented a converter and it works fine. Something like this: public class FileVisibilityConverter : IValueConverter
{
public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)
{
string fileName = System.Convert.ToString(value); // Current file name
string extension = System.Convert.ToString(parameter).ToLower(); // Visible extension, e.g. ".pdf"
if (System.IO.Path.GetExtension(fileName).ToLower() == extension)
{
return Visibility.Visible;
}
else
{
return Visibility.Collapsed;
}
}
public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)
{
throw new NotImplementedException();
}
}
<DataTemplate x:Key="AttachmentEditorTemplate">
<Grid Margin="3" Visibility="{Binding Name, Converter={StaticResource FileVisibilityConverter}, ConverterParameter='.pdf'}">
...
... View more
06-26-2014
10:33 AM
|
0
|
0
|
442
|
POST
|
Is it possible to filter the files that are displayed in the AttachmentEditor's ListBox sub-component? By default, the AttachmentEditor's internal ListBox is bound to all of the files (AttachmentInfos) associated with the current graphic. I would like to be able to tell the AttachmentEditor to only list files of, say, type .pdf, or limit the files displayed using some flexible query of the AttachmentInfo properties. This doesn't seem possible because no kind of filter/query of the attachments is built into the AttachmentEditor, nor does the attachment editor expose its ListBox sub-component or its internal list of attachments. Perhaps the easiest solution is to grab the AttachmentEditor source code and tweak as necessary. Note well, I'm not at all referring to the Filter, FilterIndex, and Multiselect properties which control the open file dialog.
... View more
06-25-2014
11:37 AM
|
0
|
5
|
698
|
POST
|
I have since used Fiddler to tamper with the queryRelatedRecords response from ArcGIS Server 10.2.1. I set a breakpoint on the response. In the JSON response I changed the "OBJECTID" attribute to "objectId" (in JSON snippet shown below). {"fields":[...],"relatedRecordGroups":[{"OBJECTID":1,"relatedRecords":[...]}]} I resumed and stepped through the C# code. With that change, the RelationshipResult now contains the related records. This seems to confirm that ESRI has changed the syntax of the relatedRecordGroups JSON object at least at v10.2.1 and this syntax is not handled by the query classes in the ArcGIS Silverlight v3.2 Tasks library.
... View more
01-30-2014
07:32 AM
|
0
|
1
|
262
|
POST
|
I've been unable to successfully complete a relationship query of my feature services using 1) the Get Related Records tool (aka Query Related Records Tool) in SL 3.2 Viewer and 2) using the SL API v3.2. My feature services run on ArcGIS Online hosted services account for developers. Note ESRI runs these ArcGIS Online subscription and developer accounts on ArcGIS Server v10.21. I believe the problem is that the query classes in the SL 3.2 API Tasks library cannot handle a new JSON syntax returned by the queryRelatedRecords REST operation on AGS v10.21. Here is a sample relationship query that successfully executes on an ESRI sample server service which ESRI happens to run on ArcGIS Server v10.0. queryTask = new QueryTask("http://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Petroleum/KSPetro/MapServer/0");
queryTask.ExecuteRelationshipQueryCompleted += QueryTask_ExecuteRelationshipQueryCompleted;
//Relationship query
RelationshipParameter relationshipParameters = new RelationshipParameter()
{
ObjectIds = new int[] { 113880 },
OutFields = new string[] { "*" },
RelationshipId = 3,
ReturnGeometry = false
};
queryTask.ExecuteRelationshipQueryAsync(relationshipParameters);
void QueryTask_ExecuteRelationshipQueryCompleted(object sender, RelationshipEventArgs e)
{
RelationshipResult pr = e.Result;
if (pr.RelatedRecordsGroup.Count == 0)
{
//RelatedRecordsGroup.Count is always zero when query is executed on ArGIS Server 10.21
//But when executed against ArcGIS Server 10.0, RelatedRecordsGroup does contain the related records
}
else
{
foreach (var pair in pr.RelatedRecordsGroup)
{
//Do something
}
}
} When I execute the same code on my feature service which runs on ArcGIS Online hosted feature services v10.21, the related records group count is always zero. Interestingly, no matter if I query the ESRI sample service or my own AGO account service, in Fiddler the REST queryRelatedRecords query is always valid AND the response DOES contain the related records. However, when I query my services on v10.21 the related records in the JSON response never make it into the ArcGIS Silverlight API query objects. I closely examine the requests and responses in Fiddler. When I query the sample service on ArcGIS Online v10.0, the JSON response format is: {"fields":[...],"relatedRecordGroups":[{"objectId":1,"relatedRecords":[...]}]} However, when I query my feature service running on ArcGIS Online v10.21, the JSON response format is {"fields":[...],"relatedRecordGroups":[{"OBJECTID":1,"relatedRecords":[...]}]} Notice the subtle difference in JSON syntax. From AGS v10.0 the related record group object is identified by the object ID attribute.In AGS v10.0 the object ID name is camel-cased: "objectId". However, in AGS v10.21 the object ID attribute is all-caps: "OBJECTID". I suspect the query classes in the ArcGIS Silverlight API v3.2 are case-sensitive to the JSON response. I think the query classes expect the relatedRecordGroups to be identified by the camel-case object ID attribute. At AGS 10.2 ESRI seems to have changed the same attribute to the all-caps "OBJECTID". According to my tests, the query classes are unable to de-serialize the related records in the JSON response presumably because the API expects the related records groups to be identified by a camel-cased object ID, rather than an all-caps object ID. This "bug" seems to make it impossible to use the ArcGIS SL API v3.2 to successfully complete a relationship query on AGS v10.21.
... View more
01-30-2014
06:26 AM
|
0
|
2
|
1448
|
POST
|
The Query Related Records tool in Viewer for SL 3.2 always shows "No related records found" when querying, in my case, a feature service that contains a feature class that participates in a 1:m relate with a table. The Get Related Records button on the Pop Up toolbar is active, so I know the Query Related Records tool recognizes the presence of the relationship. And in Fiddler, I see the tool generates a GET request that is valid and I see the response is, in fact, the expected related records as JSON. I copy and execute the GET URL in my browser and again I get the expected related records as JSON. Also, I can compose and execute the same queryRelatedRecords op on the REST services directory and I get the expected related records. So I can't figure out why in the Viewer for SL 3.2, the tool always displays "No related records found". Clearly, related records are being returned, but the tool itself doesn't handle them. I plan to download and debug the tool's source code. But for now, I'm wondering does this tool even work for anyone and am I missing anything obvious that would enable it to function correctly?
... View more
01-27-2014
01:05 PM
|
0
|
1
|
1907
|
Title | Kudos | Posted |
---|---|---|
1 | 01-28-2015 09:11 AM | |
1 | 08-23-2012 08:56 AM | |
1 | 08-21-2014 01:25 PM |
Online Status |
Offline
|
Date Last Visited |
06-08-2021
09:53 AM
|