clarifications on GeometryCollection #89
Merged
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
Addresses part of #71
|
Meeting 2023-07-10: There was no new feedback, so we decided to not introduce a new geometry collection for all geometry object types since geometry collections are very rarely used as geometries of feature types. @cportele will add an explanation to the document. If it turns out there is a need for such a geometry type, it can be added in the future. |
pvretano
approved these changes
Aug 21, 2023
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.
All geometries in a GeometryCollection must be in the same CRS. This addresses part of #71.
Open topic: should there also be a JSON-FG GeometryCollection that includes additional JSON-FG geometry types? I will make this a draft PR until this is resolved.