Latest Contributions by Nicholas-Furness

You should call loadWithCompletion() on the AGSArcGISFeature. Once loaded, you should see all the fields. We do this by default to ensure that we don't bring more down the wire than we need to. Note, you can use AGSLoadObjects() to load all the items in your selectedFeatures array. ... View more

Hi, There are ways to do that for sure but it depends on the basemap that you're using. You could check out this post which describes adding the World Transportation Layer to your basemap and making it a Reference Layer for that basemap, which means it'll be rendered above all your own layers (in this case the AGSRasterLayer). Note that everything described in that process can be done in code in the Runtime if you're building your map that way rather than using a web map. See AGSBasemap, in particular the referenceLayers and baseLayers properties. If you're using vector tile layers, you could use the Vector Tile Style Editor to create two custom styles. One with just the roads category visible (be sure to also turn off the background), and another "opposite" style with them not visible but everything else visible. Use them both in your basemap as described above (the roads only one would be a basemap reference layer, the "opposite" one would be a basemap base layer). Note, you will want to include a lot of the Labels from various categories in the reference layer rather than the non-reference layer, or they'll appear behind the roads too which makes the map unreadable pretty rapidly. The Vector Tile Style Editor allows you to click on a label in the live preview to find it in the layers list. It's a bit fiddly but will work for what you need. See this web map for an example. ... View more

When you create your Feature Collection Layer from your Feature Collection, you will see a number of subLayers (a FeatureCollection can have many FeatureCollectionTables, so when you create the FCL from a FC, it actually creates one layer per geometry-enabled table). So, even if you just have the one table, you should set the renderer on the Feature Layer found in FeatureCollectionLayer.Layers and not on the FeatureCollectionLayer itself. Or simpler still, set it on the table before you add it to the FeatureCollection (which is actually what your CreateNewFeatureCollection() function does). The FeatureLayer in the Layers collection will then derive its renderer from that upon instantiation. ... View more

You should use a Feature Collection Layer: FeatureCollectionLayer Class  The layers property on it gives access to individual FeatureLayers. A Feature Collection can include multiple tables, so when you instantiate a Feature Collection Layer, you do so using a Feature Collection, which is instantiated using the FeatureCollectionTable you created. See also this sample. ... View more