Latest Contributions by dotMorten_esri

The title seem to suggest you're also using API Key. If you're using a signed in user, do not set the API Key. It's an either/or kind of thing. ... View more

> and then lift my finger from the map, no GeoViewTabbed-event is triggered. That's correct, since that isn't a tap-gesture (it's a hold + drag gesture) ... View more

I don't believe so, considering it's a Windows-specific and deprecated code page. I've logged an internal bug to investigate, but my gut feeling is you're running into an OS limitation. ... View more

The behavior you see is by-design. While I agree in this specific scenario it's perhaps not ideal, there are many more cases where selection gets completely obscured by other layers above, making the selection invisible. ... View more

Your data seems to be using codepage 936 which, according to wikipedia, is a legacy pre-unicode character encoding for Windows. I wonder if it's possible for you to author the shapefile with a codepage that Android and iOS understands (I was able to reproduce the issue on iOS too). ... View more

Follow-up: I'm able to reproduce the issue and will have someone investigate. ... View more

Thanks! I'll have a look. Btw how do you deploy and load the file onto your Android device? Android is quite different with how you deploy content with the application compared to other apps, so want to make sure this isn't the issue first. ... View more

Are you using a SceneView or a MapView in your application? If SceneView, sometimes increasing this value on Android for certain devices can help: https://developers.arcgis.com/net/api-reference/api/android/Android/Esri.ArcGISRuntime.UI.Controls.SceneView.MemoryLimit.html ... View more

Sorry for the delay. This fix will be in 200.8 ... View more

I'm sorry. I brainfarted and said DrawStatus event, but I really mean LayerViewStateChanged: https://developers.arcgis.com/net/api-reference/api/netwin/wpf/Esri.ArcGISRuntime.UI.Controls.GeoView.LayerViewStateChanged.html Also monitor your debuggers' output window for any indication of layer rendering issues. Btw. I'd rewrite the layer load code (the code in the doc isn't ideal and I've asked to get it fixed). Instead of doing it in the event, just wait for loadasync and then add your rasters. It simplifies the flow and should give you better error propagation as well: MosaicDatasetRaster rasterMosaic = MosaicDatasetRaster.Create(@"C:\Data\mosaic.sqlite", "Shasta", SpatialReferences.WebMercator); await rasterMosaic.LoadAsync(); AddRastersParameters parameters = new AddRastersParameters { InputDirectory = @"..\incoming\data\rasters" }; await rasterMosaic.AddRastersAsync(parameters); It would be a good idea to just step through the code to see if the hang is occurring anywhere in your code and what line that might be causing it, or whether it happens somewhere else. Lastly, as mentioned please try without specifying a basemap. ... View more

No that's fine but perhaps try without a basemap, just to exclude the chance you're hitting reprojection issues. However that's why I'm asking about the DrawStatus event - this one will tell you if there are issues with rendering any of the layers. ... View more

Any chance you can share the shapefile causing this problem? ... View more

Another thing to note is to make sure your map itself is using the same spatial reference as your raster mosaic. You can set that explicitly in the Map constructor. It's also worth checking both the layer.LoadStatus as well as MapView.DrawStatus events for any indication why a layer might not render (generally this should also be written to the output window while debugging). It's also worth ensuring your source dataset is actually wgs84/epsg4326 - it's fairly rare rasters aren't in a projected coordinate system ... View more