Re: [geos-devel] [GEOS] #1084: OffsetCurve -- TopologyException: found non-noded intersection between...

[GEOS]

#1084: OffsetCurve -- TopologyException: found non-noded intersection between...
-+---
 Reporter:  jengland |   Owner:  geos-devel@…
 Type:  defect   |  Status:  new
 Priority:  major|   Milestone:  3.9.1
Component:  Default  | Version:  3.8.0
 Severity:  Unassigned   |  Resolution:
 Keywords:  OffsetCurve  |
-+---
Changes (by jengland):

 * version:  3.9.0 => 3.8.0


-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #1084: OffsetCurve -- TopologyException: found non-noded intersection between...

[GEOS]

#1084: OffsetCurve -- TopologyException: found non-noded intersection between...
-+---
 Reporter:  jengland |   Owner:  geos-devel@…
 Type:  defect   |  Status:  new
 Priority:  major|   Milestone:  3.9.1
Component:  Default  | Version:  3.9.0
 Severity:  Unassigned   |  Resolution:
 Keywords:  OffsetCurve  |
-+---
Changes (by jengland):

 * Attachment "mine_topology_exceptions.py" added.

 Python file using shapely to mine offset excpetions

-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] [GEOS] #1084: OffsetCurve -- TopologyException: found non-noded intersection between...

[GEOS]

#1084: OffsetCurve -- TopologyException: found non-noded intersection between...
+--
 Reporter:  jengland|  Owner:  geos-devel@…
 Type:  defect  | Status:  new
 Priority:  major   |  Milestone:  3.9.1
Component:  Default |Version:  3.9.0
 Severity:  Unassigned  |   Keywords:  OffsetCurve
+--
 This is coming from shapely's `parallel_offset`. Here is an example:

 {{{
 from shapely import wkt, geos

 print(geos.geos_version_string)

 wkt.loads('LINESTRING (0 9, 21 30, 49 45, 61 70, 81
 90)').parallel_offset(3)
 }}}

 Has the following output

 {{{
 3.8.0-CAPI-1.13.1
 TopologyException: found non-noded intersection between LINESTRING
 (50.4167 -21.6444, 22.8077 -36.435) and LINESTRING (22.8077 -36.435,
 37.4683 -21.7743) at 22.807666014902189 -36.434974672217095
 
 }}}

 I can mine them with the attached script at a rate of about 5-10 per
 100,000 LineString s. The LineString s I'm trying are all simple
 (relatively straight on a 100x100 integer grid with 5 points each). And
 all the offsets are 0-9 ints.

 This seems to be different from #682, because there the error message is
 different (i.e. `TopologyException: assigned depths do not match at ...`)
 and I cannot easily mine for exception of that message.

 Hopefully it's acceptable to submit a `.py` example file. I can try to
 reproduce this using GEOS directly if necessary.

-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] MakeValid and empty collection component

[Even Rouault]

On mercredi 9 décembre 2020 12:13:17 CET Sandro Santilli wrote:
> I found out that GEOSMakeValid will remove EMPTY components from
> collections. The PostGIS implementation of it does not do this.
> 
> The rationale was that a collection with EMPTY component is NOT
> invalid as per OGC specification, so why removing them ? Isn't
> that a job for CollectionHomogenize or similar ?

Actually the unit tests have checks for this.

See tests/xmltester/tests/misc/makevalid.xml


makevalid/geometry_collection
  GEOMETRYCOLLECTION(POINT EMPTY,LINESTRING EMPTY,POLYGON((0 0,0 1,1 1,1 
0,0 0),(0 0.5,0.5 0.1,1 0.5,0 0.5)))
  

GEOMETRYCOLLECTION (MULTIPOLYGON (((0.0 0.0, 0.0 0.5, 0.5 0.1, 1.0 
0.5, 1.0 0.0, 0.0 0.0)), ((0.0 0.5, 0.0 1.0, 1.0 1.0, 1.0 0.5, 0.0 
0.5))),LINESTRING EMPTY, POINT EMPTY)

  




-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #682: ST_OffsetCurve fails for some geometries

[GEOS]

#682: ST_OffsetCurve fails for some geometries
+---
 Reporter:  jventin |   Owner:  geos-devel@…
 Type:  defect  |  Status:  new
 Priority:  major   |   Milestone:  3.6.4
Component:  Default | Version:  3.4.2
 Severity:  Unassigned  |  Resolution:
 Keywords:  |
+---

Comment (by jengland):

 A cross-reference to what I think is another example of this error using
 `parallel_offset` on a LineString in Shapely.

 https://github.com/Toblerity/Shapely/issues/820

-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #910: Difference operation resulted with a wrong geometry as a result of a precision limitation

[GEOS]

#910: Difference operation resulted with a wrong geometry as a result of a
precision limitation
-+-
 Reporter:  yanivnavon   |   Owner:  geos-
 |  devel@…
 Type:  defect   |  Status:  closed
 Priority:  major|   Milestone:  3.10.0
Component:  Default  | Version:  3.6.2
 Severity:  Significant  |  Resolution:  invalid
 Keywords:  polygon, geometry, geometries,   |
  difference, union, multipolygon|
-+-

Comment (by mdavis):

 The snapping noding works well for this, and doesn't require rounding all
 the output coordinates.  Perhaps we should expose that capability as well
 as snap-rounding.

-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #1059: Cannot build GEOS on Windows 10 under MinGW

[GEOS]

#1059: Cannot build GEOS on Windows 10 under MinGW
+---
 Reporter:  twrackers   |   Owner:  geos-devel@…
 Type:  defect  |  Status:  new
 Priority:  major   |   Milestone:  3.8.2
Component:  Default | Version:  3.8.0
 Severity:  Unassigned  |  Resolution:
 Keywords:  |
+---
Changes (by pramsey):

 * milestone:  3.10.0 => 3.8.2


-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #1061: Cannot build GEOS on Windows 10 under MinGW

[GEOS]

#1061: Cannot build GEOS on Windows 10 under MinGW
-+---
 Reporter:  twrackers|   Owner:  geos-devel@…
 Type:  defect   |  Status:  new
 Priority:  major|   Milestone:  3.8.2
Component:  Default  | Version:  3.6.2
 Severity:  Unassigned   |  Resolution:
 Keywords:  MinGW geos make  |
-+---
Changes (by pramsey):

 * milestone:  3.10.0 => 3.8.2


-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #1068: Fix CMake Windows install: keep geos-config.cmake

[GEOS]

#1068: Fix CMake Windows install: keep geos-config.cmake
---+---
 Reporter:  Mike Taves |   Owner:  geos-devel@…
 Type:  defect |  Status:  closed
 Priority:  blocker|   Milestone:  3.9.0
Component:  Build/Install (cmake)  | Version:  master
 Severity:  Unassigned |  Resolution:  fixed
 Keywords: |
---+---
Changes (by pramsey):

 * milestone:  3.10.0 => 3.9.0


-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #910: Difference operation resulted with a wrong geometry as a result of a precision limitation

[GEOS]

#910: Difference operation resulted with a wrong geometry as a result of a
precision limitation
-+-
 Reporter:  yanivnavon   |   Owner:  geos-
 |  devel@…
 Type:  defect   |  Status:  closed
 Priority:  major|   Milestone:  3.10.0
Component:  Default  | Version:  3.6.2
 Severity:  Significant  |  Resolution:  invalid
 Keywords:  polygon, geometry, geometries,   |
  difference, union, multipolygon|
-+-
Changes (by pramsey):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 As of 3.9 you might find the snap-rounded operations (difference with a
 tolerance) provide more predictability in terms of holding to a
 particularly domain grid, assuming you can stand the initial round-off
 stop.

-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #1068: Fix CMake Windows install: keep geos-config.cmake

[GEOS]

#1068: Fix CMake Windows install: keep geos-config.cmake
---+---
 Reporter:  Mike Taves |   Owner:  geos-devel@…
 Type:  defect |  Status:  closed
 Priority:  blocker|   Milestone:  3.10.0
Component:  Build/Install (cmake)  | Version:  master
 Severity:  Unassigned |  Resolution:  fixed
 Keywords: |
---+---
Changes (by pramsey):

 * status:  new => closed
 * resolution:   => fixed


-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #1003: MontoneChainBuilder Assertion Error

[GEOS]

#1003: MontoneChainBuilder Assertion Error
+---
 Reporter:  apjoseph|   Owner:  geos-devel@…
 Type:  defect  |  Status:  new
 Priority:  major   |   Milestone:  3.8.2
Component:  Default | Version:  3.8.0
 Severity:  Unassigned  |  Resolution:
 Keywords:  |
+---
Changes (by pramsey):

 * version:  master => 3.8.0
 * milestone:  3.10.0 => 3.8.2


-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] [GEOS] #1049: Inconsistency with POINT(nan nan)

[GEOS]

#1049: Inconsistency with POINT(nan nan)
+---
 Reporter:  Mike Taves  |   Owner:  geos-devel@…
 Type:  defect  |  Status:  closed
 Priority:  major   |   Milestone:  3.10.0
Component:  Default | Version:  master
 Severity:  Unassigned  |  Resolution:  fixed
 Keywords:  |
+---
Changes (by Paul Ramsey ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"693c1aa855263198d42153da0d12f56b2b7a6991/git" 693c1aa/git]:
 {{{
 #!CommitTicketReference repository="git"
 revision="693c1aa855263198d42153da0d12f56b2b7a6991"
 Correctly return isEmpty for hand-built empty points, closes #1049
 }}}

-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] [GEOS] Batch modify: #1068, #833, #835, #910, #911, #922, #932, #962, ...

[GEOS]

Batch modification to #1068, #833, #835, #910, #911, #922, #932, #962, #964, 
#968, #972, #995, #997, #1000, #1003, #1009, #1012, #1032, #1039, #1040, #1041, 
#1045, #1049, #1052, #1059, #1061, #1071, #1072, #1074, #1075, #771, #915, 
#935, #940, #946, #965, #989, #1004, #1025, #1031, #1077 by pramsey:
milestone to 3.10.0

-- 
Tickets URL: 

GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.9.0 Train Departing

[Sandro Santilli]

On Wed, Dec 09, 2020 at 08:46:34AM -0800, Paul Ramsey wrote:
> I am going to package a release today, and unless someone lights their hair 
> on fire in the intervening 24 hours release tomorrow morning.

Go for it, we'll all onboard!

--strk;
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.9.0 Train Departing

[Martin Davis]

+1

On Wed, Dec 9, 2020 at 8:46 AM Paul Ramsey 
wrote:

> I am going to package a release today, and unless someone lights their
> hair on fire in the intervening 24 hours release tomorrow morning.
>
> P.
> ___
> geos-devel mailing list
> geos-devel@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel
>
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] 3.9.0 Train Departing

[Regina Obe]

Yeh +1

> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Wednesday, December 9, 2020 11:47 AM
> To: GEOS Development List 
> Subject: [geos-devel] 3.9.0 Train Departing
> 
> I am going to package a release today, and unless someone lights their
hair
> on fire in the intervening 24 hours release tomorrow morning.
> 
> P.
> ___
> geos-devel mailing list
> geos-devel@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel

___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] 3.9.0 Train Departing

[Paul Ramsey]

I am going to package a release today, and unless someone lights their hair on 
fire in the intervening 24 hours release tomorrow morning.

P.
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] MakeValid and empty collection component

[Komяpa]

Hi,

I believe there are two modes functions can operate in: geometry-preserving
or structure-preserving.
MakeValid will try to recover the geometry, but makes no effort to preserve
structure, sometimes it is impossible.

If you're using MakeValid, you expect the structure (the number of
subgeometries, multi-nonmulti, dimensionality..) to change. I don't see how
in this circumstances an attempt to save the EMPTY component will help any
use case.

On Wed, Dec 9, 2020 at 2:13 PM Sandro Santilli  wrote:

> I found out that GEOSMakeValid will remove EMPTY components from
> collections. The PostGIS implementation of it does not do this.
>
> The rationale was that a collection with EMPTY component is NOT
> invalid as per OGC specification, so why removing them ? Isn't
> that a job for CollectionHomogenize or similar ?
>
> --strk;
> ___
> geos-devel mailing list
> geos-devel@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel
>


-- 
Darafei "Komяpa" Praliaskouski
OSM BY Team - http://openstreetmap.by/
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] MakeValid and empty collection component

[Even Rouault]

Sandro,

> I found out that GEOSMakeValid will remove EMPTY components from
> collections. The PostGIS implementation of it does not do this.
> 
> The rationale was that a collection with EMPTY component is NOT
> invalid as per OGC specification, so why removing them ? Isn't
> that a job for CollectionHomogenize or similar ?

I don't remember having done anything particular regarding treatment of EMPTY 
components. Might be an accident during the porting or the PostGIS 
implementation has changed in between.

Even


-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] MakeValid and empty collection component

[Sandro Santilli]

I found out that GEOSMakeValid will remove EMPTY components from
collections. The PostGIS implementation of it does not do this.

The rationale was that a collection with EMPTY component is NOT
invalid as per OGC specification, so why removing them ? Isn't
that a job for CollectionHomogenize or similar ?

--strk;
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel