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
The current webapp hardcodes the data file to Seldovia.json. Instead, need to refactor the webapp to retrieve the data file from the /wxapp/getwxvar service as described in issue #4. Currently, this service is called without location parameters (lat and lon) on lines 95-99 of wxgrid.js, which depends on the hardcoded Seldovia response. In the refactor, we might enable several ways to pick a location:
get lat/lon parameters from the application query URI
this would be the main mechanism if the app is linked to a separate map with a clickable UI
URI format would be: /static/index.html?vlat=58.3&vlong=-134.4
those coordinates would be passed to /wxapp/getwxvar?vlat=58.3&vlong=-134.4 to get the json file to be displayed
optionally enter coordinates in new editable text boxes in the web form
enter a city name, which would be indexed against a canonical location and returned
The text was updated successfully, but these errors were encountered:
However, loading the app without the lat/lon params results in a blank screen and a console error. Maybe it would be better to load Seldovia or some default if the params are not provided.
The current webapp hardcodes the data file to Seldovia.json. Instead, need to refactor the webapp to retrieve the data file from the
/wxapp/getwxvar
service as described in issue #4. Currently, this service is called without location parameters (lat and lon) on lines 95-99 ofwxgrid.js
, which depends on the hardcoded Seldovia response. In the refactor, we might enable several ways to pick a location:/static/index.html?vlat=58.3&vlong=-134.4
/wxapp/getwxvar?vlat=58.3&vlong=-134.4
to get the json file to be displayedThe text was updated successfully, but these errors were encountered: