You need to extract boundary relations data before telling mkgmap to process it. Use osmconvert and osmfilter to do that. Then use mkgmap's built in boundary processor to process it. Lastly use the bounds argument when compiling. osmconvert xxx.osm.pbf --out-o5m >xxx.o5m osmfilter xxx.o5m --keep-nodes= --keep-ways-relations="boundary=administrative =postal_code postal_code=" --out-o5m > xxx-boundaries.o5m java -cp mkgmap.jar uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreprocessor xxx-boundaries.o5m boundary then add argument bounds=<boundary folder location> example on https://github.com/schadow1/osmphgps Ervin M. *Schadow1 Expeditions* - A Filipino must not be a stranger to his own motherland. http://www.s1expeditions.com On Wed, Sep 3, 2014 at 12:15 AM, Nelson A. de Oliveira <naoliv@gmail.com> wrote:
On Tue, Sep 2, 2014 at 2:48 AM, Marko Mäkelä <marko.makela@iki.fi> wrote:
On Mon, Sep 01, 2014 at 09:05:44PM -0300, Nelson A. de Oliveira wrote:
Does mkgmap support administrative boundaries defined only by relations? (ie, there isn't any kind of tag in the ways)
This at least used to work. I wrote the "apply" rules for getting names on the boundaries from the relations, separated by "/" or ",". It might have been broken since I wrote the code.
Basically what https://github.com/openstreetmap/mkgmap/blob/master/resources/styles/default... does? Is it necessary to apply other properties, like admin_level? _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev