[mkgmap-dev] errors in routing

2009-08-01 Thread Garvan
Hi,

Using polish format as input, I get routing errors on roads that have 
been split by mkgmap. The errors do not show up on all roads split, but 
they show up on most. The map will not route onto the split road. From 
what I can see the roads are being split because they exceed the maximum 
number of points in a line (250).

I will test OSM data to see if it has the same problem, but I assume it 
would have been reported. I guess not many are using polish format input.

Garvan


___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


[mkgmap-dev] complete list of all mkgmap options

2009-08-01 Thread Christoph Wagner
Hello list,
I searched for a complete list of all mkgmap command-line options and
what they should do, but I couldn't find a good and up-to-date list. The
list in the wiki is much too old.
In the last few month they were very cool and usefull improvements of
mkgmap but it's sometimes not easy to use and test them because they are
not known.
I would wish to have a Wiki page with all mkgmap options, their
functionality, their usage and their status (stable, unstable...).

Do you think this is a good idea?
Where can I find a list of the options to fill the wiki page?

Thank you and have a nice day!
Christoph from Dresden



signature.asc
Description: OpenPGP digital signature
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Magic highway symbols on Vista CX failing

2009-08-01 Thread Clinton Gladstone
On Jul 31, 2009, at 19:54, Alexander Wittig wrote:

 So I did some research and I think the problem is that not all of the
 magic symbols in
 src/uk/me/parabola/mkgmap/osmstyle/actions/HighwaySymbolFilter.java  
 are
 available on the unit. Also they are named wrongly for this unit.

Just out of interest, have you tried using the  --latin1 option when  
you compile your map?

This switches to 8-bit mode (or something) which uses different byte  
codes for the highway symbols. It is possible that there are errors in  
the 6-bit codes.

At any rate, I compile my maps with this option, and the highway  
symbols appear correctly, both in Mapsource and on my eTrex Vista HCx,  
which I assume should be very close to your Vista CX in display  
characteristics.

When I tested this, I also noticed that the US Interstate and other  
highway shields were of limited use, as they appeared to only display  
numeric values. Therefore I stayed with the highway-symbol:hbox, box  
and oval symbols.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] complete list of all mkgmap options

2009-08-01 Thread Johann Gail
You should get this list by calling mkgmap --help (or similar)

Christoph Wagner schrieb:
 Hello list,
 I searched for a complete list of all mkgmap command-line options and
 what they should do, but I couldn't find a good and up-to-date list. The
 list in the wiki is much too old.
 In the last few month they were very cool and usefull improvements of
 mkgmap but it's sometimes not easy to use and test them because they are
 not known.
 I would wish to have a Wiki page with all mkgmap options, their
 functionality, their usage and their status (stable, unstable...).

 Do you think this is a good idea?
 Where can I find a list of the options to fill the wiki page?

 Thank you and have a nice day!
 Christoph from Dresden

   
 

 ___
 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


Re: [mkgmap-dev] complete list of all mkgmap options

2009-08-01 Thread Garvan maew
Johann Gail wrote:
 You should get this list by calling mkgmap --help (or similar)

   

Unfortunalty the developers have not kept this list up to date, which 
was the reason for Christoph Wagner post below.

Garvan


 Christoph Wagner schrieb:
   
 Hello list,
 I searched for a complete list of all mkgmap command-line options and
 what they should do, but I couldn't find a good and up-to-date list. The
 list in the wiki is much too old.
 In the last few month they were very cool and usefull improvements of
 mkgmap but it's sometimes not easy to use and test them because they are
 not known.
 I would wish to have a Wiki page with all mkgmap options, their
 functionality, their usage and their status (stable, unstable...).

 Do you think this is a good idea?
 Where can I find a list of the options to fill the wiki page?

 Thank you and have a nice day!
 Christoph from Dresden

   

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] Translating command line strings into target charset

2009-08-01 Thread Steve Ratcliffe

Hi

I know it was quite a while back when you posted this, sorry.

On 24/06/09 21:56, Marko Mäkelä wrote:
 My friend, who owns a Garmin GPSMap 60CSx, notified me of a character set
 problem in a tile name of my map.  I wasn't aware of the problem, because
 my Edge 705 does not display map tile names.  The tile Etelä-Suomi (Southern
 Finland) appears as Etelä-Suomi, where the currency symbol ¤ is displayed
 as a black diamond.  Other ä characters in the gmapsupp.img are encoded as
 the byte code 304 in octal notation.

Yes it just slaps in the string directly without translation.
It appears from your example that it is being displayed as a
latin1 character set.  I don't know what controls that though;
does it take the character set from the LBL section or is
there something else.

A safe first step would be to transliterate to ascii which
works over the widest range of languages in mkgmap.

..Steve
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] errors in routing

2009-08-01 Thread Clinton Gladstone
On Aug 1, 2009, at 10:13, Garvan  maew wrote:

 I re-tested a sample I posted before with routing problems, except  
 this time I converted the data to OSM format first, and it has the  
 same problem with routing as I noted in a larger map, and as I  
 explained above.

 In the attached sample, snip.osm, if is not possible to route from

 N13.10744 E100.92402

 To
 N13.09385 E100.91529

 Without jumping all over the place (or any points points on these  
 roads).

I did a quick test on a map extract of Asia which I had previously  
compiled. I noted no routing errors between these points.

One thing I found suspicious is that you are routing over a motorway  
with only one lane. The default style automatically adds a oneway  
attribute to all motorways. Could this be related to your routing  
problem?

You may wish to try a style file with the add oneway statement  
removed from the following line:

highway=motorway {add oneway = yes; add bicycle = no; add foot = no }  
[0x01 road_class=4 road_speed=6 resolution 12]
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


[mkgmap-dev] Splitter and areas.list format

2009-08-01 Thread Sébastien Pierrel
Hi,

what coordinates format is used to define the areas boundaries in 
areas.list?


Cheers,
/Seb.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


[mkgmap-dev] [PATCH v1] sea polygons

2009-08-01 Thread Christian Gawron

Hi,

the attached patch adds a sea polygon  (based on the bounding box of the 
map) and a multipolygon relation with all lines tagged as 
natural=coastline as inner elements. The code merges coastline 
components as far as possible.
The patch also contains the multipolygon patch by Rudi which wasn't 
commited so far (without this patch, the rendering fails).


The sea polygon is created as natural=sea, for which I added a mapping 
to garmin type 0x32.


Caveat: I have only tested this for islands (Corsica) so far.

Best wishes
Christian
Index: src/uk/me/parabola/mkgmap/reader/osm/Way.java
===
--- src/uk/me/parabola/mkgmap/reader/osm/Way.java   (Revision 1115)
+++ src/uk/me/parabola/mkgmap/reader/osm/Way.java   (Arbeitskopie)
@@ -76,6 +76,10 @@
}
}
 
+public boolean isClosed() {
+   return points.get(0).equals(points.get(points.size()-1));
+}
+
/**
 * A simple representation of this way.
 * @return A string with the name and start point
Index: src/uk/me/parabola/mkgmap/reader/osm/MultiPolygonRelation.java
===
--- src/uk/me/parabola/mkgmap/reader/osm/MultiPolygonRelation.java  
(Revision 1115)
+++ src/uk/me/parabola/mkgmap/reader/osm/MultiPolygonRelation.java  
(Arbeitskopie)
@@ -5,7 +5,6 @@
 import java.util.List;
 import java.util.Map;
 
-import uk.me.parabola.imgfmt.Utils;
 import uk.me.parabola.imgfmt.app.Coord;
 
 /**
@@ -23,8 +22,9 @@
 * this because the type of the relation is not known until after all
 * its tags are read in.
 * @param other The relation to base this one on.
+* @param wayMap Map of all ways.
 */
-   public MultiPolygonRelation(Relation other) {
+   public MultiPolygonRelation(Relation other, MapLong, Way wayMap) {
setId(other.getId());
for (Map.EntryElement, String pairs: 
other.getRoles().entrySet()){
addElement(pairs.getValue(), pairs.getKey());
@@ -33,8 +33,16 @@
 
if (value != null  pairs.getKey() instanceof Way) {
Way way = (Way) pairs.getKey();
-   if (value.equals(outer))
-   outer = way;
+   if (value.equals(outer)){
+   // duplicate outer way and remove tags 
for cascaded multipolygons
+   outer = new Way(-way.getId());
+   outer.copyTags(way);
+   for(Coord point: way.getPoints())
+   outer.addPoint(point);
+   wayMap.put(outer.getId(), outer);
+   if (way.getTags() != null)
+   way.getTags().removeAll();
+   }
else if (value.equals(inner))
inners.add(way);
}
@@ -52,11 +60,20 @@
{   
for (Way w: inners) {   
if (w != null) {
-   ListCoord pts = w.getPoints();
-   int[] insert = 
findCpa(outer.getPoints(), pts);
-   if (insert[0]  0)
-   insertPoints(pts, insert[0], 
insert[1]);
-   pts.clear();
+   int[] insert = 
findCpa(outer.getPoints(), w.getPoints());
+   //if (insert[0]  0)
+   insertPoints(w, insert[0], insert[1]);
+   
+   // remove tags from inner way that are 
available in the outer way
+   if (outer.getTags() != null){
+   for (Map.EntryString, String 
mapTags: outer.getTags().getKeyValues().entrySet()){
+   String key = 
mapTags.getKey();
+   String value = 
mapTags.getValue();
+   if (w.getTag(key) != 
null)
+   if 
(w.getTag(key).equals(value))
+   
w.deleteTag(key);
+   }
+   }
}
}
}
@@ -64,22 +81,39 @@
   

Re: [mkgmap-dev] [PATCH v1] sea polygons

2009-08-01 Thread Christian Gawron
I forgot to mention that you have to add --generate-sea if you want to 
have the sea polygon added.

Best wishes
Christian
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] errors in routing

2009-08-01 Thread Garvan maew

Clinton Gladstone wrote:

On Aug 1, 2009, at 10:13, Garvan  maew wrote:

  
I re-tested a sample I posted before with routing problems, except  
this time I converted the data to OSM format first, and it has the  
same problem with routing as I noted in a larger map, and as I  
explained above.


In the attached sample, snip.osm, if is not possible to route from

N13.10744 E100.92402

To
N13.09385 E100.91529

Without jumping all over the place (or any points points on these  
roads).



I did a quick test on a map extract of Asia which I had previously  
compiled. I noted no routing errors between these points.


One thing I found suspicious is that you are routing over a motorway  
with only one lane. The default style automatically adds a oneway  
attribute to all motorways. Could this be related to your routing  
problem?


You may wish to try a style file with the add oneway statement  
removed from the following line:


highway=motorway {add oneway = yes; add bicycle = no; add foot = no }  
[0x01 road_class=4 road_speed=6 resolution 12]


  
Thanks for the tip about highways being one way, and for taking the time 
to look at the issue. I normally  use polish format so I did not think 
about the styles. However when I change the highway and highway_link to 
primary and primary_link the roads are no longer one way and I get the 
same error. I will attach the corrected sample to this post.


I joined roads with the same name and attributes when importing OSM data 
into Polish format, so the road lengths tend to be much longer in my 
data than in the original, making this issue more apparent. The 
unaltered data for Thailand is full of un-connected junctions so it is 
difficult to test.


I have the same error happening in five or six places, all associated 
with split roads. This sample is the smallest file I could make that 
shows the problem.


Garvan





snip.osm.gz
Description: GNU Zip compressed data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev