Public map

A public map enables the creation of a secure data viewer that is publicly accessible (no login required).

Use case

Map viewer of the Zielonka Forest Inter-Municipal Association

Employees of the Association work in the System (via a map viewer and in QGIS) updating data on the mileage and commissioning dates of individual sections of the sewer network.

The need was to create an easy-to-use viewer for residents to find out if and when the sewer system will be built next to their plot.

This map is a very effective solution because residents themselves can easily and quickly check the date on which the sewerage system in their area will be commissioned.

How does it work?

The public map is a de facto separate application that can be installed on another server. It has its own internal Administration Panel – available at the address youradresspublicmapadress/admin, to which the System administrator can log in and configure:

  1. Logo, site icon
  2. Application name
  3. Map view (default range)
  4. A set of layers from the System to be displayed on the public map.
  5. The attributes of a layer, in the public map, are displayed according to the configuration of the object card in the parent application.
  6. The layer attributes in the public map are only the displayed values from the parent application and are in no way further formatted, mapped, etc.
  7. The satellite application does not support change history, attachment notes, or relationships.

Layers come from the System (main application) – If you need a layer differently or an object card with fewer fields, then go back to the main application and prepare layers dedicated to the satellite application with the public map.

Once you have configured and saved your changes, Public Map retrieves the data from the System and creates a local copy, so there is no communication with the System when using Public Map. This avoids problems such as DDoS.

To update the layers published in the Public Map, the layer must be deleted in the administration panel and added again. For the security reasons outlined above, data is saved and served internally. The public map does not query the parent application for the status of layers or the number of new elements that may have appeared in the source. The state of a layer displayed in the public map is equivalent to the moment of adding it to the administration panel of the public map.

Was this helpful?