Re: [mkgmap-dev] Suppress POI names displayed on device
Charlie, Thanks for your advice Charlie You can use extended labels in your TYP file to hide any labelling. Charlie In TYPViewer, once you have opened the TYP: Charlie - click on the POI in question and edit it (modifier) Charlie - set label amelioré to oui (i.e. extended labels to yes) Charlie - set Style de police to Pas de label (invisible) Ahh, that is exactly what I tried, although I didn't see it in TYPViewer, but handcopied it from MapTK's results. (that is, doing it in MapTK, save it as TYP, open with TYPViewer to see the result). Might have done something wrong - will try it again now that you gave me the correct french command. Its quite exiting to try and figure out the french! Charlie You can also compile TXT files to TYP using TYPViewer, in case you Charlie didn't know this. Engegistrer le fichier.typ sous... ? Seems to be broken? Or I am. I get a overflow error message no 6, and the file saves anyway but is empty. Maybe I do something wrong? When trying to open the TYP again: Erreur inconnue lors de l'ouverture du fichier : erreur n°380 Description: Invalid property value I even tried opening a file and saving it directly, without any editing and it still doesn't work. l'ouverture seems to mean something in the file header? I tried to change the FID product ID to no avail. Maybe there is specific filename expectations? Eg. MapSetToolkit complains if the filename is too long, but I already tried to shorten it for TYPViewer. -- I tried again, the results look like this - basicaly the same as I tried already. Maybe there is some small subtle difference I don't recognise. I will apply it to my map again tonight and see if it makes a difference. (Note: MapsetToolkit does not translate Type=0x115 SubType=0x02 correct, so I handedit it to Type=0x11502, which seems to work) [_point] Type=0x115 SubType=0x02 String1=0x04,Spar ExtendedLabels=Y FontStyle=NoLabel (invisible) CustomColor=No DayXpm=10 10 4 1 Colormode=16 ! c #FF # c #00571F % c #00FF00 c none ## #### ##!!##!!## #!!!##!!!# #!!!!# #!##!# #!##!# ##!%##%!## !##%##%##! !!##!! ;1234567890 [end] BennieD This e-mail is subject to the Sappi E-Mail Legal Notice available at www.sappi.com. If you cannot access this Notice please contact the webmaster for a copy to be sent to you. # Scanned by MailMarshal - Marshal's comprehensive email content security solution. Download a free evaluation of MailMarshal at www.marshal.com # ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] TYPViewer (was Suppress POI names displayed on device)
Du Plessis, Bennie wrote: Charlie, Thanks for your advice Charlie You can use extended labels in your TYP file to hide any labelling. Charlie In TYPViewer, once you have opened the TYP: Charlie - click on the POI in question and edit it (modifier) Charlie - set label amelioré to oui (i.e. extended labels to yes) Charlie - set Style de police to Pas de label (invisible) Ahh, that is exactly what I tried, although I didn't see it in TYPViewer, but handcopied it from MapTK's results. (that is, doing it in MapTK, save it as TYP, open with TYPViewer to see the result). Might have done something wrong - will try it again now that you gave me the correct french command. Its quite exiting to try and figure out the french! Charlie You can also compile TXT files to TYP using TYPViewer, in case you Charlie didn't know this. Engegistrer le fichier.typ sous... ? Seems to be broken? Or I am. I get a overflow error message no 6, and the file saves anyway but is empty. Maybe I do something wrong? When trying to open the TYP again: Erreur inconnue lors de l'ouverture du fichier : erreur n°380 Description: Invalid property value I even tried opening a file and saving it directly, without any editing and it still doesn't work. l'ouverture seems to mean something in the file header? I tried to change the FID product ID to no avail. Maybe there is specific filename expectations? Eg. MapSetToolkit complains if the filename is too long, but I already tried to shorten it for TYPViewer. That's strange - this option works perfectly for me (Windows Vista). Are you running this under Windows or in Wine? Did you copy all the various DLLs etc that accompany TYPViewer into the same directory? ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Commit: r1620: Can now explicitly tag boundary nodes with mkgmap:on-boundary=1.
svn commit wrote: Version 1620 was commited by markb on 2010-03-22 21:24:01 + (Mon, 22 Mar 2010) Can now explicitly tag boundary nodes with mkgmap:on-boundary=1. Apologies for the beginners question, but how do I use this? In the OSM source like this? node id= -1 lat=11.00 lon=103.72 tag k = mkgmap:on-boundary=1 / /node I am assuming this is to allow us to mark external nodes that connect to external nodes in other tiles - is this correct? This would be fun to experiment with, splitting tiles in gpsmapedit, converting them to osm format and then compiling. Garvan ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Commit: r1620: Can now explicitly tag boundary nodes with mkgmap:on-boundary=1.
Hi Garvan, Can now explicitly tag boundary nodes with mkgmap:on-boundary=1. Apologies for the beginners question, but how do I use this? In the OSM source like this? node id= -1 lat=11.00 lon=103.72 tag k = mkgmap:on-boundary=1 / /node I am assuming this is to allow us to mark external nodes that connect to external nodes in other tiles - is this correct? This would be fun to experiment with, splitting tiles in gpsmapedit, converting them to osm format and then compiling. It's me that should apologise for committing that addition with no explanation. It explicitly says that a given point is a boundary node. Of course, it only makes sense to do that for routable ways. Boundary nodes are normally created automatically when a routable way is clipped at the tile's boundary. This lets you create a boundary node anywhere. It's used like this: tag k='mkgmap:on-boundary' v='1' / So, you were nearly right. Mark ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Commit: r1620: Can now explicitly tag boundary nodes with mkgmap:on-boundary=1.
Mark Burton wrote: Hi Garvan, Can now explicitly tag boundary nodes with mkgmap:on-boundary=1. Apologies for the beginners question, but how do I use this? In the OSM source like this? node id= -1 lat=11.00 lon=103.72 tag k = mkgmap:on-boundary=1 / /node I am assuming this is to allow us to mark external nodes that connect to external nodes in other tiles - is this correct? This would be fun to experiment with, splitting tiles in gpsmapedit, converting them to osm format and then compiling. It's me that should apologise for committing that addition with no explanation. It explicitly says that a given point is a boundary node. Of course, it only makes sense to do that for routable ways. Boundary nodes are normally created automatically when a routable way is clipped at the tile's boundary. This lets you create a boundary node anywhere. It's used like this: tag k='mkgmap:on-boundary' v='1' / So, you were nearly right. Mark Thanks for the more detailed explanation. Garvan ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Generate coastline - can we keep the coastline way?
When --generate-coastline=multipolygon fails, I'm left with a map that has no distinction between land and sea. However, if I don't use --generate-coastline, I at least get a line (from my style/lines). Is there any good reason why generating coastline prevents the line rules from being applied to the coastline ways? It's not a problem when I actually get sea tiles, but it's a serious nuisance when small islands have completely disappeared! ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Generate coastline - can we keep the coastline way?
Toby Speight (t.m.speight...@cantab.net) wrote: When --generate-coastline=multipolygon fails, I'm left with a map that has no distinction between land and sea. However, if I don't use --generate-coastline, I at least get a line (from my style/lines). Is there any good reason why generating coastline prevents the line rules from being applied to the coastline ways? It's not a problem when I actually get sea tiles, but it's a serious nuisance when small islands have completely disappeared! Seconded. It would be visually useful to retain the coastline even when --generate-coastline works fine, as it's nice to see a solid line twixt land and sea. -- Charlie ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Generate coastline - can we keep the coastline way?
On Wed, 24 Mar 2010 14:33:15 +
Toby Speight t.m.speight...@cantab.net wrote:
When --generate-coastline=multipolygon fails, I'm left with a map that
has no distinction between land and sea. However, if I don't
use --generate-coastline, I at least get a line (from my style/lines).
Is there any good reason why generating coastline prevents the line
rules from being applied to the coastline ways?
It's not a problem when I actually get sea tiles, but it's a serious
nuisance when small islands have completely disappeared!
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Perhaps this does what you want?
diff --git a/src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java
b/src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java
index 0b150ef..8d40da2 100644
--- a/src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java
+++ b/src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java
@@ -531,8 +531,9 @@ public class Osm5XmlHandler extends DefaultHandler {
String natural =
currentWay.getTag(natural);
if(natural != null) {
if(coastline.equals(natural))
{
-
currentWay.deleteTag(natural);
-
shoreline.add(currentWay);
+ Way w =
currentWay.copy();
+ w.deleteTag(natural);
+ shoreline.add(w);
}
else if(natural.contains(;)) {
// cope with compound
tag value
@@ -547,10 +548,11 @@ public class Osm5XmlHandler extends DefaultHandler {
others
+= ; + n;
}
if(foundCoastline) {
-
currentWay.deleteTag(natural);
+ Way w =
currentWay.copy();
+
w.deleteTag(natural);
if(others !=
null)
-
currentWay.addTag(natural, others);
-
shoreline.add(currentWay);
+
w.addTag(natural, others);
+
shoreline.add(w);
}
}
}
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Generate coastline - can we keep the coastline way?
0 In article 20100324151212.64808...@crow, 0 Mark Burton URL:mailto:ma...@ordern.com (Mark) wrote: Mark Perhaps this does what you want? Mark Mark diff --git a/src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java b/src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java That solves my problem perfectly. As to the issue with coastline;cliff, I think that's an instance of a more general issue with semicolon-separated values, and shouldn't preclude applying this patch. Anyone disagree? ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] bug in name command when combined with continue with_actions
Hi
key=value {name 'alpha'} [0x6005 resolution 20 continue with_actions]
key=value {name 'bravo'} [0x5001 resolution 20 continue with_actions]
key=value {set name=alpha} [0x6005 resolution 20 continue with_actions]
key=value {set name=bravo} [0x5001 resolution 20 continue with_actions]
then I will get the two symbols with the correct names alpha and bravo.
key=value {name 'alpha'} [0x6005 resolution 20 continue]
key=value {name 'bravo'} [0x5001 resolution 20 continue]
then I will again get the two symbols with the correct names alpha and bravo.
The difference is down to the 'name' command being like 'add' and not
like 'set'. If you use add instead of set, then it behaves
consistently with the way that name behaves.
..Steve
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Shuttle-Train
Hi, The german island Sylt can only be reached (for cars) on the shuttle train (www.syltshuttle.de). So for now our maps can't route to sylt, because we don't route over railway=rail (even if it's tagged with motorcar=yes). If I look to my Nüvi with Garmin City-Navigator Map, the way looks different than a normal rail-line, so garmin seems to have a special data type for this kind of connection. So, how to handle this? Should we add a rule to the default style to route cars over railway=rail if it is tagged additionaly with motorcar=yes ? Chris ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
