Latest Contributions by Nicholas-Furness

I'm not an expert in this, but I think the file that does NOT have embedded SR will need both the XML auxiliary file AND a world file (which positions/scales the image). See this gist for an example, including some links at the bottom that talk some more about aux and world files. ... View more

In addition to what @SomeGISGuy said above, since you mentioned creating a gallery, there is also the ArcGIS Maps SDK for .NET toolkit, which includes an open-source Basemap Gallery component. ... View more

Hi @RTC  The postscript is purely about the API Key capabilities introduced at ArcGIS Enterprise 11.4 (see link). If you're seeing that an API Key is invalid, it means it's not scoped to access the services you're using it for. For basemaps, simply follow the instructions here. API Keys can be created by either an ArcGIS Online account or an ArcGIS Location Platform account, but the important thing is to ensure that they're scoped for the service you want to access. Follow the instructions above to create an API Key and it should by default include Basemaps styles service access (which is what's needed for the service you're hitting.   ... View more

Excellent! Seems there's always another way to break things. Glad that was it, because otherwise I was out of ideas 🧐 ... View more

Hi @RTC. To clarify… there are two things being discussed here: Routing (creating turn-by-turn directions using the RouteTask API and the World Routing service or an MMPK) Navigating (following along the route, getting real-time guidance, using the RouteTracker API) There are also two other things that you talk about that are a bit muddied above: Licensing the SDK (Lite, Basic, Standard) Accessing the World Routing Service (with an appropriate access token) There's no licensing restriction to use the World Routing service or an MMPK to calculate turn-by-turn directions (Routes). However, you will need an appropriately scoped access token to use the World Routing service. To use the RouteTracker API for interactive navigation, you need a Basic license unless you are using the World Routing Service, in which case Lite is sufficient (when you pay Esri for the route calculation, that includes use of the RouteTracker API). That's covered in the Lite section of the Licensing and Capabilities table: Navigate a route using the RouteTracker API and ArcGIS location services. If you're using an MMPK (or some other routing service), then you need a Basic License to use the RouteTracker API. That's covered in the Basic section of the Licensing and Capabilities table: Navigate a route using the RouteTracker API and any ArcGIS routing service, or a network dataset that is stored locally on the device. So yes, Mobile Worker user type will allow you to use the interactive navigation guidance capabilities of the RouteTracker API with any service or local network dataset. But if you're using the World Routing service, you can even use the RouteTracker API with a Viewer user type. But: either way you need to make sure you have an access token for the World Routing service. I suspect that the "forbidden" error is because the access token you're using is not properly scoped (perhaps it just includes basemaps?). See this tutorial on selecting privileges. Hope that helps! ... View more

Hi @woodie. I was able to confirm that ANCPI deliberately took this action to prevent desktop GIS applications (both Esri and open source) from accessing the data as some of the data is sold via https://epay.ancpi.ro/epay/Welcome.action I'm unable to tell what the rules are, but they at least specifically block any user agent that contains "ArcGIS" (case sensitive). I'm told that QGIS is similarly blocked. You would need to petition ANCPI to make a change to their servers to allow the Native Maps SDKs to access them. ... View more

Hi. I took a look with the Swift SDK and it looks like your server is rejecting requests coming from the Native SDKs because of the User-Agent header. Not seen that before, but I reproduced this in Postman too. The Native SDKs add a User-Agent string to all requests. In my Swift SDK test app, the string is this: User-Agent: ArcGISMaps-Swift/200.7 (iOS 18.5; iPhone17,1,Simulator; devmode) com.esri.tutorial.Display-a-web-map/1.0 It'll be something similar for the Kotlin SDK. To open the layer, the SDKs will make a couple of metadata requests: https://geoportal.ancpi.ro/hosted_services/rest/info?f=json https://geoportal.ancpi.ro/hosted_services/rest/services/Hosted/imobile_cladiri/VectorTileServer?f=json If I make Postman GET requests to either of those URLs with no User-Agent header, I get valid JSON responses. But as soon as I add a User-Agent header like the one above, I get an HTML error response and the VectorTileLayer will fail to load with a "forbidden" error. Can you check with your server admin and see if there's configuration on the server that could be rejecting these User-Agent Native SDK headers? For reference, here's some sample output I get from the Swift SDK's ConsoleNetworkLogger: Request sent: URL: https://geoportal.ancpi.ro/hosted_services/rest/info?f=json Method: GET Request headers: User-Agent: ArcGISMaps-Swift/200.7 (iOS 18.5; iPhone17,1,Simulator; devmode) com.esri.tutorial.Display-a-web-map/1.0 Request completed: URL: https://geoportal.ancpi.ro/hosted_services/rest/info?f=json Method: GET Data: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access /hosted_services/rest/info on this server.</p> </body></html> Response headers: Connection: Keep-Alive, Content-Length: 227, Content-Type: text/html; charset=iso-8859-1, Date: Fri, 29 Aug 2025 19:10:26 GMT, Keep-Alive: timeout=5, max=100, Server: Apache, X-Content-Type-Options: nosniff To start to figure these things out, you can check the loadStatus on the VectorTileLayer or Map. I then used the ConsoleNetworkLogger to see the requests being made that were getting a loadStatus error, dug into the them a bit, and figured the only difference between a browser and the SDK might be the User-Agent string. I'm not familiar enough with Kotlin to recommend how to track requests like I can with the Swift ConsoleNetworkLogger, so I'll let someone on the Kotlin team pipe up if they have recommendations. ... View more

You just need to place the world and aux files alongside the JPG and the SDK will find them when you create the raster. Think of it this way: in the context of a georeferenced raster, the JPG file alone is incomplete data (hence the SDK error). Complete data is the JPG file + the World file + the Aux file. Contrast with a GeoTIFF where a single file is complete data for a georeferenced raster. The error could be better, and we could improve the documentation around the need for world and aux files. I'll pass that on to the team. For the aux file, you should just be able to copy straight from the Gist. For the world file, you'll need to make sure it's updated to properly position and scale the image. At the bottom of the gist there are links to documentation that describe world and aux files in more detail. ... View more

Are you georeferencing the JPG file properly? Since JPGs have no georeferencing data built in, you need to provide a World file (which defines the size and location of the image) and an Aux file (which defines a spatial reference). See this example: https://gist.github.com/nixta/9cf3b53e3340dc3314c6db40af06c709 If you are already doing that, then can you try to just add the raster layer directly to the operational layers so we can discount Group Layer being an issue? ... View more

Hey @ChristopherSwingley, thanks for the info (and sorry for the slow response!). Yeah, to my non-Qt developer eye that does look somewhat confusing. I'll check with the team to see if the code being there is an oversight, and if not, whether for a sample like this the comments could be more helpful. ... View more