Latest Contributions by Nicholas-Furness

Hi. Image tiled layers are designed for efficient display and don't have any backing information built in. A couple of thoughts… Do you have access to the source data as feature data to query against? Another option would be to export an image snapshot of the map view using exportImage(), and convert the lat/lon from an AGSPoint into a screen location using locationToScreen(), then read the pixel value of the image for the CGPoint you get back. ... View more

Hi. The identify calls available on AGSMapView are focused on interaction so revolve around tapping on the screen. To search using an arbitrary geometry, you will have to call Query on the feature tables that you're interested in. This assumes that the "symbol markers" you're referring to represent features in a feature layer. Take a look a this conceptual doc: hosted-feature-layers Also take a look at this sample, which references a feature table (in this case, an AGSServiceFeatureTable), sets up an AGSQueryParameters, and then calls queryFeatures using the parameters, which is returned a set of features. You would do the same, except that instead of setting a whereClause on the parameters, you would set the geometry to the geometry from the sketch editor, and spatialRelationship to .within. If the "symbol markers" are graphics in a graphics overlay, then you'll have to iterate over each graphic in the graphics overlay and for its geometry use the AGSGeometryEngine.geometry(graphicGeom, within: sketchGeom) to narrow it down. This code could help. It shows both GraphicsOverlay and Feature Layer approaches. I haven't actually run it, but it compiles 🙂 extension AGSGraphicsOverlay { func getGraphics(within searchPolygon: AGSPolygon) -> [AGSGraphic] { let graphicsWithinGeometry = (graphics as? [AGSGraphic])?.filter { graphic in guard let graphicGeometry = graphic.geometry else { return false } return AGSGeometryEngine.geometry(graphicGeometry, within: searchPolygon) } return graphicsWithinGeometry ?? [] } } extension Array where Element == AGSGraphicsOverlay { func getGraphics(within searchPolygon: AGSPolygon) -> [AGSGraphicsOverlay: [AGSGraphic]] { var results = [AGSGraphicsOverlay: [AGSGraphic]]() for overlay in self { results[overlay] = overlay.getGraphics(within: searchPolygon) } return results } } extension AGSMap { func queryFeatures(within searchPolygon: AGSPolygon, completion: @escaping ([AGSFeatureLayer: Result<AGSFeatureQueryResult, Error>]) -> Void) { // Create a store for all the results coming back from each feature layer var results = [AGSFeatureLayer: Result<AGSFeatureQueryResult, Error>]() // Create a Dispatch Group to coordinate the async Query calls against all the feature layers. let coordinator = DispatchGroup() // Query each feature layer in parallel, collecting all the query results in the `results` variable. for layer in operationalLayers.compactMap({ return $0 as? AGSFeatureLayer }) { guard let table = layer.featureTable else { continue } // Find all features in the feature layer that are within the search polygon let params = AGSQueryParameters() params.whereClause = "1=1" params.spatialRelationship = .within params.geometry = searchPolygon coordinator.enter() table.queryFeatures(with: params) { [layer] result, error in defer { coordinator.leave() } if let error = error { results[layer] = Result.failure(error) } else if let result = result { results[layer] = Result.success(result) } else { assertionFailure("No result OR error - that shouldn't happen") } } } // Once all the queries have completed, execute this code… coordinator.notify(queue: .main) { completion(results) } } } You could then call that with something like this… if let searchGeom = sketchEditor.geometry as? AGSPolygon { map.queryFeatures(within: searchGeom) { results in for (layer, queryResponse) in results { print("Got result for \(layer.name)") switch queryResponse { case .success(let queryResult): print("Found \(queryResult.featureEnumerator().allObjects.count) features") case .failure(let error): print("There was an error querying the layer: \(error.localizedDescription)") } } } if let results = (mapView.graphicsOverlays as? [AGSGraphicsOverlay])?.getGraphics(within: searchGeom) { for (overlay, graphics) in results { print("Found \(graphics.count) graphics in overlay \(overlay)") } } } Again, I haven't had a chance to run this code, but it should give you an idea of how to do this. ... View more

Hi @ShawnKleese, I have a theory about what's going on. Can you comment out your line of code that sets the global API Key on the ArcGISRuntimeEnvironment please and try that? Here's what I think is happening: Preplanned map areas are stored as hidden portal items that are related to the web map portal item (there's an area item for each preplanned map area, and each area item itself has related package items, all hidden). The API Key might have access to the web map, but we don't yet automatically extend the API Key access to these related portal items. By setting the global API Key on line 2, any Runtime object that doesn't have an explicit credential set will default to using that global API Key and bypass the authentication manager flow. I think that your OfflineTask can see the web map item, but cannot read the related area items to enumerate them. We need to update our API Key scoping logic to include these related area and package items when scoping an API Key for a web map. In the meantime you could do a couple of things: Do not set the API Key globally, but set it on each Runtime object that needs it. Explicitly set your credential (from line 5 in your code) on your OfflineMapTask with setCredential(). You should then be able to enumerate the preplanned areas. You will probably also need to set it on the DownloadPreplannedOfflineMapJob that you create from the OfflineMapTask Let us know if that helps. If not, you should create a test web map that is entirely public and we can investigate further from there. ... View more

Hi @mvida. Thanks for the question. Yes. Support for vector tile layers is top priority for us and we aim to deliver it late 2022 or early 2023. ... View more