-
Notifications
You must be signed in to change notification settings - Fork 28
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
Consider including Global Gazeteer requests via API #2316
Comments
@tmcelrath can you be more specific. Are you wanting to return results TW data via I feel the last bit ( |
I would like to use the API of Global Gazeteer to auto-suggest localities of un-georeferenced specimens in TW |
Revelant side note @tmcelrath @mjy there is a (funded) group building an API service for just this purpose, known as BELS. See Biodiversity Enhanced Location Services. https://github.com/VertNet/bels. |
This tool has progressed as of 28 Sep 2022 - would be amazing to run queries via BELS API: https://github.com/VertNet/bels |
We need documentation on a REST or API interface to consider progress. |
"Next steps include a REST API and the incorporation of higher geography term standardization based on VertNet vocabularies, Kurator workflows, and verbatim data shared via VertNet, iDigBio, and GBIF." |
https://github.com/VertNet/bels/wiki/User-Manual-for-the-BELS-Georeference-Matcher#georeference-matcher-api - API documentation provided. via VertNet/bels#62 (comment) |
https://localityservice.uc.r.appspot.com/
https://drive.google.com/file/d/1ujfTNhHSkLU5tPeLWCc1EbAR-260Ljrf/view
Could be a great way to auto-georeference and auto-contribute georeferences to community
Also we need to consider "Are we meeting these georeference standards?"
The text was updated successfully, but these errors were encountered: