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
take a look a the notebook in this repo, its got a quick overview. Please share with whomever and funnel feedback here, modify the json into a structure you might prefer, comment on further args that could be used, etc.
I'd welcome any feedback whatsoever,
Thanks
The text was updated successfully, but these errors were encountered:
@beautah thanks for asking for our input on this! Sorry for the delay.
This looks great. Everything that we use is in those responses and I like having the units accessible in the data response.
In the getData endpoint, returning a dictionary of element code to the underlying data instead of a list of dictionaries with the element code as an entry in the dictionaries might make things mildly quicker for my use case, but the gain is trivial so I could go either way.
Any thoughts for what the station search endpoint would look like?
I mocked to endpoint returns here:
Here for data getData
And here for station meta data getMeta
You can examine the proposed args here (under the dev namespace), for each method, I'd imagine you could guess what the search args would be for the endpoint return I mocked up, but if not I could provide you with the url that would result in those json objects. feel free to ask more questions.
@jomey @micahjohnson150 @micah-prime
take a look a the notebook in this repo, its got a quick overview. Please share with whomever and funnel feedback here, modify the json into a structure you might prefer, comment on further args that could be used, etc.
I'd welcome any feedback whatsoever,
Thanks
The text was updated successfully, but these errors were encountered: