[OSM-dev] Anybody using libosmium with GEOS?

Bas Couwenberg sebastic at xs4all.nl
Thu Oct 27 14:32:17 UTC 2016


On 2016-10-27 15:48, Jochen Topf wrote:
> GEOS 3.6 has changed its C++ interface and they recommend not to use it
> anyway, but use the C interface. I have support for creating GEOS
> geometries in libosmium using the C++ interface and am wondering what 
> do
> do with it. Is anybody using that interface in libosmium? I am not 
> using
> it myself and dont't want to support a changing GEOS interface if 
> nobody
> actually uses it.
> 
> I see several ways foreward here:
> * Use some #ifdef magic and support the old and new interface
> * Switch to the C API of GEOS
> * Remove the code entirely
> 
> Of course, removing any code would probably mean deprecating it first,
> and removing it at a later date. I would probably have to wrap the code
> into #ifdefs to switch it off with later GEOS versions so the compile
> doesn't fail if you happen to have a newer GEOS version.
> 
> Any opinions?

If the GEOS support in libosmium stays, my preference (as maintainer of 
the Debian packages) is to switch to the C API which most GEOS reverse 
dependencies use (notable exceptions are OSSIM, GRASS & osm2pgsql).

The #ifdefs are an option too, which can then serve as examples for the 
other projects also affected by the GEOS C++ API change.

Kind Regards,

Bas



More information about the dev mailing list