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 apps lets users explore temperatures (and in the future other parameters) for a point location.
In reality, the data we currently host is on a 0.25x0.25 degree regular global grid (resolution >=28 km), so temperatures will for example not account for urban heat island effects or effects of local topography.
Can we help users somehow understand these limitations? Do we need to?
Explain limitations
As a first-off, we added a technical explanation to the parameter description in
Another approach to manager the users' expectations would be to restrict the zoom. At least for temporally aggregated temperature, the data does not vary a lot on a grid cell scale anyways and the interpolation for the video at mobile quality blurs the data further.
The text was updated successfully, but these errors were encountered:
The apps lets users explore temperatures (and in the future other parameters) for a point location.
In reality, the data we currently host is on a 0.25x0.25 degree regular global grid (resolution >=28 km), so temperatures will for example not account for urban heat island effects or effects of local topography.
Can we help users somehow understand these limitations? Do we need to?
Explain limitations
As a first-off, we added a technical explanation to the parameter description in
Show with marker
Other considerations were to make the marker indicate the actual scale of data
Show grid
or to add a grid overlay e.g. as grid_lines.json and snap to grid cell centers or so - we are exploring that here:
Restrict zoom
Another approach to manager the users' expectations would be to restrict the zoom. At least for temporally aggregated temperature, the data does not vary a lot on a grid cell scale anyways and the interpolation for the video at mobile quality blurs the data further.
The text was updated successfully, but these errors were encountered: