Latest Contributions by Nicholas-Furness

Why are GIS features using one spatial reference whereas the location listener is receiving coordinates in different spatial reference? iOS's CoreLocation returns Lat/Lon, i.e. wgs84 (4326). We can't assume you need it in a specific spatial reference so we don't translate it. But you can use AGSGeometryEngine.projectGeometry() to project it to the route geometry's spatial reference. As for why the route is in Web Mercator (3857): Our major public services (World Geocoder, World Route Task) output in 3857 by default because that matches our default basemaps and so the returned geometries can be overlaid on the map with no extra transformation. If you're working with a different spatial reference in your map, you can specify the AGSRouteParameters.outputSpatialReference property when calling AGSRouteTask.solveRouteWithParameters(). One note: your logic above is likely to always return false though. The chances of the GPS location actually being precisely on the line are vanishingly small. You should buffer around your location by a few meters using AGSGeometryEngine.Buffer() or AGSGeometryEngine.geodeticBuffer() (perhaps adjusting the buffer size by considering AGSLocation.horizontalAccuracy) and check if that buffer polygon intersects with your maneuver line. Or else, as I suggested earlier, measure the distance between the location's point and the maneuver line. Lastly, may I suggest that if you have further questions about this that you post them in the iOS Forums where the community will be more likely to see them? Thanks! ... View more

Look at AGSGeometryEngine.projectGeometry(). ... View more

Hi YunFeng Wu, Are you able to share that data with us? This seems unexpected and we'd like to reproduce the issue. Thanks! Nick.‌ ... View more

Are you getting any results, or do all solves fail? I've seen that error when the stops cannot be located on the network (that is to say the network is too far away from the stops). If you're sure the stops are OK (lat/lon the right way around, and spatial reference is correct), then another thought below: Network models have a number of parameters that determine just how the network model is used and to which you make changes and add your stops. I'm not familiar with ArcMap 10.5 and how it configures those parameters, but one thing to check is whether you're using the default parameters as the basis for your runtime requests. One thing to try: once you've created your AGSRouteTask, try calling defaultRouteParametersWithCompletion() and then modifying those parameters with your stops and calling solve from that completion block. See this pattern. Let me know if that helps. Nick. ... View more

Hi Manasa Parida. Thanks for the questions. We distinguish the functionality that you're talking about as Navigation vs Routing. The Routing API that we already provide (and which you're making use of) gives you the components you need to get from A to B. But a full Navigation experience that tracks that progress and adjusts the route on the fly and intelligently (such as that provided by the Navigator app) is something you will have to build yourself for the time being.‌ Some high-level thoughts, based off your questions: Using the locationDisplay.locatidHandler is the correct approach to get updates to the user's position. Use AGSGeometryEngine.distanceBetweenGeometry1:geometry2() to calculate the distance of the user's location from the planned route.  Perhaps look at the distance between the AGSLocation.position and the AGSDirectionManeuver.geometry to see if the user has moved too far from the route. Consider building some logic to work out which maneuver the user is currently on rather than treating the route as a whole. This can help with cases where the route doubles back on itself, or crosses over itself. By working on a maneuver-by-maneuver basis, you can work out when to read the next maneuver step. E.g. get the end point of the current maneuver, and use GeometryEngine to check when the user has approached within a certain distance of it before reading the next maneuver's text. Realize the limitations of your GPS data. Does the environment cause bad data from time-to-time? How frequently do you get updates (you can control this through the AGSCLLocationDataSource.locationManager in the default case)? And you should probably smooth out bad data rather than allow it to trigger thresholds. Variables like GPS accuracy/quality/frequency or complexity of the route all play into making the work tricky. Nick. ... View more

Hi Michael‌, Not sure I have code available. At the moment, we don't expose the right properties on the symbol objects to modify the Arcade expression (deeper symbology API is coming in the next couple of releases too - you can imagine a lot of this is interrelated). In the example I've seen, this Arcade expression is created in ArcGIS Pro to drive the symbol size: As you mention, it's not an ideal workflow to manage with a lot of layers. I'm not familiar with the Pro SDK, but I imagine you should be able to write something to manage this, or manage it with some Python code. However, as a proof of concept this should at least let you figure out if this workaround will work for you. Alternatively, you can take the symbol definition JSON that this creates when the MMPK is generated, and modify that in the runtime to update as necessary, using AGSSymbol.fromJSON() to create a new symbol to apply to the layer. That's the code I have to work out how to dig up. Cheers, Nick. ... View more

Thanks Muruganandham Kuppan‌. Great to hear. Could you mark your original question as answered please? It'll help other people home in on the right answer. ... View more

To reiterate Michael Branscomb above, we agree that Reference Scale is important. Our goal is to introduce support for Reference Scale in the Q1/Q2 2019 Runtime release but of course schedules can change and functionality can slip (though we're working hard to hit that release). In the meantime, some customers have had success with a partial workaround. The gist of it is that you define a symbol's size when authoring the map using an Arcade expression along the lines of (1/$view.scale)*1000000. Some notes on this approach: This is not true Reference Scale. Reference Scale is defined by the map or layer. This approach is a function of the layer's renderer. You'd need to tweak the factor here for each layer to get close to what you want. This requires that the layer be rendered in static mode. It is not currently supported in dynamic rendering mode (Arcade support in dynamic rendering mode is coming, but is not there yet). You should use 100.3 or later for using this approach. Hope this helps! Nick. ... View more

When using a Polyline as the search geometry you probably want AGSQueryParameters.spatialRelationship to be AGSSpatialRelationshipIntersects. See here for more options. Does that help? ... View more

Good to know. Would you mind flagging the question as answered? It'll help others when browsing the questions. Thanks! ... View more

Thanks Muruganandham Kuppan‌, The documentation here has some specific requirements for ensuring the relationship is written and committed properly. If you're meeting those and are still seeing this issue, it might be best for you to open a support ticket. It's hard to tell from just the info provided above without more context, and support will be able to dig into that with you more. ... View more

Hey Deon Lengton, did this help your client out?‌ ... View more

Was the feature you're relating to created and added in code (as opposed to being retrieved from a query)? If so, have you called refreshObjectID on it after the add completed? ... View more

It's really hard to determine without more info or sample code, but in general that error means that something else is already tied to that table. The table may already be part of the map.tables collection or a layer in your map might be using it. If you still really need to duplicate the layer, you could call copy() on it and add that reference to the map but I'd suggest you double-check that you're not unwittingly duplicating things. ... View more