Closed Jegelewicz closed 5 months ago
This is specific to UTEP (https://arctos.database.museum/search.cfm?locality_id=11467864) My recommendation is to have the spec_loc simply be "White Sands National Monument" so you can suggest that to UTEP:Herb but likely the way their catalog originally has it listed. Not a geo community work but collection-level work.
Will you reach out and close?
@mkoo this happened as a result of the migration to GADM, which is why I posted this.
https://arctos.database.museum/info/localityArchive.cfm?locality_id=11467864
Everything after "No specific locality recorded" in specific locality was added by scripts when White Sands National Monument was removed from higher geography. My point is that this is probably true in a lot of other localities. I can fix this one - but I don't think that "White Sands National Monument" should be the specific locality as it is included as a Feature? I'd like some guidance there as well.
Personally I would still add WSNM as the specific locality (and would be a good use the polygon spatial footprint too!) since it's more specific than "No specific locality". But at the end of the day, doesnt matter what I or you think-- it's a collection decision since perhaps the locs should match the herbaria sheets (in which case maybe your suggestion is best). Perhaps these are "no specific locality" but are part of a WSNM survey. Basically the db needs to reflect the collection priorities so check what is their first choice and fix accordingly. Since the current spec_loc isnt ideal then Arctos should fix to what they want. thanks for bringing to attention
Can you clean for UTEP (is Vicky involved here?) The best spec_loc for this is simply "White Sands National Monument" (the other parts are useless!) I can do this is Vicky @mvzhuang agrees!
@mkoo I have fixed this one, but my point with this issue is that there will be others?
Can we find and fix them in some programmatic way? Remove the No specific locality which is now nonsensical?
@mkoo I have fixed this one, but my point with this issue is that there will be others?
Can we find and fix them in some programmatic way? Remove the No specific locality which is now nonsensical?
Thanks, and yes, this can be part of our larger clean-up work this summer with HG and other locality work. Let's close this and we can start a new one.
There are 57 localities using the higher geography
United States, New Mexico, Dona Ana County
that also includeNo specific locality recorded.
in the specific locality. It makes sense that there may be more than one, but some of them seem nonsensical.For example https://arctos.database.museum/place.cfm?action=detail&locality_id=11467864
Which clearly does have some specific locality?
No specific locality recorded., Dona Ana County, White Sands National Monument
The question here is what do you do when the specific locality is covered by a feature? The current specific locality makes no sense and I imagine there are others like this from migrating to GADM. This seems like a job for the geography committee. @mkoo