<html style="direction: ltr;">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;" bidimailui-charset-is-forced="true"
bgcolor="#FFFFFF" text="#000000">
<font face="Arial">Hi</font><br>
<br>
<div class="moz-cite-prefix">On 17/07/2016 02:42, Ken Mankoff wrote:<br>
</div>
<blockquote cite="mid:m2fur92lro.fsf@gmail.com" type="cite">
<pre wrap="">Hi Grass List,
I have a newbie question about reprojecting data. I know how to import data if it has a coordinate system with an EPSG code, or even sometimes without. Now I have some data which is UTM 33X. I can import it just fine, with
</pre>
</blockquote>
First, I have never heard of UTM 33X. Normally UTM zones are either
north or south. So you might have UTM 33N, or UTM 33S. All UTM north
zones that are based on the WGS84 datum are numbered: 326zz, where
zz is the zone. So if your data is in UTM 33N, the EPSG code will
be 32633. All UTM south projections (again based on WGS84) are
numbered 327zz, with the zz=zone again. <br>
<br>
<blockquote cite="mid:m2fur92lro.fsf@gmail.com" type="cite">
<pre wrap="">
grass70 -c -e file.grd ./grass/foo
But the region is then (from =g.region -p=),
</pre>
</blockquote>
Next, g.region does not affect the projection. Only the region
(extents and resolution) within the current LOCATION's projection.<br>
<br>
<blockquote cite="mid:m2fur92lro.fsf@gmail.com" type="cite">
<pre wrap="">
projection: 0 (x,y)
zone: 0
north: 8562350
south: 8545750
west: 509450
east: 519550
nsres: 100
ewres: 100
rows: 166
cols: 101
cells: 16766
And if I'm in another projection, and I try to import with =r.proj=, it does not work:</pre>
</blockquote>
<br>
The r.proj module does not import. Rather it does reprojection
between one CRS and another.<br>
<br>
<blockquote cite="mid:m2fur92lro.fsf@gmail.com" type="cite">
<pre wrap="">
WARNING: <PROJ_INFO> file not found for location <foo>
ERROR: Unable to get projection info of input map
The data provided told me this is UTM Zone 33X. There doesn't appear to be an EPSG code for that. Any advice will be much appreciated.
</pre>
</blockquote>
<br>
So: I think you should setup a GRASS LOCATION and MAPSET (using the
wizard) based on the EPSG code 32633 (or 32733 if your data is UTM
33S), then, within a GRASS session in that LOCATION just do: <br>
<tt>r.in.gdal -c input=file.grd output=file<br>
<br>
<br>
</tt>
<blockquote cite="mid:m2fur92lro.fsf@gmail.com" type="cite">
<pre wrap="">
Thanks,
-k.
_______________________________________________
grass-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Micha Silver
Arava Drainage Authority
+972-523-665918</pre>
</body>
</html>