Splitting an country borders?
Hi, is it possible to use or to set the splitter up in that way, that eg a europe map is split at the country borders? So it would be great to get a mapset for each country out of the europe mapset. Do you think this is possible? Thanks, Marco
you can use the downloads from geofabrik or cloudmade or use osmosis with country polygons and run splitter on this data. why duplicate the same functions in splitter? On 15 Sep 2009, at 14:45 , dom wrote:
Hi,
is it possible to use or to set the splitter up in that way, that eg a europe map is split at the country borders? So it would be great to get a mapset for each country out of the europe mapset. Do you think this is possible?
Thanks, Marco _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 09/16/2009 12:19 AM, Apollinaris Schoell wrote:
you can use the downloads from geofabrik or cloudmade or use osmosis with country polygons and run splitter on this data. why duplicate the same functions in splitter?
Because AFAIK those split files you cannot do this: - Take two or more adjacent countries, e.g. Germany and Austria - Make one Garmin map with mkgmap + splitter so you can route between all tiles
Hi, Ralf Kleineisel schrieb:
- Make one Garmin map with mkgmap + splitter so you can route between all tiles
What need mkgmap special to enable routing between tiles? I would like to use this special also in the cutting program I use for creating a completely routable worlmap... -- Viele Gruesse Computerteddy
mkgmap can create routable maps across tiles. This requires splitting on defined grids and is done with the splitter automatically It is not possible to stitch data from multiple Coudmade/Geofabrik downloads. They are broken at the boundary and this information is lost. For a world map split the whole planet with splitter and run it through mkgmap with option route. I had to lower max-nodes for splitter to 850000 for north America. some tiles in canada have a different node-way ratio and splitter still uses only node count to make the split decision. not perfect but still pretty large tiles. routing across tiles is not perfect and as efficient as on original Garmin maps. But it works pretty well already. On 16 Sep 2009, at 24:09 , Carsten Schwede wrote:
Hi,
Ralf Kleineisel schrieb:
- Make one Garmin map with mkgmap + splitter so you can route between all tiles
What need mkgmap special to enable routing between tiles? I would like to use this special also in the cutting program I use for creating a completely routable worlmap...
-- Viele Gruesse Computerteddy _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Wed, Sep 16, 2009 at 12:29:42AM -0700, Apollinaris Schoell wrote:
mkgmap can create routable maps across tiles. This requires splitting on defined grids and is done with the splitter automatically It is not possible to stitch data from multiple Coudmade/Geofabrik downloads. They are broken at the boundary and this information is lost.
I seem to remember someone mentioning that Garmin supports non-rectangular map tiles. Would that help? Or would it be too much effort with too little gain to implement that in mkgmap (and splitter)? Best regards, Marko
I seem to remember someone mentioning that Garmin supports non-rectangular map tiles. Would that help? Or would it be too much effort with too little gain to implement that in mkgmap (and splitter)?
I have seen a Garmin map with boundary points that do not lie on a rectangle so, it's plausible that the boundary between two tiles can be any shape. The important thing is that the coordinates of the boundary points have to be the same in both tiles so that the GPS can match them up. In principle, it should be quite possible to route across tiles that have a wiggly boundary. This could be achieved quite straightforwardly by the splitter tagging the boundary points so that mkgmap knows where they are. Mark
In principle, it should be quite possible to route across tiles that have a wiggly boundary. This could be achieved quite straightforwardly by the splitter tagging the boundary points so that mkgmap knows where they are.
The attached patch is possibly all you need in mkgmap to be able to route across non-straight boundaries - it simply recognises nodes that have been tagged with mkgmap:on-boundary=1. Note, that this is an XML attribute on the node element not an OSM "tag" element. The splitter would have to add this tag to the last point in each way that has been split at a tile boundary. Completely untested but it could be worth experimenting with. Mark
I seem to remember someone mentioning that Garmin supports non-rectangular map tiles. Would that help? Or would it be too much effort with too little gain to implement that in mkgmap (and splitter)?
I have seen a Garmin map with boundary points that do not lie on a rectangle so, it's plausible that the boundary between two tiles can be any shape. The important thing is that the coordinates of the boundary points have to be the same in both tiles so that the GPS can match them up.
In principle, it should be quite possible to route across tiles that have a wiggly boundary. This could be achieved quite straightforwardly by the splitter tagging the boundary points so that mkgmap knows where they are.
Yes, the official garmin maps have a not ractangular boundary and routing works perfect. So it is possible. The problem seems to be the osmosis data from geofebtric. They dont cut a line at the boundary and create a new node exact on the boundary, but instead simply drop the last segement, which crosses the border. If you try to merge two parts from geofabric, e.g. austria and germany, then all segments crossing the borderline are missing. (At least this was the case last time I tried it an year ago. There was an other thread on the list discussing this). So imho it would be an better idea to fix the osmosis sources than implement it to splitter.
This my answer. Not the expected, but I asked this. :-) Thanks. So is it possible to configure the splitter do split the maps not after x-Number of nodes but at these coordinates? Or is it posilbe to do a presplit, which creates a tile for each country and then in a second step splitting the country files? Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map. Marco Johann Gail schrieb:
I seem to remember someone mentioning that Garmin supports non-rectangular map tiles. Would that help? Or would it be too much effort with too little gain to implement that in mkgmap (and splitter)?
I have seen a Garmin map with boundary points that do not lie on a rectangle so, it's plausible that the boundary between two tiles can be any shape. The important thing is that the coordinates of the boundary points have to be the same in both tiles so that the GPS can match them up.
In principle, it should be quite possible to route across tiles that have a wiggly boundary. This could be achieved quite straightforwardly by the splitter tagging the boundary points so that mkgmap knows where they are.
Yes, the official garmin maps have a not ractangular boundary and routing works perfect. So it is possible.
The problem seems to be the osmosis data from geofebtric. They dont cut a line at the boundary and create a new node exact on the boundary, but instead simply drop the last segement, which crosses the border. If you try to merge two parts from geofabric, e.g. austria and germany, then all segments crossing the borderline are missing. (At least this was the case last time I tried it an year ago. There was an other thread on the list discussing this).
So imho it would be an better idea to fix the osmosis sources than implement it to splitter.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
So is it possible to configure the splitter do split the maps not after x-Number of nodes but at these coordinates?
No, this is not what I have written. There is some missunderstanding. The recent splitter is not able to split at geographical boundaries. This is the task of osmosis. Maybe it is not too complicated to build this feature into splitter, but at the moment it doesn't.
Or is it posilbe to do a presplit, which creates a tile for each country and then in a second step splitting the country files?
Yes, this way should work. But for the presplitting you can't use splitter. I don't use osmosis by myself, so I don't know internals of it. But I know, that geofabrik splits its regions with osmosis.
Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map I would expect the interstate routing to work. Precondition is obviously that the presplitted tiles don't miss any segments at the border and the border nodes have exactly the same coordinates.
Regards, Johann
Johann Gail schrieb:
So is it possible to configure the splitter do split the maps not after x-Number of nodes but at these coordinates?
No, this is not what I have written. This was not what I said. ;-) It was a further question.
Thanks for your answer. Marco
There is some missunderstanding. The recent splitter is not able to split at geographical boundaries. This is the task of osmosis. Maybe it is not too complicated to build this feature into splitter, but at the moment it doesn't.
Or is it posilbe to do a presplit, which creates a tile for each country and then in a second step splitting the country files?
Yes, this way should work. But for the presplitting you can't use splitter. I don't use osmosis by myself, so I don't know internals of it. But I know, that geofabrik splits its regions with osmosis.
Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map
I would expect the interstate routing to work. Precondition is obviously that the presplitted tiles don't miss any segments at the border and the border nodes have exactly the same coordinates.
Regards, Johann _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 19 Sep 2009, at 4:29 , Johann Gail wrote:
So is it possible to configure the splitter do split the maps not after x-Number of nodes but at these coordinates?
No, this is not what I have written. There is some missunderstanding. The recent splitter is not able to split at geographical boundaries. This is the task of osmosis.
even osmosis can't do that. osmosis takes a polygon as input and doesn't read boundaries from osm files
Maybe it is not too complicated to build this feature into splitter, but at the moment it doesn't.
neither splitter or osmosis insert new points. but it is required to have boundary nodes in mkgmap. splitter would need to calculate crossing points with the boundary or a provided split polygon with all ways and insert the boundary points.
Or is it posilbe to do a presplit, which creates a tile for each country and then in a second step splitting the country files?
Yes, this way should work. But for the presplitting you can't use splitter. I don't use osmosis by myself, so I don't know internals of it. But I know, that geofabrik splits its regions with osmosis.
you can do the presplit but routing can't work then across boundaries. osmosis has different modes - clip ways at the boundary -> no routing across tiles due to missing nodes - include the whole way -> long ways extend far beyond the boundary, areas aoutside the boundary will be incomplete, tiles will overlap in huge areas. routing may break in these overlap tiles - don't clip the way but omit the points outside the box/polygon -> combining 2 osm files should work. but then why did you split them?
Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map I would expect the interstate routing to work. Precondition is obviously that the presplitted tiles don't miss any segments at the border and the border nodes have exactly the same coordinates.
still don't understand why this is useful. If you want multiple countries and route across countries and tiles why split it more than necessary and try to assemble again?
Regards, Johann _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Apollinaris Schoell escribió:
On 19 Sep 2009, at 4:29 , Johann Gail wrote:
So is it possible to configure the splitter do split the maps not after x-Number of nodes but at these coordinates?
No, this is not what I have written. There is some missunderstanding. The recent splitter is not able to split at geographical boundaries. This is the task of osmosis.
even osmosis can't do that. osmosis takes a polygon as input and doesn't read boundaries from osm files
Maybe it is not too complicated to build this feature into splitter, but at the moment it doesn't.
neither splitter or osmosis insert new points. but it is required to have boundary nodes in mkgmap. splitter would need to calculate crossing points with the boundary or a provided split polygon with all ways and insert the boundary points.
Or is it posilbe to do a presplit, which creates a tile for each country and then in a second step splitting the country files?
Yes, this way should work. But for the presplitting you can't use splitter. I don't use osmosis by myself, so I don't know internals of it. But I know, that geofabrik splits its regions with osmosis.
you can do the presplit but routing can't work then across boundaries. osmosis has different modes - clip ways at the boundary -> no routing across tiles due to missing nodes - include the whole way -> long ways extend far beyond the boundary, areas aoutside the boundary will be incomplete, tiles will overlap in huge areas. routing may break in these overlap tiles - don't clip the way but omit the points outside the box/polygon -> combining 2 osm files should work. but then why did you split them?
Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map
I would expect the interstate routing to work. Precondition is obviously that the presplitted tiles don't miss any segments at the border and the border nodes have exactly the same coordinates.
still don't understand why this is useful. If you want multiple countries and route across countries and tiles why split it more than necessary and try to assemble again?
If I understand right your question, I can give you a reason. I build maps for Spain, Portugal and South of France. If I could combine Geofabrik osm files so that routing would work, it would be much faster to download individual country files (~300 MB altogether), assemble them and split the resulting file with splitter than download all Europe (2 GB->30 GB uncompressed) and processing such a big file to get my area of interest. Regards Carlos
Regards, Johann
Apollinaris, I don't know if you questions was directed to my, but to create a map which alows routing drom kopenhagen to rome, I have to take a full europe map. It is not possible to download demark, germany, austria and italy, because routing is not possilbe then. routing only works if I take europe and create a map out of this. I'm providing these maps fordownoad. In this case the user can download a denmark, ermany, austria and italy map and is able to route over map/country borders. Currently the user must always download the whole europe map. Marco Apollinaris Schoell schrieb:
On 19 Sep 2009, at 4:29 , Johann Gail wrote:
So is it possible to configure the splitter do split the maps not after x-Number of nodes but at these coordinates?
No, this is not what I have written. There is some missunderstanding. The recent splitter is not able to split at geographical boundaries. This is the task of osmosis.
even osmosis can't do that. osmosis takes a polygon as input and doesn't read boundaries from osm files
Maybe it is not too complicated to build this feature into splitter, but at the moment it doesn't.
neither splitter or osmosis insert new points. but it is required to have boundary nodes in mkgmap. splitter would need to calculate crossing points with the boundary or a provided split polygon with all ways and insert the boundary points.
Or is it posilbe to do a presplit, which creates a tile for each country and then in a second step splitting the country files?
Yes, this way should work. But for the presplitting you can't use splitter. I don't use osmosis by myself, so I don't know internals of it. But I know, that geofabrik splits its regions with osmosis.
you can do the presplit but routing can't work then across boundaries. osmosis has different modes - clip ways at the boundary -> no routing across tiles due to missing nodes - include the whole way -> long ways extend far beyond the boundary, areas aoutside the boundary will be incomplete, tiles will overlap in huge areas. routing may break in these overlap tiles - don't clip the way but omit the points outside the box/polygon -> combining 2 osm files should work. but then why did you split them?
Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map
I would expect the interstate routing to work. Precondition is obviously that the presplitted tiles don't miss any segments at the border and the border nodes have exactly the same coordinates.
still don't understand why this is useful. If you want multiple countries and route across countries and tiles why split it more than necessary and try to assemble again?
Regards, Johann _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Marco, There is a problem with Geofabrik downloads and it is not possible to combine 2 of them into a complete osm file. Since they provide it for free we can't complain. Instead we have to use other methods. I am sure Geofabrik does that for a reason because there are other use cases than Garmin routing. For a user it should matter if tiles are across borders. they will need all tiles from denmark to italy. why not simply create whole europe and a user downloads the tiles needed. Lambertus offers exactly such a service already at http://garmin.na1400.info/routable.php why would anyone split the map into more tiles just to stop at the border? since inter tile routing is still not perfect try to keep tiles as big as possible. On 20 Sep 2009, at 11:50 , dom Team OiD wrote:
Apollinaris,
I don't know if you questions was directed to my, but to create a map which alows routing drom kopenhagen to rome, I have to take a full europe map. It is not possible to download demark, germany, austria and italy, because routing is not possilbe then. routing only works if I take europe and create a map out of this. I'm providing these maps fordownoad. In this case the user can download a denmark, ermany, austria and italy map and is able to route over map/country borders. Currently the user must always download the whole europe map.
Marco
Apollinaris Schoell schrieb:
On 19 Sep 2009, at 4:29 , Johann Gail wrote:
So is it possible to configure the splitter do split the maps not after x-Number of nodes but at these coordinates?
No, this is not what I have written. There is some missunderstanding. The recent splitter is not able to split at geographical boundaries. This is the task of osmosis.
even osmosis can't do that. osmosis takes a polygon as input and doesn't read boundaries from osm files
Maybe it is not too complicated to build this feature into splitter, but at the moment it doesn't.
neither splitter or osmosis insert new points. but it is required to have boundary nodes in mkgmap. splitter would need to calculate crossing points with the boundary or a provided split polygon with all ways and insert the boundary points.
Or is it posilbe to do a presplit, which creates a tile for each country and then in a second step splitting the country files?
Yes, this way should work. But for the presplitting you can't use splitter. I don't use osmosis by myself, so I don't know internals of it. But I know, that geofabrik splits its regions with osmosis.
you can do the presplit but routing can't work then across boundaries. osmosis has different modes - clip ways at the boundary -> no routing across tiles due to missing nodes - include the whole way -> long ways extend far beyond the boundary, areas aoutside the boundary will be incomplete, tiles will overlap in huge areas. routing may break in these overlap tiles - don't clip the way but omit the points outside the box/polygon -> combining 2 osm files should work. but then why did you split them?
Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map
I would expect the interstate routing to work. Precondition is obviously that the presplitted tiles don't miss any segments at the border and the border nodes have exactly the same coordinates.
still don't understand why this is useful. If you want multiple countries and route across countries and tiles why split it more than necessary and try to assemble again?
Regards, Johann _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
neither splitter or osmosis insert new points. but it is required to have boundary nodes in mkgmap. splitter would need to calculate crossing points with the boundary or a provided split polygon with all ways and insert the boundary points.
This is my opinion too. Whatever tool does the splitting into countries, it has to create new nodes at the intersection of the roads and the state borders.
you can do the presplit but routing can't work then across boundaries. osmosis has different modes - clip ways at the boundary -> no routing across tiles due to missing nodes
As I'he written before, I don't know the internals of osmosis. But if I the ways are clipped at a border, then it should be possible to create a new node at the intersection and mark the node as a border node. Is there a developper of osmosis reading this list?
Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map
I would expect the interstate routing to work. Precondition is obviously that the presplitted tiles don't miss any segments at the border and the border nodes have exactly the same coordinates.
still don't understand why this is useful. If you want multiple countries and route across countries and tiles why split it more than necessary and try to assemble again?
As some other users have written, then it would be possible to download the regions of interest from geofabrik and compile them with splitter and mkgmap and have a routable map. Then its not neccessary to download whole europe, when I want only bavaria and austria. I could furthermore load the precompiled maps of countires onto my etrex, just as I need them. So I would really appreciate it, if the presplitted maps from geofabrik are clipped 'correctly' at the borders.
Johann Gail wrote:
neither splitter or osmosis insert new points. but it is required to have boundary nodes in mkgmap. splitter would need to calculate crossing points with the boundary or a provided split polygon with all ways and insert the boundary points.
This is my opinion too. Whatever tool does the splitting into countries, it has to create new nodes at the intersection of the roads and the state borders.
you can do the presplit but routing can't work then across boundaries. osmosis has different modes - clip ways at the boundary -> no routing across tiles due to missing nodes
As I'he written before, I don't know the internals of osmosis. But if I the ways are clipped at a border, then it should be possible to create a new node at the intersection and mark the node as a border node. Is there a developper of osmosis reading this list?
I'm not an osmosiv dev, but there is already (in theory because it's not working, at least for me) - the option completeway=yes and completerelations=yes which should be sufficient (both by default if not given resort to no).
Then it would be possilbe to download europe from geofabrik, split it into countries and then crate maps from it. These maps would be interroutable. It would be also need less computing power/memory for doing this compared of processing the whole europe map
I would expect the interstate routing to work. Precondition is obviously that the presplitted tiles don't miss any segments at the border and the border nodes have exactly the same coordinates.
still don't understand why this is useful. If you want multiple countries and route across countries and tiles why split it more than necessary and try to assemble again?
As some other users have written, then it would be possible to download the regions of interest from geofabrik and compile them with splitter and mkgmap and have a routable map. Then its not neccessary to download whole europe, when I want only bavaria and austria. I could furthermore load the precompiled maps of countires onto my etrex, just as I need them.
So I would really appreciate it, if the presplitted maps from geofabrik are clipped 'correctly' at the borders.
I think many many people would like this.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
As I'he written before, I don't know the internals of osmosis. But if I the ways are clipped at a border, then it should be possible to create a new node at the intersection and mark the node as a border node. Is there a developper of osmosis reading this list?
I guess Brett has different priorities and a list of more important work. And it is not that simple. you need code to calculate intersection between ways and polygons. I bet osmosis doesn't have such code. this is not even a trivial, simple and fast thing to do. also you will need to use the same polygon across all tools to get the same border clipping. you need a slightly blown polygon since garmin tiles have a small overlap between tiles.
As some other users have written, then it would be possible to download the regions of interest from geofabrik and compile them with splitter and mkgmap and have a routable map.
no Geofabrik osm files are created with clipIncompleteEntities. impossible to merge them into a consistent format. They offer data for free. take it or leave it ....
Then its not neccessary to download whole europe, when I want only bavaria and austria. I could furthermore load the precompiled maps of countires onto my etrex, just as I need them.
but why split along the border? if you for example load bavaria-nord, bavaria-south+austria-northwest, austria-southwest-italy-nord is there any disadvantage? all borders are open in most of europe.why reintroduce them everywhere.
So I would really appreciate it, if the presplitted maps from geofabrik are clipped 'correctly' at the borders.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
2009/9/20 Apollinaris Schoell <aschoell@gmail.com>:
but why split along the border? if you for example load bavaria-nord, bavaria-south+austria-northwest, austria-southwest-italy-nord is there any disadvantage? all borders are open in most of europe.why reintroduce them everywhere.
For every .img file we generate, we have to specify country, don't we? Once destination search begins to work, it's likely to become very difficult to Navigate to, say, Kufstein in Austria if it happens to appear on a map tile mostly containing Bavaria and therefore set to Germany as a country. Dermot -- -------------------------------------- Iren sind menschlich
On 20 Sep 2009, at 15:11 , Dermot McNally wrote:
2009/9/20 Apollinaris Schoell <aschoell@gmail.com>:
but why split along the border? if you for example load bavaria- nord, bavaria-south+austria-northwest, austria-southwest-italy-nord is there any disadvantage? all borders are open in most of europe.why reintroduce them everywhere.
For every .img file we generate, we have to specify country, don't we? Once destination search begins to work, it's likely to become very difficult to Navigate to, say, Kufstein in Austria if it happens to appear on a map tile mostly containing Bavaria and therefore set to Germany as a country.
first someone needs to figure out how search works at all. it may not even use country specified in a img tile.
Dermot
-- -------------------------------------- Iren sind menschlich _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
2009/9/20 Apollinaris Schoell <aschoell@gmail.com>:
first someone needs to figure out how search works at all. it may not even use country specified in a img tile.
While we should certainly keep an open mind, it's too convenient that Garmin choose to break all their maps at national borders too. Dermot -- -------------------------------------- Iren sind menschlich
Dermot McNally escribió:
2009/9/20 Apollinaris Schoell <aschoell@gmail.com>:
but why split along the border? if you for example load bavaria-nord, bavaria-south+austria-northwest, austria-southwest-italy-nord is there any disadvantage? all borders are open in most of europe.why reintroduce them everywhere.
For every .img file we generate, we have to specify country, don't we? Once destination search begins to work, it's likely to become very difficult to Navigate to, say, Kufstein in Austria if it happens to appear on a map tile mostly containing Bavaria and therefore set to Germany as a country.
Dermot
Also the styles we apply may vary from one country to another, so borders are important. Carlos
On Sep 16, 2009, at 09:42, Marko Mäkelä wrote:
I seem to remember someone mentioning that Garmin supports non- rectangular map tiles. Would that help? Or would it be too much effort with too little gain to implement that in mkgmap (and splitter)?
Am 16.09.2009, Carsten Schwede wrote:
What need mkgmap special to enable routing between tiles? I would like to use this special also in the cutting program I use for creating a completely routable worlmap...
On Sep 16, 2009, at 09:14, dom@team-oid.de wrote:
I'm currently a bit confused. Is it possible to route over mapssets or not? I think it's still not working for maps which are splitted without splitter.
Since there's some confusion I'll try to summarize, though my knowledge may be a little out-of-date. # IMG format For routing to work between two different IMGs, the nodes on the "boundary" need to be marked specially. Here, "boundary" is in theory just the nodes where both routing graphs meet. These don't necessarily need to lie on the edge of the map, and the map doesn't necessarily need to have a rectangular shape. AFAIK, it should be possible to route using two tiles where one contains a country's motorway network and another contains the lower- class roads, with boundary nodes at the motorway ramps. It may well be that the routing algorithm expects a different, tile-like separation, however. It's unlikely that a tile needs to be rectangular, but it may well be that a tile should be convex (geographically and/or with respect to the routing graph). # mkgmap Mkgmap needs to know which nodes to mark as boundary nodes. The simple way is to just tell mkgmap, which is what happens when using polish (.mp) input, where you flag boundary nodes. If you want to test some of the above speculation, creating appropriate .mp files is probably the easiest way to go. For .osm, mkgmap determines boundary nodes itself. Here lies the restriction to rectangular tiles: The .osm input needs to contain a <bounds>-element specifying the desired bounds of the output IMG. The OSM data itself need not be contained within the <bounds>-element. mkgmap clips all geometry to these bounds and generates boundary nodes wherever ways are clipped (there's probably lots of special cases here). Cheers Robert
participants (12)
-
Apollinaris Schoell -
Carlos Dávila -
Carsten Schwede -
Dermot McNally -
dom -
dom Team OiD
-
Felix Hartmann -
Johann Gail -
Mark Burton -
Marko Mäkelä -
Ralf Kleineisel -
Robert Vollmert