On 25/02/08 18:57, andrea antonello wrote:
Hi Paul,
Can you give some specific examples? I think "all" sounds like a bit of a
generalisation. What is wrong with the internal GRASS functions
GPJ_grass_to_wkt() and GPJ_grass_to_osr()? Or the -p, -d, -j, -w and -e
options of g.proj? The GRASS representation can be converted to PROJ.4
format without using any external libraries at all, and to WKT format
using the OGR libraries of GDAL. PROJ.4 is not required at all for
converting to either of those.
I guess my point is that it is a reasonable requirement for other software
to use GRASS libraries to access data in GRASS locations, rather than
reverse engineering the internal GRASS database formats which can and will
change in future. But I suppose that is a topic definitely open to
debate?....
Why does it seem to strange that we want to base on the grass
database-workspace format to exploit GRASS as well as tools
implemented in java? Why should I always import/export data to do
calculations on them?
You haven't really answered Paul's question: What is the problem with
using the current g.proj '-w' or '-e' flags ?
Moritz
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
