[GRASS5] [bug #3172] (grass) d.where -l is giving wrong results

Request Tracker grass-bugs at intevation.de
Thu Apr 21 06:29:59 EDT 2005

this bug's URL: http://intevation.de/rt/webrt?serial_num=3172

Subject: d.where -l is giving wrong results

Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: grass61_13_04_05_1052

Seems a serious one but I didn't dare to "critical" it.

I have a following mapset:

GRASS 6.1.cvs (caves_utm33):~ > g.proj -p
name       : Universe Transverse Mercator
proj       : utm
datum      : wgs84
a          : 6378137
es         : 0.0066943800
zone       : 33
no_defs    : defined
unit       : metre
units      : metres
meters     : 1

GRASS 6.1.cvs (caves_utm33):~ > g.region -p
projection: 1 (UTM)
zone:       33
datum:      wgs84
ellipsoid:  a=6378137 es=0.00669438
north:      5724924
south:      5724724
west:       572360
east:       572688
nsres:      1
ewres:      1
rows:       200
cols:       328

When query point's coordinates with d.where, I'm getting different results whether switch -l or -w is used:

d.where -l
EAST:             NORTH:               LON:               LAT:
        572500.425        5724830.725   16:02:54.226371E   51:40:11.746412N

d.where -w
WGS84 Co-ordinates
             EAST:             NORTH:               LON:               LAT:
        572500.425        5724830.725   16:02:54.226371E   51:40:11.179813N

It looks that "-l" is wrong, because cs2cs gives the same as "-w":

trawiarz at quercus trawiarz]$ echo "572500.425 5724830.725" | cs2cs +proj=utm +zone=33 +to +proj=latlong +ellps=WGS84
16d2'54.226"E   51d40'11.18"N 0.000

That's quite a difference: 17.51m N and 0.25m E.


-------------------------------------------- Managed by Request Tracker

More information about the grass-dev mailing list