Additional capabilities required for completeness

[jerstlouis]

Definitely missing to add

• geometry selection (property) -- discussion: accessing members / array elements for rings, points to create new geometry e.g., first and last points
• Perpendicular offset: geometry manipulation function? PostGIS st_offsetCurve?
• Centroid function
• ContrastEnhancement
• Hue rotation / Saturation / Brightness (Gamma?)
• vis.feature.pass
• size of graphics that repeats -> border between repeat item (padding)
• Extrusion is missing
• Default Values: Move to core
• Gradient control (linear / radial, extent)
• Math functions (cos, sin, atan, sqrt, log...)
• Symbolizing Coverages with Markers (graphics) e.g., symbolizing Eastward and Northward wind speed with oriented arrows
• Clarify lines labeling -- separate "shield" property for road shields?

To discuss

• vertical / horizontal hatches ?
• arrow caps?
• substitute(): parameter to replace occurrences x..y?
• Images outline? (Merge Font/Shape outline and move to Graphic?)
• Look at QGIS 3D Symbology: https://docs.qgis.org/3.28/en/docs/user_manual/style_library/3d_symbols.html
• Dash / hatch / stipple offsets necessary?
• Interpolate function? (probably not needed: can achieve with math functions)

[maxcollombin]

Trying to go through SLD/SE...

What about:

• [x] Filter -- > ElseFilter (default rule outside nested rules, overiding rule concept)

• [x] Gap, InitialGap (pattern stroke): see link1, link2, link3

• [x] OverlapBehavior for Coverage styling (LATEST_ON_TOP, EARLIEST_ON_TOP, AVERAGE, RANDOM) (<> viz.feature.pass) -- > zOrder & sortBy? sortBy can also controls the cloudcover; not client but server side?: see link -- > should be moved to clause_18_functions as an aggregatefunction such as colorChannels.r: Aggregate(red, average, ['time'])

• [x] ContrastEnhancement for Coverage styling: Normalize, Histogram, or GammaValue (link1,link2, link3,link4,link5)

• [x] Hill shading (ShadedRelief in SE) Consider brightness only (multiply blend mode)

• [x] During the 126th OGC Member Meeting, someone also suggests to add polyhedron styling calpabilities (like edges and faces color selection in CesiumJS).

• [x] We could also add the voronoi diagram and the concave hull in the geometry manipulation functions. (not in OGC Simple Feature Access); Voronoi diagram should be considered as a proper rc (to be discussed).

[maxcollombin]

Define proper clause/class (one for points, another for lines & polygons) for raster to vector (representation of coverages with markers, lines, etc.) Something like "Rendering Transformation"?

NOTE: Instead of the coverage to feature transformation, the following properties: contour field, contour distance & contour start should be added.

[maxcollombin]

Backlog

• [x] geometry selection (property) -- discussion: accessing members / array elements for rings, points to create new geometry e.g., first and last points: see link1, link2
• [x] Perpendicular offset: geometry manipulation function? PostGIS st_offsetCurve?: see link
• [x] Centroid function: see link
• [x] Hue rotation / Saturation / Brightness (Gamma?): see link
• [x] size of graphics that repeats -> border between repeat item (padding)
• [x] Extrusion is missing: see link1, link2, link3
• [x] Default Values: Move to core: see link
• [x] Gradient control (linear / radial, extent): see link1, link2, link3
• [x] Math functions (cos, sin, atan, sqrt, log...): see link1, link2
• [x] Clarify lines labeling -- separate "shield" property for road shields? (this should be covered by the class "Pattern Strokes")
• [x] vertical / horizontal hatches ? (this should be covered by the class "Pattern Strokes")
• [x] arrow caps? (it doesn't seems to be relevant and shouldn't be considered)
• [x] Images outline? (Merge Font/Shape outline and move to Graphic?): see link
• [x] Dash / hatch / stipple offsets necessary?: see link1, link2
• [x] Interpolate function? (probably not needed: can achieve with math functions; exists in SE): see link
• [x] Should a Recoding class be defined (as in SE; proposed in the associated PR; can be removed): Link
• [x] Filter -- > ElseFilter
• [x] Gap, InitialGap
• [x] OverlapBehavior for Coverage styling (LATEST_ON_TOP, EARLIEST_ON_TOP, AVERAGE, RANDOM) -- > should be moved to clause_18_functions
• [x] ContrastEnhancement for Coverage styling (Normalize, Histogram, or GammaValue)
• [x] Symbolizing Coverages with Markers (graphics) e.g., symbolizing Eastward and Northward wind speed with oriented arrows Link1, Link2

NOTE: to be taken over from here⬇:

• [x] Hill shading (ShadedRelief in SE) Consider brightness only (multiply blend mode); This is equivalent to the opacityMap parameter
• [x] Add concave hull to in the geometry manipulation functions. (not in OGC Simple Feature Access): see link
• [x] Voronoi diagram should be considered as a proper conformance class (to be discussed).: see link
• [x] vis.feature.pass (cf issue #20)(mutliple symbolizers vs mutliple rules vs mutliple featuretypestyle; which relation with z-order? ): see link
• [x] Define proper conformance classes (one for points, another for lines & polygons) for raster to vector transformation (representation of coverages with markers, lines, etc.) see this reference
• [ ] 3D and consideration on AR/VR (in the same rc)
• [ ] Polyhedron styling calpabilities (like edges and faces color selection in CesiumJS).

To be partially considered:

• [ ] Look at QGIS 3D Symbology: https://docs.qgis.org/3.28/en/docs/user_manual/style_library/3d_symbols.html

Not to be considered:

• [ ] substitute(): parameter to replace occurrences x..y?
• [ ] Composite and blending modes (see viz.pass or could be included in an extension)

[maxcollombin]

Should we also include rc on AR/VR and Big Geospatial Data in relation to the discussions at the Portayal Workshop (ICA & OGC) at the 126th Member Meeting?

[chris-little]

@maxcollombin I definitely think so. In the past in the Portrayal sessions, i raised those use cases. I have never been convinced by the approach of '3D is just an extension of 2D'. By exploring 3/4D, some concepts will be seen to be too narrow or even wrong. For example

1. In a stereo display, labels (subtitles in the movies) may be on a different focal plane.
2. Gaps in roads/rail/rivers at bridges do not exist.
3. Markers of a 2D point like feature may be a 4D animated object (little 3D animations of lightning or snow falling are very common on TV weather forecasts).

[maxcollombin]

Consider also the following classes/ressources:

• [ ] Composite and blending modes (see viz.pass or could be included in an extension)

• [ ] Simplification (Douglas-Peucker, Visvalingam / effective area, Visvalingam / weighted area: could be defined as a custom function but should'nt be integrated in the spec; also a part of OGC API Features

• [ ] 3D

• [ ] AR/VR cf @chris-little comment's 1st bullet point

[maxcollombin]

Thanks for you comment @chris-little

1. In a stereo display, labels (subtitles in the movies) may be on a different focal plane.

This should definitely be considered

2. Gaps in roads/rail/rivers at bridges do not exist.

We are not sure to perfectly understand your comment. Could you be more explicit?

3. Markers of a 2D point like feature may be a 4D animated object (little 3D animations of lightning or snow falling are very common on TV weather forecasts).

This should also be added and considered with issues #3 and #7

[chris-little]

Gaps in roads/rail/rivers at bridges do not exist. A lot of styling for 2D maps fusses over bridges - e.g. red road crosses over black railway - Ah we can set z order and over-painting mode in the graphics display - oh no, we can't as black railway then crosses over red road. So we split the road and railway into segments, etc.... Or am I being too simplistic?

[sumitsane]

Can we have additional class requirement for shadow (vector symbol)?

[jerstlouis]

Fallback values for complex expressions.

[maxcollombin]

sysId extension that reflects the percentage of the position on the LineString https://docs.qgis.org/3.34/en/docs/user_manual/style_library/symbol_selector.html#id5