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
A user may want to know where data exist before performing a search. At present, a user can go to the rgd/statistics view to see a heatmap of all the available data.
I propose adding a widget in the GeoJS map (bottom left corner) in the base search map (in django-rgd/rgd/templates/rgd/_include/search_map.html) that is essentially a checkbox to show a heatmap of available data.
This will require an async call to an endpoint in RGD to gather the points for this heatmap (note that the current rgd/statistics view adds these points in the context of the page). The new widget would have a callback that is essentially the JS code in django-rgd/rgd/templates/rgd/statistics.html that uses a new endpoint to fetch those points.
To implement the new endpoint for gathering the heatmap, we should add a new api/rgd/statistics endpoint that is essentially the same as StatisticsView.get_context_data() but in RetrieveAPIView form.
Please wait until #539 lands to follow the conventions laid out there (basically just subclassing BaseRestViewMixin and RetrieveAPIView)
After all of this, we should refactor the StatisticsView view and its template to utilize these changes
The text was updated successfully, but these errors were encountered:
A user may want to know where data exist before performing a search. At present, a user can go to the
rgd/statistics
view to see a heatmap of all the available data.I propose adding a widget in the GeoJS map (bottom left corner) in the base search map (in
django-rgd/rgd/templates/rgd/_include/search_map.html
) that is essentially a checkbox to show a heatmap of available data.This will require an async call to an endpoint in RGD to gather the points for this heatmap (note that the current
rgd/statistics
view adds these points in the context of the page). The new widget would have a callback that is essentially the JS code indjango-rgd/rgd/templates/rgd/statistics.html
that uses a new endpoint to fetch those points.To implement the new endpoint for gathering the heatmap, we should add a new
api/rgd/statistics
endpoint that is essentially the same asStatisticsView.get_context_data()
but inRetrieveAPIView
form.Please wait until #539 lands to follow the conventions laid out there (basically just subclassing
BaseRestViewMixin
andRetrieveAPIView
)After all of this, we should refactor the
StatisticsView
view and its template to utilize these changesThe text was updated successfully, but these errors were encountered: