Trying to work with the get_nhd function today, and I've run into the issue that the data set is just massive, especially when your template is a union of multiple HUC6 watersheds. One way to speed this up would be to allow for more fine grained queries on the server-side.
You could add function parameters like fcode and gnis_name. This would - I think - allow a user to, for example, retrieve a MULTILINE of the Colorado River. Or, a where parameter that takes a list in the httr fashion. Or, both? Though, this might require some changes to your esri functions. (BTW, are you familiar with the USGS SPEC-X website? It's pretty clean and minimal, and provides data dictionaries for all its data sets. Here is the page for the NHD.)
A minimally invasive alternative would be a layers argument, but even just taking one layer can be time-consuming for a large template.
If you think this functionality would be worth implementing, I'd be happy to help with it.
Cheers,
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4