#378: g.region: weird w if input e=w
----------------------+-----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: default | Version: svn-develbranch6
Keywords: | Platform: All
Cpu: All |
----------------------+-----------------------------------------------------
In a latlon location specifing e=w gives a weird w border. E.g.:
#378: g.region: weird w if input e=w
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: default | Version: svn-develbranch6
Resolution: | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Comment (by hamish):
It is ambiguous, do you want 0 columns or 360? What is the goal?
g.region -p says:
e 180E
w 180E
anyway I think that it handles the ambiguous input as best as can be
expected, I don't see the problem here. Possibly throw an error message
out complaining that it has to guess what you meant, but as there cannot
be 0 columns, the only valid choice is the 360 case.
A bug would be if the global wrap around magic fails with e>360.