The Water Data Challenge use case includes the following boundary files that are higher-resolution versions of reference features in info.geoconnex.us:
We should tag every well in wells.gpkg with the state, place, county, and huc8 they are in. Probably have to do some st_intersect or whatever you like to do in python.
Then, the following fields can be added to wells.gpkg:
The Water Data Challenge use case includes the following boundary files that are higher-resolution versions of reference features in info.geoconnex.us:
We should tag every well in
wells.gpkg
with the state, place, county, and huc8 they are in. Probably have to do some st_intersect or whatever you like to do in python.Then, the following fields can be added to wells.gpkg:
state
with the relevant reference geoconnex pid for that state: https://geoconnex.us/ref/states/{FIPS} (NM FIPS is 35)place
with the relecant reference geoconnex pid for that place: https://geoconnex.us/ref/places/{GEOID}county
with county geoconnex pid : https://geoconnex.us/ref/counties/{5-digit FIPS or GEOID}huc8
with huc8 geoconnex pid: https://geoconnex.us/ref/hu08/{8-digit code} .Then, the semantics can be added to the
context:
part ofwdi.config.yml
:Restart pygeoapi and ready to go!