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

Should we use locality instead of verbatimLocality #101

Open
peterdesmet opened this issue Feb 4, 2016 · 0 comments
Open

Should we use locality instead of verbatimLocality #101

peterdesmet opened this issue Feb 4, 2016 · 0 comments

Comments

@peterdesmet
Copy link
Member

In GBIF simple CSV downloads, the locality information consists of locality, countryCode, decimalLatitude and decimalLongitude. We populate the latter 3, but not locality. We've always used verbatimLocality, as we consider our locality information not part of a vocabulary, but maybe we should change that and use locality instead, so that information is actually included in downloads.

The definition of locality seems to allow it:

The specific description of the place. Less specific geographic information can be provided in other geographic terms (higherGeography, continent, country, stateProvince, county, municipality, waterBody, island, islandGroup). This term may contain information modified from the original to correct perceived errors or standardize the description.

verbatimLocality:

The original textual description of the place.

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

No branches or pull requests

1 participant