This is great!
The ideal thing to do would to make it a full geotools coverager reader,
so that it fits in to our APIs - it would be the same for the programmer
to work with geotiff, grib, or grass binary, and would then be available
for display through uDig and GeoServer.
If you're interested in learning geotools more that would be great, or
what we could do is start a grass module, and await a future volunteer
to put it in to the api, while also allowing anyone to make use of the
reader.
I'm interested in learning more about JGrass, as it seems like there
could be some more overlap, less replication of work.
It looks like JGrass is pure java, is that right? So it's sort of a
complete re-write of Grass? To have similar functionality, but written
for Java?
What data formats do you read? This to me seems like the most sensible
area of overlap. GeoTools defines a very good feature model for
vectors, and we read in shapefile, postgis, oracle, db2, WFS, GML,
MySQL, and coming VPF and MapInfo. We're still working on good raster
interfaces, based on some ISO spec (sorry, not my area of expertise),
and experimenting with some very nice speed improvements. So we could
perhaps work on the same set of data readers, or at least share
interfaces with GeoAPI (http://geoapi.sourceforge.net) and then be able
to use one another's readers.
We're also hoping to eventually have an operations API, which I feel
like is where GRASS excels. It could be a big win if we collaborate on
that, as they could then be used in uDig, or in GeoServer as a WPS.
It looks like you guys are GPL, so it would make sense to collaborate on
the interfaces, keep them in GeoTools/GeoAPI, and then keep your
algorithms and implementations in JGrass.
Just a few thoughts, but thanks a lot for taking the time to start
collaborations, it would be great if we can get more cross overs.
best regards,
Chris
Andrea Antonello wrote:
Hi folks,
I could finally force myself to extract the GRASS binary reader from the
JGrass code and make a small standalone versione, cleaning up all the JGrass
dependent code.
I would really love to see that added to the geotools package at some point,
since the GRASS raster binary format is a highly important format because of
the importance of GRASS.
In the attched zip you can find the base classes reduced to the bone and a
TestGrassRasterReader class to see how it works.
The class reads a raster map and writes it to ascii. The steps should be
clear. I also tried to document as well as possible the various steps. I hope
you will enjoy it.
My best regards and my contribution to this important osgeo community,
Many thanks
Andrea
--
Chris Holmes
The Open Planning Project
thoughts at: http://cholmes.wordpress.com
begin:vcard
fn:Chris Holmes
n:Holmes;Chris
org:The Open Planning Project
adr:;;377 Broadway, 11th Floor;New York;NY;10013;USA
email;internet:[EMAIL PROTECTED]
title:VP, Strategic Development
x-mozilla-html:FALSE
url:http://topp.openplans.org
version:2.1
end:vcard
