Christian Gawron schrieb:
If anyone has a good idea how to handle an incomplete shoreline, please
let me know. Right know, it might be best to do the following:
- get a country extract like germany.osm.bz2 from geofabrik,
- calculate the boundary box,
- use xapi or same other source to get
and what about Chris Miller's suggestion the increase
the overlap area for the splitter. Has someone checked
if this gives better results or is it not needed ?
Sorry for answering myself. The splitter default of 2000
map units is round 3 kilometers. Typical distance of
two coastline nodes is
RJ - similar situation at the adriatic sea: the part of italy that is
RJ inside the bbox is flooded, as is venice.
Maybe it's OK and Venice is just having one of their famous high tides? :-)
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Dear Robert,
thank you for the feedback!
Can you send me one of the input tiles (or a download link) where sea
and land are flipped?
Best wishes
Christian
Robert Joop schrieb:
christian, thank you very much for working on this!
here are some current observations with my big bbox cut from
Robert Joop schrieb:
christian, thank you very much for working on this!
Yes, great to see that the sea is going blue.
here are some current observations with my big bbox cut from the planet:
For germany (geofabrik extract) :
Inner Land tiles w/o coast are ok.
The northern sea area is
Dear Chris,
I also get similar problems for some tiles (the result may depend on the
splitter parameters).
The problem is that there are several shoreline segments that do not end
at the map boundary. Two examples are:
- Rügen: The shoreline ends at the border to Poland. The current patch
dear christian,
On 09-08-26 09:23:28 CEST, Christian Gawron wrote:
Can you send me one of the input tiles (or a download link) where sea
and land are flipped?
i've copied them to an external host:
https://mlist.timesink.de/osm/090819-berlin_HR-tiles/
(if your browser complains, you probably
dear christian,
On 09-08-26 10:37:12 CEST, Christian Gawron wrote:
I also get similar problems for some tiles (the result may depend on the
splitter parameters).
The problem is that there are several shoreline segments that do not end
at the map boundary. Two examples are:
- Rügen: The
CG - I have noticed problems due to partly missing shoreline segments
CG for
CG example at the Elbe. This, however, seems to be a problem in the
CG splitting of the data.
Assuming you're talking about the splitter... is this because the nodes that
make up the shoreline are quite far apart where
Hi
On 25/08/09 22:46, Christian Gawron wrote:
This version of the patch fixes a bug in the previous version which
caused tiles with no shoreline to be flooded.
I've separated out the sea generation from the multipolygon
patches and applied them to the multipolygon branch.
It would be great if
Hi Christian
Can you send me the tile causing the problem or provide me a download link?
http://www.mkgmap.org.uk/tmp/63240014.osm.gz
It also takes 30min to compile. There is a lot of coastline
there of course.
..Steve
___
mkgmap-dev mailing list
On 09-08-26 14:52:24 CEST, Steve Ratcliffe wrote:
I've separated out the sea generation from the multipolygon
patches and applied them to the multipolygon branch.
It would be great if further patches could be relative to
this branch to make it easier to see what is being changed by
each
This version of the patch fixes a bug in the previous version which
caused tiles with no shoreline to be flooded.
Other improvements are
- Shorelines are clipped at the boundary prior to the processing (may
fix some problems related to input data)
- Somewhat improved handling of non-closed
13 matches
Mail list logo
