Re: [mkgmap-dev] Inundated tile with no coastline
Am 01.03.2011 21:38, schrieb Nakor: > Hello, > > I have a tile with no coastline that shows up inundated. How can this > be? How can I fix it? > > The tile is split us_midwest from geofabrick with: > > 4162: 2183168,239616 to 2215936,280576 > # : 46.845703,5.141602 to 47.548828,6.020508 Are you sure, that there is no natural=coastline inside the tile. Sometimes someone taggs a lake or somthing like that as natural=coastline, which may cause your error. If possible, you could unzip your 41662.osm.gz and open osm-file in josm, and filter every object without natural=coastline. Then you can search the fault. Henning ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Inundated tile with no coastline
> If possible, you could unzip your 41662.osm.gz and open osm-file in > josm, and filter every object without natural=coastline. Then you can > search the fault. > > I did and opened the tile in JOSM. A search for natural=coastline did not return anything. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Inundated tile with no coastline
Please post your parameters you are using. WanMil > Hello, > > I have a tile with no coastline that shows up inundated. How can this > be? How can I fix it? > > The tile is split us_midwest from geofabrick with: > > 4162: 2183168,239616 to 2215936,280576 > # : 46.845703,5.141602 to 47.548828,6.020508 > > > Thanks, > > N. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Inundated tile with no coastline
On 3/1/2011 3:38 PM, Nakor wrote: > Hello, > > I have a tile with no coastline that shows up inundated. How can this > be? How can I fix it? > > The tile is split us_midwest from geofabrick with: > > 4162: 2183168,239616 to 2215936,280576 > # : 46.845703,5.141602 to 47.548828,6.020508 > > > Thanks, > > N. Nevermind. This was a MapSource cache issue. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev