Making stid mandatory had good intentions...it prevented users from requesting the full set of data and killing MesoWest servers. However, forcing users to provide a stid limits their request options as the API will search for stid first and ignore other geographic parameters like state, county, bbox, etc.
Instead, users will have to provide at least one of the geographic constraints 'stid', 'state', 'country', 'county', 'radius', 'bbox', 'cwa', 'nwsfirezone', 'gacc', or 'subgacc'. If at least one of these is passed, everything's gravy, otherwise an error is thrown.
I plan to fix this immediately (well I already have), but I'll push it in the morning when I have time to change all the docs to reflect stid as not being mandatory.
Making stid mandatory had good intentions...it prevented users from requesting the full set of data and killing MesoWest servers. However, forcing users to provide a stid limits their request options as the API will search for stid first and ignore other geographic parameters like state, county, bbox, etc.
Instead, users will have to provide at least one of the geographic constraints 'stid', 'state', 'country', 'county', 'radius', 'bbox', 'cwa', 'nwsfirezone', 'gacc', or 'subgacc'. If at least one of these is passed, everything's gravy, otherwise an error is thrown.
I plan to fix this immediately (well I already have), but I'll push it in the morning when I have time to change all the docs to reflect stid as not being mandatory.