Geoprocessing/Buffer features plug-in - various defects: i18n, PG connection leak, fails to load buffer layer

[smizuno]

• Needs internationalization

• PostgreSQL connection left hanging on cancel or failure to buffer

• sometimes fails to load the buffer layer table when requested - seems to depend on the user

• "Buffer distance in map units" box should accept negative numbers; it is valid to do negative buffers, at least on polygons

• should show schemas the user has CREATE privilege on

• the geometry column needs to be "shape" - anything else fails

[gsherman]

This plugin is a third-party plugin. The developers may not see this bug report.

[hdus]

Replying to gsherman:

This plugin is a third-party plugin. The developers may not see this bug report.

In the meantime there exists two plugins which offers buffering of geometries.

1. The C++ Geoprocessing Plugin delivered with QGIS
2. The third party python plugin "Geoprocessing"

Which plugin do you mean?

[smizuno]

Replying to hdus:

Replying to gsherman:

This plugin is a third-party plugin. The developers may not see this bug report.

In the meantime there exists two plugins which offers buffering of geometries.

1. The C++ Geoprocessing Plugin delivered with QGIS
2. The third party python plugin "Geoprocessing"

Which plugin do you mean?

I was referring to the C++ Geoprocessing Plugin delivered with QGIS (qgspggeoprocessing.cpp)

[hdus]

In priciple we should decide whether we keep the C++ plugin in the QGIS distribution or not. I believe that my new Geoprocessing plugin is much more flexible due to use of all OGR and PostGIS data sources. It is not neccessary to have two plugins doing the same.

[jef]

the c++ plugin was removed

[(none)]

Milestone Version 1.0.0 deleted