#1084: OffsetCurve -- TopologyException: found non-noded intersection between...
-+---
Reporter: jengland | Owner: geos-devel@…
Type: defect | Status: new
Priority: major| Milestone: 3.9.1
Component:
#1084: OffsetCurve -- TopologyException: found non-noded intersection between...
-+---
Reporter: jengland | Owner: geos-devel@…
Type: defect | Status: new
Priority: major| Milestone: 3.9.1
Component:
#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 |
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
#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
#910: Difference operation resulted with a wrong geometry as a result of a
precision limitation
-+-
Reporter: yanivnavon | Owner: 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
#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 |
#1068: Fix CMake Windows install: keep geos-config.cmake
---+---
Reporter: Mike Taves | Owner: geos-devel@…
Type: defect | Status: closed
Priority: blocker| Milestone:
#910: Difference operation resulted with a wrong geometry as a result of a
precision limitation
-+-
Reporter: yanivnavon | Owner: geos-
|
#1068: Fix CMake Windows install: keep geos-config.cmake
---+---
Reporter: Mike Taves | Owner: geos-devel@…
Type: defect | Status: closed
Priority: blocker| Milestone:
#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:
#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:
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
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;
___
+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
>
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
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
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
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
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
21 matches
Mail list logo
