As more folks are starting to come on board, they are going to need an "easy" way to identify which reference features to use. For NHDPlusV2 comids/reachcodes, the NLDI point lookup endpoint may be suitable. For cataloging features, mainstems, and reference gages, some kind of other lookup will be necessary.
One option is to have a web map, similar to the shiny app. But this requires a lot of manual looking around for each and every feature of interest. Another option I was thinking would be to have a pygeoapi process running on reference.geoconnex.us, where you could programmatically supply a lat/lon, and get a response of the members of every reference collection within a small bbox of the supplied lat/long.
As more folks are starting to come on board, they are going to need an "easy" way to identify which reference features to use. For NHDPlusV2 comids/reachcodes, the NLDI point lookup endpoint may be suitable. For cataloging features, mainstems, and reference gages, some kind of other lookup will be necessary.
One option is to have a web map, similar to the shiny app. But this requires a lot of manual looking around for each and every feature of interest. Another option I was thinking would be to have a pygeoapi process running on reference.geoconnex.us, where you could programmatically supply a lat/lon, and get a response of the members of every reference collection within a small bbox of the supplied lat/long.
e.g.
https://reference.geoconnex.us/processes/lookup?lon=x&lat=y
might return something like:
We could even possible have a https://reference.geoconnex.us/processes/lookup/map?lon=x&lat=y that would give you something like this