You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A "parent" geography would be useful, particularly for small features (if those should be geography at all - #1366) and those without their own polygons. For example,
It might be possible to dynamically derive parent for some entries, but some will be more complicated than scripts can readily handle and will produce unintended results.
A "parent" geography would be useful, particularly for small features (if those should be geography at all - #1366) and those without their own polygons. For example,
https://arctos.database.museum/place.cfm?action=detail&geog_auth_rec_id=1005444
The northern points are almost certainly outside of both the asserted geography and the "parent" county, which does have spatial boundaries.
https://arctos.database.museum/place.cfm?action=detail&geog_auth_rec_id=1001706
It might be possible to dynamically derive parent for some entries, but some will be more complicated than scripts can readily handle and will produce unintended results.
Suggest adding "parent geography"
which would allow users to assert a "check at least this much" option (and perhaps we can attempt to initially populate it with scripts).
The text was updated successfully, but these errors were encountered: