[Geoserver-devel] ogr2ogr based output format ready

Hi all,
the ogr2ogr based output format is ready for wider testing,
and possibly to become and extension too:
- the code is available in community/ogrout
- the test code coverage exceeds 80%
- there is a wiki page explaining how to use it here:
   http://geoserver.org/display/GEOS/Ogr2Ogr+based+WFS+output+format

Feedback welcomed. If there are no objections I'll ask for
a vote to turn the module into an official extension shortly.
Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Good stuff Andrea. A quick code review I don't see anything that pops out at me.

One nit-picky thing is when you move it to extension can you rename the module to simply "ogr". I would like us to continue to follow the convention of keeping profile names the same as module names. And I like the concise name "ogr" better than "ogrout" ;).

Andrea Aime wrote:

Hi all,
the ogr2ogr based output format is ready for wider testing,
and possibly to become and extension too:
- the code is available in community/ogrout
- the test code coverage exceeds 80%
- there is a wiki page explaining how to use it here:
   http://geoserver.org/display/GEOS/Ogr2Ogr+based+WFS+output+format

Feedback welcomed. If there are no objections I'll ask for
a vote to turn the module into an official extension shortly.
Cheers
Andrea

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

Justin Deoliveira ha scritto:

Good stuff Andrea. A quick code review I don't see anything that pops out at me.

One nit-picky thing is when you move it to extension can you rename the module to simply "ogr". I would like us to continue to follow the convention of keeping profile names the same as module names. And I like the concise name "ogr" better than "ogrout" ;).

Sure thing. What will we do if we resume work on the OGRDataStore
in GeoTools thought? That was the main reason I did not call it
simpy ogr, as you told me you had an interesting in reviving
the OGR Data store.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

Sure thing. What will we do if we resume work on the OGRDataStore
in GeoTools thought? That was the main reason I did not call it
simpy ogr, as you told me you had an interesting in reviving
the OGR Data store.

True... i guess in that case no additional geoserver module will be required right? So we could just add the gt-ogr (or whatever its called) as a dependency to the ogr extension.

Cheers
Andrea

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

Justin Deoliveira ha scritto:

Sure thing. What will we do if we resume work on the OGRDataStore
in GeoTools thought? That was the main reason I did not call it
simpy ogr, as you told me you had an interesting in reviving
the OGR Data store.

True... i guess in that case no additional geoserver module will be required right? So we could just add the gt-ogr (or whatever its called) as a dependency to the ogr extension.

Oh, ok, I saw some modules popping up for db2 and stuff and thought
it was necessary to create a new extension module per gt2 datastore
now (thought I did not understand the reason in fact).

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.