when a user searches for a place via search form, this will be interpreted as a filter on passage.text.place (e.g. /api/stelle/?text__ort=3).
however, on the map view, the place will not be interpreted as a filter (i.e. not/api/spatialcoverage/?stelle__text__ort=3), but will dispatch a separate request to get geojson data for that place. is this intentional?
the special casing of place queries only makes sense in a place-details sidepanel to show place location. otherwise, place should be treated as a filter on passages, like on other screens.
when a user searches for a place via search form, this will be interpreted as a filter on passage.text.place (e.g.
/api/stelle/?text__ort=3
).however, on the map view, the place will not be interpreted as a filter (i.e. not
/api/spatialcoverage/?stelle__text__ort=3
), but will dispatch a separate request to get geojson data for that place. is this intentional?