Follow-up Comment #3, bug #36261 (project maposmatic):
Apart from figuring out why MapOSMatic passed those parameters for this job
and preventing that, I think this kind of error should probably also be
checked for in OcitySMap.
Some people might prefer to use the latter with a different front-end or
straight up from the command-line, in which case a fix in the former doesn't
do anything.
As far as the OcitySMap part goes, rather than checking if Lat1 - Lat2 == 0 or
Lon1 - Lon2 == 0, how about that bit of code that adjusts the bounding box to
accommodate the paper size check for this error? Maybe it can also enforce a
minimum height/width in km of the mapped area?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?36261>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
