internetofwater / geoconnex.us

URI registry for https://geoconnex.us based URIs
Other
23 stars 14 forks source link

National Inventory Of Dams #139

Closed dblodgett-usgs closed 2 years ago

dblodgett-usgs commented 2 years ago

In a recent meeting with the USACE, we had some good discussion of registering identifiers and hydrologic locations for dams in the NID. Given that NID has landing content now, (e.g. https://nid.usace.army.mil/#/dams/system/549739/summary) we should be able to move forward in cooperation with USACE folks.

Sounds like the Corps is used to doing hydrologic addressing using "river miles" which should be pretty compatible with the mainstem work that we are pushing. (https://github.com/internetofwater/docs.geoconnex.us/wiki/hydrologic-location-json-ld-guidance)

Am recording this issue for inclusion in an email to Corps collaborators -- hoping we can just engage with them here going forward.

ksonda commented 2 years ago

Any scope for salvaging the addressing that @mikejohnson51 did already? Could be a test case for incorporating multiple addresses in a document.

dblodgett-usgs commented 2 years ago

I think so. Once we have authoritative identifiers to link those updated addresses to, I think we'll have a more coherent way to pursue updating / fixing geospatial and hydrologic locations of the official NID features.

dblodgett-usgs commented 2 years ago

Based on our meeting on Friday with @bvanbockern, we have decided to pursue an NID namespace:

https://geoconnex.us/usace/nid/{nid-id}

that will redirect to

https://nid.usace.army.mil/#/dams/system/{nid-id}

For now, those redirect URLs will not work as USACE wires up the canonical IDs in the API rather than placeholder IDs that are in there now.

In addition to the NID namespace, we will pursue:

https://geoconnex.us/ref/dams/{id}

Where id is assigned arbitrarily in the context of the reference dams dataset and resolve to:

https://reference.geoconnex.us/ref/dams/{id}

The reference dams dataset will be curated through a process led initially by @mikejohnson51 and @dblodgett-usgs with input from USGS, NOAA, and USACE colleagues. We have a few initial sources of truth, including @mikejohnson51's work with open street map, past work from the USGS NAWQA program, and past work on dams from the USGS ecosystems mission area led in part by @dwief-usgs.

ksonda commented 2 years ago

Looks like this API call will give a csv of all the Federal IDs for a regex contribution to /usace/nid/. https://nid.usace.army.mil/api/nation/csv @webb-ben we can kludge together the sitemap from that

dwief-usgs commented 2 years ago

I think using NID namespace makes sense given NID is considered the authoritative dataset.

My biggest concern: I'm sure you are all aware but in the past recycling of NIDIDs has been an issue. Is there a way to handle this, or do you know if NID is addressing this in newer versions? Does initial registration should be specific to a publication year?

In addition, in past versions I've seen states handle removed dams differently where some states drop a dam from NID after removal, others retain the dam noted as removed, others have dropped in one version and added in another. Again just noting this... I have been working with the dam removal community to try documenting these dams and relating ongoing information to individual features... I'd be interested to talk more on that topic and how to best proceed.

I look forward to learning more about geoconnex and using this moving forward!

ksonda commented 2 years ago

hmm. Not sure about that. You and Mike are probably more plugged in on that, and of course @bvanbockern would know better. These folks may also know and have good opinions on this and similar for the NLD https://connectivity.sarpdata.com

dwief-usgs commented 2 years ago

I work with SARP but Kat Hoenke (kat@southeastaquatics.net) and @brendan-ward (bcward@astutespruce.com; e.g. https://github.com/astutespruce/sarp-connectivity) would be best points of contact to get up to date details on that effort. Also not sure what NLD is referring too.

ksonda commented 2 years ago

Ah thanks for the direct contacts. NLD I meant National Levee Database.

dwief-usgs commented 2 years ago

I was looking at the new NID data and looks like there is a new field that in most cases mimics NIDID called "Federal ID". Would be worth investigating to see if that is more appropriate to use than NIDID

ksonda commented 2 years ago

@bvanbockern said on our call last week that the URL pattern https://nid.usace.army.mil/#/dams/system/{six-digit-number}/summary would indeed be being replaced by https://nid.usace.army.mil/#/dams/system/{NID ID/ Federal ID}/summary

I don't recall if he made a distinction between them, in our convo we used them interchangeably. Would be good to clarify.

ksonda commented 2 years ago

Closing for now #161