David Blasby a écrit :
IF YOU ARE INTERESTED IN GRID COVERAGES OR THINK GRID COVERAGE WORK WILL
AFFECT YOU - PLEASE SPEAK UP NOW.
Of course I am :)
Sorry for having been unable to attempt to the IRC early enough to catch the coverage discussion...
But there is some quick note from my reading of IRC log:
- Of course I support Simone's suggestion to "hide" GDAL behind the J2SE Image
I/O API.
Same apply for OSSIM operations behind JAI operators.
- Axis flipping: there is an option to turn it on/off with EPSG-HSQL or
EPSG-Access:
OrderedAxisAuthorityFactory.register("EPSG");
But it should be considered as a temporary solution for allowing applications
to make
their transition toward a more robust axis handling. I guess that this is the
switch
that uDig is using.
- The GO-1 module has basic classes for a new renderer with more rigourous axis
support.
It take advantage of GO-1 specification (which help to clarify some aspects),
as well
as the experience I gained with J2D renderer (which was already handling axis
flipping
for a long time). You may notice that the package javadoc is in large part
about CRS:
http://javadoc.geotools.fr/snapshot/org/geotools/display/canvas/package-summary.html
Note that this basic classes there are build with 3D rendering in mind (i.e.
the basic
classes are nD; only the ReferencedCanvas2D subclass is 2D specific). As
specified in
GO-1 specification, they are also build with various output device geometries
in mind
(i.e. the output device may not be a flat screen; it could also be a
planetarium dome.
No Geotools's renderer currently consider this eventuality).
I admit that I have been away of ext/go development, as well as
module/coverage, for
much longer than I expected. I'm stuck with an internal project which is
eating most
of my energy currently.
- Now about the GridCoverage merge: I would like (if possible) to participate
to the
merge in referencing and coverage modules (I'm afraid that I will not be
available
for participating to the merge in other modules like streaming renderer,
until my
internal project is finished). Since I know well "module/referencing" and
"module/coverage",
I may have a chance to point out unoticed issues and propose solution during
the
merge process.
There is my time frame: I'm completly stuck right now with a project unrelated to Geotools. If I can
free some time, I will put my energy in the grid coverage merge (referencing and coverage modules
only) as the top priority when Simone will tell us that he is ready for doing the merge. I'm not
sure however how much time I will be able to invest during the next 3 months. However, I will leave
my current job no later than July 27 and have some hope that my next place will give me more
opportunities to work on fundamental (for my work) geotools modules. Sorry for being so vague; it is
not possible for me to give a clear schedule right now... Of course if I can't free myself when the
merge process will be ready to start, don't wait for me.
Martin.
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
