cd
cd copied to clipboard
tdwg
Property:countryCode
| Label | Country Code |
| Definition | The standard code for the country in which the Location occurs. |
| Usage | The standard code for the country in which the objects held in the collection were collected. |
| Existing property | dwc:countryCode |
| Existing class | Location |
| Existing property identifier | http://rs.tdwg.org/dwc/terms/countryCode |
| Format | Text |
| Required | No |
| Repeatable | No |
| Constraints | |
| Examples | AR SV CN |
| Notes | This terms refers to the code of the country from which the collection originated. Recommended best practice is to use an ISO 3166-1-alpha-2 country code. |
Format: List - A collection often covers multiple countries http://rs.tdwg.org/dwc/terms/countryCode --> Recommended best practice is to use ISO 3166-1-alpha-2 country codes. Should be linked to country
Updating definition to match dwc
| Definition | The standard code for the country in which the Location occurs. |
| Dimension | |
| Existing property | dwc:countryCode |
| Existing class | Location |
| Existing property identifier | http://rs.tdwg.org/dwc/terms/countryCode |
| Format | controlled vocabulary |
| Required | |
| Repeatable | |
| Constraints | |
| Examples | AR, SV, CN |
| Notes | This terms refers to the code of the country from which the collection originated. Recommended best practice is to use an ISO 3166-1-alpha-2 country code. |
Format: List - A collection often covers multiple countries http://rs.tdwg.org/dwc/terms/countryCode --> Recommended best practice is to use ISO 3166-1-alpha-2 country codes. Should be linked to country
Outcome of subsequent discussion about this point within the group: Where multiple categorical values are relevant/required for a collection description object, we should avoid concatenating these values into a single string-y property, and instead encourage people to attach multiple GeographicOrigin classes to a single Collection Description.
So, I've set this property as not-repeatable, but as the parent GeoOrigin class is repeatable the capacity to affiliate multiple countries to one collection is preserved.
One thing that we need to address is that this standard relates to country names and not their borders. Country borders change over time. The country code for ukraine does not tell you if someone was referring to ukraine including or excluding the krim. I therefore like the tdwg area codes that are a combination of iso codes and geographic shapes.
On Thu, 4 Jun 2020 at 17:57, Sarah Vincent [email protected] wrote:
Format: List - A collection often covers multiple countries http://rs.tdwg.org/dwc/terms/countryCode --> Recommended best practice is to use ISO 3166-1-alpha-2 country codes. Should be linked to country
Outcome of subsequent discussion about this point within the group: Where multiple categorical values are relevant/required for a collection description object, we should avoid concatenating these values into a single string-y property, and instead encourage people to attach multiple GeographicOrigin classes to a single Collection Description.
So, I've set this property as not-repeatable, but as the parent GeoOrigin class is repeatable the capacity to affiliate multiple countries to one collection is preserved.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tdwg/cd/issues/140#issuecomment-638948091, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADAUXXYHTNTXNNR62GGNPTRU7AAPANCNFSM4JRYDTDA .
-- Coördinator Research-data and E-infrastructure
International Biodiversity Infrastructures Natural Biodiversity Center, P.O. Box 9517, 2300 RA Leiden, The Netherlands
Coordination team member, Distributed System of Scientific Collections ( DiSSCo http://dissco.eu/) Node Manager for DiSSCo, Global Biodiversity Information Facility (GBIF http://www.gbif.org/) Regional representative for Europe, Biodiversity Information Standards Organisation (TDWG http://tdwg.org/) Chair Biodiversity Data Integration IG, Research Data Alliance (RDA http://www.rd-alliance.org/) Catalogue of Life Ambassador (CoL http://www.catalogueoflife.org)
ORCID: 0000-0002-3090-1761 | Linkedin: linkedin.com/in/wouteraddink/ http://linkedin.com/in/wouteraddink/
Twitter: @wouter99999 | Tel: +31 (0) 71 751 9364
[email protected] - www.naturalis.nl - www.catalogueoflife.org - www.dissco.eu
See the following file for country codes. The two files are exactly the same apart from different file types. http://data.naturalsciences.org/data/geography/countries.csv http://data.naturalsciences.org/data/geography/countries.xlsx The files contain the following: ISO 3166 alpha-2 codes (2 Letter Country Codes) ISO 3166 alpha-3 codes (3 Letter Country Codes ISO 3166 Numeric Country Codes US Board of Geographic Names - Short Form US Board of Geographic Names - Long Form ISO Country Short Name - English ISO Country Short Name - French ISO Country Short Name - Spanish Source
Country codes are unambiguous. A country name can have more than a dozen variations. If you provide the country code, then the end-user can convert that to the form and language of their choosing (The file upload was simpler than the aforementioned API endpoint).
Furthermore, a 2-letter countrycode is sufficient.
On Fri, Feb 18, 2022 at 10:24 PM Ben Norton @.***> wrote:
See the following file for country codes. The two files are exactly the same apart from different file types. The files contain the following: ISO 3166 alpha-2 codes (2 Letter Country Codes) ISO 3166 alpha-3 codes (3 Letter Country Codes ISO 3166 Numeric Country Codes US Board of Geographic Names - Short Form US Board of Geographic Names - Long Form ISO Country Short Name - English ISO Country Short Name - French ISO Country Short Name - Spanish Source
Country codes are unambiguous. A country name can have more than a dozen variations. If you provide the country code, then the end user can convert that to the form and language of their choosing.
— Reply to this email directly, view it on GitHub https://github.com/tdwg/cd/issues/140#issuecomment-1045500298, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADQ722TVC4LM6RORGGHMRLU33WLRANCNFSM4JRYDTDA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
As I said before, countries are political regions, not geographic regions, and iso country codes refer to the political region and do not change if the geograpic area of a country changes. Since in our data we usually want to indicate geograpic origin and not political region, if countries cannot be avoided then country codes should be used that are linked to a geographic shape and time period for which they are valid.