As an end-user I would like to have a spatial representation on the landing page so that I can determine relevance.
Not sure what the user story should be here. Maybe we can require the landing page to have a full-blown OpenLayer map application (in this case, this pushes some config on the admin side to decide what layers should be provided in addition to the feature itself).
As a user, I expect the geometry shown on the map is easy to recognize (not mixed with other feature is such a way I can't identify the one in context)
Where will the spatial information be stored?
The catalog contains the spatial representation (à la GeoSPARQL)
The HTML MIR is smart enough to fetch the geometry from one of the DIR (which in turn implies that HTML has some magic other MIR representations don't have, ie, spatial object is explicit in HTML and implicit in other formats as the user must figure how to get the same spatial object than the HTML)
As an end-user I would like to have a spatial representation on the landing page so that I can determine relevance.
Not sure what the user story should be here. Maybe we can require the landing page to have a full-blown OpenLayer map application (in this case, this pushes some config on the admin side to decide what layers should be provided in addition to the feature itself).
As a user, I expect the geometry shown on the map is easy to recognize (not mixed with other feature is such a way I can't identify the one in context)
Where will the spatial information be stored?