|
From: andrea a. <and...@gm...> - 2008-05-26 16:45:28
|
Morning Jody, > That is because I have not been able to sit down the interested parties and > hammer out an "high level" API yet. They have a low level api in the form of > a Format / Reader / Writer combo that is based on a dead OGC specification > about "Grid Coverage Exchange". Here are user doc pages with examples: > - http://docs.codehaus.org/display/GEOTDOC/08+Coverage > - http://docs.codehaus.org/display/GEOTDOC/01+Format > - http://docs.codehaus.org/display/GEOTDOC/GeoTIFF+Plugin Thanks, I already browsed those once and I missed the importance of 01format. I'll have a better look. > The difficulty here is the example for "Format" above; the read parameters > are not quite enough information to make a pretty dynamic API allowing a > user to set the connection parameters. Here is the proposal our best guess > on what needs to be built (ie base our work off the WCS specification which > at the very least is not dead). > - > http://docs.codehaus.org/display/GEOTOOLS/GridAccess+based+on+WCS+Specification Hmm... wcs... I like that... for udig? :) > See above; you will be making an AbstractGridCoverageReader or some such... >> >> Any hint here? Any help very appreciated, > > I will be on IRC; and if you want we can troll through the test case > examples looking up a few more examples. Thanks Jody, I will first have to study a bit though, don't want to torment you before I do not have a better picture on the coverage-imageio "mappings". One question though: I didn't expect that many deprecated classes at that level. I checked out the arcgrid plugin and there are some of them. Is that ok? I'm pretty sure I have the right code.... but... Andrea > Jody > |