[GRASS-user] problem with disk space. Raster data

[Antonio Rodríguez]

Hi Helmut,
The process was as follows:
1) I defined a newlocation with the coordinates in lat/lon of the NE and SW
corners of the area of the data file, converted to UTM, previously
defining the EPSG code (in my case 32718)
2) Once in Grass I imported my data file (Aster Dem, geotiff format) with
the r.in.gdal tool and forced the data to use the projection defined in my
newlocation. Everything went fine and I am able to visualize my dem with
its new UTM coordinates.

Any idea?
Cheers!
Antonio






El domingo, 16 de septiembre de 2012, Helmut Kudrnovsky escribió:

> >The problem arise when after creating a newlocation with the
> >corresponding lat/lon coordinates transformed to UTM ones I try to
> >follow the steps above.
>
> how did you reproject the data?:
>
> within grass (r.proj) or outside grass (i.e. gdalwarp,...)?
>
> can you post the command for raster-reprojection and g.region -p of the
> Lat/Lon-location and the UTM-location.
>
>
>
> -----
> best regards
> Helmut
> --
> View this message in context:
> http://osgeo-org.1560.n6.nabble.com/problem-with-disk-space-Raster-data-tp5002151p5002153.html
> Sent from the Grass - Users mailing list archive at Nabble.com.
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org <javascript:;>
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20120916/29a0a70b/attachment.html>