Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ArcGIS layer index #47

Open
10 tasks
maxmalynowsky opened this issue Apr 11, 2024 · 2 comments
Open
10 tasks

ArcGIS layer index #47

maxmalynowsky opened this issue Apr 11, 2024 · 2 comments
Assignees

Comments

@maxmalynowsky
Copy link

maxmalynowsky commented Apr 11, 2024

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
Screenshot 2024-04-11 at 16 33 53

Breaks assumption of admin level = layer index
Screenshot 2024-04-11 at 16 33 32

@UGA-ITOSHumanitarianGIS
Copy link
Owner

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....

@maxmalynowsky
Copy link
Author

maxmalynowsky commented Apr 11, 2024

I was initially trying to use the COD services API with a location like BWA but this location isn't supported:

Even for supported countries like EGY, some endpoints don't return valid geoJSON:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants