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
In some cases there is more than one ref_dam representing a unique feature (2 entries, 1 dam). When this happens do we want to remove one of the reference dams or leave them both? Either way if we are fairly certain an entry is a duplicate we should cross reference IDs, right?. Below are a few examples I ran into:
I'm not sure how much the sameAs version matters - owl:sameAs is the stronger of the two and the two really are the exact same physical feature -- so probably fine to go that route. schema:sameAs seems better for softer "webby" sameAs associations.
In some cases there is more than one ref_dam representing a unique feature (2 entries, 1 dam). When this happens do we want to remove one of the reference dams or leave them both? Either way if we are fairly certain an entry is a duplicate we should cross reference IDs, right?. Below are a few examples I ran into:
https://geoconnex.us/ref/dams/1078803 and https://reference.geoconnex.us/collections/dams/items/1087478. In the NID these appear to have been reported by neighboring states and therefor have 2 entries but appear to be the same dam.
https://geoconnex.us/ref/dams/1090897, https://geoconnex.us/ref/dams/1051295, and https://geoconnex.us/ref/dams/1051297
These all appear to represent the same dam feature.
The text was updated successfully, but these errors were encountered: