Alongside this, we should bring in a change to the results page so that the maps shown of individual entities are static - i.e. they cannot be panned or zoomed but only show the relevant area for the geometry. However, the map on the individual entity page should include the pan/zoom options. This should be less of a risk as each entity page will only be loading the one map, as opposed to the search results that are loading multiple.
Additionally, the lat/long strings of the map is being added to the URL. This is fairly non-sensical as it could apply to one of many maps. Whilst causing the maps to be static should fix this, we should doubly check that this bug does not occur after implementing that change.
Acceptance Criteria/Tests
Regardless of the URL used, the maps should display and not blank out
All entity maps shown on results pages should be static - i.e. no ability to pan or zoom.
The URL of the results page should not contain the lat/long coordinates - and these should not change based on interaction with the map.
Overview
@psd has raised a concern that when searching via a hard-coded route https://www.planning.data.gov.uk/entity/?geometry_reference=E07000096&limit=500&dataset=conservation-area, the maps displayed are very buggy and blank out. We should work out why this is happening. This does not occur when accessing the same data via the URL created when manually searching via the toolbar: https://www.planning.data.gov.uk/entity/?dataset=conservation-area&geometry_curie=statistical-geography%3AE07000096&entry_date_day=&entry_date_month=&entry_date_year=
Alongside this, we should bring in a change to the results page so that the maps shown of individual entities are static - i.e. they cannot be panned or zoomed but only show the relevant area for the geometry. However, the map on the individual entity page should include the pan/zoom options. This should be less of a risk as each entity page will only be loading the one map, as opposed to the search results that are loading multiple.
Additionally, the lat/long strings of the map is being added to the URL. This is fairly non-sensical as it could apply to one of many maps. Whilst causing the maps to be static should fix this, we should doubly check that this bug does not occur after implementing that change.
Acceptance Criteria/Tests