Latest Contributions by Nicholas-Furness

Not out of the box, but there is this Swift extension we published as part of the data-collection-ios Open Source app:  https://github.com/Esri/data-collection-ios/blob/1b846d7c8f19d994a83fae259ec2cceeef19be2f/data-collection/data-collection/Extensions/Foundation/Bundle%2BVersion.swift#L18-L45 extension Bundle { private static let agsBundle = AGSBundle() /// An end-user printable string representation of the ArcGIS Bundle version shipped with the app. /// /// For example, "2000" static var sdkBundleVersion: String { return (agsBundle?.object(forInfoDictionaryKey: "CFBundleVersion") as? String) ?? "?" } /// An end-user printable string representation of the ArcGIS Runtime SDK version shipped with the app. /// /// For example, "100.0.0" static var sdkVersion: String { return (agsBundle?.object(forInfoDictionaryKey: "CFBundleShortVersionString") as? String) ?? "?" } /// Builds an end-user printable string representation of the ArcGIS Bundle shipped with the app. /// /// For example, "ArcGIS Runtime SDK 100.0.0 (2000)" static var ArcGISSDKVersionString: String { return String(format: "ArcGIS Runtime SDK %@ (%@)", sdkVersion, sdkBundleVersion) } }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Yep. This looks like a bug. Thanks for reporting it! ... View more

I wasn't involved in the design phase, but I suspect that this is down to inheriting from FeatureTable (I'm not sure if the .NET API has OMDs so here's the one from the iOS documentation😞 I further suspect that to inherit the properties of a FeatureTable without allowing the type model to accept it into the FeatureLayer constructor would involve some convoluted hierarchy and protocol designs that might not even work well in some SDKs. The solution I can think of that would solve this through typing would really ugly up that diagram. To be fair, the error you get when you do try isn't bad… System.ArgumentException: 'Invalid argument: Cannot create a feature layer from a feature collection table. Add the feature collection table to a feature collection.' …but I agree it could perhaps a little more usefully point you at the FeatureCollectionLayer as well the FeatureCollection. I'll see if we can get that updated. ... View more

Don't add the sublayers to the map's operational layers. They're already "owned" by the FeatureCollectionLayer (hence the error you're seeing - the map can't take "ownership" as they already belong to something else). Instead, just add the FeatureCollectionLayer itself. In your case, it will only have one sublayer and you'll get the result you want. In the case of the sample, simply don't add the other tables to the FeatureCollection. ... View more

Hi Manasa. You're really close. You should just need to encapsulate your snap-to-road logic within a custom AGSLocationDataSource. When the mapview is provided new locations from that data source, it'll take care of smoothing interpolating between them. I am pulling together a sample project and blog post to demonstrate this which I'll be sharing shortly. ... View more

Just to close this out, after offline discussion (thank you, Manasa) it turns out the dual inclusion was down to a bug in our Cocoaspec for 100.4. This is fixed at release 100.5. Note that the impact on app size is about 1.1Mb (the compressed size of the bundle, which is largely highly-compressible text-based localization files). ... View more

Hey Michael Davis, The output is not drawn as part of an overlay. All the rendering for the interactive GPU analysis is direct to canvas, for performance reasons, so unfortunately you won't be able to do your calculations there. Related to Distance Along Line, it won't help you here, but in Runtime 100, AGSGeometryEngine has the pointAlongPolyline:distance:() method. Incidentally, points also now cater for M and Z values so that should be a lot less painful now. Cheers, Nick. ... View more

Hi Brandon Land, I'm a little confused by your mention of "query task" in your question, having mentioned "identify task", but assuming you mean "identify"… There's no plan at present to bring it back, although we are investigating ways to improve identify for Map Image Services. In the meantime you could try a couple of things… If you create an instance of AGSArcGISMapImageLayer‌ pointing at your service, you should be able to pass that to AGSMapView.identifyLayer...() to get the results you're after (for best results, you might want to hold on to an instance of the layer and explicitly load it ahead of time). I haven't tested this, but I don't think you even need to add it to the map view if calling one of the identify methods that explicitly specifies a layer. I believe you could furthermore modify the mapImageSublayers array to determine which layers are included in the identify (note there's a resetSublayers() method to set things back). An alternative might be to iterate over the sublayers and if there's a "table" property set and call queryFeatures() on each table of interest. I know that's not an ideal solution, but should work. Hope this helps. Nick. ... View more

Hi Michael, I can't think of a direct way to do this yet (essentially you want a join between the Shapefile and a CSV), but it would help to understand the nature of your data. In particular, how is the CSV contents related to the shapefile records, and does the contents of the CSV change frequently or is it pretty static? Also, is the shapefile very large (i.e. do you want to operate directly against the shapefile, or could you work with an in-memory copy of it?). Depending on the data, one approach you could take would be to create an AGSFeatureCollectionTable from the result of a query against the shapefile using featureCollectionTableWithFeatureSet() (an AGSFeatureQueryResult is an AGSFeatureSet). Create an AGSFeatureCollectionLayer using that. In the layers collection, you'll see a single AGSFeatureLayer that you can set your renderer on. The AGSFeatureCollectionTable you create would essentially be an in-memory version of the shapefile data in which you could then edit the "KTNR" values based off the CSV contents without modifying the shapefile itself. Or if you prefer to merge/import some other field from the CSV to key your renderer off, you could populate the AGSFeatureCollectionTable slightly more manually using featureCollectionTableWithGeoElements:fields() copying the fields from the Shapefile (or a subset if you don't need them all), and add an additional field that the renderer will be keyed on, populating that from the CSV. Could you give us some more information on the nature of the CSV and how it relates to the Shapefile? Nick. ... View more

Hi. Unfortunately Runtime 10.2.x cannot render vector tiles. This was introduced with Runtime 100.0. With Runtime 100.0, you should work with VTPK files, either generated from ArcGIS Pro or by using the AGSExportVectorTilesTask. ... View more

Hi. The Samples app is built to work with the downloaded SDK, which you can get from here. You should open an issue here if you really need the app to use CocoaPods and you can't get it to work. ... View more

As it happens, we just wrote a blog post discussing this: Selection behavior changes in Runtime 100.5  At 10.2, you could set a selection symbol on the Graphics Layer or the Feature Layer, not the graphic itself. But yes, the behavior is changed at 100.x, for two primary reasons: performance, and consistency with the rest of the platform. Our "halo" approach works well as selection feedback for a GIS but I can see it's not necessarily the best UX for a custom location app. I'll bring it up with the team. If you're working with graphics overlays, one approach I've used in the past is to use a UniqueValueRenderer on a "highlighted" or "focused" attribute on the graphic. Rather than manipulating the graphics selection, you would set the attribute to "true" and let the renderer handle the rest. But that would get tricky once you started working with Feature Layers. ... View more