Latest Contributions by Nicholas-Furness

HI Shimin Cai, If you're still looking to implement your own data source, look at the reference doc here. Here's what you need to do. Implement a class that inherits from AGSLocationDataSource. The key functions you need to implement are doStart() and doStop(). These are the entry points to your class. << Runtime communicating to your custom location data source: doStart() will be called by the Runtime when you call AGSMapView.locationDisplay.startWithCompletion(). doStop() will be called by the Runtime when you call AGSMapView.locationDisplay.stop(). >> Providing feedback to Runtime during startup/shutdown: Starting your external device - When Runtime calls your doStart() function, you need to tell Runtime once the external device has started up. Call self.didStartOrFailWithError:() from within your doStart() function to let the Runtime know your external device has started or that it failed to start. Stopping your external device - When Runtime calls your doStop() function, you need to tell Runtime once the external device has stopped. Call didStop() from within your doStop() function to let the Runtime know your external GPS device has stopped. >> Providing location updates to Runtime: Getting a new location - Whenever your external device's API gives you a new location, construct a new AGSLocation object and pass it to self.didUpdateLocation:(). Getting a new heading - If you get a new heading only (and not a completely new location), call self.didUpdateHeading:() with the new heading to let the Runtime know. Hope this helps. Cheers, Nick. ... View more

Hi, You don't need to use an AGSGraphic to create a new feature. The pattern is: Create a new feature on the AGSFeatureTable with geometry and attributes using AGSFeatureTable.createFeature(). Add the feature to the AGSFeatureTable using AGSFeatureTable.add(). See Edit features—ArcGIS Runtime SDK for iOS | ArcGIS for Developers. Since you are working with a server (and not local data), then there is one more call to make to push your add to the server, namely applyEdits. The applyEditsWithCompletion() function is found on AGSServiceFeatureTable (and since you created your feature layer with a URL to a service, the AGSFeatureLayer.featureTable property will be an AGSServiceFeatureTable). See the Edit features (connected) sample, in particular the applyEdits call. This should get you going. ... View more

Hi, Update 3 of the runtime (due in the June timeframe) will expose Subtypes through the API. I'm afraid that in the meantime you'll have to get the metadata from the REST endpoint and parse out the information yourself (as you mention, you'll need to upgrade your server). This code might help point you in the right direction: func parseSubtypeInfo(forServiceFeatureTable featureTable:AGSServiceFeatureTable) {     guard let url = featureTable.url else {         return     }     let operation = AGSJSONRequestOperation(remoteResource: featureTable,                                             url: url,                                             queryParameters: nil)     operation.registerListener(AGSOperationQueue.shared()) { (jsonResult, error) in         guard error == nil else {             print("Error loading resources: \(error!.localizedDescription)")             return         }         guard let jsonDict = jsonResult as? [String:Any] else {             print("JSON not a dictionary!")             return         }         guard let subtypeField = jsonDict["subtypeField"] as? String,             let defaultSubtypeCode = jsonDict["defaultSubtypeCode"] as? Int,             let subtypes = jsonDict["subtypes"] as? [[String:Any]] else {                 print("Couldn't find Subtype info")                 return         }         print("Subtype Field: \(subtypeField)")         // subtypes is now an Array of subtype definition Dictionaries.     }     AGSOperationQueue.shared().addOperation(operation) } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Hope this helps, Nick. ... View more

Hey Shimin, You're nearly there. You just need to make sure the gdb is loaded. gdb.load(completion: { (error) in     guard error == nil else {         print("Error loading the geodatabase! \(error!.localizedDescription)")         return     }     for table in gdb.geodatabaseFeatureTables {         let layer = AGSFeatureLayer(featureTable: table)         map.operationalLayers.add(layer)     } })‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ But note that the tables won't have loaded either at this point, so to read hasGeometry, you might want to do this: gdb.load(completion: { (error) in     guard error == nil else {         print("Error loading the geodatabase! \(error!.localizedDescription)")         return     }     AGSLoadObjects(gdb.geodatabaseFeatureTables, { (allLoaded) in         if !allLoaded {             for table in gdb.geodatabaseFeatureTables where table.loadError != nil {                 print("Error loading \(table.tableName): \(table.loadError!.localizedDescription)")             }         }         for table in gdb.geodatabaseFeatureTables where table.hasGeometry {             let layer = AGSFeatureLayer(featureTable: table)             map.operationalLayers.add(layer)         }     }) })‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ If you know your geodatabase only has featuretables with geometry, you can just add them to the operational layers without first loading them. ... View more