On 25 Mar 2010, at 7:50 , Carsten Schwede wrote:
> Hi,
>
> Am 25.03.2010 15:27, schrieb Apollinaris Schoell:
>> for rectangle tiles with correct bounding box info mkgmap will create
>> the boundary nodes. there is no need to do it in splitter. Mark added
>
> We use a special splitting program t
Hi,
Am 25.03.2010 15:27, schrieb Apollinaris Schoell:
> for rectangle tiles with correct bounding box info mkgmap will create
> the boundary nodes. there is no need to do it in splitter. Mark added
We use a special splitting program that cares about the ways. All ways
are complete in one tile, a
>>
> I think you got it right, although I have not tested it yet, and it is
> different than the way gpsmapedit does it. If B is tagged as a boundary
> node in both tiles then it should work. That is the way it works in
> other garmin map compilers, so it should be an underlying feature of the
Carsten Schwede wrote:
> Hi,
>
> Am 25.03.2010 10:42, schrieb garvan.m...@online.com.kh:
>
>> Before splitting the nodes are like this
>>
>> C
>> |
>>A-B
>> |
>> |
>> D
>>
>
> Right.
>
>
Hi,
Am 25.03.2010 10:42, schrieb garvan.m...@online.com.kh:
>
> Before splitting the nodes are like this
>
> C
> |
>A-B
> |
> |
> D
Right.
> After splitting the nodes are like this
> with a new n
Quoting Carsten Schwede :
> Hi there,
>
> last I have read here on the mailing list about the tag for routing over
> the tile boundary.
>
> Since we dont use splitter for cutting the planet my question is on
> which nodes must this tag be?
>
> A sample:
>
> Tile1 # Tile2
># C
>
Hi there,
last I have read here on the mailing list about the tag for routing over
the tile boundary.
Since we dont use splitter for cutting the planet my question is on
which nodes must this tag be?
A sample:
Tile1 # Tile2
# C
# |
A-#---B
# |
