Juli 2, 2015 um 11:35 #5233
JohnPercyTeilnehmerJuli 2, 2015 um 13:34 #5235Juli 2, 2015 um 16:49 #5237
I too had found that the map displayed OK in Atlas but came to the conclusion that did not necessarily mean that the map was „OK“. If it was really „OK“ it would display OK in Atlas, Locus and all others map apps! I’ll ask the Locus folk and see..Juli 2, 2015 um 17:38 #5238
EmuxTeilnehmerJuli 4, 2015 um 11:58 #5252
I too had found that the map displayed OK in Atlas but came to the conclusion that did not necessarily mean that the map was “OK”. If it was really “OK” it would display OK in Atlas, Locus and all others map apps! I’ll ask the Locus folk and see..
If I would use the old MapWriter the problem with a very few tiles would not occur.
In the other hand it would be impossible to render the monster Water-MultiPolygons in the North of Canada, the woods in Japan. It would take ages even to render the mid of Sweden, Alaska, Parts of Russia aso…
So I had to make a decission.
Better a very few tiles redering wrong than a lot of countrys not rendering or with missing water and wood or with redicoulus render times.
Best regards, ChristianJuli 4, 2015 um 12:12 #5253Juli 4, 2015 um 18:50 #5254
Yes its an issue with the mapWriter too – thats the reason I modified the rendering process to allow different MapWriters for different Maps.
The MapWriter of the first MapsForge3 Version is slow and cant render big MPs.
The latest Versions of The MapWriter is rendering MUCH faster, allows big MPs, needs much more java heap and sometimes (not worth to mention) it produces strange results. I cant see a clear picture behind this behaviour so I use the Writer Version that is fine for the Map in question.
And – simple to say the TagMapping of the OAM is very close at the limits whats possible so ist hard to say whats going wrong in general.
Over all: nothing to worry about in the end.
Du musst angemeldet sein, um auf dieses Thema antworten zu können.