GEOS Developers

This forum is an archive for the mailing list geos-devel@lists.osgeo.org (more options) Messages posted here will be sent to this mailing list.
This is the developers mailing list for GEOS.

GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite (JTS). As such, it aims to contain the complete functionality of JTS in C++. This includes all the OpenGIS "Simple Features for SQL" spatial predicate functions and spatial operators, as well as specific JTS topology functions such as IsValid().
1234 ... 31
Topics (1080)
Replies Last Post Views
[GEOS] #846: UTF8 BOM in headers ? by geos-2
1
by geos-2
[GEOS] #845: Head Use-After-Free geos::geomgraph::index::SweepLineEvent::isDelete() by geos-2
1
by geos-2
Segmentation fault when using intersect with multithreading by Fardet Tanguy
0
by Fardet Tanguy
Alternative licensing for GEOS by James Turner
7
by Regina Obe
Thoughts on Backporting the emit warning message to GEOS 3.6 and GEOS 3.5 by Regina Obe
8
by Paul Norman
Re: MOTION to accept this patch [geos] Emit a warning at compile time about C++ API being unstable (#14) - PASSES by Regina Obe
1
by Sandro Santilli-4
Re: RFC6 - Discourage use of C++ API by requiring a configure switch to install the c++ headers and SDK by Regina Obe
12
by Sebastiaan Couwenber...
Re: MOTION to accept this patch [geos] Emit a warning at compile time about C++ API being unstable (#14) - Summarize of votes by Regina Obe
3
by Dale Lutz
GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?) by Mateusz Loskot
6
by Paul Norman
MOTION to accept this patch [geos] Emit a warning at compile time about C++ API being unstable (#14) by Regina Obe
1
by Sandro Santilli-4
Re: RFC6 - Drop GEOS C++ API at GEOS 3.8 by Kurt Schwehr-2
6
by Regina Obe
Re: [postgis-devel] RFC6 - Require explicit configure to use the C++ API by Regina Obe
3
by Sandro Santilli-4
Re: [postgis-devel] RFC6 - Drop GEOS C++ API at GEOS 3.8 by Mateusz Loskot
13
by Sebastiaan Couwenber...
[GEOS] #844: Geos 3.6.2 tests failing on ppc64le architecture by geos-2
0
by geos-2
[PSC] Commit access removal by Mateusz Loskot
4
by Mateusz Loskot
Re: [GEOS] #712: Single-sided buffer gives unexpected result by geos-2
4
by geos-2
[GEOS] #843: Deprecated declarations warning macro by geos-2
0
by geos-2
GEOS 3.7.0 beta end this week by Regina Obe
6
by Regina Obe
[clang-tidy] modernize-use-nullptr and modernize-use-override by Mateusz Loskot
0
by Mateusz Loskot
Can we deprecate GeometryList class? by Mateusz Loskot
1
by Mateusz Loskot
Order of results in GEOSDelaunayTriangulation by Nyall Dawson
6
by username
[GEOS] #841: Regression in prepared polygons contains by geos-2
4
by geos-2
Correct use of setPrecision by Nyall Dawson
5
by Mateusz Loskot
Reviewing std::auto_ptr spaghetti by Mateusz Loskot
2
by Mateusz Loskot
git hooks updated to hit Winnie and Debbie web hooks by Sandro Santilli-4
2
by Sandro Santilli-4
GEOS 3.7.0 release in 2 weeks by Regina Obe
6
by Mateusz Loskot
[GEOS] #832: LinearLocation::isValid and LinearLocation::normalize, faulty comparisons by geos-2
5
by geos-2
Re: [GEOS] #588: [JTS fixed] valid polygon when cw, not valid when ccw by geos-2
0
by geos-2
Re: [GEOS] #584: Port robust distance fixes from JTS by geos-2
0
by geos-2
Re: [GEOS] #572: Contains issue for complex LineStrings [JTS fails too] by geos-2
0
by geos-2
Re: [GEOS] #546: polygonize::EdgeRing::ptNotInList bug ? by geos-2
0
by geos-2
Re: [GEOS] #544: Port JTS bugfix and testcases for MCIndexSnapRounder / GeometryNoder by geos-2
0
by geos-2
Accompanying .editorconfig with .gitattributes? by Mateusz Loskot
5
by Mateusz Loskot
[GEOS] #840: PointOnSurface strange behavior by geos-2
5
by geos-2
Re: [GEOS] #587: Memory leak in geos trunk by geos-2
1
by geos-2
1234 ... 31