[Geoserver-users] GeoBI: GeoServer datastore extension for GeobiLocate

GeoServer GeoServer User
1

Hello,
we uploaded GeoReport prototype here [1] (regarding GeoBI Open Source Project [2] as discussed some mails ago in this ML).
Now, we are thinking about the possibility to extend GeoServer DataStore and create a new module GeobiLocate in order to serve data coming from:

   1. GeoNames
   2. OpenGeoCoding
   3. Google Geocoding
   4. .....
   5. other services......

Any experience\help about datasource customization?

Consider that GeoReport prototype now works using GeoServer WFS interface and geojson output format.
We'd like to receive from wfs response also point features generated starting from geocoding processes as explain above.

We could start with GeoNames.
I read this link http://docs.codehaus.org/display/GEOTDOC/DataStore+Developers+Guide.
Is it enough?

[1] http://code.google.com/p/geobi
[2] www.geobi.org

Thank you

--
Fabio D'Ovidio
Geospatial solutions

INOVA s.r.l.
Web : http://www.inovaos.it
Tel.: 081 197 57 600
mail: fabiodovidio@anonymised.com

2

Fabio D'Ovidio ha scritto:

Hello,
we uploaded GeoReport prototype here [1] (regarding GeoBI Open Source Project [2] as discussed some mails ago in this ML).

Nice. Hope you're getting good feedback, sorry for not providing much,
never been involved in BI :slight_smile:

Now, we are thinking about the possibility to extend GeoServer DataStore and create a new module GeobiLocate in order to serve data coming from:

   1. GeoNames
   2. OpenGeoCoding
   3. Google Geocoding
   4. .....
   5. other services......

Any experience\help about datasource customization?

Consider that GeoReport prototype now works using GeoServer WFS interface and geojson output format.
We'd like to receive from wfs response also point features generated starting from geocoding processes as explain above.

We could start with GeoNames.
I read this link http://docs.codehaus.org/display/GEOTDOC/DataStore+Developers+Guide.
Is it enough?

Well, that is all we got GeoTools wise. Enough, hum, don't know,
that code is actually pretty old, I would try to stay away
from the attribute reader part and do your own feature building.

I guess as a reference you can have a look at the current code
of the PropertyDataStore, and the code of JDBCDataStore
(in unsupported/jdbc-ng).
Beware, they use two different base classes. Pick the one that
suits you better.

Cheers
Andrea

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