Hi there, last I have read here on the mailing list about the tag for routing over the tile boundary. <tag k='mkgmap:on-boundary' v='1' /> 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 # | # | # D # tile boundary Our cutting creates the tiles so, that node A and the way between A and B i in the Tile 1. The nodes B, C, D and the way between them are in the Tile 2. Must the node B have the special on-boundary tag in both tiles, or only in the tile 1? -- Best wishes Computerteddy
Quoting Carsten Schwede <computerteddy@gmx.de>:
Hi there,
last I have read here on the mailing list about the tag for routing over the tile boundary. <tag k='mkgmap:on-boundary' v='1' />
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 # | # | # D
# tile boundary
Our cutting creates the tiles so, that node A and the way between A and B i in the Tile 1. The nodes B, C, D and the way between them are in the Tile 2. Must the node B have the special on-boundary tag in both tiles, or only in the tile 1?
This is what I have understood. Before splitting the nodes are like this C | A-------------B | | D After splitting the nodes are like this with a new node S inserted into A-B. Tile1 # Tile2 # # C # | A-----S-------B # | # | # D The node S must appear in both tiles and be flagged as a boundary node in both for routing to work. In gpsmapedit you have external nodes that allow routing across different img files. The external nodes do not have to be on the tile boundary they could be international border crossing points. I am hoping the new boundary tags work like this. You are unlikely to need to use this tag unless you are splitting your maps using some external tool because - as I understand it - if you use splitter then mkgmap trims the routes correctly. I plan to try splitting using gpsmapedit. Garvan
Hi, Am 25.03.2010 10:42, schrieb garvan.maew@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 node S inserted into A-B.
Tile1 # Tile2 # # C # | A-----S-------B # | # | # D
No there isnt a new node S after cutting. After cutting the tiles look like this: Tile 1 A-------------B Tile 2 C | B | | D The boundary node is now B. Its apperas in both tiles.
The node S must appear in both tiles and be flagged as a boundary node in both for routing to work.
So I think it could be ok with B tagged as boundary node in both tiles.
You are unlikely to need to use this tag unless you are splitting your maps using some external tool because - as I understand it - if you
I use a own tile splitter. -- Viele Gruesse Computerteddy
Carsten Schwede wrote:
Hi,
Am 25.03.2010 10:42, schrieb garvan.maew@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 node S inserted into A-B.
Tile1 # Tile2 # # C # | A-----S-------B # | # | # D
No there isnt a new node S after cutting.
After cutting the tiles look like this:
Tile 1
A-------------B
Tile 2 C | B | | D
The boundary node is now B. Its apperas in both tiles.
The node S must appear in both tiles and be flagged as a boundary node in both for routing to work.
So I think it could be ok with B tagged as boundary node in both tiles.
You are unlikely to need to use this tag unless you are splitting your maps using some external tool because - as I understand it - if you
I use a own tile splitter.
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 garmin format. Garvan
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 garmin format.
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 the feature long time ago to allow polygon shaped maps where the boundary node is not on the rectangular bounding box. to my knowledge no splitter exists which supports cutting into polygon shaped files and is able to insert the boundary nodes.
Garvan
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
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, also with all nodes. They will never be cutted.
the feature long time ago to allow polygon shaped maps where the boundary node is not on the rectangular bounding box. to my knowledge no splitter exists which supports cutting into polygon shaped files and is able to insert the boundary nodes.
We want to extend our splitting program to insert this boundary nodes on the end of the ways, not on the boundary of the boundary box. -- Viele Gruesse Computerteddy
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 that cares about the ways. All ways are complete in one tile, also with all nodes. They will never be cutted.
that is fine. mkgmap will clip them anyway if there is a bounding box in the osm file. without bbx the whole way is kept in both tiles. not sure if routing will still work.
the feature long time ago to allow polygon shaped maps where the boundary node is not on the rectangular bounding box. to my knowledge no splitter exists which supports cutting into polygon shaped files and is able to insert the boundary nodes.
We want to extend our splitting program to insert this boundary nodes on the end of the ways, not on the boundary of the boundary box.
should work too if you don't use a bbx or the bbx is covers all ways and mkgmap doesn't need to clip and doesn't need to insert boundary nodes. btw there is also a mkgmap option to ignore the bbx
-- Viele Gruesse Computerteddy _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
Apollinaris Schoell -
Carsten Schwede -
Garvan & maew -
garvan.maew＠online.com.kh