-
Notifications
You must be signed in to change notification settings - Fork 5
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
Testing feature and geometry equality #188
Labels
Comments
navispatial
added
enhancement
New feature or request
🌐 geobase
Related to the code package "geobase"
labels
Aug 12, 2023
navispatial
added a commit
that referenced
this issue
Sep 3, 2023
navispatial
added a commit
that referenced
this issue
Sep 3, 2023
…als3D of geometries and features #188
navispatial
added a commit
that referenced
this issue
Sep 3, 2023
navispatial
added a commit
that referenced
this issue
Sep 3, 2023
…tureCollection and GeometryCollection #188
navispatial
added a commit
that referenced
this issue
Sep 3, 2023
navispatial
added a commit
that referenced
this issue
Sep 3, 2023
navispatial
added a commit
that referenced
this issue
Sep 10, 2023
Closed
Implemented in geobase 0.6.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
See #146 that contained
equalsCoords
,equals2D
andequals3D
methods for feature and geometry classes, and partially also different coordinate position and position arrays classes.Position
/Geographic
/Projected
/PositionCoords
andBox /
GeoBox/
ProjBox/
BoxCoordsalso has the standard equality operator and hash functions. For example
Geographicand
Projectedimplement using static functions provided by
Position`:Using equality operator for position arrays and large coordinate data (including also geometries and features that contain coordinate data) is potentially a performance issue if need to loop through large about of positions and coordinate values.
Because of this, there are separate
equalsCoords
,equals2D
andequals3D
. Using this it's possible to test geometries.But
Feature
(andFeatureCollection
) may contain also other data:Feature
FeatureCollection
Testing these is possible by testing data got from getters, but some easier method might be handy.
For example
Feature
already has:There could be also following test methods for
Feature
:Maybe some other too, to be defined...
The text was updated successfully, but these errors were encountered: