Intersection Geometry Vocabulary #535
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Consensus in 7/24 SWG Meeting is to look at a convention for using provenance to describe that a geometry was derived from an intersection rather than defining new subclasses of geometry. |
|
Nick to add in a proposal for the provenance |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #239
This pull request wants to collect the necessary changes for describing intersection geometries and their properties which were requested in #239
Idea Sketch:
New SubClass of Geometry: CompoundGeometry
New SubClass of CompoundGeometry: IntersectionGeometry
CompoundGeometry geo;hasPart Geometry to describe parts of Compound Geometries
How to describe constraints of Intersection Features/Geometries using SHACL?
To Discuss: intersection features should be consistent with ISO19017 topology complexes