search

gbif / doc-georeferencing-best-practices

This publication provides guidelines to the best practice for georeferencing. Though it is targeted specifically at biological occurrence data, the concepts and methods presented here can be applied in other disciplines where spatial interpretation of location is of interest.
https://doi.org/10.15468/doc-gg7h-s853
Other
3 stars 1 forks source link

3.1.1 Data preparation phase locality meaning #36

Closed RicardoOrtizG closed 3 years ago

RicardoOrtizG commented 3 years ago

I think that the meaning of locality in the step "Extract different localities" in the data preparation phase, should be broader, because it is not only the description of the locality that is the source of the georeferencing, but it also includes the elevation, the coordinates textual and superior geographic information. For example, a locality: Río Negro, is different from the same locality documented with elevation. Similar cases with the higher geography, for example, Colombia have more than 3 Río Negro in 3 different states (Departments). So, my suggestion is to mention that the different locaties not only correspond to the textual description, but other geographic information such as the ones mentioned above (stateProvince, county, locality, elevation, depth, coordinates, etc.) must be taken into account.

ArthurChapman commented 3 years ago

I presume you are talking about §3.1.1 this refers to "extract distinct localities" not "extract different localities". This is in reference to developing unique identifiers (GUIDs) for distinct localities. To identify what are each distinct locality, one would need the extra information as you describe. What we are suggesting is that (as in your example) you extract the three different _Rio Negro_s and then give each a unique identifier. This can be valuable for georeferencing each at later times.

Perhaps we could change the line to "Identify and extract distinct localities ..." (@tucotuco ?)

tucotuco commented 3 years ago

This whole section needs revision after what Paula had to go to to try to interpret it for a presentation on the subject in tomorrow's webinar. To just add "Identify and will not go well with the rest of that sentence. I think rather that what that sentence needs is a reminder that locality consists of the combination of everything to do with place, not just a specific locality string or a single entity.

On Sun, Nov 22, 2020 at 8:47 PM Arthur Chapman notifications@github.com wrote:

I presume you are talking about §3.1.1 this refers to "extract distinct localities" not "extract different localities". This is in reference to developing unique identifiers (GUIDs) for distinct localities. To identify what are each distinct locality, one would need the extra information as you describe. What we are suggesting is that (as in your example) you extract the three different _Rio Negro_s and then give each a unique identifier. This can be valuable for georeferencing each at later times.

Perhaps we could change the line to "Identify and extract distinct localities ..." (@tucotuco https://github.com/tucotuco ?)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gbif/doc-georeferencing-best-practices/issues/36#issuecomment-731867842, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADQ72Y4OC3ODKC6JFXBFK3SRGPHPANCNFSM4TFBNY5Q .

tucotuco commented 3 years ago

Addressed with 5205a226581bfdaf03e0fadea241343abab1a042