Bug #569

pscoast -L produces wrong length map scale

Added by Eric about 3 years ago. Updated about 3 years ago.

Status:ClosedStart date:2014-05-29
Priority:NormalDue date:
Assignee:Paul% Done:

100%

Category:-
Target version:Candidate for next bugfix release
Affected version:all Platform:

Description

When using an oblique mercator projection (-JO) the map scale produced by pscoast -L is too large by a significant amount. Example script:

pscoast -L0/40/40/100 -Sgray -Df -Na -JOa0/40/90/6i -Ba1f15m -R-2/39.5/2/40.5r -P -K > test.ps
project -C0/40 -A90 -G100 -L-50/50 -Q | psxy -W4p,red -J -R -O -K >> test.ps
pscoast -L0/40/40/100 -Sgray -Df -Na -JM6i -Ba1f15m -R-2/2/39.5/40.5 -Y3i -O -K >> test.ps
project -C0/40 -A90 -G100 -L-50/50 -Q | psxy -W4p,red -J -R -O -K >> test.ps
psxy -J -R -O -T >> test.ps

The 'project' command produces a line the same length as the map scale. This works fine with a mercator projection -JM, but not with -JO.

This bug exists in version 5.1.1 as well as several older instances of version 4.

Associated revisions

Revision 13228
Added by Paul about 3 years ago

Address issue #569

History

#1 Updated by Paul about 3 years ago

  • Status changed from New to Resolved
  • Assignee set to Paul
  • Target version set to Candidate for next bugfix release

I've redone how the scale end points are computed in the map scale code and now your example works correctly. Please check revision r13228 and report back if there are other issues. I will then fix things in GMT 4 as well.

#2 Updated by Eric about 3 years ago

Looks great! Thanks for fixing it so quickly.

#3 Updated by Paul about 3 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100

Closing this issue as fixed.

Also available in: Atom PDF