[Geoserver-devel] New plugin supporting upcoming POSTGIS 2.0 Raster

GeoServer GeoServer Developer
,
1

I added a PostGis raster plugin to the imagemosaic-jdbc module on geotools trunk and did a backport to geotools 2.7.x

The documentation is here

http://docs.geotools.org/latest/userguide/library/coverage/pgraster.html

Should I make an announcement on the user mailing lists ?

Cheers
Christian

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

2

On Sun, Sep 25, 2011 at 10:19 AM, <christian.mueller@…1326…> wrote:

I added a PostGis raster plugin to the imagemosaic-jdbc module on
geotools trunk and did a backport to geotools 2.7.x

The documentation is here

http://docs.geotools.org/latest/userguide/library/coverage/pgraster.html

Should I make an announcement on the user mailing lists ?

That would work, a blog post would do fine as well.

Looking at that page and wondering, is there any way to make the
configuration of those raster sources easier?
Ideally a graphical way to specify the data source (maybe even as
just ponting to an existing postgis store) and the table containing the
mosaic, provided that some conventions has been followed to setup
the data, would be really nice.
In case you’re interested the GUI has pluggable API to provide your own
custom configuration panel, see the StoreEditPanel class, the
ArcSDECoverageStoreEditPanel is an example of how to do that
for coverages.

I can’t speak for others, but I personally find having to setup all these
configuration files really cumbersome

Cheers
Andrea

–

Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584 962313
fax: +39 0584 962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

3

On Sun, Sep 25, 2011 at 9:15 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Sun, Sep 25, 2011 at 10:19 AM, <christian.mueller@anonymised.com> wrote:

I added a PostGis raster plugin to the imagemosaic-jdbc module on
geotools trunk and did a backport to geotools 2.7.x

The documentation is here

http://docs.geotools.org/latest/userguide/library/coverage/pgraster.html

Should I make an announcement on the user mailing lists ?

That would work, a blog post would do fine as well.

Looking at that page and wondering, is there any way to make the
configuration of those raster sources easier?
Ideally a graphical way to specify the data source (maybe even as
just ponting to an existing postgis store) and the table containing the
mosaic, provided that some conventions has been followed to setup
the data, would be really nice.
In case you’re interested the GUI has pluggable API to provide your own
custom configuration panel, see the StoreEditPanel class, the
ArcSDECoverageStoreEditPanel is an example of how to do that
for coverages.

I can’t speak for others, but I personally find having to setup all these
configuration files really cumbersome

Yeah, I agree with Andrea. I think one thing that could work well is to have several datastore factories in the ‘Image Mosaicing Pyramidal JDBC Plugin’. Like one for PostGIS Raster, one for Oracle GeoRaster, one for the generic case, etc. Many of the params should be known if a user is to select PostGIS. I think Oracle has an example of more than one datastore factory. Ideally then users are just specifying the connection params in the GUI.

And I agree it’d be even better if one could just use one datastore connection for both vector and raster. I think ArcSDE may have gotten that improvement, though not oracle and postgis.

Cheers
Andrea

–

Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584 962313
fax: +39 0584 962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2

Geotools-devel mailing list
Geotools-devel@anonymised.coms.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

4

Oh, and awesome work Christian - it’s quite cool to have pgraster available in GeoServer.

On Sun, Sep 25, 2011 at 12:52 PM, Chris Holmes <cholmes@anonymised.com> wrote:

On Sun, Sep 25, 2011 at 9:15 AM, Andrea Aime <andrea.aime@anonymised.com…1268…> wrote:

On Sun, Sep 25, 2011 at 10:19 AM, <christian.mueller@anonymised.com> wrote:

I added a PostGis raster plugin to the imagemosaic-jdbc module on
geotools trunk and did a backport to geotools 2.7.x

The documentation is here

http://docs.geotools.org/latest/userguide/library/coverage/pgraster.html

Should I make an announcement on the user mailing lists ?

That would work, a blog post would do fine as well.

Looking at that page and wondering, is there any way to make the
configuration of those raster sources easier?
Ideally a graphical way to specify the data source (maybe even as
just ponting to an existing postgis store) and the table containing the
mosaic, provided that some conventions has been followed to setup
the data, would be really nice.
In case you’re interested the GUI has pluggable API to provide your own
custom configuration panel, see the StoreEditPanel class, the
ArcSDECoverageStoreEditPanel is an example of how to do that
for coverages.

I can’t speak for others, but I personally find having to setup all these
configuration files really cumbersome

Yeah, I agree with Andrea. I think one thing that could work well is to have several datastore factories in the ‘Image Mosaicing Pyramidal JDBC Plugin’. Like one for PostGIS Raster, one for Oracle GeoRaster, one for the generic case, etc. Many of the params should be known if a user is to select PostGIS. I think Oracle has an example of more than one datastore factory. Ideally then users are just specifying the connection params in the GUI.

And I agree it’d be even better if one could just use one datastore connection for both vector and raster. I think ArcSDE may have gotten that improvement, though not oracle and postgis.

Cheers
Andrea

–

Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584 962313
fax: +39 0584 962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2

Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

5

Thanks for feedback and improvement proposals. The primary goal of this work was to support pgraster with a minimum effort. I need 3-4 days to get it working.

I am not lucky with the whole imagemosic-jdbc code and configuration either. Some weeks ago I invested two days to integrate with Simones modules. Unluckily, this integration is quite complicated and I aborted.

Additionally I do not want to invest more time since I want to mark the imagemosiac-jdbc module as deprecated. My long term idea would be

1) Invent a geotools raster data type for the (JDBC) feature architecture, comparable to the jts geometry we use now. The raster type should support some base spatial functions, st_intersects as an example.

2) Map the geotools raster type to the PGRaster or Oracle Georaster type directly. For all other jdbc stores, map the raster to two columns, a geometry (the image boundary) and a BLOB.

3) Perhaps I can reuse the gt-featurepregeneralized code. This code is not limited to geometry objects.

4) Having a geotools raster data type, it would be less complicated to integrate with Simones plug ins. The code is already using features for storing tile envelopes or for temporal support.

Benefits would be
- kick out a lot of duplicated code for image processing
- simplified configuration
- inheriting features of gt-image* and not duplicate code again

But first I have to continue with my GSOC work (Security) because I have to produce a master thesis about this topic.

Cheers
Christian

Zitat von Chris Holmes <cholmes@anonymised.com>:

Oh, and awesome work Christian - it's quite cool to have pgraster available
in GeoServer.

On Sun, Sep 25, 2011 at 12:52 PM, Chris Holmes <cholmes@anonymised.com> wrote:

On Sun, Sep 25, 2011 at 9:15 AM, Andrea Aime <andrea.aime@anonymised.com
> wrote:

On Sun, Sep 25, 2011 at 10:19 AM, <christian.mueller@anonymised.com> wrote:

I added a PostGis raster plugin to the imagemosaic-jdbc module on
geotools trunk and did a backport to geotools 2.7.x

The documentation is here

http://docs.geotools.org/latest/userguide/library/coverage/pgraster.html

Should I make an announcement on the user mailing lists ?

That would work, a blog post would do fine as well.

Looking at that page and wondering, is there any way to make the
configuration of those raster sources easier?
Ideally a graphical way to specify the data source (maybe even as
just ponting to an existing postgis store) and the table containing the
mosaic, provided that some conventions has been followed to setup
the data, would be really nice.
In case you're interested the GUI has pluggable API to provide your own
custom configuration panel, see the StoreEditPanel class, the
ArcSDECoverageStoreEditPanel is an example of how to do that
for coverages.

I can't speak for others, but I personally find having to setup all these
configuration files really cumbersome

Yeah, I agree with Andrea. I think one thing that could work well is to
have several datastore factories in the 'Image Mosaicing Pyramidal JDBC
Plugin'. Like one for PostGIS Raster, one for Oracle GeoRaster, one for
the generic case, etc. Many of the params should be known if a user is to
select PostGIS. I think Oracle has an example of more than one datastore
factory. Ideally then users are just specifying the connection params in
the GUI.

And I agree it'd be even better if one could just use one datastore
connection for both vector and raster. I think ArcSDE may have gotten that
improvement, though not oracle and postgis.

Cheers
Andrea

--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584 962313
fax: +39 0584 962313

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-------------------------------------------------------

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.