Recommendations on a two-way workflow for boundary data

[christophertull]

First off, awesome effort, and I hope this becomes the de facto standard for national boundary data.

I wanted to ask your thoughts on developing a two-way workflow for a user of this data.

Using data

• Looks like we could download an import the data, but then we would have outdated info going forward.
• Alternatively, it looks like the OGC API would give us up-to-date boundaries based on PWSIDs?

Contributing data
Sometimes in the course of our work with agencies, we notice that their boundary does not line up with the actual meter locations we have access to. It looks like we would need to

1. correct the boundary locally
2. export to geojson
3. submit a PR with the new geojson file

Is that right?

On a related note, your contributing info mentions to submit changes through an official state repository when possible. Do you have a list of official state repositories that we could reference? It would be helpful to know how to go about this.

[ksonda]

Thanks for this @christophertull.

We're working on a more interactive system for data submission. I can show you it sometime. Will be ready by EOY. In the meantime, your assessment of contributing data is correct, and the most up to data boundaries will always be available from via geoconnex identifier https://geoconnex.us/ref/pws/[pwsid].

EG https://geoconnex.us/ref/pws/NC0368010 for an html representation
https://geoconnex.us/ref/pws/NC0368010?f=json for geojson

Or you can use https://reference.geoconnex.us OGC-API endpoint (collection name is pws) or the OGC-API endpoint you referenced as well to pull data for multiple pwsid based on any filters.

[christophertull]

Awesome! Thanks @ksonda. Looking forward to seeing the more interactive system you mention 👍

Love the geoconnex links that allow preview of the shapefile.

As an aside, looks like the HTML page is failing with an internal server error when querying for a PWSID that doesn't exist in the data such as CA3390049. Maybe intended? JSON seems to return NotFound which makes sense.