Opened 13 years ago

Closed 13 years ago

#438 closed defect (invalid)

ST_Equals(X,X) = false ??

Reported by: strk Owned by: geos-devel@…
Priority: major Milestone: 3.3.0
Component: Default Version: main
Severity: Unassigned Keywords:
Cc:

Description

While producing the testcase for bug #368 I've got to a point where expected result doesn't match obtained result but they are really the same, in HEXWKB form.

So I tried a relate and... they don't result as being the same !!!

HEXWKB is this: 

010300000001000000340000007711061EC4DE06C1B56E2A7A590F0F4124BB1E1EC4DE06C14E21D979590F0F410000000028E406C100000000900C0F410000000078EA06C10000000070090F410000000038ED06C10000000020080F4100000000C0F706C10000000050030F4100000000580C07C10000000048FB0E4100000000F03307C10000000010F10E4100000000306C07C10000000048EE0E410000000080AA07C10000000000FA0E4100000000B8FF07C100000000901E0F4100000000785208C10000000078510F41E4EE881B7A6908C1F437AB9BC6610F410A3CCF227A6908C108190F8EC6610F4129F772288E6908C129F77228AE610F4108190F8EA66908C10A3CCF229A610F41E6B79F63C26908C10A9F1D428B610F41EEF84F97E06908C12CD0BB1882610F4100000000006A08C1A887CB007F610F411207B0681F6A08C12CD0BB1882610F411A48609C3D6A08C10A9F1D428B610F41F8E6F071596A08C10A3CCF229A610F41D7088DD7716A08C129F77228AE610F41F6C330DD856A08C108190F8EC6610F41F660E2BD946A08C1E6B79F63E2610F41D42F44E79D6A08C1EEF84F9700620F41587834FFA06A08C10000000020620F41D42F44E79D6A08C11207B0683F620F41F660E2BD946A08C11A48609C5D620F41F6C330DD856A08C1F8E6F07179620F4191A6A830806A08C12024DB5B80620F4100000000E8A308C100000000308B0F4174C9FEC2BFF408C12FD8B0D3E7C50F4113C7FEC2BFF408C196D6B0D3E7C50F41E1D0D6FFE7A308C1FD4D3900308B0F41257C3830CC6A08C1FB85F738B6620F415C13F5C8046A08C10FAD4CF9CB620F419CFDB25F956908C12E4B3B1DA8620F4120CE9B206F6908C14C46985980620F41EE59F5B7566908C1C4681D0347620F41AB33315D526908C11519783FE5610F41A3915A77746908C1415A1B9CC2610F41BC295D36785208C1A5C6872678510F413F6E957FB8FF07C13FB57C4E901E0F41C8E5AACE80AA07C19F62AB5800FA0E410C8D11ED306C07C168B7952C48EE0E41CBC32D03F03307C12778E01410F10E41C4243C02580C07C16AC5ED0648FB0E411B9D2F36C0F706C1FA47DEEA4F030F412633850F38ED06C1EA5BE8F81F080F41CF5B10F027E406C137673D08900C0F417711061EC4DE06C1B56E2A7A590F0F41

Might be happening only in my development branch, so isn't confirmed yet.

Change History (3)

comment:1 by strk, 13 years ago

The polygon is invalid: NOTICE: Self-intersection at or near point -199983 257080

comment:2 by robe, 13 years ago

Is this really a bug? I would say its invalid. ST_Equals is supposed to return false in this case is my understanding because the boundaries of the geometry are not well formed.

Therefore you can't say it is or isn't spatially equal to itself. Is outer space = outer space? I've always accepted this as a given. Am I missing something?

comment:3 by strk, 13 years ago

Resolution: → invalid
Status: new → closed

No, I was missing the input was invalid at the time of bug filing. The input came out from a JTS union, so I expected it to be valid. It became a JTS bug then... reported on mailing list..

NOTE: this is the output of the Union reported in bug #368.

Note: See TracTickets for help on using tickets.