0> In article ,
0> Chris-Hein Lunkhusen mailto:chris66...@gmx.de> ("CL") wrote:
CL> Map this beast with a new way (railway=shuttle or something like
CL> that).
That first solution is probably simpler than
CL> Or implement a mkgmap option to unglue railway_crossings.
I have a third idea, simila
> In case multiple ways were joined to a polygon the polygon was tagged
> with the union set of tags of all joined ways. This algorithm is not
> compatible to the tag join algorithm described on the multipolygon
> relation definition
> (http://wiki.openstreetmap.org/wiki/Relation:multipolygon#Taggi
> WanMil wrote:
>> Hi Steve,
>>
>> I have just started to have a look on the internals of the garmin
>> fileformat. The wiki
>> (http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Format) tells me
>> that there are the formats
>> TRE
>> NOD
>> MDR
>> SRT
>> GMP
>> DEM
>>
>> The documentation of t
Steve Ratcliffe schrieb am 25.03.2010 18:24:
> The best place is on the wiki at:
> http://wiki.openstreetmap.org/wiki/Mkgmap/help/style_rules
>
> On the whole it doesn't include things that were not added by me
> though.
Obviously there are some features missing. At least now I know, where I sho
Hi
> Actually where is the best description/user guide for the different commands
> of
> the style files? The help for the command line parameters is maintained within
> the help parameter of mkgmap, but details of the style-commands are hard to
> find. I don't even know a single list on the net
> 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
>
Steve Ratcliffe schrieb am 25.03.2010 00:49:
> 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.
Ah, thanks for the explanation.
Actually where is the best description/
On 25 Mar 2010, at 7:50 , Carsten Schwede wrote:
> Hi,
>
> Am 25.03.2010 15:27, schrieb Apollinaris Schoell:
>> for rectangle tiles with correct bounding box info mkgmap will create
>> the boundary nodes. there is no need to do it in splitter. Mark added
>
> We use a special splitting program t
Marko Mäkelä schrieb:
>>> I found that I had to set the ferry road class to 3 to be able to
>>> reliably route using them.
>> Ohhh. So maybe this should be changed in the default style.
> Consider it done in revision 1609.
Hi,
thanks but the patch did not solve my problem. Still routing
is only
Hi,
Am 25.03.2010 15:27, schrieb Apollinaris Schoell:
> for rectangle tiles with correct bounding box info mkgmap will create
> the boundary nodes. there is no need to do it in splitter. Mark added
We use a special splitting program that cares about the ways. All ways
are complete in one tile, a
>>
> I think you got it right, although I have not tested it yet, and it is
> different than the way gpsmapedit does it. If B is tagged as a boundary
> node in both tiles then it should work. That is the way it works in
> other garmin map compilers, so it should be an underlying feature of the
Carsten Schwede wrote:
> Hi,
>
> Am 25.03.2010 10:42, schrieb garvan.m...@online.com.kh:
>
>> Before splitting the nodes are like this
>>
>> C
>> |
>>A-B
>> |
>> |
>> D
>>
>
> Right.
>
>
25.03.2010 13.14.28, Toby Speight wrote:
> I'll look into enabling logging; last time I did, there was *masses*
> of output.
I have that too, but I shove the "harmless" or "known" warnings under
the carpet with a set of regexps.
Some weeks ago, I classified all multipolygon errors that I got
0> In article <1269513322.3023...@x60s>,
0> Marko Mäkelä mailto:marko.mak...@iki.fi> ("Marko") wrote:
Marko> I wanted to say that if you are always generating the same
Marko> region, it should not be that hard to enable the logging and to
Marko> work out from the error messages what the issues are
24.03.2010 16.35.55, Marko Mäkelä kirjoitti:
> 24.03.2010 16.33.15, Toby Speight kirjoitti:
>> 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 st
Hi,
Am 25.03.2010 10:42, schrieb garvan.m...@online.com.kh:
>
> Before splitting the nodes are like this
>
> C
> |
>A-B
> |
> |
> D
Right.
> After splitting the nodes are like this
> with a new n
24.03.2010 16.33.15, Toby Speight kirjoitti:
> 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 genera
Quoting Carsten Schwede :
> Hi there,
>
> last I have read here on the mailing list about the tag for routing over
> the tile boundary.
>
> Since we dont use splitter for cutting the planet my question is on
> which nodes must this tag be?
>
> A sample:
>
> Tile1 # Tile2
># C
>
Hi there,
last I have read here on the mailing list about the tag for routing over
the tile boundary.
Since we dont use splitter for cutting the planet my question is on
which nodes must this tag be?
A sample:
Tile1 # Tile2
# C
# |
A-#---B
# |
19 matches
Mail list logo
