In the same map I have sometimes the unwanted effect that a stream (river) overlays a way. That's what I want: http://gis.638310.n2.nabble.com/file/n7078255/Bridge-OK.png But often I get this: http://gis.638310.n2.nabble.com/file/n7078255/Bridge-NOK.png The streams are defined after the ways in the lines files. mkgmap = 2136 splitter = 194 Has someone an idea what's going wrong? Regards - Klaus -- View this message in context: http://gis.638310.n2.nabble.com/Draw-priority-of-lines-tp7078255p7078255.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
there is no draw-priority of lines, if you find out any system behind it, that works universally, then shout out to the world... (universally== what happens reliably in Mapsource, what happens in Basecamp, what happens in Qlandkarte GT, what happens on old generation GPS like Vista HCx, what happens on new generation outdoor GPS like Dakota/Oregon/etrex 30/Monatan, what happens on other GPS...) AFAIK with non NT maps it's simply by chance what happens... On 09.12.2011 14:53, toc-rox wrote:
In the same map I have sometimes the unwanted effect that a stream (river) overlays a way.
That's what I want: http://gis.638310.n2.nabble.com/file/n7078255/Bridge-OK.png
But often I get this: http://gis.638310.n2.nabble.com/file/n7078255/Bridge-NOK.png
The streams are defined after the ways in the lines files. mkgmap = 2136 splitter = 194
Has someone an idea what's going wrong?
Regards - Klaus
-- View this message in context: http://gis.638310.n2.nabble.com/Draw-priority-of-lines-tp7078255p7078255.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
OK - and how to interpret this comment from the mkgmap default lines file? ... # The following boundary styles are after the highway rules because ways # are frequently tagged with both and we want the highway to take priority. boundary=administrative { name '${mkgmap:boundary_name}' } ... -- View this message in context: http://gis.638310.n2.nabble.com/Draw-priority-of-lines-tp7078255p7078304.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
That comment meant (!!!) that in case on line in OSM is both a highway and a boundary, it will be shown in the map as highway only (and boundary dropped -- which could be changed with "continue" command and both inserted into the map) it has to do absolutely nada with draw-priority which only exists for polygons (for POI it's the same mystery and crap) On 09.12.2011 15:09, toc-rox wrote:
OK - and how to interpret this comment from the mkgmap default lines file?
... # The following boundary styles are after the highway rules because ways # are frequently tagged with both and we want the highway to take priority. boundary=administrative { name '${mkgmap:boundary_name}' } ...
-- View this message in context: http://gis.638310.n2.nabble.com/Draw-priority-of-lines-tp7078255p7078304.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I've used layers with different drawing priority (mkgmap --draw-priority=nn parameter). It seems to work ok for me although this may not be universal for all devices. However, this is not the same as a priority for a single line using a single style. Regards, Harri -- On 12/09/2011 03:56 PM, Felix Hartmann wrote:
there is no draw-priority of lines, if you find out any system behind it, that works universally, then shout out to the world...
(universally== what happens reliably in Mapsource, what happens in Basecamp, what happens in Qlandkarte GT, what happens on old generation GPS like Vista HCx, what happens on new generation outdoor GPS like Dakota/Oregon/etrex 30/Monatan, what happens on other GPS...)
AFAIK with non NT maps it's simply by chance what happens...
On 09.12.2011 14:53, toc-rox wrote:
In the same map I have sometimes the unwanted effect that a stream (river) overlays a way.
That's what I want: http://gis.638310.n2.nabble.com/file/n7078255/Bridge-OK.png
But often I get this: http://gis.638310.n2.nabble.com/file/n7078255/Bridge-NOK.png
The streams are defined after the ways in the lines files. mkgmap = 2136 splitter = 194
Has someone an idea what's going wrong?
Regards - Klaus
-- View this message in context: http://gis.638310.n2.nabble.com/Draw-priority-of-lines-tp7078255p7078255.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
This sounds like today's weather reports, but it isn't. For some time I have been downloading the England, Scotland and Wales files from Geofabrik, and compiling these with mkgmap. Today, I have encountered a problem with sea flooding in SW Scotland/NW England. Compiling Scotland alone works fine. Compiling England has a small area of flooding around Carlisle. Compiling both together produces a very large area of flooding in both England and Scotland. Screenshots from mapsource for these last two are at http://www.rogercalvert.me.uk/OSM/england.jpg and http://www.rogercalvert.me.uk/OSM/uk.jpg respectively. My command line includes --generate-sea=multipolygon,extend-sea-sectors,close-gaps=1000,floodblocker Has anyone else encountered this? I would appreciate any ideas as to where to look for the problem. Many thanks, Roger ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------
Hi, yesterday I fixed the coastline in the east of Edinburgh. Afterwards the coastline of UK seems to be ok. How old is your data? Maybe there is someone who wants to improve coastline, but don't know what he does? Henning
Henning, Thanks for the info. My download was yesterday for England and today for Scotland, so your correction will not be included. But I suspect there may be something near Carlisle as well as near Edinburgh. Roger ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------ On 09/12/2011 20:46, Henning Scholland wrote:
Hi, yesterday I fixed the coastline in the east of Edinburgh. Afterwards the coastline of UK seems to be ok. How old is your data? Maybe there is someone who wants to improve coastline, but don't know what he does?
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I have today downloaded new files for Scotland and England (and Wales) from Geofabrik, and I still get extensive sea flooding in NW England and SW Scotland. I have examined the coastlines in the area in as much detail as I can (using Potlatch 2 and Geofabrik Tools) and can't find any problems. Has anybody else experienced this? Or please could someone else try compiling these, to test whether the problem is with my splitter/mkgmap use or is in the data. My splitter command line is: "%OSM%\splitter\splitter.jar" --mapid=%fn%%fid%001 --max-nodes=2500000 --cache=%2 --description=%country-name% --max-threads=auto %1 My mkgmap command line is: %OSM%\mkgmap\mkgmap.jar" --code-page=1252 --latin1 --mapname="%map%" --family-id=%FID% --mapname="66%FID%001" --overview-mapname="%map%" --series-name="%map%" --family-name="Roger's Maps: %map%" --description="%map%" --no-poi-address --ignore-maxspeeds --remove-short-arcs --preserve-element-order --lower-case --route --net --tdbfile --gmapsupp --generate-sea=multipolygon,extend-sea-sectors,close-gaps=1000,floodblocker --style-file=..\resources\styles --style=roger -c template.args Many thanks Roger ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------ On 09/12/2011 19:59, Roger Calvert wrote:
This sounds like today's weather reports, but it isn't.
For some time I have been downloading the England, Scotland and Wales files from Geofabrik, and compiling these with mkgmap.
Today, I have encountered a problem with sea flooding in SW Scotland/NW England. Compiling Scotland alone works fine. Compiling England has a small area of flooding around Carlisle. Compiling both together produces a very large area of flooding in both England and Scotland.
Screenshots from mapsource for these last two are at http://www.rogercalvert.me.uk/OSM/england.jpg and http://www.rogercalvert.me.uk/OSM/uk.jpg respectively.
My command line includes --generate-sea=multipolygon,extend-sea-sectors,close-gaps=1000,floodblocker
Has anyone else encountered this? I would appreciate any ideas as to where to look for the problem.
Many thanks,
Roger ------------------------------------------------------------------------
Roger Calvert ------------------------------------------------------------------------
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Fri, Dec 30, 2011 at 08:01:42PM +0000, Roger Calvert wrote:
I have today downloaded new files for Scotland and England (and Wales) from Geofabrik, and I still get extensive sea flooding in NW England and SW Scotland. I have examined the coastlines in the area in as much detail as I can (using Potlatch 2 and Geofabrik Tools) and can't find any problems.
Did you enable logging in mkgmap? Do you see any coastline related messages in mkgmap.log.*? One thing that you could try is to extract the natural=coastline ways from the Geofabrik extract that you are using, loading that in JOSM and having Validator check it. Sometimes, mkgmap remains silent about flooding. A few months ago, there was an island in a lake in SE Finland drawn as natural=coastline. mkgmap did what it was told to, and flooded the whole map tile except for the tiny island, because there were no other natural=coastline ways in the tile. mkgmap could perhaps have done a better job and complain that some natural=water polygons or multipolygons are overlapping with the natural=coastline multipolygon. This error I fixed by looking at the natural=coastline extract in JOSM. The commands go something like this: osmosis --rb xxx.osm.pbf --tf accept-ways natural=coastline \ --tf reject-relations --used-node --wx coastline.osm josm coastline.osm [invoke the Validator in JOSM, and be sure to enable INFO level in the preferences, because coastline checks are in the INFO level] If you are using a single map extract, I guess that the valid situation for the UK is that there are no incomplete coastlines in the map extract, except maybe for (North) Ireland. For most other countries with a coastline, you have to somehow tell splitter or mkgmap to augment the lsat bit of coastline, or to ensure that your tile borders clip the map before the end of the coastline. I do that for my map of Finland <http://www.polkupyoraily.net/osm/>. The SE end of the mainland coastline is clipped by my carefully chosen tile boundary, and the NW end is augmented to the tile boundary by mkgmap. If you are using multiple map extracts that partly overlap, then I guess that you should be expecting trouble. Best regards, Marko
You can always use my daily updated coastlines as well. These are based on the Geofabrik Europe extract respectively the complete planet file, so they will be more complete than the coastlines you get from a single-country extract: http://fabianowski.eu/osm/coastlines/ - Bartosz
Marko and Bartosz, Thank you both for your advice. The mkgmap log showed a very large number of messages, but none at all relating to coastline. But using Bartosz's coastlines-europe file solved the problem (once I had remembered to reference it before the data files), at the expense of a rather larger gmapsupp file. Once again, many thanks. Roger ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------ On 30/12/2011 21:04, Bartosz Fabianowski wrote:
You can always use my daily updated coastlines as well. These are based on the Geofabrik Europe extract respectively the complete planet file, so they will be more complete than the coastlines you get from a single-country extract:
http://fabianowski.eu/osm/coastlines/
- Bartosz _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Sat, Dec 31, 2011 at 05:37:43PM +0000, Roger Calvert wrote:
Thank you both for your advice. The mkgmap log showed a very large number of messages, but none at all relating to coastline.
There could have been some MultiPolygonRelation errors related to coastlines. I should mention that the checks in JOSM Validator and mkgmap are not overlapping that much. JOSM detects some things better, but it does not detect land-on-land or sea-on-sea situations as well as mkgmap, as it does not "colour" the areas.
But using Bartosz's coastlines-europe file solved the problem (once I had remembered to reference it before the data files), at the expense of a rather larger gmapsupp file.
OK, in that case the issue might be that the Geofabrik cutting polygon is intersecting with some islets that have been added or moved fairly recently. The Europe coastline at http://fabianowski.eu/osm/coastlines/ looks like it could be loaded into JOSM on a computer with enough RAM. It could be an interesting exercise to ask Frederik Ramm for the cutting polygon in *.osm format and load it and the coastlines in JOSM, to see if the Geofabrik polygon can be improved. I did this for Finland a couple of years ago. In addition to the coastline, I observed the country border and a few lakes near the border when I edited the cutting polygon. It took a couple of iterations to get it fully right. Marko
Marko, Thanks for the comments.
There could have been some MultiPolygonRelation errors related to coastlines. I should mention that the checks in JOSM Validator and mkgmap are not overlapping that much. JOSM detects some things better, but it does not detect land-on-land or sea-on-sea situations as well as mkgmap, as it does not "colour" the areas. mkgmap came up with many errors relating to 'anti-islands' - I suspect these are round Scotland, and I'll leave it to local people to sort them out!
But using Bartosz's coastlines-europe file solved the problem (once I had remembered to reference it before the data files), at the expense of a rather larger gmapsupp file. OK, in that case the issue might be that the Geofabrik cutting polygon is intersecting with some islets that have been added or moved fairly recently. This seems possible. On closer inspection, I saw a little flooding on the England/Wales border too. The Europe coastline at http://fabianowski.eu/osm/coastlines/ looks like it could be loaded into JOSM on a computer with enough RAM.
It could be an interesting exercise to ask Frederik Ramm for the cutting polygon in *.osm format and load it and the coastlines in JOSM, to see if the Geofabrik polygon can be improved. I did this for Finland a couple of years ago. In addition to the coastline, I observed the country border and a few lakes near the border when I edited the cutting polygon. It took a couple of iterations to get it fully right. I think I'll leave this to someone with a bigger computer and more time and expertise. At present, I am not a JOSM or OSMOSIS user.
Thanks for the interest and advice. Roger
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Sun, Jan 01, 2012 at 02:00:17PM +0000, Roger Calvert wrote:
mkgmap came up with many errors relating to 'anti-islands' - I suspect these are round Scotland, and I'll leave it to local people to sort them out!
An anti-island is normally easy to sort out. You would simply reverse the nodes of the way so that land would be on the left side of the way. If aerial image shows that it is not an island, but a small pond of water, then you should use something else for it, such as natural=water or landuse=reservoir. Other types of coastline errors can be more tricky. Last November, it took me several iterations to fix the coastline west of Helsinki when a beginner had deleted sections of coastline in the archipelago and redrawn it from high-resolution Bing images. Both JOSM and me failed to notice that he had reversed some of the mainland coastline ways. After fixing all islands, it still kept flooding, and I finally noticed it. Currently, the coastline validator in JOSM should detect this.
I think I'll leave this to someone with a bigger computer and more time and expertise. At present, I am not a JOSM or OSMOSIS user.
OK. I cannot call myself an advanced Osmosis user either. It is a complex 'Swiss army knife' type of tool, but there are some examples in the documentation http://wiki.openstreetmap.org/wiki/Osmosis/Detailed_Usage JOSM might be a bit different matter. It could require some more learning, but IMO it is worth it. I have been using it for 3 years now, since the beginning of my involvement with OSM. Best regards, Marko
participants (7)
-
Bartosz Fabianowski -
Felix Hartmann -
harri -
Henning Scholland -
Marko Mäkelä -
Roger Calvert -
toc-rox