Hi Rodrigo,
>
> I've spoken with the developers of Brazilians maps and they told me that
> probably the problem is not with the map boundaries.
>
> If on one hand the your official Garmin maps works with QLandkarte, on
> the other hand the Brazilian free maps works with Mapsource
>
> Does anyone have ever tested before QLandkarte with a map that contain
> negative latitude and longitude? I'm asking because I've just tested
> QLandkarte with Australian maps
> (
http://www.gpsoz.com.au/tracks4australia/) and it works perfectly.
> After I've tested with Argentinian maps
> (
http://www.proyectomapear.com.ar/), also with negative latitude and
> longitude, and I've got the same problem. In order to find the map I
> need to first zoom out.
>
> What do you think?
yes, negative coordinates are always a good source of bugs. However
before I can tell you if there is a bug in QLandkarte I need sensible
values.
You can check yourself: In CGarminDBMap.cpp line 267 ff. I read the
north/east/south/west extends from the *tdb file. Those are 24 bit
values stored in a 32 bit type shifted to the left boundary. The DEG
macro will convert them to values in [°]. A debug message will print
north east south west
8.4375 -2.14577e-05 -2.14577e-05 -2.14577e-05
In hex values:
0x06000000 0xFFFFFF00 0xFFFFFF00 0xFFFFFF00
If you take a hex editor and have a look at the tdb file you will find
the start of section 0x42 at 0x00b9. Use the tdb_map_t structure to
decode the section. The north value will start at 0x00C4. All values are
coded little endian. That proves that QLandkarte reads the values from
the tdb correctly.
In other words: Fix that tdb file and then we have a look if I hit the
famous negative coord. bug once again
Oliver
. 
