Hello all. Has anyone been able to successfully load the "USA Soils Map Units" layer from Living Atlas in QML? For reference, here is the link...
https://www.arcgis.com/home/item.html?id=06e5fd61bdb6453fb16534c676e1c9b9
I am using my organization's arcgis online portal and my account, but for whatever reason when I try to load any Living Atlas layer that has a service endpoint from landscape11.arcgis.com, the layer's status goes to Enums.LoadStatusLoaded, but it never renders on the map. If I try any of the other Living Atlas layers that have service endpoints referencing services.arcgis.com, they load and render fine.
Oddly enough if I click on "Open in Map Viewer" from my org's online portal it loads fine in the browser based map viewer.
I have attached a sample of my QML. I am on a Mac with Qt 5.15.6 running runtime 100.10. I did copy my main.qml to a Win machine and same result.
Do you find anything reported by MapView.Layer.layerViewStateChanged?
GeoView QML Type | ArcGIS Runtime API for Qt | ArcGIS Developers
layerViewStateChanged(Layer layer, LayerViewState layerViewState)
Hello. I went ahead and added in something like the following in MapView...
onLayerViewStateChanged: {
console.log("LAYER NAME: "+layer.name);
var stateFlag = layerViewState.statusFlags;
if (stateFlag == Enums.LayerViewStatusActive)
console.log("layerViewState Active");
if (stateFlag == Enums.LayerViewStatusNotVisible)
console.log("layerViewState Not Visible");
if (stateFlag == Enums.LayerViewStatusOutOfScale)
console.log("layerViewState Out of scale");
if (stateFlag == Enums.LayerViewStatusLoading)
console.log("layerViewState Loading");
if (stateFlag == Enums.LayerViewStatusError)
console.log("layerViewState Error");
}
This resulted in...
qml: LAYER NAME: USA Soils Map Units
qml: layerViewState Not Visible
qml: LAYER NAME: USA Soils Map Units
qml: layerViewState Active
So seems like the end result is that it is "Active". I also checked map.operationalLayers.get(0).visible and it is "true".
Thanks for the feedback! I'm still baffled and don't know why it isn't visible.
@JeremyRoberts2 I looked into this a bit and that layer should be working for you. I have logged a bug in internal bug tracker and we will look into this. Thank you for letting us know about this.