Opened 14 years ago
Closed 12 years ago
#232 closed enhancement (fixed)
Update Geos in OSGeo4w package
Reported by: | aperi2007 | Owned by: | warmerdam |
---|---|---|---|
Priority: | major | Component: | Package |
Version: | Keywords: | geos | |
Cc: | jef |
Description
I think would be great to update the geos in OSGeo4W package to use the last Geos 3.3.0. It add some new and nice Spatial function like CommonShared to retrieve common segments with orientation, CoverBy and CoveredBy, UnaryUnion, and a Snap function.
Again it resolve some bug in the Geometry expecially in Union function.
Change History (19)
comment:1 by , 14 years ago
Cc: | added |
---|---|
Keywords: | geos added |
Status: | new → assigned |
follow-up: 3 comment:2 by , 14 years ago
No the upgrade should be fine. QGIS only uses the GEOS C-API. QGIS also doesn't use the spatialite package - but spatialite is pure C anyway.
So I don't forsee any problems upgrading the GEOS version.
comment:3 by , 13 years ago
Replying to jef:
No the upgrade should be fine. QGIS only uses the GEOS C-API. QGIS also doesn't use the spatialite package - but spatialite is pure C anyway.
So I don't forsee any problems upgrading the GEOS version.
happy to read this.
follow-up: 6 comment:5 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
After more informations and news, I guess the geos 3.3.0 was no more the right choice for qgis future. So I close the ticket I opened.
Sorry for noise.
follow-up: 7 comment:6 by , 13 years ago
comment:7 by , 13 years ago
Replying to jef:
Replying to aperi2007:
After more informations and news,
Which are?
I see in postgis the firsts experimental version will use the geos 3.3.1-dev, so perhaps is better to wait to update geos and also wait the release of postgis 200 to see what version of geos will be used. After the release of postgis 200 could be update the package to the used version of geos.
comment:8 by , 13 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
Hi, I see just now is released the geos 3.3.1. I guess this is a good version to update the geos version on osgeo4w.
regards
comment:9 by , 13 years ago
Hi, any chance that the geos available in the osgeo4w package was update to the last stable 3.3.1 ?
Regards,
comment:10 by , 13 years ago
Hello,
some new digitizing features in QGIS-master are only available with geos version >= 3.3;
If geos ver 3.3 makes no trouble, it would be of advantage, to update the package on OSGeo4W.
Thanks and regards
Gerhard Spieles
comment:12 by , 12 years ago
Also excludes advanced stuff (like {{line_interpolate_point}}) in spatialite.
comment:13 by , 12 years ago
Hi.
There is available the Geos 3.3.5. I see the osgeo4w is still using the geos 3.2.2.
Perhaps there is some incompatibility between the Geos 3.3.5 and the osgeo libraries to avoid the update ?
comment:14 by , 12 years ago
The makefile.vc and nmake.opt for GEOS has changed quite a lot since I prepared it and I find I am no longer sufficiently motivated to build this package from the current nmake files. Perhaps someone else would like to do it?
follow-up: 17 comment:16 by , 12 years ago
This page:
http://trac.osgeo.org/osgeo4w/wiki/pkg-geos
indicates VC9 (I think this is Visual Studio Express 2008).
The reason it (may) be sensitive is because I believe that QGIS uses the C++ API directly as opposed to the suggested approach of using the C API which makes versioning less sensitive.
Possibly Jurgen can comment on this.
comment:17 by , 12 years ago
Replying to warmerdam:
Possibly Jurgen can comment on this.
Um, I already did 18 months, when you had the same question - see the comment above ;)
comment:18 by , 12 years ago
Doh!
Well, then I'll try it with my new VC version and see how things go.
comment:19 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
GEOS Package updated to 3.3.5 and it seems to be working ok. Please test.
Note that this packaging was essentially "out of the box" from the source, and was done on the new OSGeo4W Amazon build instance.
Jurgen,
Does QGIS or the OSGeo4W Spatiallite package use the GEOS C++ API? Do you perceive problems with my upgrading to GEOS 3.3?