mkgmap_svn_index: sending one tile always works, several tiles sometimes

Basically the subject title says everything. For some tiles I can up to 4-5 tiles and sending to gps with Basecamp/Mapsource works. Other tiles however only transfer if one sends them as single tile. Anyone found out a reason? It seems to be independant of the maxnodes value (usually I use 1200000 but also 550000 failed). The same regions as before seem to cause the problems. So I think it must be dependant on some (missing?) data that causes the problem.

Hello
Basically the subject title says everything. For some tiles I can up to 4-5 tiles and sending to gps with Basecamp/Mapsource works. Other tiles however only transfer if one sends them as single tile.
Anyone found out a reason?
I found a group of three tiles, I can send any two of the three but not all three. So it seems like it a conflict between tiles rather than something to with a particular tile. Can you always send two if they are not adjacent? From experiments I believe that it is something to do with cities too, or streets within cities. ..Steve

Am 13.02.2011 18:30, schrieb Steve Ratcliffe:
Can you always send two if they are not adjacent?
Tried some combinations. It always worked without crash when the selected tiles are not adjacent. 2 adjacent tiles sometimes work. Chris

Can you always send two if they are not adjacent?
Tried some combinations. It always worked without crash when the selected tiles are not adjacent.
2 adjacent tiles sometimes work.
It was an idea I had while writing the email. Thanks for testing it out so quickly. Interesting... ..Steve

On 13.02.2011 18:30, Steve Ratcliffe wrote:
Hello
Basically the subject title says everything. For some tiles I can up to 4-5 tiles and sending to gps with Basecamp/Mapsource works. Other tiles however only transfer if one sends them as single tile.
Anyone found out a reason?
I found a group of three tiles, I can send any two of the three but not all three. So it seems like it a conflict between tiles rather than something to with a particular tile.
Can you always send two if they are not adjacent?
Seems so on a quick test. I have not found a group of three with your behaviour though. There seem to be certain tiles that block for me as soon as they are sent with an adjacent one... For others the same as you experienced is valid: OK OK Not OK:
From experiments I believe that it is something to do with cities too, or streets within cities.
..Steve

Hello Right I think I have got it. I've now sent a complete set of 51 tiles down to my Legend. Ironically I couldn't find a pair of adjacent tiles that didn't work, only well separated ones. My thinking was that it was probably down to cities with the same name in different tiles and that this was most likely in tiles next to each other. The problem was indeed with repeated city names so your observations helped, thanks. ..Steve
Seems so on a quick test. I have not found a group of three with your behaviour though. There seem to be certain tiles that block for me as soon as they are sent with an adjacent one... For others the same as you experienced is valid:

On 13.02.2011 23:32, Steve Ratcliffe wrote:
Hello
Right I think I have got it. I've now sent a complete set of 51 tiles down to my Legend.
Ironically I couldn't find a pair of adjacent tiles that didn't work, only well separated ones. My thinking was that it was probably down to cities with the same name in different tiles and that this was most likely in tiles next to each other.
The problem was indeed with repeated city names so your observations helped, thanks.
..Steve
Seems so on a quick test. I have not found a group of three with your behaviour though. There seem to be certain tiles that block for me as soon as they are sent with an adjacent one... For others the same as you experienced is valid:
Can confirm it, with 1850 sending maps works fine - though somehow the "building map set" phase in Mapsource when sending maps takes quite long, never noticed this before. Not tried out on GPS yet though....
participants (3)
-
Chris66
-
Felix Hartmann
-
Steve Ratcliffe