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

[API] Base API not reflecting current data and/or missing fields #3408

Closed
sgoodm opened this issue Jan 2, 2024 · 2 comments
Closed

[API] Base API not reflecting current data and/or missing fields #3408

sgoodm opened this issue Jan 2, 2024 · 2 comments

Comments

@sgoodm
Copy link

sgoodm commented Jan 2, 2024

1 - not all items on https://www.geoboundaries.org/api/ contain all relevant fields (e.g., openAvailable may be missing when there is an open dataset for the item)

2 - missing items (e.g., BIH ADM3 is not listed on https://www.geoboundaries.org/api/ but does exist https://www.geoboundaries.org/api/current/gbOpen/BIH/ALL/)

@DanRunfola
Copy link
Member

Hey @sgoodm - right now that API endpoint is largely undocumented, and I actually hope to deprecate it at some point in the future. I think it may have stale data, but not sure without looking back at the code.

For your use case, is there any reason not to use https://www.geoboundaries.org/api/current/gbOpen/ALL/ALL/ ? I think it will give nearly equivalent information to you, and shouldn't go stale (as I build that at the same time as all the other files).

@sgoodm
Copy link
Author

sgoodm commented Jan 8, 2024

Oh that should be perfect. I didn't even see that ALL/ALL was there - got too mixed in with the all the ISO 3 chars.

@sgoodm sgoodm closed this as completed Jan 8, 2024
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