Daniele Romagnoli a écrit :
> Hi,
> In a recent thread on gt2-user ML, Martin told us that they are 
> working on refactoring geographicMetadata to be more GML-JPEG2000 
> compliant.
> Me and Alessio have already started some months ago a work to handle 
> metadata for imageio plugin involved in multidimensional coverages 
> management. It is mainly based on GML / GML in JPEG2000 / ISO19111 / 
> WCS 1.1.0 specifications. Moreover we have started a document 
> containing structures and schemas.
> It would be great if we can collaborate to discuss/merge the works.
>
Hi Daniele and other GeoSolutions' developers,

I come in the conversation because I'm the one who currently works on 
the unsupported/coverageio module created by Martin, and he's guiding me 
for the refactoring of this module. I base this refactoring on the GML 
in JPEG2000 standard, and I've read the paper about ImageIO metadata for 
ND coverage your team has seend us (nice paper :)). I'm trying to deal 
with the standard (to stay as close as I can), and the way you see some 
particular points this standard does not covered totally.
Of course I will be pleased to collaborate with you on this work :)

It was in a corner of my head to come on the list to discuss about this 
point, thank you for coming again to us :)

I've already begun something, my first commit was done at revision 
30775. I cheer you to have a look at this class, where you can find a 
detailed tree of the metadata (in the middle of the page) :
http://svn.geotools.org/trunk/modules/unsupported/coverageio/src/main/java/org/geotools/image/io/metadata/GeographicMetadataFormat.java

But we (Martin and I) are not totally happy with this tree, it lacks 
some information as projection, that's why we have added some more nodes 
in the tree. These changes are on my local version of Geotools, and I've 
copied you the new tree here : http://rafb.net/p/aDQFVD42.html.
Wherever there is a (!) comment, it is something not present in the GML 
in JPEG2000 standard, but something we require.
I hope this tree will be the one you expected, and if you have some 
comments / addings for it, please do.

I'm now working on the unsupported/coverageio/org/geotools/coverage/io 
module, in order to split the MetadataBuilder class in two, a part that 
read metadata from a text file into the org.geotools.image.io.text 
package, the rest (which puts metadata read in the good node/leaf of the 
metadata tree) still lingers in the MetadataBuilder class.

Cheers,
Cédric.
> Cheers,
> Daniele
>
> -- 
> -------------------------------------------------------
> Eng. Daniele Romagnoli
> Software Engineer
>
> GeoSolutions S.A.S.
> Via Carignoni 51
> 55041 Camaiore (LU)
> Italy
>
> phone: +39 0584983027
> fax: +39 0584983027
> mob: +39 328 0559267
>
>
> http://www.geo-solutions.it
>
> -------------------------------------------------------
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geotools-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>   


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to