mapbender/coordinates-utility

Transform coordinates in different SRS. Navigate to coordinates on the map.

Deprecated

This repository is deprecated. Its functionality was integrated into the mapbender core repository in version 4.0. Propose any changes there., _(*1)

Old description: Mapbender coordinates utility module

Retrieve coordinates from the map, Zoom to a given map coordinate, _(*2)

Features

• Get coordinates by clicking on the map
• Transform coordinates to different SRS
• Navigate to selected coordinates on the map

Element configuration

Coordinates utility element supports the following configuration values:, _(*3)

<...>
  sidepane:
    class: Mapbender\CoordinatesUtilityBundle\Element\CoordinatesUtility
    addMapSrsList: true      # =default; offer all SRS configured on the Map element
    srsList: ['EPSG:25834']  # Add an additional SRS for transformation
    zoomlevel: 3             # zoom in closer than default on "Center map"

Customizing SRS titles

It is possible to change the displayed title of SRS choices by using an object form or a pipe separator. For the object form, use objects with "name" and "title" keys. The pipe separator form is "<srs name>|<custom title>"., _(*4)

<...>
    srsList: 
      # Rename using object form
      - {name: 'EPSG:25832', title: 'Renamed UTM32N'}
      # Rename using pipe separator form
      - 'EPSG:25834|Renamed UTM34N'
      # Use standard name
      - 'EPSG:25831'

NOTE: the backend form input only supports using pipe separator for SRS renaming. The explicit object format is legal in Yaml Application definitions only., _(*5)

Installation

The backend form srs suggestions will only work after registering the controller routes with the Symfony router., _(*6)

Mapbender Starter already does this., _(*7)

To do it manually, add the following to your app/config/routing.yml:, _(*8)

mapbender_coordinatesutilitybundle:
    resource: "@MapbenderCoordinatesUtilityBundle/Controller/"
    type: annotation

Note that the top key "mapbender_coordinatesutilitybundle" is technically irrelevant, but must be unique in your routing configuration., _(*9)