On 02.03.2012 22:27, RheinSkipper wrote:
Betreff: Re: [mkgmap-dev] Holes in the Sea
The problem is that splitter and mkgmap don't work together at all. The
solution would be that splitter does more checking against the possibility
of
such empty tiles, or other way around - an improvement
I dont use osmosis, where do you need it for?
I usually use osmosis for merging, so I missed that you suggested
osmconvert.
Unlike osmosis omsconvert produces no error messages on merging the
josm-made island to the coastline-file or directly to the offshore tile. But
the output doesn´t
I think that it has to do with the negative node-id's when you draw an island
that isn't in the OSM database. Probably it will not merge with the osm data.
Well, either way it will be an inconvenient workaround, I agree.
Maybe Wanmil's floodblocker can do something like this, but then
the
The problem is that splitter and mkgmap don't work together at all. The
solution would be that splitter does more checking against the
possibility of such empty tiles, or other way around - an improvement on
how max-nodes are counted. The other possibility would be, if there was
an automatic
Betreff: Re: [mkgmap-dev] Holes in the Sea
The problem is that splitter and mkgmap don't work together at all. The
solution would be that splitter does more checking against the possibility
of
such empty tiles, or other way around - an improvement on how max-nodes
are counted. The other
I have used osmconvert to merge a part of the N-African coast with the European
coast:
osmconvert coastlines_europe-latest.osm.pbf coastlineafrica.osm
-o=coastlines_europe.osm.pbf
As far of the islands, it's better to merge them with the osm extract instead
of the coastline-file,
because
I have used osmconvert to merge a part of the N-African coast with the
European coast:
osmconvert coastlines_europe-latest.osm.pbf coastlineafrica.osm -
o=coastlines_europe.osm.pbf
As far of the islands, it's better to merge them with the osm extract instead
of the coastline-file, because
I dont use osmosis, where do you need it for?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Use --description in your splitter args, otherwise if there are no places
in that
tile, the splitter takes the description of the previous tile.
When I use --description=somename then the --geoname-file option does not
work anymore. All tiles are named somename then.
Did you use
When I use --description=somename then the --geoname-file option does not
work anymore. All tiles are named somename then.
You have to put first --geoname-file then --description=somename
It might be easier to tell mkgmap which empty tiles are sea. How can I do
that?
I'd like to know that too,
You have to put first --geoname-file then --description=somename
I will try it.
If this works and I can name just the empty tiles INT-Offshore, it should
be possible to develop an option for mkgmap to overcome the sea hole
problem.
Just let mkgmap recognize all tiles with a defined
If you know where those empty tiles are located, maybe put a tiny almost
invisible island there
created with josm and merge it with your coastlinefile.
And label it with place=created by mkgmap so the empty tile will not cause
booting problems?
Just let mkgmap recognize all tiles with a
If you know where those empty tiles are located, maybe put a tiny almost
invisible island there created with josm and merge it with your
coastlinefile.
And label it with place=created by mkgmap so the empty tile will not
cause
booting problems?
This sounds easier than it is. I created an
Hi RheinSkipper,
Strange is: The tiles with the holes have completely incorrect geonames.
Other geonames seem to be OK.
Use --description in your splitter args, otherwise if there are no places
in that tile, the splitter takes the description of the previous tile.
Did you use --no-trim in your
On Tue, Feb 28, 2012 at 02:19:28PM +0100, RheinSkipper wrote:
To make sure, coastline is OK, I extracted one from the planet and used
this as coastline-file this time.
How can you be sure that the planet coastline was fully OK on that day?
Does anyone have validator statistics on good/bad
Hi
I use josm (validator) to find the bug in the coastline. I think this
method is quiet easy.
But I only search for errors, if mkgmap generates wrong water-textures.
Then I convert pbf-tile to osm-xml, change =-1 to =1 an load this
file into josm.
Afterwards filter natural=coastline an use
On Sun, Feb 26, 2012 at 07:17:39PM +0100, RheinSkipper wrote:
The empty tile south of Monaco is attached here. I converted it to XML
and there are 28 occurrences of natural=coastline in it.
How did you convert it to XML? In my conversion, there is no
natural=coastline left. Can you upload the
You can try to add --coastlinefile=coastlines_europe.osm.pbf
I downloaded the latest from http://fabianowski.eu/osm/coastlines/
and added the coastline of the North-African coast to it:
http://mijndev.openstreetmap.nl/~ligfietser/coast/coastlines_europe.osm.pbf
Works for my Europe map, without
I have a similar problem with portugal (unmodified geofabrik extract,
coastlines).
http://gis.19327.n5.nabble.com/file/n5519589/Screenshot_20120227_180429.png
Klaus
splitter:
--mixed --overlap=1 --max-nodes=60
mkgmap:
Klaus,
If you use the splitter with --no-trim and/or a higher max-nodes (10) those
holes are gone,
the sea tiles will touch the coastlines.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Nachricht-
Von: mkgmap-dev-boun...@lists.mkgmap.org.uk [mailto:mkgmap-dev-
boun...@lists.mkgmap.org.uk] Im Auftrag von Marko Mäkelä
Gesendet: Freitag, 17. Februar 2012 22:29
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Holes in the Sea
On Fri, Feb 17, 2012 at 05:14:53PM +0100
-
boun...@lists.mkgmap.org.uk] Im Auftrag von Marko Mäkelä
Gesendet: Freitag, 17. Februar 2012 22:29
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Holes in the Sea
On Fri, Feb 17, 2012 at 05:14:53PM +0100, RheinSkipper wrote:
Also attached is a screenshot of those terrible holes
22 matches
Mail list logo
