Overview

In some situations it is desirable to show previously submitted reports on a Logger Map. These can come from two places: a third-party data source, or from iShare’s internal report storage. These are still iShare Standard Layers, just configured to use report data.

Third-party report data

These layers are configured as per any other Standard Layer. The data in the layer could be used by a web application that is embedding Logger, or they could be used for purely informational purposes, e.g. to try an reduce duplicate reports.

The report data could to imported into iShare’s database using Workflow. Alternatively it could be present as spatial data in another PostgreSQL database available in Workflow Connections. In either case it can be configured as normal: Standard Layer Configuration.

iShare Reports

Reports made through the use of Logger ReportManager are stored as records in the public.at_incidents table in the iShareData database. To display these on the map requires a Layer to be created in the Map Source used by Logger.

Converting legacy reports

In cases where reports logged by iShare Logger - Classic are present in the the public.at_incidents table and need to be included in layers for Logger maps, the following steps should be followed:

1. Ensure that there exist Layers in the Map Source to be used in the Logger map for each layer referenced in the public.at_incidents layer column (at least for those records that are to be shown on the map)

2. Update each record so that layer names match those in the MapSource, e.g. :

   TODO: UPDATE layer example

3. Update each record so that it references the Map Source the layer is in, e.g. :

   TODO: UPDATE adding Map Source example

4. Create an iShare report layer, as above, in the Map Source, the SQL for layer would be something like: TODO: UPDATE adding Map Source example

   TODO: SELECT records updated in previous code example