Dear All,
I'm using GRASS 6.3 (both linux and Win) and I need to reprojecting
raster data from Lat/Long WgS84 to UTM33N ED50.
I've defined a new location for UTM33-N ED50 with the corresponding EPSG
code (23033), but grass has reported this alert"
g.proj: WARNIG: DATUM unknown not recognized by grass and no parameters
found".
So, the new location datum is by default WGS84, not ED50.
it's a bug or I wrong anything?
Thanks
(my English sounds really bad)
On Sat, Jan 10, 2009 at 10:38 AM, edmondo.elisei
<edmondo.elisei@gmail.com> wrote:
Dear All,
I'm using GRASS 6.3 (both linux and Win) and I need to reprojecting
raster data from Lat/Long WgS84 to UTM33N ED50.I've defined a new location for UTM33-N ED50 with the corresponding EPSG
code (23033), but grass has reported this alert"
g.proj: WARNIG: DATUM unknown not recognized by grass and no parameters
found".
GRASS 6.4.svn (spearfish60):~ > g.proj -c epsg=23033 location=ed50
Location ed50 created!
GRASS 6.4.svn (spearfish60):~ > exit
grass64 ~/grassdata/ed50/PERMANENT/
GRASS 6.4.svn (ed50):~ > g.proj -w
PROJCS["UTM Zone 33, Northern Hemisphere",
GEOGCS["international",
DATUM["European_Datum_1950",
SPHEROID["International_1924",6378388,297]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",15],
PARAMETER["scale_factor",0.9996],
PARAMETER["false_easting",500000],
PARAMETER["false_northing",0],
UNIT["metre",1]]
Looks good to me.
So, the new location datum is by default WGS84, not ED50.
it's a bug or I wrong anything?
Which was your command to generate it?
Markus
(please keep the conversation on the list)
On Sat, Jan 10, 2009 at 12:37 PM, edmondo.elisei
<edmondo.elisei@gmail.com> wrote:
Dear Markus,
now I've followed your procedure:
from spearfish60 location (PERMANENT):
"g.proj -c epsg=23033 location=ed50 "
grass said:"Datum <unknown> not recognised by GRASS and no parameters found.
Location ed50 created!"
I've never encountered this problem before I installed 6.3svn
The message comes from
lib/proj/convert.c
Questions:
- did you change your installation (or of PROJ4)?
- could you use GRASS 6.4.0RC1 instead to see if the
problem persists (it works for me with that version):
http://trac.osgeo.org/grass/wiki/Release/6.4.0RC1-News
?
Markus
edmondo.elisei schreef:
Dear All,
I'm using GRASS 6.3 (both linux and Win) and I need to reprojecting
raster data from Lat/Long WgS84 to UTM33N ED50.I've defined a new location for UTM33-N ED50 with the corresponding EPSG
code (23033), but grass has reported this alert"
g.proj: WARNIG: DATUM unknown not recognized by grass and no parameters
found".So, the new location datum is by default WGS84, not ED50.
it's a bug or I wrong anything?
Thanks
(my English sounds really bad)
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
Hi Edmundo,
I face the same problem since I switched from SUSE10.2 to UBUNTU intrepid. In SUSE I never had any problems with grass 6.3 making a new location with EPSG codes. Since I switched however (and installed the 6.3 version via Les-Ejk repository) I get the same problem as you do with the Amersoort- RD new projection (EPSG code 28992). I get the message g.proj: Warning DATUM <unknown> not recognised....
However, if I print projection information form a location previously made within grass6.3 under SUSE, g.proj clearly does find a datum:
g.proj -p
-PROJ_INFO-------------------------------------------------
name : sterea
proj : sterea
datum : rd18
ellps : bessel
lat_0 : 52.15616055555555
lon_0 : 5.38763888888889
k : 0.9999079
x_0 : 155000
y_0 : 463000
no_defs : defined
-PROJ_UNITS------------------------------------------------
unit : metre
units : metres
meters : 1
I am also wondering if there is any relation with the problems Nikos and Paolo had with importing vectors in grass with version 6.3 under intrepid (see thread:
http://n2.nabble.com/gdal,-v.in.ogr,-Ubuntu-intrepid-td1886320.html
That's another new problem I did not encounter using Grass6.3 under Suse).
Until now I could not think of any solution (except making the step to version 6.4 as the problem doesn't seem to occur there)
Hoping somebody else comes with a smart idea.
Regards
Wout Bijkerk