> Is JGrass available as a library that I could place into uDig? We are > limping with geotools coverage support > right now (all the cool kids are on a branch fixing it, for an update > see the last IRC logs on the geotools > website). We are also working with OSSIM, in a manner similar to you - > JNI bindings.
JGrass isn't a library at the moment, but the future effort is that to create a modular structure as geotools has. From that point on it will be easy to use. > You may do better to look at what simboss is doing right now based on > ISO specs. There are a couple pdfs you can > read as well. Indeed, I will :) > > Yes and no, we try to exploit everything that already is there in GRASS, > > therefore we started with JNI binding. Very soon that got a killing thing > > for the portability and we started to port the most important (in our > > eyes) parts, which included the raster I/O and some modules. The choice > > was in direction hydro-geomorphology, because the jobs done in that field > > supported the development. > > Sweet. Sweet and sour to be exact :) > Indeed, I am looking forward to being through this. However next time > please give us feedback - we are only so many > minds and any holes you find would be great to point out. If you are > interested the improvements are available for reivew, > although I have not yet added operation support. No, I found your interfaces (I used the features part) really good. Just they were different from ours and so we forced then temporarily to fit... like squares in triangles. Which temporarily works, but in a long period isn't that nice. Ciao, Andrea > Jody > > > My warmest regards, > > Andrea > > > >> 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 -- ____________________________________________________________________________ HydroloGIS - Environmental Safety Modelling www.hydrologis.com Andrea Antonello Environmental Engineer mobile: +393288497722 "Let it be as much a great honour to take as to give learning, if you want to be called wise." Skuggsja' - The King's mirror - 1240 Reykjavik ____________________________________________________________________________ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
