Latest Contributions by Nicholas-Furness

Yes. This is fixed in 100.5 ... View more

Note that if you're just using the AGSGraphicsOverlay's selection to track/flag certain graphics, you could set the mapView.selectionProperties.color property to UIColor.clear. However, if that's the case, I would probably keep a separate Set<AGSGraphic> variable that I used to track those graphics. Granted, you might need to do some additional logic when graphics are removed from the AGSGraphicsOverlay, and it depends on what you're trying to do, but that could be a cleaner solution. ... View more

You've pretty much got it, Reed Hunter  I think of it this way (this is pretty loosey-goosey, but it describes things well enough): A FeatureLayer and the underlying FeatureTable are pretty tightly coupled once they've been brought to life. By brought to life, in practice I mean showing it in an AGSMapView through an AGSMap's operationalLayers (an exception may be simply loading the AGSMap with AGSLoadable which may trigger that coupling for some layers/tables to determine a spatial reference, but you'd have to be missing a basemap). Once the Map is alive, it pretty much "owns" the layer - you can't add that layer to another map at the same time (you'd have to remove it from the map's operational layers and then you should be able to use it in another AGSMap). Given that tight coupling, what you should be able to do is take a map's FeatureLayer, and call copy() on it. This should give you an instance of the feature layer that you can use in another map (this will also copy() the underlying FeatureTable so you don't break that tight coupling). It'll point at the same source data, but will be an entirely separate layer unbeholden to the "owning" map of the original layer (since the copy won't be in any operationalLayers collection). e.g. let mySafeToUseFeatureLayer = featureLayerAlreadyInAMap.copy() as! AGSFeatureLayer Safest way, to avoid these races as maps are brought to life and claim layers, would be to cherry pick the layers you want from the various maps in various MMPKs, and copy() them to add to your own map that you're compiling. Just be aware that if you're doing this with multiple visible map views at once, you may end up hitting that single underlying geodatabase data table at the same time for both map views if you're navigating them both at the same time. Should work just fine, but you might notice some performance drops as data is read. I should stress that this is not something I have delved into myself. And map projection should work pretty well. The projection engine is fast and flexible, but it is an additional performance hit if every geometry has to be projected. ... View more

An MMPK is a container for Maps. Each AGSMapView can display one Map at a time. You can open a TPK and add it to a map. If you need to show a different map in a map view, simply replace the AGSMapView.map property with the other AGSMap. ... View more

It looks like you took the authentication code from the OAuth 2 DevLab. It's hard to know where things went wrong, but I would like to dig a little deeper in case we can improve things. I know you moved on from the point where things weren't working, but if you are able to DM me an Xcode project that shows this behavior, I'd be happy to take a look. Let me know. ... View more

It sounds like it. Assuming you used the Maps App as your starting point, did you follow the steps in "Register an Application" and "Configure the project"? I'm intrigued as to precisely what went wrong so that I can see if we can do better with the instructions and the error messages. ... View more

Hi Manasa. By default, the polyline will be turned into AGSLocations, with one for each point in the source polyline. Remember that if you densify a polyline, you will get the original points plus any densification results, so they might be less than maxSegmentLength apart.‌ Once you have called AGSSimulatedLocationDataSource.setLocationsWithPolyline, the AGSSimulatedLocationDataSource.locations array will be populated with AGSLocations. These locations will be provided to the AGSLocationDisplay at 1 location per second. Each location in the locations array will initially have a velocity of -1 and a course of -1. You can modify the velocities and courses to a value >= 0 if need be. The AGSSimulatedLocationDataSource will emit a location every second. If it finds a velocity < 0, it will use 1 meter per second. If it finds a course < 0, it will calculate heading based off the direction from the previous location to the current location. For the GPX data, it looks like we ignore the timestamps on the GPX source points, and emit one location every second regardless of the timing of the original data points. That probably explains why it looks like it's running too fast. ... View more

Hi Samer Abraham. Were you able to make any progress? Was it the type of account that you were using? ‌ ... View more

I meant that you should call mapView.LocationToScreen, not write your own function. Something like… double longitude = 100.458802; //reference starting point double latitude = 5.997545; location = new MapPoint(longitude,latitude, SpatialReferences.Wgs84); screenPoint = mapView.LocationToScreen(location); ‍‍‍‍ Perhaps I misunderstood your question. ... View more

Hi Mohamad Fathin, Does this help? MapView.LocationToScreen Method  Pass in any MapPoint and you get a screen position relative ‌to the top-left corner of the MapView control. Nick. ... View more

I think that was my original reply above, which I edited to be more explicit/correct. ... View more

Comment out the line AGSAuthenticationManager.shared().oAuthConfigurations.add(config). Then when you call routeTask.defaultRouteParameters you should be prompted with an alert box for your credentials instead. If you enter your credentials (it should be a free developer account or an ArcGIS Online organizational account, not a personal account), you'll be fine. I think there may be one of two things going on: 1. You're using a personal Esri account OR 2. There's an issue with how your app's OAuth configuration is being defined. But if you're entering your credentials through the OAuth page and control returns to your app, that doesn't seem likely to be the case. If it turns out to be 1) above, yes, I agree, that error message is not good and we'll have to improve that. Let me know if this helps. ... View more

That's the right URL. Should just work (I can't reproduce it here). Is your routeTask going out of scope for some reason? And which version of the Runtime SDK are you using? ... View more

Thanks for the follow-up, Worth Sparks.‌ This is helpful info. Glad you've got a workaround. We'll take a look internally though. ... View more