Continuing the discussion here:
We have a mandate to simplify the PostGIS raster support.
My plan is to create a JDBCPGRasterConfigurationBuilder which, starting
from an input folder containing tiles created with gdal_retile, do this:
- store tiles into DB (using raster2pgsql script)
- create metadata table and store tileTables into it
- create XML configuration file (starting from a template) to specify
connection params, mapping params, and coverage properties
- pass down the newly created config file to the usual reader.
Parameters (such as DB credentials, table prefixes, ) will be passed down
as a JDBCPGRasterConfigurationBean through Hints.
>From a GS point of view, we can setup a new wicket to specify them.
Cheers,
Daniele
Daniele
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Daniele Romagnoli
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
On Wed, Jul 10, 2013 at 6:23 PM, Daniele Romagnoli <
daniele.romagn...@geo-solutions.it> wrote:
> A few notes about this JIRA.
> I would like to do something like this:
>
> 1) specify basic parameters (maybe as Hints or as a ConfigurationBean):
> - tablename_prefix
> - mosaic_table_name
> - mosaic_name
> - db properties (host, user, password, db, schema)
>
> 2) configure an ImageMosaicJDBC against a folder contained data prepared
> with gdal_retile.
>
> Automatic steps performed by new code:
> i) insert each level using raster2pgsql into the proper
> ${tablename_prefix}_level table into the proper $db.$schema
> ii) create a new ${mosaic_table_name} and insert new rows using
> ${mosaic_name} as value for the "name" column and previously created
> tablename_prefix_level tables as values for "tiletable" column.
> iii) create the XML file starting from a template and replace postgis
> connection parameter entries, mastertable name entry, and coverage name.
> iv) open the reader on top of the configuration.
>
> About point #1, I would like to work with wickets to allow specifying
> these parameters at configuration time when using it from GeoServer.
>
> What do you think about it?
> Cheers,
> Daniele
>
>
>
>
> ==
> Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
> information.
> ==
> Ing. Daniele Romagnoli
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
>
> On Wed, Jul 10, 2013 at 6:12 PM, Daniele Romagnoli (JIRA) <
> j...@codehaus.org> wrote:
>
>> Daniele
>> Romagnoli<https://jira.codehaus.org/secure/ViewProfile.jspa?name=dany111>created
>> [image:
>> Improvement] GEOT-4507 <https://jira.codehaus.org/browse/GEOT-4507>
>> *Easiest way to setup
>> imageMosaicJDBC-PGRaster*<https://jira.codehaus.org/browse/GEOT-4507>
>> *Issue Type:* [image: Improvement] Improvement *Assignee:*
>> Unassigned
>> *Components:* imagemosaic-jdbc plugin *Created:* 10/Jul/13 11:11 AM
>> *Description:*
>>
>> Right now, in order to config an imageMosaic JDBC against PGRaster DB
>> there are several steps to be performed:
>> 1) use gdal_retile to create tiles for images
>> 2) insert tiled data as new table (one for level) into PGRaster using
>> raster2pgsql scripts invokation
>> 3) create a table containing level information (reference table,
>> envelope, resolutions)
>> 4) create 3 XML config files with JDBC mapping, coverage properties,
>> table mapping
>> 5) configure the mosaic.
>>
>> It would be good to have some automagic way to do steps 2 through 5 with
>> minimal user intervention.
>>
>> As an instance, it would be great if we could just provide the location
>> of the folder containing tiled images (levels), as well as a set of some
>> additional parameters (table name prefix, mosaic name, coverage name, DB
>> credentials) and let the imageMosaicJDBC do all these steps automatically.
>> *Project:* GeoTools <https://jira.codehaus.org/browse/GEOT> *
>> Priority:* [image: Minor] Minor *Reporter:* Daniele
>> Romagnoli<https://jira.codehaus.org/secure/ViewProfile.jspa?name=dany111>
>> This
>> message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA
>> administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
