-
Notifications
You must be signed in to change notification settings - Fork 1
Support additional geometry types, refactor geometry handling #382
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
Conversation
| import org.slf4j.LoggerFactory; | ||
|
|
||
| // TODO: how to handle name collisions for id or geometry | ||
| // TODO: how to handle name collisions for id, geometry, or place |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A new Todo was discovered. If it is not a priority right now,consider marking it for later attention.
TODO: how to handle name collisions for id, geometry, or place
- Ignore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
revisit when extending CRUD to JSON-FG
|
@cportele |
... after the unit test has been migrated
Using NaN is the typical way to encode POINT EMPTY in WKB (see, e.g., GeoPackage), so we will use it also for GML. NaN is a valid double value in XML Schema.
there is probably not much benefit by converting the classes to visitors. It just adds internal complexity.
Tests already exist; move tests to xtraplatform-geometries to the encoder/decoder
The changes in #392 did not fully handle the new `onGeometry()` event introduced in #382. In `FeatureTokenStatsCollector` the event was not passed downstream. Closes ldproxy/ldproxy#1519.
No description provided.