You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Barebones example assigns a new methodID for each valueID in GetValues responses. This means if I download 2600 values, I get 2600 method descriptions, making for a very bulky WaterML file. The unique method descriptions should be compiled either in memory or as an additional table in the example (or maybe removed from the example to keep it simple). It would be cool if there was a SQLAlchemy way to do that in memory, but I’m not familiar with it. It’s like SELECT DISTINCT METHOD FROM DATAVALUES…AND PUT IT IN THIS DICTIONARY.
The text was updated successfully, but these errors were encountered:
Barebones example assigns a new methodID for each valueID in GetValues responses. This means if I download 2600 values, I get 2600 method descriptions, making for a very bulky WaterML file. The unique method descriptions should be compiled either in memory or as an additional table in the example (or maybe removed from the example to keep it simple). It would be cool if there was a SQLAlchemy way to do that in memory, but I’m not familiar with it. It’s like SELECT DISTINCT METHOD FROM DATAVALUES…AND PUT IT IN THIS DICTIONARY.
The text was updated successfully, but these errors were encountered: