IDEA
|
Hello, With Arcpy it is possible to enable Time on a MXD's feature layers. This can be done with the 'UpdateLayerTime' utility from the 'arcpy.mapping'. We also want this utility for tables! After support from Esri, it is confirmed that it is not possible to enable Time on a MXD's tables. Some extra info, when you put a MXD's table in the UpdateLayerTime utility you get an error. We would like to get the feature to enable Time on tables with Arcpy. With kind regards, Cees van Altena
... View more
10-19-2017
11:45 PM
|
5
|
4
|
865
|
POST
|
Me and two other developers have been pulling our hairs for 4 hours to find out where this post build event was coming from and the above reply is definitely not helping.
... View more
12-12-2016
05:05 AM
|
0
|
1
|
1628
|
POST
|
[...] featureLayer.graphicsCollection does not exist. The Migration page in the guide is wrong and will be updated soon. featureLayer.graphics exists, but as the original post mentions, doesn't actually do anything. This too will likely go away and accessing graphics on the view will change in the future. Stay tuned for documentation updates explaining this. [...] This is a major difference between our 3.x and 4.x APIs, so keep a look out for updated documentation, blogs, etc that go into greater depth explaining these concepts and classes. Hi Kristian, Thank you for this relatively in-depth answer. Can you tell us more about the beta release cycle? Will all the updates be pushed iterative or do we have to wait for all these changes for the next beta release?
... View more
08-03-2015
12:12 AM
|
0
|
1
|
1203
|
POST
|
Hello Bhaskar, Have you tried running the html file in your Welcome.html.zip? It also has two typo's according to my IDE
... View more
07-30-2015
05:32 AM
|
0
|
8
|
1066
|
POST
|
Hello, We found a bug in the 4.0 beta 1 of the ArcGIS Api for JavaScript. When restricting the height of the map and placing a table below it that is long enough to create a vertical scrollbar, the tiles are not loading. But when you scroll to the bottom and scroll back, the map tiles are showing. To demonstrate this I created a Plunker. Open the link below and click on ‘Run’. http://plnkr.co/edit/iWQgTveUCcrHzGwk1shW With kind regards,
... View more
07-30-2015
02:50 AM
|
0
|
2
|
2338
|
POST
|
Hello, We found a bug in the 4.0 beta 1 of the ArcGIS Api for JavaScript. Chrome crashes and IE 11 freezes when a AngularJS deferred object is resolved with a MapView instance. To demonstrate this I created a Plunker. Open the link below and click on ‘Run’. http://plnkr.co/edit/SqswhEdJUEDsVnDcvshz I am curious if this is already a known bug by the API for JavaScript team. With kind regards.
... View more
07-29-2015
04:48 AM
|
0
|
3
|
3260
|
POST
|
Yeah, you are right What set me on the wrong foot was that the outField property was available and that querying the ArcGIS REST Service responded on setting the outField property. Think I suffered from tunnel vision.
... View more
07-15-2015
06:08 AM
|
0
|
0
|
1478
|
POST
|
Okey, with some help I've figured it out. The solution is the use of the options parameter in the FeatureLayer constructor. I rewrited my code from: var featureLayer = new FeatureLayer($scope.url);
featureLayer.mode = FeatureLayer.MODE_ONDEMAND;
featureLayer.setSelectionSymbol(symbols.getFeatureMarkerSelection());
featureLayer.outFields = vm.outFields;
featureLayer.setInfoTemplate(template); To: var featureLayerOptions = {
mode: FeatureLayer.MODE_ONDEMAND,
outFields: vm.outFields,
infoTemplate: template
}
var featureLayer = new FeatureLayer($scope.url, featureLayerOptions);
featureLayer.setSelectionSymbol(symbols.getFeatureMarkerSelection()); So not using the options parameter does NOT affect the request/response to the ArcGIS REST Service. The same requests and responses are visible in Fiddler. In the end, featurelayer.outFields is settable but not possible if you read the FeatureLayer reference.
... View more
07-15-2015
01:22 AM
|
0
|
2
|
1478
|
POST
|
No problem. This is the code of creating the FeatureLayer: var featureLayer = new FeatureLayer($scope.url);
featureLayer.mode = FeatureLayer.MODE_ONDEMAND;
featureLayer.setSelectionSymbol(symbols.getFeatureMarkerSelection());
featureLayer.outFields = vm.outFields; //This is: ['OBJECTID', 'NAME']
featureLayer.setInfoTemplate(template); This feature layer is added to the map: map.addLayer(layer); After that the layer is added to the instance of the arcgis map it queries the ArcGIS REST Service with four queries. This is the first request with response (four features): The other three request holds the geometry information of the feature objects. But when I check the InfoTemplate it only displays the OBJECTID: The javascript for the InfoTemplate is: var template = new InfoTemplate();
template.setTitle('<b>Feature</b>');
template.setContent('${*}'); As you can see, with '${*}' it displays all the known attributes of the feature. Even if I look in the graphics array of the FeatureLayer instance, it let me know he only knows the OBJECTID of each feature. Below is a screenshot from my Chrome developer tools where you can see what is in the graphics array of the FeatureLayer object: Conclusion I think the other three request overwrites the first request with attribute information. This is just a hunch because all the ArcGIS Javascript is minified. I can not traceback where the request and responses to the ArcGIS REST Service are handled.
... View more
07-15-2015
12:12 AM
|
0
|
0
|
1478
|
POST
|
I could see that response coming.. The outFields property is filled with ['OBJECTID', 'NAME']. As you can read in my opening post, in Fiddler I can see those attributes are being send from the ArcGIS REST Service to the JavaScript client.
... View more
07-14-2015
11:20 AM
|
0
|
2
|
1478
|
POST
|
Hello, We are working on an ArcGIS for JavaScript application and are displaying some features on a map with a FeatureLayer. The attributes of those features are: - OBJECTID - NAME - FID_1 When I want to show the attributes in a InfoTemplate, only the OBJECTID is shown. When I use Fiddler to look at the request and response to the ArcGIS REST service, more then only the OBJECTID attribute is retrieved. But when I look at the 'graphics' array in the FeatureLayer object, only the OBJECTID is known. First question: Why? Second question: How can I solve this without another roundtrip (like QueryTask etc.) to the ArcGIS REST Service?
... View more
07-14-2015
07:26 AM
|
0
|
7
|
4476
|
Title | Kudos | Posted |
---|---|---|
5 | 10-19-2017 11:45 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|