November 2010 - mkgmap-dev - The mkgmap lists

Feature request: accept osm data from stdin
by Lambertus 02 Nov '10

02 Nov '10

Would it be possible that Mkgmap supports reading the OSM data from stdin? Splitter is capable of doing so and it would eliminate the need for a temporary file if Mkgmap could do so too. E.g. --input-file="-" or assume stdin if no filename is given?

3 4

Re: [mkgmap-dev] Missing ways part 1
by Adrian 02 Nov '10

02 Nov '10

Marko wrote: > If I remember previous discussions correctly, splitter does not split > lines exactly at the tile border, but instead it includes all nodes > that are not too much outside the tile. That is also what I understood. Splitter includes in each tile, the nodes that fall within the tile, and also the nodes in an overlap region around the tile. The width of the overlap can be set with --overlap. > An almost-straight long way can be drawn with few nodes. You could > help the situation by adding a point to the line close to the > splitting border. I would expect it to cause a problem, if a particular way does not have a node in the overlap region. The difficulty with your fix is that it would only work for me (and only if I use the same areas.list each time); it will not work for other users. Also, it will not work for me in the long term, because data is continuously added to OSM, so the tiles need to be made smaller as time goes on. As I understand it, splitter is intended to clip ways at the last included node. [This is done to avoid an additional pass through the input file.] If there is no node in the overlap region, I would expect the way to stop short of the bounding box. In the finished map, I would expect to see a gap in the way at the tile boundary. The maximum length of the gap would be one segment, between adjacent nodes. What I am actually seeing is that the way is entirely lost from both tiles. When inspecting the tiles in JOSM, I can see that all the nodes are present, including those from the missing way. But few of the nodes in the overlap region have ways attached. So it appears that splitter is not working as intended.

4 8

Turn restrictions apparently broken in osm.pbf
by Marko Mäkelä 02 Nov '10

02 Nov '10

Hi Steve, I am seeing bogus warnings like this when processing a file in the OSM Protobuf format: 2010/10/31 21:17:25 WARNING (RestrictionRelation): finland.osm.pbf: Turn restriction http://www.openstreetmap.org/browse/relation/168868 (at http://www.openstreetmap.org/?mlat=61.89944&mlon=27.80067&zoom=17) lacks 'via' node (guessing it should be at http://www.openstreetmap.org/?mlat=61.89854&mlon=27.80311&zoom=17, why don't you add it to the OSM data?) If I process the same data in the OSM XML format, I do not see these messages. Could it be that the RestrictionRelation handler is picky about the order of the relation members when processing osm.pbf input? Best regards, Marko

2 3

Commit: r1726: Do not omit node members when parsing osm.pbf relations.
by svn commit 02 Nov '10

02 Nov '10

Version 1726 was commited by marko on 2010-11-02 08:13:39 +0000 (Tue, 02 Nov 2010) Do not omit node members when parsing osm.pbf relations.

1 0