Dear all,
probably this is not the only place where I should have write, but JGrass is
a bridge between GRASS and uDig and for this reason I'm writing here.

I have a geotiff  http://n2.nabble.com/file/n2254422/file1.tif file  I'm
able to load in JGrass. Then I import it with JGrass in a grass mapset, and
I make some JGrass works with it (i.e. slope calculation). At the end I
export it as geotiff. I make this because this format gives me the
opportunity to exchange and archive simply the result of my geospatial
process.

The problem is that it's impossible to open in JGrass 
http://n2.nabble.com/file/n2254422/from_jgrass.tif this JGrass   exported
geotiff file.

To open it properly, I must use gdal libraries:
  > gdal_translate -a_srs epsg:23033 input.tif output.tif 

There are several 
http://n2.nabble.com/file/n2254422/file1%2Bvs%2Bfrom_jgrass.pdf differences  
between these metainfo files: that one that makes it impossible to open the
last file in uDig is the lack of this raw: AUTHORITY["EPSG","23033"].

I know this is a problem related to standards, and it's in some way more
related to GRASS. Do you have some advice to solve this unpleasant
incompatibility. Is there in this list some GRASS experienced user or some
geotiff experienced user?

I think that to solve this problem would be a benefit for grass, udig and
jgrass users.

Best regards,

Andrea




-----
Andrea Borruso

----------------------------------------------------
email: aborr...@tin.it
website: http://blog.spaziogis.it
my 2.0 life: http://aborruso.storytlr.com/
feed: http://feeds2.feedburner.com/Tanto
38° 7' 48" N, 13° 21' 9" E
----------------------------------------------------
-- 
View this message in context: 
http://n2.nabble.com/About-GRASS%2C-uDig-and-GeoTiff-tp2254422p2254422.html
Sent from the JGrass-devel -- Developer list for jgrass mailing list archive at 
Nabble.com.

_______________________________________________
JGrass-devel mailing list
JGrass-devel@dev.fsc.bz.it
https://dev.fsc.bz.it/cgi-bin/mailman/listinfo/jgrass-devel

Reply via email to