Am 26.10.2012 08:34, schrieb Carlos Dávila:
>> Where is it picking up the configuration to amend the labelling?
>>
> These may be default labels added by Garmin software
Yes, and if using a Typfile they can be set there.
Chris
___
mkgmap-dev mail
I've come across the same only when someone actually named the foot path
Public Footpath - perhaps check the osm?
I'm using the same typ number .
In my experience Mapsource/Basecamp or gps units do not add tags. In the
TOPO GB the word path is found in the lbl.
--
View this message in context:
>
>> So if I understand it right it can be rendered in two ways?
>>
>> In my lines style, add a rule
>> waterway=canal & mkgmap:wayclosed=true {add natural=water}
>>
>> Or
>>
>> Use the continue in the line style after each waterway that needs to
>> be processed
>> and in the polygon style add a ru
Wanmil wrote:
> Yes, the patch prints out the results for *all* ways with log level
> SEVERE. This should enable you to check manually which rules are used
> for which way.
> "Use line rules only..." means that only the lines style file is used
> for this way.
> "Use both rules for..." means that t
> Ok, I have runned the patch on a Benelux extract with only waterways now.
> In the log file I see only SEVERE (StyledConverter): splitter\map.osm: Use
> line rules only for WAY:
> There are no lines saying "Use both rules for..." altough there are some
> waterways that are converted as polygon.
Am 26.10.2012 17:07, schrieb Minko:
> Wanmil wrote:
>> Yes, the patch prints out the results for *all* ways with log level
>> SEVERE. This should enable you to check manually which rules are used
>> for which way.
>> "Use line rules only..." means that only the lines style file is used
>> for thi
wanmil wrote:
> I see: the message "Use both rules..." is printed out only if the way
> is
> not closed and both endpoints are outside the bounding box. So it is
> quite seldom. Anyhow I wonder why you don't see such a message. The
> message is generated before the style files are evaluated so your
Am 26.10.2012 18:52, schrieb Minko:
> I added natural=water to it. If I delete the tag waterway=canal, it will be
> in no matter of time changed by a Potlatch user who thinks that this is not a
> "lake" ;-) If you render it with mkgmap, this canal would be empty otherwise
> (unless the new pa
Hi
> Rule rules;
> + way.addTag("mkgmap:closed",String.valueOf(way.isClosed()));
> + way.addTag("mkgmap:autoclosing", "false");
I don't much like the idea of adding two tags to every single way.
> + // the way may be closed autom
Steve wrote:
> I don't much like the idea of adding two tags to every single way.
>
> > + // the way may be closed automatically because both endpoints are
> > outside the bbox
> > + // set a tag so that these ways can be ignored in the style rules
> > + way.addTag("mkgmap:autoclosing", "true");
>
Hi
> In my test case I haven't seen those issues yet. Even this canal which was
> split in two tiles
> http://www.openstreetmap.org/browse/way/53011144 was rendered as polygon,
> maybe because the first node
> was just within the overlap range (3000) of the other tile?
> So it would only be brok
On 26/10/12 23:38, svn commit wrote:
>
> Version 2341 was commited by steve on 2012-10-26 23:38:41 +0100 (Fri, 26 Oct
> 2012)
> BRANCH: style-include
>
> Bump the style version to 1 and use the new include directive for all the
> address parts that
> are common to the points, lines and polygons f
Yes.
- Original Message -
From: "Steve Ratcliffe"
To: "mkgmap development"
Sent: Saturday, October 27, 2012 5:36 AM
Subject: [mkgmap-dev] Fwd: Maps randomly disappear when zooming (was Fwd:
[OSMPH GPS:25] testing latest mkgmap compiler r2340)
> Hi
>
> I accidentally deleted this pos
13 matches
Mail list logo
