tdb wrong NSEW limits
@Steve I've been wondering why maps covering only a small area disappear when zooming in on Mapsource. I've looked at the limits in the overview section of a tdb,4.07 and realised to my surprise that N & S are identical, and so are E & W. The img correctly contains the following limits. N 50.7405 & S 50.7387 W -3.4688 & E -3.4647 in the TDB I notice: N & S 50.7568 E & W -3.4716 Replacing them with those found in the img & recompiling them in my own tdb compiler solves the problem I'm using mkgmap 2486 -- View this message in context: http://gis.19327.n5.nabble.com/tdb-wrong-NSEW-limits-tp5751792.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Have delved a bit deeper and noticed wrong pointers (&21) to TRE1 in the preview img . So it's not just the tdb file. -- View this message in context: http://gis.19327.n5.nabble.com/tdb-wrong-NSEW-limits-tp5751792p5751872.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
On 04/03/13 14:31, n Willink wrote:
Have delved a bit deeper and noticed wrong pointers (&21) to TRE1 in the preview img .
So it's not just the tdb file.
The bounds are rounded that way on purpose. We could make a special case and make sure that dimensions are never zero. It is also possible that the reason why we do the rounding is not actually necessary. Having map bounding boxes that overlap is allowed since it unavoidable when the map boundary is not rectangular. ..Steve
participants (2)
-
n Willink -
Steve Ratcliffe