You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we went through the conformance classes to check that none were missing. Some were missing. For example: Geometry Selection conformance class in relation to the possibility in a symbolizer to access the underlying geometry to manipulate it (e.g. transforming a polygon into a point with ST-Centroid to draw a proportional symbol). E.g. use case Proportional symbol #20
following the idea presented at the opening plenary, we are indeed moving towards a version 2.0 "Styles & Symbology Model & Encodings" gathering SymCore and the conceptual/logical definitions of the concrete extensions to be packaged in a Part 1
we started the documentation in github of this V2, structured as follows: ...
in parallel we worked on relevant 9 use cases to test the functional coverage of the proposed model and to relate them to the conformance classes we have
in doing so we tested existing encodings (e.g. GeoCSS) to start imagining the "natural" encoding that would be also documented with the Part 1
The text was updated successfully, but these errors were encountered:
we went through the conformance classes to check that none were missing. Some were missing. For example: Geometry Selection conformance class in relation to the possibility in a symbolizer to access the underlying geometry to manipulate it (e.g. transforming a polygon into a point with ST-Centroid to draw a proportional symbol). E.g. use case Proportional symbol #20
following the idea presented at the opening plenary, we are indeed moving towards a version 2.0 "Styles & Symbology Model & Encodings" gathering SymCore and the conceptual/logical definitions of the concrete extensions to be packaged in a Part 1
we started the documentation in github of this V2, structured as follows: ...
in parallel we worked on relevant 9 use cases to test the functional coverage of the proposed model and to relate them to the conformance classes we have
in doing so we tested existing encodings (e.g. GeoCSS) to start imagining the "natural" encoding that would be also documented with the Part 1
The text was updated successfully, but these errors were encountered: