
Hi List, I have some questions related to the splitting and rendering of bigger areas of the sea. For instance when there is no land or coastline at this tile 97800427 (1) on my map it is rendered as 'land' Maybe because I use the floodblocker in my generate-sea: extend-sea-sectors,close-gaps=6000,floodblocker,land-tag=natural=background Do I actually need to use the floodblocker parameter if I also use coastlinefile=coastlines_europe-latest.osm.pbf ? Or can I use some extra options for the floodblocker so that it recognize those empty areas? Another issue is that the splitter generates a comment mark # in the description field if it doesn't find a city from the geonames-file mapname: 97800427 # description: OSM Map input-file: 97800427.osm.pbf This will lead to a description of the previous tile, which isn't quite in the same area. Suggestion for improvement is not to add a # sign, better leave it "OSM Map" in the sea (or sparsely populated areas without towns) than for instance "London" Or is there a trick for this (I only know search "# description" and replace for "description") (1) http://img17.imageshack.us/img17/3153/seaq.jpg

On Mon, Jan 30, Minko wrote:
Do I actually need to use the floodblocker parameter if I also use coastlinefile=coastlines_europe-latest.osm.pbf ? Or can I use some extra options for the floodblocker so that it recognize those empty areas?
If you use the coastlinefile you don't need the floodblocker, at least not if your coastlinefile is correct.
Another issue is that the splitter generates a comment mark # in the description field if it doesn't find a city from the geonames-file
mapname: 97800427 # description: OSM Map input-file: 97800427.osm.pbf
I don't have the '#' in my template.args, but maybe that's because I use the --description option of splitter additional. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

Thanks Thorsten, I'll give it a try. Btw I notice some floodings south of Ipswich, UK in the European coastlinefile from 28-Jan from http://fabianowski.eu/osm/coastlines/ so I dont think this one is correct (or maybe some riverbanks there are broken). So the # issue will be solved if I use both --geonames-file and --description in the splitter?

On Mon, Jan 30, Minko wrote:
Thanks Thorsten, I'll give it a try. Btw I notice some floodings south of Ipswich, UK in the European coastlinefile from 28-Jan from http://fabianowski.eu/osm/coastlines/ so I dont think this one is correct (or maybe some riverbanks there are broken).
Is the flooding coming from the sea or from a lake? In Canada I have the problem with big lakes flooding land ...
So the # issue will be solved if I use both --geonames-file and --description in the splitter?
At least it works for me. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

Thanks Thorsten, I'll try the geonames/description next time. The reason of the flooding is a bit complicated. Inspection of the problematic tile turned out that the flooding was not caused by a broken coastline, but some kind of problem with rendering of the land-polygon. It looked flooded but that was because I used "sea" blue as background colour (0x4b) and green for land, because in some parts of the sea there were no sea tiles at all and in Mapsource they get the default grey background: http://img814.imageshack.us/img814/9278/nosea.jpg With this particular tile near Ipswich the splitter returns an "Area too small to split" error at http://www.openstreetmap.org/?lat=51.87639&lon=1.24321&zoom=17 Maybe this is the cause that it doesn't get a land background, it only gets the default 0x4b background (which was blue in my case). If I make the 0x4b grey again it looks like this screenshot: http://img685.imageshack.us/img685/2331/ipswich.jpg Also note the upper right corner of the sea, it is filled with land, despite of the fact that I turned off the floodblocker. This area contains some ferry lines, marine borders and a windmill park: http://www.openstreetmap.org/browse/way/113741007 So I still keep two problems with the generate-sea option: multipolygon, extend-sea-sectors,land-tag=natural=background A) the sea is not totally filled with polygons and has some gaps. Those gaps can be filled with a blue 0x4b background as workaround. B) sometimes there is a tile generated in the sea without coastline but then the whole tile is turned into land. I tried a different option for generate-sea: polygons,extend-sea-sectors,close-gaps=6000,land-tag=natural=background Land in the problematic tile around Ipswich is now land again (green), sea is empty, 0x4b (which can be blue if I use that colour). I still have a land tile in the North Sea. As workaround I can delete that tile, then it will be an empty tile with 0x4b background but then I loose the objects in this tile.
participants (2)
-
Minko
-
Thorsten Kukuk