search

sitmun / sitmun-viewer-app

A basic map viewer application for the SITMUN platform.
European Union Public License 1.2
1 stars 1 forks source link

Adjust Map Extent to Default Zoom Level and Point of Interest for Territories #66

Open fjlopez opened 1 month ago

fjlopez commented 1 month ago

Is your feature request related to a problem? Please describe.

The SITMUN administrator can currently associate a default zoom level to a territory or assign a center point that is distinct from the extent’s center. This center is often a point of interest within the territory, such as the administrative seat.

Describe the solution you’d like

When the description of an application has either a defaultZoomLevel or a pointOfInterest, the extent displayed in the map viewer should adjust to reflect these attributes. This allow a more accurate display of important territorial features such as the administrative seat.

Describe alternatives you’ve considered

One alternative could be to maintain the current functionality without automatic adjustments. However, this would require users to manually zoom and navigate to points of interest, which reduces efficiency.

Additional context

See support in the backend:

fjlopez commented 1 month ago

@RicardCots could you confirm the description?

RicardCots commented 1 month ago

Confirmed!

The only question I have is whether it is the Backoffice that performs the calculation and sends the correct boundig box to the client or whether the calculation should be done by the client.

fjlopez commented 1 month ago

At the moment, it’s unclear where this calculation should be handled. To move forward, there are two considerations:

  1. Backend Changes Required: We need to introduce an additional field in the backend to specify whether the Application should account for this bounding box calculation. This flag would guide when and how the calculation is performed.

  2. Bounding Box in Current Model: Our current model can store an additional bounding box as part of the relationship between a Territory and an Application. However, this relationship is not editable nor visible yet through the Application Form (or any other form). If we make this relationship visible and editable in the Administration Application, administrators could manually set the correct bounding box for the application, thereby eliminating the need for dynamic calculation.