Should we make an NHD & WBD PostGIS dataset? #354
-
In relationship to #347 a question that comes up ALL the time, is how should we filter by FCODE? To really know how to answer this we would really like the context of what is the distribution and occurrence of those FCODEs everywhere (i.e. entire NHD dataset) or somewhere specific (e.g. ALL HUC 2s of Mississippi or some specific HUC 12). @philipbaileynar this screams to me we should be asking those questions as queries. However, we can't currently do that, because we don't have the data all in one place at our fingerprints. Why? Not because it doesn't exist, but because it is too big and cumbersome. Can and should we make a PostGIS database of these? A potential downside is that that PostGIS database may not reflect rolling and occasional updates USGS makes to that dataset. I don't care. We can still construct ChannelArea projects off of a API call to the latest. However, for this (i.e. informed context), the slightly out of date will more than suffice. Thoughts? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Answer is YES. See: https://github.com/Riverscapes/RiverscapesData/issues/11 for request. @philipbaileynar and I discussed, and answer is YES. We'll pilot with a HUC 6 or something and then test. |
Beta Was this translation helpful? Give feedback.
Answer is YES. See: Riverscapes/RiverscapesData#11 for request.
@philipbaileynar and I discussed, and answer is YES. We'll pilot with a HUC 6 or something and then test.