mesowx/MesoPy

timeseries_obs issue with Nevada stations?

ajoros opened this issue · 3 comments

ajoros commented

I am getting data for the CA/Yuba County timeseries_obs call, but I am getting nothing when I do the same for Washoe County in NV? There are many stations in Washoe County (specifically here in Reno) that contain the wind_speed parameter. I looked on the MESOWEST website too and the stations in Washoe County seem functional and returning data.

Run these two lines and you'll see what I'm talking about:

ts = m.timeseries_obs(start='201508100000',end='201510120000',state='NV',county='Washoe', vars='wind_speed')
pp.pprint(ts)

ts = m.timeseries_obs(start='201508100000',end='201510120000',state='CA',county='Yuba',vars='wind_speed')
pp.pprint(ts)

Deleted user commented

@ajoros give us a bit to look in to it.

ajoros commented

No worries, just wanted to bring it to your attention.
On Mon, Oct 19, 2015 at 11:26 AM Joshua Clark notifications@github.com
wrote:

@ajoros https://github.com/ajoros give us a bit to look in to it.

—
Reply to this email directly or view it on GitHub
#15 (comment).

Deleted user commented

@ajoros, We looked at your query for 103 stations in Washoe County for the time period specified and it seems your query exceeds our API limit of 100,000 station-hours. Your query was for 150,000 station-hours of data.

From the MesoWest documentation:

Restrictions

There is currently a hard-coded limit of 100,000 station-hours for most queries. Requests for larger amounts of data will return an error and no data. Excessive usage of the API from any particular user will be monitored and blocked at the either the token or API key level.

This is calculated as number-of-hours x number-of-stations.

Right now, you will need to reduce the amount of hours you are requesting by splitting your query in to two separate calls.

However, the API should have warned you of this by returning an error which would have been raised as an exception in MesoPy. It seems the API detected that the query was too large but failed to let you know, our bad! I'll get this fixed as soon as possible.

Closing this because it's an API issue