You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the HDX URL's all became standardized like https://data.humdata.org/dataset/cod-ab-tcd, I was able to do things like iterate through all ISO3 codes and get metadata from HDX associated to every dataset from the API using "https://data.humdata.org/api/3/action/package_show?id=cod-ab-tcd". For the ArcGIS server, it would be useful if the index position of each layer corresponded to their admin level to be able to build out URL's like the following:
Thanks for suggesting! I believe this will compromise other aspects of the services such as layer drawing order, which may be a legacy issue... will check. But this may be addressed in the COD Services API that denotes the layer index to use for the location and admin level. The output may also denote whether the layer is nested or compeletely in scope with extent as parent layer or next broadest level coverage....
For that EGY example, the request exceeds the transfer limit, which starts happening at ADM2 and above. Normally, I would be able to get around this when using GDAL by setting FEATURE_SERVER_PAGING=YES. This automatically scrolls through results with a ArcGIS Feature Service endpoint, and was key to be able to pull in all the layers of the ArcGIS server. However, this only works when giving it a URL against the original ArcGIS server, it can't work for URL's that redirect like the one above.
When the HDX URL's all became standardized like https://data.humdata.org/dataset/cod-ab-tcd, I was able to do things like iterate through all ISO3 codes and get metadata from HDX associated to every dataset from the API using "https://data.humdata.org/api/3/action/package_show?id=cod-ab-tcd". For the ArcGIS server, it would be useful if the index position of each layer corresponded to their admin level to be able to build out URL's like the following:
https://codgis.itos.uga.edu/arcgis/rest/services/COD_External/{iso_3}_pcode/FeatureServer/{adm_lvl}/query?where=1=1&outFields=*&f=json
The following layers prevent the above assumptions of layer indexes from holding all the time:
Follows assumption of admin level = layer index

Breaks assumption of admin level = layer index

The text was updated successfully, but these errors were encountered: