Latest Contributions by Nicholas-Furness

Hi @ChristopherSwingley. That's concerning. Could you help me understand where our documentation was misdirecting you please? We try to be very clear about the difference between access tokens and license strings, so if we've missed the mark we need to address that. Please DM me (or if you happen to be going to the DevTech Summit in Palm Springs, we can connect then). Thanks! ... View more

Based off the screenshot of the folders, you already have a downloaded map on disk at the location you're trying to download to. When you specify the download location, you should make sure there isn't already something at that location on disk. There are two things you can do: If the downloaded map you already have on disk is suitable, you can just re-open that instead of re-downloading it. To re-open without re-downloading, see Step 2 here. Otherwise, if you need to get a fresh copy of the map, delete the previously downloaded map (folder) and re-download to the same location (or you can download to a different location and keep both copies of the offline maps, but if they're the same map, that's probably not what you want). Hope that helps. ... View more

Hi @julianrua, apologies for the delay in replying. As you noticed, arcgis-runtime-toolkit-android is built for the 100.x ArcGIS Runtime SDK for Android. It's not expected that it will work with the 200.x ArcGIS Maps SDK for Kotlin. The good news is that we intend to add a scale bar component to the arcgis-maps-sdk-kotlin-toolkit soon, but in the meantime you should be able to do what you're proposing by observing the MapView's mapScale property. Hope that helps! ... View more

Great news everyone. After a very successful beta (thanks to all that contributed), today we launched the first public release of the ArcGIS Maps SDK for Flutter, alongside the other 200.6 ArcGIS Maps SDKs for Native Apps. Thank you all for your interest, and we look forward to seeing what you build. You can learn more about this release at the announcement blog post and the product homepage. ... View more

Yeah, the app should remain responsive while those 3000 files are opened (except perhaps when you're stepping through in the debugger). Thanks for opening that other issue. That's the best way to get feedback on this issue. ... View more

Hi @imbachb. No problem! Not off topic yet 🙂 The load() method should not be blocking (though it might take some time to open and load all 3,000 files, but that should happen in the background). If you're stepping through in the debugger, that might have something to do with it. Can you set a breakpoint after the load rather than stepping through it? Or try the app without the debugger. If that doesn't show things working as expected, then we are starting to get off topic here so could I ask you to pose the question about RasterElevationSource load() blocking over in the Qt forum please? ... View more

Hi @imbachb (this might also be of interested to @IgnisDev). What you're doing is reasonable, but we do have APIs that can make it much easier for you. What you need to do is create a standalone Surface. You can add 1 or more ElevationSources to it, where an ElevationSource can be an ArcGISTiledElevationSource (using a service or a local TPK/TPKX file), or it can be a RasterElevationSource (which can use one or more local DTED files). Please note: when using a standalone Surface like this, you do currently need to explicitly load each of its ElevationSources. Here's some sample Swift code (though you would use a RasterElevationSource instead)… let surface: Surface = { let surface = Surface() let worldElevationServiceURL = URL(string: "https://elevation3d.arcgis.com/arcgis/rest/services/WorldElevation3D/Terrain3D/ImageServer")! let elevationSource = ArcGISTiledElevationSource(url: worldElevationServiceURL) surface.addElevationSource(elevationSource) Task { await surface.elevationSources.load() let failedSources = surface.elevationSources.filter({ $0.loadStatus == .failed }) for source in failedSources { print("Elevation source \(source) failed to load: \(String(describing: source.loadError))") } } return surface }() and you can then call it with something like this… let elevationAtPoint = try await surface.elevation(at: mapPoint) Hope that helps. ... View more

Hi @sveinhal.  How we cache internally varies by layer type, and I agree is quite opaque. It's something that's been on our backlog to improve for some time, and internally we're considering how we can deliver a better experience. Posts like this really help us to prioritize that, so thank you. In terms of us responding to system memory pressure notifications, a better solution would probably be via an API like the one you suggest, so that you as a developer can flush the cache when you receive the notification; for many developers, having data simply disappear from their map without their say-so can be a showstopper. That said, I'm glad you've identified a solution that can tide you over until we can deliver something more refined. We have made some improvements in the past. For example, we used to cache image tiled data in memory but realized that for many platforms this was duplicating OS-level HTTP cached data. That did make a good difference to the memory footprint for a lot of people, but there is definitely more that we can do across many layer types. Just to set expectations: this is probably not something we'd deliver in the next release or two. But it is something we're very interested in improving and is high on our list of priorities. ... View more

Hi. Yeah, not all Living Atlas content is completely free. You can see from the details page of the item in question, that it's "Subscriber" content. You can learn more about what that means here, but the short of it is that you'll need to authenticate to use it. It won't cost you any credits to access, but there are some items of content that for various reasons we cannot just open up publicly. You should be able to use a user-based or app-based OAuth token. ... View more