>> http://www.asprs.org/a/resources/grids/10-99-norway.pdf > >After a quick skim of that article, I'm not sure why you sent it. It doesn't mention 33X, and only,
in these documents there are sometimes nice informations about special cases of projections, grids etx in some regions of the world. >> maybe it helps to define a GRASS location for this area for your own. > >I'm not sure what you mean by "define a GRASS location for this area for your own". you can define a location by define all needed parameters manually, have a look at the GRASS startup wizzard >I think I've done >that (or more correctly GRASS has done that): > >grass70 -text -c -e file.grid ./grass/foo >grass70 -text ./grass/foo/PERMANENT >r.import input=file.grd output=f please post the output of g.proj -p (https://grass.osgeo.org/grass73/manuals/g.proj.html) and also post the output of: gdalinfo file.grid or try: testepsg file.grid (see attached the file gdal_testepsg_espsg_32633.txt <http://osgeo-org.1560.x6.nabble.com/file/n5276749/gdal_testepsg_espsg_32633.txt> of the example testepsg EPSG:32633 to get an idea which parameters are needed to define a projection). >But being a newbie to grass, I don't know how to get it out of this location and into another location for >analysis that requires other data. the outputs of g.proj -p and/or gdalinfo file.grid are needed to see which parameters may be missing for a successfull reprojection into another location. ----- best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/UTM-33x-tp5276714p5276749.html Sent from the Grass - Users mailing list archive at Nabble.com. _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
