Thanks for commenting Martin.
If we did that, we'd have to use instanceof because GeometryCollection
extends Geometry, which is icky.
I would really prefer that you fix this in JTS, even if it means
creating yet another equals method.
On 2013-08-20 03:12, Martin Davis wrote:
Not a bug in JTS. JTS Geometry.equals() computes *topological*
equality, not exact representation equality. The method is
unfortunately named due to historical accident.
You may wish to use equalsExact - although this does not check for Z
values. Other alternative is to write your own equalsExact3D.
On Monday, August 19, 2013 6:47:38 AM UTC-7, Noel Grandin wrote:
No, that's a bug in the com.vividsolutions.jts.geom.Geometry#equals
method, which the JTS guys will need to fix.
Let us know when they have a fixed build available.
On 2013-08-19 14:46, Nicolas Fortin (OrbisGIS) wrote:
> I wrote a unit test:
>
https://github.com/nicolas-f/h2database/commit/ea22bd7532150a17a1e92b009a98bf389a7f3f7f#L1R533
<https://github.com/nicolas-f/h2database/commit/ea22bd7532150a17a1e92b009a98bf389a7f3f7f#L1R533>
>
> If you take two geometries A "POLYGON ((67 13, 67 18, 59 18, 59
13, 67
> 13)) and B "POLYGON ((67 13 , 67 18 5, 59 18, 59 13, 67 13 ))"
>
> The result of A.equal(B) is true.. Then the cache system of
Value will
> keep only A and garbage B. The only way to fix this issue is to
do a
> binary comparison in ValueGeometry.equals( )
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
