We have multiple types of transforms, we could consolidate into a pluggable, data-configurable presentation paradigm.
Where we have "transforms" we could have a set of X where X is user defined characterisation of execution types:
- validations
- transforms
- query executions
- assertion tests
- [user defined]
(and these can be chained)
The general case is that the outputs of these steps need to be visualised.
Transforms of various forms geospatial objects -> common visualised geometry forms is an obvious priority for OGC.
Here is an example of an (open source transformer with a visualisable output)
https://github.com/icsm-au/3d-csdm-profile-wa/blob/main/.github/workflows/pancadastre.yaml
this does validation and builds a GeoJSON object as a postprocess - e.g.
https://github.com/icsm-au/3d-csdm-profile-wa/blob/main/build/tests/profiles/wa/extended-example.jsonld-geojson.json
it would be great is this was a transformer opengeospatial/bblocks-postprocess#63 that registers the output so it can be integrated in the viewer - but also pushed as a resource to the Rainbow node so users can see the example there before diving into the Building blocks to understand or reuse the mechanisms and specs.
We have multiple types of transforms, we could consolidate into a pluggable, data-configurable presentation paradigm.
Where we have "transforms" we could have a set of X where X is user defined characterisation of execution types:
(and these can be chained)
The general case is that the outputs of these steps need to be visualised.
Transforms of various forms geospatial objects -> common visualised geometry forms is an obvious priority for OGC.
Here is an example of an (open source transformer with a visualisable output)
https://github.com/icsm-au/3d-csdm-profile-wa/blob/main/.github/workflows/pancadastre.yaml
this does validation and builds a GeoJSON object as a postprocess - e.g.
https://github.com/icsm-au/3d-csdm-profile-wa/blob/main/build/tests/profiles/wa/extended-example.jsonld-geojson.json
it would be great is this was a transformer opengeospatial/bblocks-postprocess#63 that registers the output so it can be integrated in the viewer - but also pushed as a resource to the Rainbow node so users can see the example there before diving into the Building blocks to understand or reuse the mechanisms and specs.