Hello Joris,
I have interest in help with portuguese (0x10) translate.
How can I help?
Regards,
Wesley
On Sat, Jan 19, 2019 at 7:04 AM Joris Bo wrote:
> Hello Nick
>
>
>
> Thx for your feedback!
>
>
>
> I wrote a program to extraxt icons from a master library to be used on
> different elements in somebodies else his style.
>
> I abuse both language tags as exchange-fields to keep track of mother /
> child relationships.
>
> In the final export, those fields are cleared, but you just find out that
> this is not bullet proof
>
> Thx, I’ll have a look
>
>
>
>
>
> *Van:* mkgmap-dev *Namens *
> osm@pinns
> *Verzonden:* vrijdag 18 januari 2019 12:44
> *Aan:* mkgmap-dev@lists.mkgmap.org.uk
> *Onderwerp:* Re: [mkgmap-dev] default style improvements / updated
> typ-file
>
>
>
> Hi Jorus
>
> Great job!
>
> Just to be a pain, all (I think) your elements have a one character text
> string for Basque and Korean:
>
> ie
>
> String5=0x09,
> String6=0x24,
>
> Perhaps you had big plans for translating labels into Basque or Korean ;)
>
> r
>
> Nick
>
> On 16/01/2019 18:56, Joris Bo wrote:
>
> Hello
>
>
>
> Thx Nick
>
> Attached both issues changed
>
>
>
> @Ticker
>
> It was not easy to address a good polygon color for [0x1e] used for
> ‘historic’
>
> historic=* & historic!=no & historic!=yes & boundary!=* {add
> name='${historic|subst:"_=> "}'} [0x1e resolution 21]
>
>
>
> “Historic” can be used on almost anything from park to building to museum
> and ruins.
>
> After a compare on ‘Luxembourg’ I decided that ‘building’ is the most
> common occurrence.
>
> So I choosed the arbritrary color ‘grey’
>
>
>
> Maybe you could consider to use poi’s instead of polygons for historic.
>
> If somebody likes a different color, give me a hint.
>
>
>
> Kind regards,
>
> Joris
>
>
>
>
>
>
>
>
>
> *Van:* mkgmap-dev
> *Namens *osm@pinns
> *Verzonden:* dinsdag 15 januari 2019 22:01
> *Aan:* mkgmap-dev@lists.mkgmap.org.uk
> *Onderwerp:* Re: [mkgmap-dev] default style improvements / updated
> typ-file
>
>
>
> Hi Jorus
>
> You have a draworder for 0x1e without a matching polygon.
>
> (Also, to have 0x53 sharing the same draworder as 0x4b might depending on
> your map be problematic)
>
> r
>
> Nick
>
> On 15/01/2019 20:51, Joris Bo wrote:
>
> Hello
>
>
>
> My previous typ had 2 bugs (No draworder for new lake 0x41) making lakes
> invisible and missing wilderniss hut
>
> Both are fixed in attached typ.
>
>
>
> There were also a couple of polygons and lines having a night color bitmap,
> for now I removed them and introduce them again if complete. There is help
> coming up from Michael to fill that gap.
>
> Feel free to send more findings
>
>
>
> Kind regards
>
> Joris
>
>
>
>
>
> -Oorspronkelijk bericht-
>
> Van: mkgmap-dev
> Namens Ticker Berkin
>
> Verzonden: maandag 14 januari 2019 12:24
>
> Aan: Development list for mkgmap
>
>
> Onderwerp: Re: [mkgmap-dev] default style improvements / upated typ-file
>
>
>
> Hi
>
>
>
> I agree the name change from mkgmap.txt to something else (no problem with
> mapnik.txt) is needed.
>
>
>
> I haven't been through this TYP in detail yet. Some of my previous comments
> still stands:
>
> http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q4/029103.html
>
>
>
> I'd like another, much, much simpler, TYP file for the default style also to
> be available. It would avoid re-defining representation that the typical
> Garmin device shows.
>
>
>
> In my next set of changes I'm planning to change quite a few TYPE numbers,
> many as suggested in this thread on 13-Nov-2018:
>
> http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q4/029146.html
>
> but there will be some differences from this post.
>
>
>
> Some of these cover Joris's "changes to be considered". Some of the other
> suggestions I feel are too much for the default style but I will consider
> them.
>
>
>
> It will be a few days before I'm able to do anything in this area.
>
>
>
> We need some pointers in the documentation to the collection of TYP -files.
>
>
>
> Please can we have these TYP-files in "trunk". I think the "default -typ"
> branch it is a hindrance.
>
>
>
> Regards
>
> Ticker
>
>
>
> On Mon, 2019-01-14 at 06:51 +, Gerd Petermann wrote:
>
> Hi Joris,
>
>
>
> I've replaced the default style in the typ branch by that from trunk
>
> and added your typ with that. I hope that was right?
>
> http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4263
>
>
>
> I think about a move/rename of styles\default\typ.txt to typ
>
> -files\mapnik.txt using the command svn move styles\default\typ.txt
>
> typ-files\mapnik.txt
>
>
>
> Would that be okay for you?
>
>
>
> Reg. the other changes I hope that Ticker has an answer.
>
>
>
> Gerd
>
>
>
>
>
> Von: mkgmap-dev
> im Auftrag
>
> von Joris Bo
>
> Gesendet: Sonntag, 13. Januar 2019 12:11
>
> An: Development list for mkgmap
>
> Betreff: Re: [mkgmap-dev] default style improvements / upated typ
>
> -file
>
>
>
> Hello,
>
>
>
> I
