[GRASS-user] UTM 33x

[Helmut Kudrnovsky]

>If I could get GRASS to define the lat,lon boundaries as I tried to do in my
last email, but without >crashing, wouldn't that solve this? 

mybe yes

>And perhaps I'm still confused, but the projection is *known*, even if it
isn't encoded in this file.

that's the point: the file itself is missing the projection information, see
your gdalinfo output:

"Coordinate System is `'"

and this information is needed for accurate re-projection for GIS.

>If this were known as 33N instead of 33X, I could define a location with an
EPSG code, and then import >with "r.in.gdal -o", where "-o" is "Override
projection (use location's projection)".

that would be the first what I may do (as mentioned in the GDAL ML thread):
try the data to import into  UTM 33N location and see if there are
distortions or any other problems at a first step.

another idea:

ask in the proj-ML (http://lists.maptools.org/mailman/listinfo/proj) and
maybe there metacrs (https://lists.osgeo.org/mailman/listinfo/metacrs).

the former is known for good advices for defining projections.

HTH



-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/UTM-33x-tp5276714p5276758.html
Sent from the Grass - Users mailing list archive at Nabble.com.