Forest reserves: List of additional features required for the interactive map of each Forest Reserve record

[LeScruf]

This ticket is for each individual CFR.

For each CFR record, the interactive map needs:

• A layer control widget to control the visibility of the following layers (the list may grow):
• Old polygon - in grey
• Newly digitized polygon - Cutline - in red
  • Inter-protected area cutline - in green
  • Natural boundary - water - in blue
  • Natural boundary - ridge - in yellow
• Location of pillars / way points - Cardinal / corner pillars - red circle with an annotation of pillar and coordinates
  • Intermediate pillars - red dot with an annotation of pillar and coordinates

There should be form fields for each of these additional attributes.

• The form fields for this information should be organised as a time- and user-stamped data set.
• Multiple geospatial data sets can exist for any single CFR record - and should be treated as a time series. The idea being that each change to a CFR record can be seen and tracked through time. If a master polygon is uploaded and an error is discovered, then this master polygon is archived and then a new polygon can be uploaded. The associated layers would also need to be archived and the layers would need to be repeated.
• Each geospatial data set is to be viewable as a layer on the map - with the most recent line and point data viewable as default.
• All layers can be turned on and off at the layer control widget.
• The time-stamp and user ID that created the data set must be readily viewable.

A key security feature is that once uploaded, geospatial data cannot be removed from the system (without admin intervention). This ensures that data-tampering is more difficult to effect.

[ygoex]

This depends on https://github.com/National-Forestry-Authority/brms/issues/47 (upload and validation of polygons) and Geolayer type#96

[ygoex]

• When the user edits the content, it needs to be locked until they unlock it or save it. For this feature, we will need here some content lock feature/module like: https://www.drupal.org/project/content_lock
• When we edit, the first thing we would be doing is cloning the original one, and then we work on the copy. The original one always remains locked/untouched.
• The objective is to add meta information to segments of the polygon (how many kms of natural boundaries, disputed borders: this would be another polygon layer, annotate the elements of the map, add other polygons like sub-areas, click on a part of the map and add notes, label it, tag it, etc).