Mapping for county-only localities

[dperriguey]

We have to follow certain laws about not publishing locality information to reduce fossil poaching and protect paleontological resources. Also, we'd like to mask private land localities for the same and other obvious reasons. We're currently masking coordinates, but that is not helpful when trying to also show the geographic extent of our collections in iDigBio. http://vertpaleo.org/the-Society/Advocacy/Paleontological-Resources-Preservation-Act.aspx

Might there be a way to reduce the resolution of the published locality information to the county level, without destroying the actual coordinates? Coordinates can be requested, and we'd only give them out for scientific purposes.

[Jegelewicz]

@dperriguey I have a possible solution, but it would be easier if we just talked it out. I'll email you my number and you can call me.

[dperriguey]

Ok, great! Thanks!

[dustymc]

That conversation is scattered all over the place, but https://github.com/ArctosDB/documentation-wiki/issues/130#issuecomment-542321149 is a decent place to start.

[Jegelewicz]

Just talked to @dperriguey and here is what we are trying to accomplish.

We have these public localities that are only presenting locality to the level of county. Yay! we have thwarted fossil poachers and pleased Federal agencies and private landowners.

BUT these generic localities will not map anywhere because there are no coordinates associated with them. Is there any way to automagicically get county-level coordinates with appropriate errors/datum so that we can get these public localities to map?

For NMMNH, any locality with the specific locality "Contact collection for details" should be mapped to higher geography. (Could we use this as a code for "map this to county"?)

I know I can create all of these manually, but I'm looking for a way to make it easier. @dustymc any ideas?

[dustymc]

We have WKT for most (all?) counties, I assume (based on nothing) that drawing a circle around it won't be much of a trick once we get to a place from which we can access real spatial tools.

Until then, it doesn't seem THAT horrible to make a bunch of named localities ("Whatever County, Some State" might be nice...), add whatever spatial data you want with them, and use them as the 'public' stack.

@tucotuco @mkoo might have something useful to add.

[mkoo]

I agree, use the wkt's in HG as the locality; if you need a centroid, we can calculate them (local gis is fine) and have a set of localities at the county-level. Believe me, more than one collection will use them!

Given that we should also determine a consistent way of describing them in SpecLocality. Right now we have a ton of "No Specific Locality" which is not helpful in reviewing lots of points on a map (HG is not visible until you access the specific record). Recently, I've had student amend with "No Specific Locality; georeferenced to Lagos State" or whatever. Not sure if that's the best phrasing but.... barring anything else it helps and seems better at distinguishing between the truly ungeoreferencable "No Specific Locality"

So what are the states/counties that immediate need such county level localities?

On Thu, Oct 31, 2019 at 10:41 AM dustymc notifications@github.com wrote:

We have WKT for most (all?) counties, I assume (based on nothing) that drawing a circle around it won't be much of a trick once we get to a place from which we can access real spatial tools.

Until then, it doesn't seem THAT horrible to make a bunch of named localities ("Whatever County, Some State" might be nice...), add whatever spatial data you want with them, and use them as the 'public' stack.

@tucotuco https://github.com/tucotuco @mkoo https://github.com/mkoo might have something useful to add.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/2353?email_source=notifications&email_token=AATH7UNDZABDO2M2L3M234TQRMKFDA5CNFSM4JHNWA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYUVMA#issuecomment-548489904, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATH7UJYKCBUHOJWE35P65TQRMKFDANCNFSM4JHNWA4A .

[Jegelewicz]

@mkoo YES! The only thing for us is that we DO have more specific locality info, but we are barred from making it publicly available. Rather than "No Specific Locality: Georeferenced to XXX" I'd like to have these say "Contact collection for more details: georeferenced to XXX"

For us, all counties the state of New Mexico would be a really good start. @dperriguey is looking at stuff in the Western Interior Seaway.

[dustymc]

I would like to see specific locality more machine-readable, which is also more human-readable. "No Specific Locality; georeferenced to Lagos State" is remarks-or-something.

I think the most "correct" way of conveying that is specloc=NULL, and "georeferenced to..." can be read from the georeference itself. If we must put something in there, "Whatever County, Some State" doesn't make me TOO twitchy.

If we still hate NULL, it's worth following the guidance at http://handbook.arctosdb.org/documentation/locality.html#specific-locality

"Contact collection for more details: georeferenced to XXX" sounds like a specimen event remark to me - you may be withholding more than georeference precision (geology stuff, event attributes, collecting method, etc. are all possible), that should cover it all and provide a consistent way for users to figure out what's going on.

A small sample of current data:

     no locality recorded
 Exact locality unknown. Outcrop of "greensand conglomerate" in place. Along south fork of Nikolai Creek about one-third

 No specific locality recorded.
 no locality recorded
 no specific locality recorded

Exact Locality Unknown
Exact Locality Unknown. Probably SW Washington State
Exact locality unknown
Exact locality unknown.
Exact locality unknown. Likely OJsaurus bonebed. Prince Creek Formation outcrops, Colville River.
Exact locality unknown. Likely in Alaska.
Exact locality unknown; "somewhere in West Alabama"
Exact locality unkown.

LOCALITY UNKNOWN
LOCALITY UNKOWN
LOCALITY UNREADABLE
LOCALITY unknown.
LOCALITY?, 0250 m.
Locality specified with coordinates.
Locality unknown
NO LOCALITY
NO LOCALITY (BIOLOGY 121 LAB SPECIMEN)
NO LOCALITY DATA
NO SPECIFIC LOCALITY
NO SPECIFIC LOCALITY  : CAPTIVE ALBUQUERQUE
NO SPECIFIC LOCALITY DATA
NO SPECIFIC LOCALITY GIVEN; T20S, R8W, SW 1/4, SEC 19
NO SPECIFIC LOCALITY GIVEN; T24S, R8W, SEC 36
NO SPECIFIC LOCALITY UNM MALARIA RESEARCH COLONY
NO SPECIFIC LOCALITY.
NO SPECIFIC LOCALITY: RECIEVED FROM RIO GRANDE ZOO
NO SPECIFIC LOCALITY: RIO GRANDE ZOO, ALBUQUERQUE
NO SPECIFIC LOCALITY; T10N, R4E, NE 1/4 SEC 35
NO SPECIFIC LOCALITY; T10N, R4E, SEC 2
NO SPECIFIC LOCALITY; T10N, R5E, NE 1/4 SEC 34
NO SPECIFIC LOCALITY; T10N, R5E, NE 1/4 SEC 35
NO SPECIFIC LOCALITY; T15S, R11E, SEC 32
NO SPECIFIC LOCALITY; T17N, R8W, SW 1/4, SEC 12
NO SPECIFIC LOCALITY; T17S, R8W, SW 1/4, SEC 12
NO SPECIFIC LOCALITY; T17S, R8W, SW 1/4, SEC 19
NO SPECIFIC LOCALITY; T20S, R8W, SW 1/4, SEC 19
NO SPECIFIC LOCALITY; T21, R53, N1/2, SE 1/4 SEC 2
NO SPECIFIC LOCALITY; T21N, R54W, NW 1/4 SEC 19
NO SPECIFIC LOCALITY; T23S, R13E
NO SPECIFIC LOCALITY; T24S, R8W, SEC 36
NO SPECIFIC LOCALITY; T25S, R7W, NE 1/4, SEC 7
NO SPECIFIC LOCALITY; T28S, R21W, MIDDLE SEC 11
NO SPECIFIC LOCALITY; T29S, R19W, SEC 4
NO SPECIFIC LOCALITY; T30S, R16W, NW 1/4 SEC 34
NO SPECIFIC LOCALITY; T30S, R18W, NE 1/4 SEC 18
NO SPECIFIC LOCALITY; T31S, R15W, NE 1/4 SEC 3
NO SPECIFIC LOCALITY; T31S, R18W, MW 1/4 SEC 6
NO SPECIFIC LOCALITY; T31S, R18W, NW 1/4 SEC 6
NO SPECIFIC LOCALITY; T31S, R19W, MIDDLE SEC 33
NO SPECIFIC LOCALITY; T31S, R21W, SE CORNER SEC 31
NO SPECIFIC LOCALITY; T32N, R7W, NW 1/4 SEC 24
NO SPECIFIC LOCALITY; T32S, R19W, MIDDLE SEC 35
NO SPECIFIC LOCALITY; T33S, R18 W, NW 1/4 SEC 18
NO SPECIFIC LOCALITY; T33S, R18W, MIDDLE SEC 12
NO SPECIFIC LOCALITY; T33S, R18W, NW 1/4 SEC 18
NO SPECIFIC LOCALITY; T33S, R21W, SEC 8
NO SPECIFIC LOCALITY; T34S, R18W, NW 1/4 SEC 1
NO SPECIFIC LOCALITY; T34S, R22W, SE 1/4 SEC 1
NO SPECIFIC LOCALITY; T37N, R11W, SW 1/4 SEC 4
NO SPECIFIC LOCALITY; T37N, R12W, SE 1/4 SEC 33
NO SPECIFIC LOCALITY; T3S, R16E, SEC 20
NO SPECIFIC LOCALITY; T5N, R4E, SEC 2
NO SPECIFIC LOCALITY; T5S, R18E, MIDDLE SEC 20
NO SPECIFIC LOCALITYNDE ZOO, IN CAPTIVITY

No Locality Given
No Specific Locality
No Specific Locality Given
No Specific Locality Recorded
No Specific Locality, No Date
No Specific locality recorced
No Specific locality recorded
No Specific locality reocrded
No Specific locatliy recorded
No locality
No locality data
No locality data, but likely from Alaska.
No locality information given
No locality recorded
No locality recorded.
No spec locality given
No spec locality recorded
No specfic locality recorded.
No specific locaility
No specific locality
No specific locality available
No specific locality data
No specific locality data given
No specific locality data recorded
No specific locality given
No specific locality given.
No specific locality noted
No specific locality provided
No specific locality recoded
No specific locality recorded
No specific locality recorded, likely from zoo.
No specific locality recorded.
No specific locality recorded; georeferenced Florida.
No specific locality recorded; georeferenced Lagos State.
No specific locality recoreded
No specific locality reported
No specific locality reported.
No specific locality.
No specific locality. Pet trade.
No specific localtity recorded
No specific locatlity recorded.
No specififc locality recorded
No speciifc locality.
SPECIFIC LOCALITY NOT KNOWN; T163N, R55W, SEC 31
SPECIFIC LOCALITY UNKNOWM; T29S, R19W, SEC 32
SPECIFIC LOCALITY UNKNOWN
SPECIFIC LOCALITY UNKNOWN, ACQUIRED FROM RIO GRAND
SPECIFIC LOCALITY UNKNOWN, LABORATORY SPECIMEN
SPECIFIC LOCALITY UNKNOWN; S 1/2 T3N, R1W
SPECIFIC LOCALITY UNKNOWN; T10N, R3E
SPECIFIC LOCALITY UNKNOWN; T10N, R4E
SPECIFIC LOCALITY UNKNOWN; T10N, R4E, NW 1/4 SEC 11
SPECIFIC LOCALITY UNKNOWN; T10N, R4E, SW 1/4 SEC 24
SPECIFIC LOCALITY UNKNOWN; T10N, R5E, NW 1/4 SEC 30
SPECIFIC LOCALITY UNKNOWN; T10N, R5E, W 1/2 SEC 1
SPECIFIC LOCALITY UNKNOWN; T11N, R4E, E 1/2 SEC 11
SPECIFIC LOCALITY UNKNOWN; T11N, R4E, MIDDLE SEC 2
SPECIFIC LOCALITY UNKNOWN; T11N, R4E, NE 1/4 SEC 10
SPECIFIC LOCALITY UNKNOWN; T11N, R4E, SEC 26
SPECIFIC LOCALITY UNKNOWN; T11N, R4E, SEC 3
SPECIFIC LOCALITY UNKNOWN; T11N, R4E, SW 1/4 SEC 2
SPECIFIC LOCALITY UNKNOWN; T11N, R4E, W 1/2 SEC 2
SPECIFIC LOCALITY UNKNOWN; T11N, R5E, SW 1/4 SEC 14
SPECIFIC LOCALITY UNKNOWN; T11N-R4E, SEC 26
SPECIFIC LOCALITY UNKNOWN; T12N, R4E, MIDDLE HALF SEC 3
SPECIFIC LOCALITY UNKNOWN; T15N, R1E, SEC 12
SPECIFIC LOCALITY UNKNOWN; T163N, R55W, SEC 31
SPECIFIC LOCALITY UNKNOWN; T163N, R55W, SEC 32
SPECIFIC LOCALITY UNKNOWN; T163N, R56W, SEC 36
SPECIFIC LOCALITY UNKNOWN; T17N, R10W, NE 1/4 SEC 36
SPECIFIC LOCALITY UNKNOWN; T17S, R8W, SW 1/4 SEC 12
SPECIFIC LOCALITY UNKNOWN; T23S, R19W, SEC 32
SPECIFIC LOCALITY UNKNOWN; T27N, R11W, NW 1/4 SEC 14
SPECIFIC LOCALITY UNKNOWN; T28S, R19W, SEC 20
SPECIFIC LOCALITY UNKNOWN; T28S, R19W, SEC 32
SPECIFIC LOCALITY UNKNOWN; T28S, R22W, NW 1/4 SEC 13
SPECIFIC LOCALITY UNKNOWN; T29S, R19W, SEC 32
SPECIFIC LOCALITY UNKNOWN; T2S, R6E, E 1/2 SEC 19
SPECIFIC LOCALITY UNKNOWN; T32N, R7W
SPECIFIC LOCALITY UNKNOWN; T32N, R7W, NE 1/4 SEC 24
SPECIFIC LOCALITY UNKNOWN; T33S, R19W, SEC 29
SPECIFIC LOCALITY UNKNOWN; T34S, R18W, N W 1/4 SEC 1
SPECIFIC LOCALITY UNKNOWN; T34S, R18W, NW 1/4 SEC 1
SPECIFIC LOCALITY UNKNOWN; T34S, R19W, SEC 7
SPECIFIC LOCALITY unknown, 4600 FT.
SPECIFIC LOCALITY unknown, 7000 FT, ORGAN MTS.
SPECIFIC LOCALITY unknown.

Souwestern part, exact locality unknown
Specific Locality Unknowm
Specific Locality Unknown
Specific locality not given
Specific locality not recorded
Specific locality not recorded.
Specific locality not specified
Specific locality unknown
Specific locality unknown.
Unknown Exact Locality
Unknown Locality
Unknown Specific Locality

[Locality obscured by annotation]
[No further locality info given.]
[No locality given on label.]
[No locality given on label]
[No locality on label.]
[No location on label.]
[Township, range & section are the only location data given.]; Township 12S, Range 5W, Section 2
[no locality information given].
[no locality recorded]
[no specific locality recorded]
[no specific locality]
[specific locality indecipherable]
[transcribed directly into formatted locality fields]

captive, local
coll. By city rodent control-- no specific locality
local aquarium
locality of collection unknown
locality unknown
no locality
no locality data
no locality data, from pet trade
no locality data, from pet trade, received from Elen Nicole
no locality data, from pet trade, received from James Barzyk
no locality data, recieved from U.S.G.S.
no locality information given
no locality recorded
no locality. Nest #12
no location data
no location given
no location: probably from Savoonga???
no other locality data
no sepcific locality recorded
no soec locality recorded
no spec locality given
no spec locality recorded
no specfic locality
no specfic locality recorded
no specif locality recorded
no specifc locality recorded
no specific  locality recorded
no specific Locality recorded
no specific locaility recorded
no specific locale recorded
no specific localilty recorded
no specific localitty recorded
no specific locality
no specific locality
no specific locality  recorded
no specific locality  recorded
no specific locality available
no specific locality data
no specific locality data recorded
no specific locality entered
no specific locality given
no specific locality information given
no specific locality listed
no specific locality located
no specific locality noted
no specific locality provided
no specific locality recoded
no specific locality recorded
no specific locality recorded
no specific locality recorded (T:68S R:81E S:31 NE)
no specific locality recorded (T:68S R:81W S:20 )
no specific locality recorded (marine)
no specific locality recorded (terrestrial species)
no specific locality recorded (terrestrial)
no specific locality recorded, pet from N. Carolina
no specific locality recorded, see coordinate data
no specific locality recorded.
no specific locality recorded.   Specific Gulf inferred from context.
no specific locality recorded; Arizona?
no specific locality recordedc
no specific locality recoreded
no specific locality redorded
no specific locality reocrded
no specific locality reorded
no specific locality reported
no specific locality reported.
no specific locality specified
no specific locality, Yosemite National Park
no specific locality, only coordinates given
no specific localityrecorded
no specific locallity recorded
no specific localtity recorded
no specific localtiy recorded
no specific location
no specific location recorded
no specific locatlity recorded
no specificlocality recorded
no speciific locality recorded
no verbatim locality recorded

specific locality non recorded
specific locality not found
specific locality not provided
specific locality not recoded
specific locality not recorded
specific locality not recorded ("Shore of Lower St. Lawrence")
specific locality not recorded on prep sheet
specific locality not recorded.
specific locality not reported
specific locality not specified
specific locality not unknown
specific locality provided as coordinates only
specific locality recorded
specific locality uknown
specific locality uncertain, 0.9 miles E of junction Highways 81 and Farm to Market Road 1327
specific locality uncertain.  Delray or Debary Beach
specific locality unclear
specific locality unknown
specific locality unknown, assumed to be from SE USA
specific locality unknown, attributed to Alaska
specific locality unknown; data inferred from specimen label
specific locality unknown; specimen attributed to Yakutia
specific locality/island unknown
specific location unknown

unknown locality

[mkoo]

I'm going to chalk this up to being Halloween and Dusty is trying to be SCARY-- it's working... yes we need to deal with this a whole hella better

I think we need a new page just for No Specific Locality IF it will have an accompanying georeference.

I can live with localities that have the generalized georeferenced site as the SpecLoc but wont that be an awkward concatenation with HG (where they occur)?

HG: United States: California; Alameda County SpecLoc: Alameda County, CA

The thing with specimen-event notes it's harder to batch change (unless there's something new I'm missing). It's so much nicer to update a locality and assign to a bunch of specimens via coll-event.

If we tackle this scary clean-up I suggest: 1) protocol and documentation, 2) we fix up top-priority states (NM, UT, NV) with WKT's ( UT, NV includes our grant needs now), 3) get next set of priorities from incoming migrating collections; 4) tackle everything else last

Oh and lastly, is there an easy way to move media WKT from geog_auth_rec to locality (in Media)?

On Thu, Oct 31, 2019 at 12:54 PM dustymc notifications@github.com wrote:

I would like to see specific locality more machine-readable, which is also more human-readable. "No Specific Locality; georeferenced to Lagos State" is remarks-or-something.

I think the most "correct" way of conveying that is specloc=NULL, and "georeferenced to..." can be read from the georeference itself. If we must put something in there, "Whatever County, Some State" doesn't make me TOO twitchy.

If we still hate NULL, it's worth following the guidance at http://handbook.arctosdb.org/documentation/locality.html#specific-locality

"Contact collection for more details: georeferenced to XXX" sounds like a specimen event remark to me - you may be withholding more than georeference precision (geology stuff, event attributes, collecting method, etc. are all possible), that should cover it all and provide a consistent way for users to figure out what's going on.

A small sample of current data:

 no locality recorded

Exact locality unknown. Outcrop of "greensand conglomerate" in place. Along south fork of Nikolai Creek about one-third

No specific locality recorded. no locality recorded no specific locality recorded

Exact Locality Unknown Exact Locality Unknown. Probably SW Washington State Exact locality unknown Exact locality unknown. Exact locality unknown. Likely OJsaurus bonebed. Prince Creek Formation outcrops, Colville River. Exact locality unknown. Likely in Alaska. Exact locality unknown; "somewhere in West Alabama" Exact locality unkown.

LOCALITY UNKNOWN LOCALITY UNKOWN LOCALITY UNREADABLE LOCALITY unknown. LOCALITY?, 0250 m. Locality specified with coordinates. Locality unknown NO LOCALITY NO LOCALITY (BIOLOGY 121 LAB SPECIMEN) NO LOCALITY DATA NO SPECIFIC LOCALITY NO SPECIFIC LOCALITY : CAPTIVE ALBUQUERQUE NO SPECIFIC LOCALITY DATA NO SPECIFIC LOCALITY GIVEN; T20S, R8W, SW 1/4, SEC 19 NO SPECIFIC LOCALITY GIVEN; T24S, R8W, SEC 36 NO SPECIFIC LOCALITY UNM MALARIA RESEARCH COLONY NO SPECIFIC LOCALITY. NO SPECIFIC LOCALITY: RECIEVED FROM RIO GRANDE ZOO NO SPECIFIC LOCALITY: RIO GRANDE ZOO, ALBUQUERQUE NO SPECIFIC LOCALITY; T10N, R4E, NE 1/4 SEC 35 NO SPECIFIC LOCALITY; T10N, R4E, SEC 2 NO SPECIFIC LOCALITY; T10N, R5E, NE 1/4 SEC 34 NO SPECIFIC LOCALITY; T10N, R5E, NE 1/4 SEC 35 NO SPECIFIC LOCALITY; T15S, R11E, SEC 32 NO SPECIFIC LOCALITY; T17N, R8W, SW 1/4, SEC 12 NO SPECIFIC LOCALITY; T17S, R8W, SW 1/4, SEC 12 NO SPECIFIC LOCALITY; T17S, R8W, SW 1/4, SEC 19 NO SPECIFIC LOCALITY; T20S, R8W, SW 1/4, SEC 19 NO SPECIFIC LOCALITY; T21, R53, N1/2, SE 1/4 SEC 2 NO SPECIFIC LOCALITY; T21N, R54W, NW 1/4 SEC 19 NO SPECIFIC LOCALITY; T23S, R13E NO SPECIFIC LOCALITY; T24S, R8W, SEC 36 NO SPECIFIC LOCALITY; T25S, R7W, NE 1/4, SEC 7 NO SPECIFIC LOCALITY; T28S, R21W, MIDDLE SEC 11 NO SPECIFIC LOCALITY; T29S, R19W, SEC 4 NO SPECIFIC LOCALITY; T30S, R16W, NW 1/4 SEC 34 NO SPECIFIC LOCALITY; T30S, R18W, NE 1/4 SEC 18 NO SPECIFIC LOCALITY; T31S, R15W, NE 1/4 SEC 3 NO SPECIFIC LOCALITY; T31S, R18W, MW 1/4 SEC 6 NO SPECIFIC LOCALITY; T31S, R18W, NW 1/4 SEC 6 NO SPECIFIC LOCALITY; T31S, R19W, MIDDLE SEC 33 NO SPECIFIC LOCALITY; T31S, R21W, SE CORNER SEC 31 NO SPECIFIC LOCALITY; T32N, R7W, NW 1/4 SEC 24 NO SPECIFIC LOCALITY; T32S, R19W, MIDDLE SEC 35 NO SPECIFIC LOCALITY; T33S, R18 W, NW 1/4 SEC 18 NO SPECIFIC LOCALITY; T33S, R18W, MIDDLE SEC 12 NO SPECIFIC LOCALITY; T33S, R18W, NW 1/4 SEC 18 NO SPECIFIC LOCALITY; T33S, R21W, SEC 8 NO SPECIFIC LOCALITY; T34S, R18W, NW 1/4 SEC 1 NO SPECIFIC LOCALITY; T34S, R22W, SE 1/4 SEC 1 NO SPECIFIC LOCALITY; T37N, R11W, SW 1/4 SEC 4 NO SPECIFIC LOCALITY; T37N, R12W, SE 1/4 SEC 33 NO SPECIFIC LOCALITY; T3S, R16E, SEC 20 NO SPECIFIC LOCALITY; T5N, R4E, SEC 2 NO SPECIFIC LOCALITY; T5S, R18E, MIDDLE SEC 20 NO SPECIFIC LOCALITYNDE ZOO, IN CAPTIVITY

No Locality Given No Specific Locality No Specific Locality Given No Specific Locality Recorded No Specific Locality, No Date No Specific locality recorced No Specific locality recorded No Specific locality reocrded No Specific locatliy recorded No locality No locality data No locality data, but likely from Alaska. No locality information given No locality recorded No locality recorded. No spec locality given No spec locality recorded No specfic locality recorded. No specific locaility No specific locality No specific locality available No specific locality data No specific locality data given No specific locality data recorded No specific locality given No specific locality given. No specific locality noted No specific locality provided No specific locality recoded No specific locality recorded No specific locality recorded, likely from zoo. No specific locality recorded. No specific locality recorded; georeferenced Florida. No specific locality recorded; georeferenced Lagos State. No specific locality recoreded No specific locality reported No specific locality reported. No specific locality. No specific locality. Pet trade. No specific localtity recorded No specific locatlity recorded. No specififc locality recorded No speciifc locality. SPECIFIC LOCALITY NOT KNOWN; T163N, R55W, SEC 31 SPECIFIC LOCALITY UNKNOWM; T29S, R19W, SEC 32 SPECIFIC LOCALITY UNKNOWN SPECIFIC LOCALITY UNKNOWN, ACQUIRED FROM RIO GRAND SPECIFIC LOCALITY UNKNOWN, LABORATORY SPECIMEN SPECIFIC LOCALITY UNKNOWN; S 1/2 T3N, R1W SPECIFIC LOCALITY UNKNOWN; T10N, R3E SPECIFIC LOCALITY UNKNOWN; T10N, R4E SPECIFIC LOCALITY UNKNOWN; T10N, R4E, NW 1/4 SEC 11 SPECIFIC LOCALITY UNKNOWN; T10N, R4E, SW 1/4 SEC 24 SPECIFIC LOCALITY UNKNOWN; T10N, R5E, NW 1/4 SEC 30 SPECIFIC LOCALITY UNKNOWN; T10N, R5E, W 1/2 SEC 1 SPECIFIC LOCALITY UNKNOWN; T11N, R4E, E 1/2 SEC 11 SPECIFIC LOCALITY UNKNOWN; T11N, R4E, MIDDLE SEC 2 SPECIFIC LOCALITY UNKNOWN; T11N, R4E, NE 1/4 SEC 10 SPECIFIC LOCALITY UNKNOWN; T11N, R4E, SEC 26 SPECIFIC LOCALITY UNKNOWN; T11N, R4E, SEC 3 SPECIFIC LOCALITY UNKNOWN; T11N, R4E, SW 1/4 SEC 2 SPECIFIC LOCALITY UNKNOWN; T11N, R4E, W 1/2 SEC 2 SPECIFIC LOCALITY UNKNOWN; T11N, R5E, SW 1/4 SEC 14 SPECIFIC LOCALITY UNKNOWN; T11N-R4E, SEC 26 SPECIFIC LOCALITY UNKNOWN; T12N, R4E, MIDDLE HALF SEC 3 SPECIFIC LOCALITY UNKNOWN; T15N, R1E, SEC 12 SPECIFIC LOCALITY UNKNOWN; T163N, R55W, SEC 31 SPECIFIC LOCALITY UNKNOWN; T163N, R55W, SEC 32 SPECIFIC LOCALITY UNKNOWN; T163N, R56W, SEC 36 SPECIFIC LOCALITY UNKNOWN; T17N, R10W, NE 1/4 SEC 36 SPECIFIC LOCALITY UNKNOWN; T17S, R8W, SW 1/4 SEC 12 SPECIFIC LOCALITY UNKNOWN; T23S, R19W, SEC 32 SPECIFIC LOCALITY UNKNOWN; T27N, R11W, NW 1/4 SEC 14 SPECIFIC LOCALITY UNKNOWN; T28S, R19W, SEC 20 SPECIFIC LOCALITY UNKNOWN; T28S, R19W, SEC 32 SPECIFIC LOCALITY UNKNOWN; T28S, R22W, NW 1/4 SEC 13 SPECIFIC LOCALITY UNKNOWN; T29S, R19W, SEC 32 SPECIFIC LOCALITY UNKNOWN; T2S, R6E, E 1/2 SEC 19 SPECIFIC LOCALITY UNKNOWN; T32N, R7W SPECIFIC LOCALITY UNKNOWN; T32N, R7W, NE 1/4 SEC 24 SPECIFIC LOCALITY UNKNOWN; T33S, R19W, SEC 29 SPECIFIC LOCALITY UNKNOWN; T34S, R18W, N W 1/4 SEC 1 SPECIFIC LOCALITY UNKNOWN; T34S, R18W, NW 1/4 SEC 1 SPECIFIC LOCALITY UNKNOWN; T34S, R19W, SEC 7 SPECIFIC LOCALITY unknown, 4600 FT. SPECIFIC LOCALITY unknown, 7000 FT, ORGAN MTS. SPECIFIC LOCALITY unknown.

Souwestern part, exact locality unknown Specific Locality Unknowm Specific Locality Unknown Specific locality not given Specific locality not recorded Specific locality not recorded. Specific locality not specified Specific locality unknown Specific locality unknown. Unknown Exact Locality Unknown Locality Unknown Specific Locality

[Locality obscured by annotation] [No further locality info given.] [No locality given on label.] [No locality given on label] [No locality on label.] [No location on label.] [Township, range & section are the only location data given.]; Township 12S, Range 5W, Section 2 [no locality information given]. [no locality recorded] [no specific locality recorded] [no specific locality] [specific locality indecipherable] [transcribed directly into formatted locality fields]

captive, local coll. By city rodent control-- no specific locality local aquarium locality of collection unknown locality unknown no locality no locality data no locality data, from pet trade no locality data, from pet trade, received from Elen Nicole no locality data, from pet trade, received from James Barzyk no locality data, recieved from U.S.G.S. no locality information given no locality recorded no locality. Nest #12 no location data no location given no location: probably from Savoonga??? no other locality data no sepcific locality recorded no soec locality recorded no spec locality given no spec locality recorded no specfic locality no specfic locality recorded no specif locality recorded no specifc locality recorded no specific locality recorded no specific Locality recorded no specific locaility recorded no specific locale recorded no specific localilty recorded no specific localitty recorded no specific locality no specific locality no specific locality recorded no specific locality recorded no specific locality available no specific locality data no specific locality data recorded no specific locality entered no specific locality given no specific locality information given no specific locality listed no specific locality located no specific locality noted no specific locality provided no specific locality recoded no specific locality recorded no specific locality recorded no specific locality recorded (T:68S R:81E S:31 NE) no specific locality recorded (T:68S R:81W S:20 ) no specific locality recorded (marine) no specific locality recorded (terrestrial species) no specific locality recorded (terrestrial) no specific locality recorded, pet from N. Carolina no specific locality recorded, see coordinate data no specific locality recorded. no specific locality recorded. Specific Gulf inferred from context. no specific locality recorded; Arizona? no specific locality recordedc no specific locality recoreded no specific locality redorded no specific locality reocrded no specific locality reorded no specific locality reported no specific locality reported. no specific locality specified no specific locality, Yosemite National Park no specific locality, only coordinates given no specific localityrecorded no specific locallity recorded no specific localtity recorded no specific localtiy recorded no specific location no specific location recorded no specific locatlity recorded no specificlocality recorded no speciific locality recorded no verbatim locality recorded

specific locality non recorded specific locality not found specific locality not provided specific locality not recoded specific locality not recorded specific locality not recorded ("Shore of Lower St. Lawrence") specific locality not recorded on prep sheet specific locality not recorded. specific locality not reported specific locality not specified specific locality not unknown specific locality provided as coordinates only specific locality recorded specific locality uknown specific locality uncertain, 0.9 miles E of junction Highways 81 and Farm to Market Road 1327 specific locality uncertain. Delray or Debary Beach specific locality unclear specific locality unknown specific locality unknown, assumed to be from SE USA specific locality unknown, attributed to Alaska specific locality unknown; data inferred from specimen label specific locality unknown; specimen attributed to Yakutia specific locality/island unknown specific location unknown

unknown locality

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/2353?email_source=notifications&email_token=AATH7UOM5TJ2N3Y24HCOCDLQRMZZFA5CNFSM4JHNWA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECZBSCA#issuecomment-548542728, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATH7UKHHSJ5URHPT4FEVW3QRMZZFANCNFSM4JHNWA4A .

[dustymc]

Boo....

awkward concatenation

Yea, good point.

specimen-event notes ... update a locality

The paleo stuff is weird in that they won't (probably) - it's purposefully vague, and not limited to localities. For "normal" stuff (you'd like to be more precise but county is all you have, you'll add more later if you find it) yes that would be a horrible place to put locality data.

easy way to move media WKT

Hu! WKT is all in media - there's no reason to move anything, just use geog_auth_rec.WKT_MEDIA_ID as locality.WKT_MEDIA_ID.

Here's some data. Would be good to patch point-radius in, then @Jegelewicz has a formula for getting localities I can load to me. (I'll probably need a reminder to add WTK to that.)

create table temp_geo
 as select * from geog_auth_rec where state_prov in ('New Mexico','Utah','Nevada') and
feature is null and 
drainage is null and
quad is null and
island is null
;

temp_geo.csv.zip

You can pull WKT from that by building URIs around the media_id: https://arctos.database.museum/media/10599572?open

[mkoo]

hmm, ok let check that out. @Jegelewicz https://github.com/Jegelewicz does something that look like this work? https://arctos.database.museum/editLocality.cfm?locality_id=10148106

We already have all the counties we need in Arctos

On Thu, Oct 31, 2019 at 1:37 PM dustymc notifications@github.com wrote:

Boo....

awkward concatenation

Yea, good point.

specimen-event notes ... update a locality

The paleo stuff is weird in that they won't (probably) - it's purposefully vague, and not limited to localities. For "normal" stuff (you'd like to be more precise but county is all you have, you'll add more later if you find it) yes that would be a horrible place to put locality data.

easy way to move media WKT

Hu! WKT is all in media - there's no reason to move anything, just use geog_auth_rec.WKT_MEDIA_ID as locality.WKT_MEDIA_ID.

Here's some data. Would be good to patch point-radius in, then @Jegelewicz https://github.com/Jegelewicz has a formula for getting localities I can load to me. (I'll probably need a reminder to add WTK to that.)

create table temp_geo as select * from geog_auth_rec where state_prov in ('New Mexico','Utah','Nevada') and feature is null and drainage is null and quad is null and island is null ;

temp_geo.csv.zip https://github.com/ArctosDB/arctos/files/3795719/temp_geo.csv.zip

You can pull WKT from that by building URIs around the media_id: https://arctos.database.museum/media/10599572?open

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/2353?email_source=notifications&email_token=AATH7UMDNGMEOYDPIP7V3ULQRM62NA5CNFSM4JHNWA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECZFOBQ#issuecomment-548558598, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATH7UL6OPGYU3K6YPX7P3DQRM62NANCNFSM4JHNWA4A .

[Jegelewicz]

@mkoo yeah, I think that will work, See https://arctos.database.museum/guid/NMMNH:Paleo:3006

[Jegelewicz]

As for https://github.com/ArctosDB/arctos/issues/2353#issuecomment-548542728

Add this to the low quality data dashboard! If I had a list of specimens using these errant versions of "no specific locality" I'd add it to my never-ending to-do list of stuff I need to clean up!

[Jegelewicz]

I was pretty sure where to find this one:

Exact locality unknown; "somewhere in West Alabama"

So I just changed the specific locality for this one to : "Alabama (no specific locality)"

@mkoo can we do all 50 states too?

[Jegelewicz]

Once this is set up, it needs documentation.

[dustymc]

dashboard

Issue, but I'm not sure how useful it would be - I think that was %LOCA%, which just finds something I saw earlier today. There are endless possibilities!

 select spec_locality from locality where upper(spec_locality) like '%DATA%' group by spec_locality order by spec_locality;
" No Data"
"Summit"  [= No Data]
(no data)
Addditonal data "?"
Additionaal data found dead in snow

DATA ?
DATA?
Data Error
Data Pending
NO  DATA
NO AVAILABLE DATA
NO DATA
NO DATA | Land Between the Lakes sector: NA
NO DATA, CAPTIVE PET, CDC JOB 2390
NO DATA, JOB 1846, (I)
NO DATA, JOB 1846, (J)
NO DATA, JOB 1846, (K)
NO DATA, JOB 1846, (L)
NO DATA, JOB 1846, (M)
NO DATA, JOB 1846, (N)
NO DATA, JOB 1846, (O)
NO DATA, JOB 1846, (P)
NO DATA, JOB 1846, (Q)
NO DATA, JOB 1846, (R)
NO DATA, TEACHING COLLECTION; TO HIWA MUSEUM 1-29-
NO DATA- AVIARY BIRD
NO DATA- GOTTEN FROM LOCAL BUTCHER
NO DATA: ACQUIRED ON PERMANENT LOAN FROM US FISH & WILDLIFE SERVICE
NO DATA: EXCHANGE FROM ROSSOLIMO IN RUSSIA
NO DATA: OBTAINED FROM PET SHOP
NO DATA?
NO DATA| LABORATORY SPECIMEN
NO LOCALITY DATA
NO SPECIFIC LOCALITY DATA
New York, Candor no data
No Data
No Data - Received From Adobe Mt. Wildlife Center
No Data [prob Southeast Alaska]
No Data, From Rio Grande zoo
No Data, prob. Central New Mexico
No Data, via J SouthApplegarth
No Data, wrong measurements on tag
No Data; Probably Greater El Paso Area
No data
No data recorded
No data recorded; location assumed to be Rainbow Ridge area, NW of McCallum Creek
No data, Davis Mts. State Park
No data, Gungahlin
No data.
No data. Was in RM freezer
No data; possibly Colorado.
No field notes found.  Field bags labeled "Shell Bed 'D' Ocean Point" (on dino data map Ocean Point is a little south of
 Bed D)  Assoc. with dino work of 1985, 1985 P-023

No locality data
No locality data, but likely from Alaska.
No other data
No other data available
No specific locality data
No specific locality data given
No specific locality data recorded
North Bend; no other data
Okaylekok Inlet, Wales  (spelled Okaloyak on data card
Okaylekok Inlet, Wales  (spelled Okaloyak on data card)
Reserva Natural Cerro Datanlí El Diablo, El Gobiado
SE Arizona, no other data
SEPANG, OTHER DATA UNKNOWN
SEVILLETA NWR; NO FURTHER DATA
SEVILLETA NWR; NO SPECIFIC DATA
SIERRA ARMY DEPOT, NO DATA
Sitka area- no data
Spring Creek, near mouth. (Incomplete locality data).
Talikud Island, off Dadatan
Talkeetna Mountains; no other data
There is no specific locality data for this specimen.
UNIVERSITY OF ALASKA MUSEUM NO-DATA
UNIVERSITY OF ALASKA MUSEUM-NO DATA
UNIVERSITY OF ALASKA MUSEUM-NO DATA GM UNIT 24
UNIVERSITY OF ALASKA MUSEUM-NO DATA NEAR KANTIDHNA
USA LIKELY, NO DATA
Universidad Centroamericana field station, Reserva Datanlí-El Diablo
Uranga , Farm ENS , Grid No data
WT 102.3 g LE 30.5 cm WS 73 cm WC 24 cm "No data, received COA summer 1982" "Banded as a chick on Great Gull Island, New
 York, June 23, 1981"

Wales, Okaylekok Inlet (also spelled Okaloyak on data card)
Wales; Okaylekok Inlet (spelled Okaloyak on data card)
YELLOWSTONE NAT PK.  NO DATA
[Township, range & section are the only location data given.]; Township 12S, Range 5W, Section 2
additional data collected jan 1982 hit window WT. .9 oz W 87mm WS 10 3/8 in L 6 in 5 FAT (MBO) Heavy molt ( ILLEGIBLE WR
ITING) OUTER TRERICES Salvaged by Stan Grierson

addtional data collected summer 1985
addtional data hit by auto length 6 1/8in wing 3 1/2in span 10 1/2 in weight 1 1/2 oz
near Limpopo River (no other data)
no additional data
no available data
no data
no data Washington?
no data, New Guinea region
no data, probably Davis
no data, probably Kenai
no data, received from U.S. Fish and Wildlife Service
no data- probably Sitka area
no further data
no locality data
no locality data, from pet trade
no locality data, from pet trade, received from Elen Nicole
no locality data, from pet trade, received from James Barzyk
no locality data, recieved from U.S.G.S.
no location data
no other data
no other locality data
no specific locality data
no specific locality data recorded
no specific locality recorded, see coordinate data
nodata
not recorded- see lat/long data
obtain from Tom Jung host data
obtained at Alamogordo Rattlesnake Roundup (no other data)
obtained live from Alamogordo Rattlesnake roundup (no other data available)
specific locality unknown; data inferred from specimen label

[Jegelewicz]

OMG - this is insane.

[Jegelewicz]

BTW @dperriguey please also see all of our discussion at #2354 #2347 and https://github.com/ArctosDB/documentation-wiki/issues/133

Let me know if you have any questions about how we are handling this at NMMNH.

[mkoo]

when will halloween be over!!!???? ok on my list. but working on US counties and states first.

I have a student to put on this, too.

On Thu, Oct 31, 2019 at 4:01 PM Teresa Mayfield-Meyer < notifications@github.com> wrote:

BTW @dperriguey https://github.com/dperriguey please also see all of our discussion at #2354 https://github.com/ArctosDB/arctos/issues/2354

2347 https://github.com/ArctosDB/arctos/issues/2347 and

ArctosDB/documentation-wiki#133 https://github.com/ArctosDB/documentation-wiki/issues/133

Let me know if you have any questions about how we are handling this at NMMNH.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/2353?email_source=notifications&email_token=AATH7UPZUVKJDF2A7KWY5BTQRNPWHA5CNFSM4JHNWA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECZQEHA#issuecomment-548602396, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATH7UPR65B6CJZVN2PWDQLQRNPWHANCNFSM4JHNWA4A .

[campmlc]

Ooh, this is scary. Can we do global search and replace with a standardized version, putting all existing non- georeferenced versions in collecting event remarks?

On Thu, Oct 31, 2019, 5:41 PM Michelle Koo notifications@github.com wrote:

when will halloween be over!!!???? ok on my list. but working on US counties and states first.

I have a student to put on this, too.

On Thu, Oct 31, 2019 at 4:01 PM Teresa Mayfield-Meyer < notifications@github.com> wrote:

BTW @dperriguey https://github.com/dperriguey please also see all of our discussion at #2354 https://github.com/ArctosDB/arctos/issues/2354

2347 https://github.com/ArctosDB/arctos/issues/2347 and

ArctosDB/documentation-wiki#133 https://github.com/ArctosDB/documentation-wiki/issues/133

Let me know if you have any questions about how we are handling this at NMMNH.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/ArctosDB/arctos/issues/2353?email_source=notifications&email_token=AATH7UPZUVKJDF2A7KWY5BTQRNPWHA5CNFSM4JHNWA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECZQEHA#issuecomment-548602396 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AATH7UPR65B6CJZVN2PWDQLQRNPWHANCNFSM4JHNWA4A

.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/2353?email_source=notifications&email_token=ADQ7JBDEIM3KVBNPCUN2FT3QRNUKBA5CNFSM4JHNWA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECZSJGA#issuecomment-548611224, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADQ7JBG7FGWZVWR5O5UOHFDQRNUKBANCNFSM4JHNWA4A .

[Jegelewicz]

Actually, a bit of a revision on what Mariel said. Could we use higher geography coordinates for ANY locality without any coordinates?

If locality has no coordinates (or encumbered coordinates), then publish coordinates associated with higher geography.

Then, instead of creating a zillion "XXX (no specific locality)" localities with higher geography coordinates, we just put the coordinates right in the higher geography?

[dustymc]

global search and replace

If I could, I'd just do that when people search or something. I can help make lookup tables and such, but this pretty much takes a human to fix.

This is essentially the easiest place in Arctos to be consistent when you don't have to be; I think this is the only text field with documentation (and it's always been there for most of us), the only place you can copy-paste the "correct" value.

Given these data, imagine (because that's about all you can do without investing serious time!) what the other ~half-million records really look like, and what every other free-text field on the planet looks like.

This sort of thing is part of the reason I'm always trying to get the model correct, advocating saying nothing (NULL) when there's nothing to say, when possible exploiting services in pursuit of consistency, and trying to develop guidelines (https://github.com/ArctosDB/arctos/issues/1107). We could do better here, but these data will ALWAYS be inconsistent.

1.5 mi WSW McKerick Park
1.5 mi WSW McKerick Peak
1.5 mi WSW McKesick Peak
1.5 mi WSW McKesick Peak, 6000 ft elev.
1.5 mi WSW McKessick Peak

1.5 mi W of Sagavanirktok River, opp. of Accomplishment Creek
1.5 mi W of Sagavanirktok River, opposite of Accomplishment Creek

1.5 mi up Mary Peak Rd., SW Philomath
1.5 mi up Mary's Peak Rd. from Hwy. 34
1.5 mi up Marys Peak Rd., SW Philomath
SW Philomath, 1.5 mi up Mary's Peak Rd.
ca. 6 mi SW Philomath

Wildcat Canyon, Berkeley
Wildcat Canyon, Berkeley Hills
Wildcat Canyon, Berkeley Hills near Berkeley
Wildcat Canyon, near Berkeley

Etc., etc., etc. Berkeley, Fairbanks, Albuquerque each find at least a thousand distinct speclocs (and doesn't find "MVZ","UA","ABQ", etc., etc., etc.). Many (maybe even most!) are references and such, but there are probably a few hundred easy functional duplicates in there.

Could we use higher geography coordinates for ANY locality without any coordinates?

Most localities have service-derived coordinates, I use higher geog to get them. (Given spatial tools, maybe I could do a bit more with geography - they'd be a nice checksum, minimally.) I could do more with those, and have offered to many times - that's 100% social problem from my perspective.

or encumbered coordinates

I don't think it's the job of Arctos to mess with encumbrances. The model easily accommodates publishing lower-precision data, I could make it easier to create that, but I don't think there are any valid global assumptions about the relationship between geography and encumbrances.

zillion

UAM@ARCTOS> select count(*) from geog_auth_rec where WKT_MEDIA_ID is not null;

  COUNT(*)
----------
      3373

[dustymc]

Also: Other text fields contribute to this. The model can't work like it's designed to if we don't use it properly. All of this adds up to having sometimes thousands of rows (a daunting problem that will probably get ignored) from what should be a very few (something someone might just fix).

Locality remarks (60K unique values) is probably the biggest influence; it contains a lot of comments on non-locality things (something about a specimen or two is most common). It's designed to be a mess, but it doesn't have to be a denormalized mess!

Georeference source (7K unique value) is also a factor, with the usual:

uknown
unavailable
unkknown
unknonw
unknown
unknown
unknown - supplied by Collector
unknown, presumably GPS
unknwon
unknwown
unkown
unkwown
unnkown

not
not available
not given
not reco
not recorded
not recorded
not recorded, extent measured using Google Earth Pro, 22 Sep 2008, Europa Technologies, Cnes/Spot Image, 2008 Kingway Lt
d., eye alt. 12 mi

not recorded.
not recored
not stated
observer's location
observer's notation

Dictionary of Alaska Place Names
Dictionary of Alaska Place Names (Orth
Dictionary of Alaska Place Names (Orth 1967)
Dictionary of Alaska Place Names (Orth, 1967)

and a smattering of misplaced data.

My solution (which actually may be somewhat realistic under locality attributes) would just be to get that out of the model - I don't think we need a bunch of remarks fields with slightly different labels, and that's absolutely what georeference source has become.

[Jegelewicz]

This has made me sad. Going away to have a cry in the corner....

[mkoo]

For now to preserve sanity I am going to forego looking (too) much at Dusty's scary lists (plus Halloween is over) so let's get back to our 'no specific locality' issue. (will this help Teresa's tears?) Here's my update:

I took the least scary csv from Dusty and turned it into a working doc for localities that have HG but 'no specific locality'. There, I searched on 'no specific locality' + State to find localities already in use. I prioritized Locs used by MVZ (but not always) and edited those first:

• editing the SpecLoc to reflect "{county} (no specific locality)"
• then added media wkt
• georeferenced usually by GL but tried a few things too. (side note - I want to see if we can get Berkeleymapper to display wkt/media)

So the Google Doc can be used to find the localities that are "{county} (no specific locality)" and georeferenced, which MVZ students can use now and so can Teresa. The ones without links to locs are still to be done but you can track here. I can have a student create a bunch of new localities based on this model (they will be empty of records which i generally like to avoid because that is sad!) but for now I think I will do the first pass as there are clean-ups I'm doing as I go along.

The more I do of these, the more I am convinced that this is the way to go for "NSL" records with some higher geography. I think where you want to add a remark about other contact info or other info like elevation or whatever is in Specimen-event.

Here's the proposed changes to the Handbook. Please help as brain fried and needs to make more sense!

I will update handbook once I have some feedback -thanks!

[dustymc]

Don't be sad, just georeference! Georeferenced records have service-supplied data and are much more discoverable no matter what's in the asserted data.

@mkoo you might think about naming these- @DerekSikes has some named general localities ("somewhere in Alaska" kinds of things) that I think work pretty well, and prevent not-quite-duplicates from working their way into the system. Names will also prevent the empty records from going away - http://handbook.arctosdb.org/documentation/locality.html#maintenance

[mkoo]

Yea, that's a missing piece! something like 'Generalized county locality"

On Fri, Nov 1, 2019 at 5:40 PM dustymc notifications@github.com wrote:

Don't be sad, just georeference! Georeferenced records have service-supplied data and are much more discoverable no matter what's in the asserted data.

@mkoo https://github.com/mkoo you might think about naming these- @DerekSikes https://github.com/DerekSikes has some named general localities ("somewhere in Alaska" kinds of things) that I think work pretty well, and prevent not-quite-duplicates from working their way into the system. Names will also prevent the empty records from going away - http://handbook.arctosdb.org/documentation/locality.html#maintenance

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/2353?email_source=notifications&email_token=AATH7UM2IRU7XRG5Q6UNQMDQRTEAXA5CNFSM4JHNWA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC4PPQI#issuecomment-548992961, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATH7UJOI77LUDLWLIJSPZLQRTEAXANCNFSM4JHNWA4A .

[Jegelewicz]

BUT - our "no specific localities include geology information that we NEED and it should not be placed in the specimen event. So we probably couldn't use a named "generalized county locality", although we could use the same coordinates as the named locality. Correct?

[Jegelewicz]

Locality nickname will be county + state. WKT will be associated with the locality as well.

[ewommack]

Could we get an example Teresa of a Locality with the new Locality nick name please?

[mkoo]

Beth, here's one: Esmeralda County, Nevada (no specific locality) https://arctos.database.museum/editLocality.cfm?locality_id=10148658 no specimens attached yet! (just a photo)

On Mon, Nov 11, 2019 at 12:41 PM Elizabeth Wommack notifications@github.com wrote:

Could we get an example Teresa of a Locality with the new Locality nick name please?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos/issues/2353?email_source=notifications&email_token=AATH7UPDHMVJIUVCFC4SI7LQTG7NZA5CNFSM4JHNWA4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDYBU5A#issuecomment-552606324, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATH7UNPNTADUGENMGIQFUTQTG7NZANCNFSM4JHNWA4A .

[dperriguey]

Yeah, I have the same problem that @Jegelewicz has. I need to be able to use specific locality and locality nickname. I need to be able to put in the real data (real coordinates), mask them, and be able to select a lower resolution option for publishing that is not masked.

[dustymc]

You can do that now.

https://github.com/ArctosDB/documentation-wiki/issues/130

tl;dr: geology_attribute access=private

[dperriguey]

I'm not trying to mask the geology attributes. Just the coordinates and have an alternative set of coordinates that is publishable.

[dustymc]

https://github.com/ArctosDB/documentation-wiki/issues/130#issuecomment-542321149

[dperriguey]

I just tried the attribute with a record. This is not what I'm looking for. Is your comment saying that you're working on making "access" have options other than "private," like "fuzzy coordinates?"

[Nicole-Ridgwell-NMMNHS]

Here is what we are doing - each specimen has two localities. One private locality and one public locality. The private locality has everything. The public locality has higher geography, names, dates, and geology. To see what this public locality looks like, look at this link: NMMNH P-16505

I suppose you could pick a method to fuzzy your coordinates and add them to the public locality (see discussion above) keeping in mind we need to make sure to do this in a consistent way that doesn't muddle things up.

[dperriguey]

Ok, cool. I don't understand how to make my records look like that.

[Nicole-Ridgwell-NMMNHS]

talk to @Jegelewicz to get a how to on what we're doing. If you want to come over sometime to talk about it in person, you are welcome to.

[dustymc]

1. Any record can have any number of locality-stacks.
2. The access attribute can hide any of them.

From that, you can put your 'private' data in a hidden stack (or several of them, or whatever), replicate it to a (or many, or none, or whatever) non-private stack(s), and alter the public stack(s) however you want. You can share exactly what you want to for each specific catalog record, and I don't have to guess what you mean by "fuzzy," or put Arctos in the position of being required to do things like interpret your permits (which I probably won't have, and certainly can't make legal sense of), or write a bunch of impossibly-complicated code to manipulate an infinite number of subsets of the infinite number of things that you could pull together into a locality stack.

the public locality

Yes, that's what this thread is about - if "somewhere in the county" fits your definition of "fuzzy" you can use the pre-built county-level localities. If it doesn't, you might still be able to clone them and add stuff.

make sure to do this in a consistent way

While that's almost certainly a good idea, it's not a requirement of the model. This provides the ability to access 'standardized fuzzy' data, or to do something unique for every single specimen.

[dperriguey]

Ok, great!

[Jegelewicz]

Just added edits to the proposed handbook change - let me know if you have questions.

[Jegelewicz]

UGH - I see now that I originally said "COUNTY, STATE (no specific locality)", then just added one as "STATE, COUNTY (no specific locality)"

Here's an idea - for these things the specific locality should be "HIGHER GEOG (no specific locality)" that way we don't have issues like the one I just created...

@mkoo @dustymc thoughts?

[dperriguey]

@mkoo this is my list of counties I need for the wkt/coordinates, as per @Jegelewicz suggestion in https://github.com/ArctosDB/documentation-wiki/issues/133 , thanks.

UNM_County_List.zip

[dustymc]

Done?