QTileRenderer & Canada somewhat broken

[GoogleCodeExporter]

While the current revision already improves things, Canada still causes several 
problems.

I used the Canada data set from: http://monav.openstreetmap.de/

* Some edges seem the use the wrong coordinate, creating the fan-like 
structures in image 1
* When zooming in very far nothing is displayed and the console log states 
"Failed to find index". Maybe an overflow issue ( Canada has negative longitude 
). Labels are displayed correctly, though. See image 2.

Original issue reported on code.google.com by veaac.fd...@gmail.com on 22 May 2011 at 10:59

Attachments:

• [Screenshot - 05232011 - 12:51:04 AM.png](https://storage.googleapis.com/google-code-attachments/monav/issue-53/comment-0/Screenshot - 05232011 - 12:51:04 AM.png)
• [Screenshot - 05232011 - 12:51:42 AM.png](https://storage.googleapis.com/google-code-attachments/monav/issue-53/comment-0/Screenshot - 05232011 - 12:51:42 AM.png)

[GoogleCodeExporter]

Maybe this is caused by Canada being partly outside the projection OSM and 
MoNav employs. This means there might be negative coordinates for parts of the 
country ( way north ).

Original comment by veaac.fd...@gmail.com on 5 Jul 2011 at 9:22

[GoogleCodeExporter]

i get a similar looking error with the new zealand mapset 
at certan zoom levels the roads go like the first screenshot but i also get 
random missing parts of the road ( cut out in such a way it appears a square is 
missing)
i also get some towns showing up at odd zoom levels - maybe just a corrupt file 
in the download? will ty a locally generated one tommorw ...hopefully

Original comment by chainsawbike@gmail.com on 17 Jul 2011 at 11:17

[GoogleCodeExporter]

this issue is fixed for me with updated builds
client - 0.3 release 3 +hg5585bb4a8d77 ( n900 )
preprocessor "changeset:   507:23b2fd7f5b5f" used for locally pre-processing 
the data

thanks :)

Original comment by chainsawbike@gmail.com on 4 Oct 2011 at 9:06