-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional capabilities required for completeness #45
Comments
Trying to go through SLD/SE... What about:
|
Define proper clause/class (one for points, another for lines & polygons) for raster to vector (representation of coverages with markers, lines, etc.) NOTE: Instead of the coverage to feature transformation, the following properties: contour field, contour distance & contour start should be added. |
Backlog
NOTE: to be taken over from here⬇:
To be partially considered:
Not to be considered:
|
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? |
@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
|
Consider also the following classes/ressources:
|
Thanks for you comment @chris-little
This should definitely be considered
We are not sure to perfectly understand your comment. Could you be more explicit?
This should also be added and considered with issues #3 and #7 |
|
Can we have additional class requirement for shadow (vector symbol)? |
Fallback values for complex expressions. |
sysId extension that reflects the percentage of the position on the LineString |
Definitely missing to add
To discuss
The text was updated successfully, but these errors were encountered: