this bug's URL: http://intevation.de/rt/webrt?serial_num=3172
Request number 3172 was commented on by 'msieczka' (Maciek Sieczka).
Responding to this message will send mail to the requestor.
Request Tracker
rt@intevation.de
--------------------------------------------------------------
Cc: grass5@grass.itc.it
Folks
Nobody has answered on this bug. Is it really neglectable you think? Whos is
taking care of d.where?
Cheers
-------------------------------------------- Managed by Request Tracker
I read it before and it does sound like a bug, but there wasn't enough information in the bug report for me to see what was wrong. It would be good if you could drill it down to a single test point working with cs2cs and reproduce the results that way. Should be easy to fix then.
Another thing to try (if you still have GRASS 5.4 around) is to try separately with --without-proj and --with-proj options to the configure script. The built-in proj in GRASS does things a little bit differently from remotesensing.org proj with regards to interpreting datum paramters as part of a co-ordinate system (i.e. it tries to ignore them if they are only specified as part of one of the co-ordinate systems being projected from/to).
Paul
On Wed, 11 May 2005, Maciek Sieczka via RT wrote:
this bug's URL: http://intevation.de/rt/webrt?serial_num=3172
Request number 3172 was commented on by 'msieczka' (Maciek Sieczka).
Responding to this message will send mail to the requestor.
Request Tracker
rt@intevation.de
--------------------------------------------------------------
Cc: grass5@grass.itc.it
Folks
Nobody has answered on this bug. Is it really neglectable you think? Whos is
taking care of d.where?
Cheers
-------------------------------------------- Managed by Request Tracker
_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5
From: "Paul Kelly" <paul-grass@stjohnspoint.co.uk>
I read it before and it does sound like a bug, but there wasn't enough information in the bug report for me to see what was wrong. It would be good if you could drill it down to a single test point working with cs2cs and reproduce the results that way.
But I did... In the bug report there *is* a comparison with the results from cs2cs. As you can see the E coordinate is the same in all 3 cases ("d.where -l", "d.where -w" and cs2cs) but in regard to N "d.where -w" and cs2cs are different from "d.where -l".
Should be easy to fix then.
Another thing to try (if you still have GRASS 5.4 around) is to try separately with --without-proj and --with-proj options to the configure script. The built-in proj in GRASS does things a little bit differently from remotesensing.org proj with regards to interpreting datum paramters as part of a co-ordinate system (i.e. it tries to ignore them if they are only specified as part of one of the co-ordinate systems being projected from/to).
I migrated to grass6 for good but if you decide it is critical to test the problem in 5.4 I can do it next week.
siema
Maciek