Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forecast service not respecting dates and observables #1

Open
benjamminf opened this issue Jan 12, 2017 · 1 comment
Open

Forecast service not respecting dates and observables #1

benjamminf opened this issue Jan 12, 2017 · 1 comment

Comments

@benjamminf
Copy link

benjamminf commented Jan 12, 2017

The forecast service seems to ignore any observables and to/from date parameters, and return a fixed set of observable data over a fixed date range. The only parameters that seem to affect the results is the selection type (with lat/lon's) and the HRRRX flag.

For example, the following two URI's return the same data:

  • https://firemap.sdsc.edu:5443/forecast?hrrrx=true&selection=withinRadius&lat=33.100492&lon=-116.3013267&radius=2&observable=wind_speed&from=2016-10-24T07:20:14.369271-07:00&to=2016-10-25T10:20:14.369271-07:00
  • https://firemap.sdsc.edu:5443/forecast?hrrrx=true&selection=withinRadius&lat=33.100492&lon=-116.3013267&radius=2&observable=temperature
@crawld
Copy link
Member

crawld commented Jan 12, 2017

The issue is that Pylaski silently ignores unexpected parameters when it should return an error. reqparse cannot do validation and is no longer supported, so need to find a replacement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants