Each Layer ETL pulls data from a source and transforms it into a valid GeoJSON Feature. Properties on this GeoJSON Feature are unknown and passed through to Node-CoT which picks up the properties it needs to create a CoT and ignores the remainder.
As such the frontend UI does not know what the data passing through looks like and cannot provide any way for the user to map Properties into Node-CoT fields.
One prime example would be the Callsign or Remarks field. Without being able to map these fields, the ETL is unable to pick sensible defaults.
This PR introduces a JSON Schema that can be optionally stored alongside a layer to provide the UI hints to allow the user to sensibly transform the input data to Node-COT properties.
Context
Each Layer ETL pulls data from a source and transforms it into a valid GeoJSON Feature. Properties on this GeoJSON Feature are unknown and passed through to Node-CoT which picks up the properties it needs to create a CoT and ignores the remainder.
As such the frontend UI does not know what the data passing through looks like and cannot provide any way for the user to map Properties into Node-CoT fields.
One prime example would be the
CallsignorRemarksfield. Without being able to map these fields, the ETL is unable to pick sensible defaults.This PR introduces a JSON Schema that can be optionally stored alongside a layer to provide the UI hints to allow the user to sensibly transform the input data to Node-COT properties.
https://github.com/openaddresses/esri-dump/pull/39 was the precursor to this work
cc/ @bs-in-co