Regards
>
> Gary
>
>
> From: mkgmap-dev on behalf
> of Ticker Berkin
> Sent: 28 July 2016 16:41
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Option to output polygons in size order
>
> Hi Gary
>
> For my problem areas I'll look at the O
t;
> Gary
>
>
> From: mkgmap-dev on behalf
> of Ticker Berkin
> Sent: 28 July 2016 16:41
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Option to output polygons in size order
>
> Hi Gary
>
> For my problem areas I'll look at the OS
From: mkgmap-dev on behalf of Ticker
Berkin
Sent: 28 July 2016 16:41
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Option to output polygons in size order
Hi Gary
For my problem areas I'll look at the OSM relationships in exact detail
- I&#
y
>
>
> From: mkgmap-dev on behalf
> of Ticker Berkin
> Sent: 24 July 2016 17:59
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Option to output polygons in size order
>
> Hi Gary
>
> I wasn't proposing to change priority of anything or make render
On Sun, Jul 31, Gerd Petermann wrote:
> The only other input file is the bounds file. I cannot think of a good reason
> why that would
> change the result unless it is somehow corrupted.
The coastlines where several times broken in the last weeks and I saw
a flooding of europe. Somebody was so
ile and use that as input for mkgmap.
>
> Next, you can enable logging so that you see what happens in mkgmap.
>
>
> Gerd
>
> --
> *Von:* mkgmap-dev im Auftrag von
> Felix Hartmann
> *Gesendet:* Freitag, 29. Juli 2016 13:12:05
>
> *A
: [mkgmap-dev] Option to output polygons in size order
I guess the area_size() function kinda checks if it's big enough - and in turn
does not check anymore if it is part of the multipolygon or not. Else I really
cannot explain the flooding. I can change all lines which have 0x3c to a unique
n
--
> *Von:* mkgmap-dev im Auftrag von
> Felix Hartmann
> *Gesendet:* Freitag, 29. Juli 2016 11:45:47
>
> *An:* Development list for mkgmap
> *Betreff:* Re: [mkgmap-dev] Option to output polygons in size order
>
> Nope - it's not the splitter - it&#x
mkgmap
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Nope - it's not the splitter - it's fully within one tile. I guess there is a
bug in the style parser together with area_size() filter and continue command?
I actually looked at it with gpsmapedit - and I see the isl
d
>
> avoid that.
>
>
> Gerd
> ----------
> *Von:* mkgmap-dev im Auftrag von
> Felix Hartmann
> *Gesendet:* Freitag, 29. Juli 2016 00:11:45
> *An:* Development list for mkgmap
> *Betreff:* Re: [mkgmap-dev] Option to output polygons in size order
&
Gesendet: Freitag, 29. Juli 2016 00:11:45
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Well - recompiled and this time the Chieemsee is fine. Really do wonder why it
missed the islands. Next time someone reports somethink like this - or I notice
a
gt; the way 4605746 is an inner member of mp-relation
> > > https://www.openstreetmap.org/relation/32246
> > >
> > > I see no problems with the default style. Do you still have the 18.07.
> > > data ?
> > >
> > >
> > > Gerd
> > >
> >
y
>
>
> From: mkgmap-dev on behalf
> of Ticker Berkin
> Sent: 24 July 2016 17:59
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Option to output polygons in size order
>
> Hi Gary
>
> I wasn't proposing to change priority of anything or make render
mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Option to output polygons in size order
Hi Gary
I wasn't proposing to change priority of anything or make rendering
priority lists, just to change the order of polygons in the output
file. I don't see that this would make any difference t
t; data ?
> >
> >
> > Gerd
> >
> >
> > --
> > *Von:* mkgmap-dev im Auftrag von
> > Felix Hartmann
> > *Gesendet:* Mittwoch, 27. Juli 2016 14:59:51
> >
> > *An:* Development list for mkgmap
> > *Betreff:*
Gesendet: Mittwoch, 27. Juli 2016 15:30:09
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Ah - I guess the Chieemsee will be taken from the sea input files - won't it? I
never really now what water features are taken from which input. If
* Mittwoch, 27. Juli 2016 14:59:51
>
> *An:* Development list for mkgmap
> *Betreff:* Re: [mkgmap-dev] Option to output polygons in size order
>
> Oh - check the Herreninsel Chieemsee. It was flooded based on 18.07 data
> and already flodded in June. Was fine in March though.
&g
. Juli 2016 14:59:51
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Oh - check the Herreninsel Chieemsee. It was flooded based on 18.07 data and
already flodded in June. Was fine in March though.
http://www.openstreetmap.org/way/4605746
It should
ctive. Do you know such a region?
>>
>>
>> Gerd
>>
>>
>> --
>> *Von:* mkgmap-dev im Auftrag
>> von Felix Hartmann
>> *Gesendet:* Mittwoch, 27. Juli 2016 14:31:28
>>
>> *An:* Development list for mkgmap
>&g
re important. Do you have examples for that,
>>
>> esp. cases where shapes do only partially overlap?
>>
>>
>> Gerd
>> --
>> *Von:* mkgmap-dev im Auftrag
>> von Felix Hartmann
>> *Gesendet:* Mittwoch, 27
von Felix
Hartmann
Gesendet: Mittwoch, 27. Juli 2016 14:31:28
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Well the smaller polygon in usual is the one that people expect to end up on
top. HOWEVER - before even checking for size - there could
> polygon is more important. Do you have examples for that,
>
> esp. cases where shapes do only partially overlap?
>
>
> Gerd
> --
> *Von:* mkgmap-dev im Auftrag von
> Felix Hartmann
> *Gesendet:* Mittwoch, 27. Juli 2016 13:24:37
> *An
erkin
Gesendet: Mittwoch, 27. Juli 2016 13:35:05
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Hi Gerd
Thanks for this. I've just tested it and a see quite a few land-use
type features that I didn't see before, and changes in my sus
etreff: Re: [mkgmap-dev] Option to output polygons in size order
On 27 July 2016 at 09:29, Gerd Petermann
mailto:gpetermann_muenc...@hotmail.com>> wrote:
reg. the idea of "cutting out overlaps": I guess it would consume quite a lot
of CPU and it would heavily increase the img size
cker Berkin
> Gesendet: Mittwoch, 27. Juli 2016 11:57:17
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] Option to output polygons in size order
>
> Hi all
>
> Gerd, do you have a patch I can try - I have some examples where this
> should fix things.
>
> I&
On 27 July 2016 at 09:29, Gerd Petermann
wrote:
> reg. the idea of "cutting out overlaps": I guess it would consume quite a
> lot of CPU and it would heavily increase the img size
>
> because we would have to write many more points. Think of a shape for
> "place=village" with hundreds of holes fo
at's why I did not yet publish the patch.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Mittwoch, 27. Juli 2016 11:57:17
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Hi all
Gerd, do you
Gerd
> Von: mkgmap-dev im Auftrag
> von Felix Hartmann
> Gesendet: Sonntag, 24. Juli 2016 21:40:47
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Option to output polygons in size order
>
> That is not really a good approach. Basecamp orders the polygons
>
s that the order is not
important or if there is a complex rules behind this.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Sonntag, 24. Juli 2016 21:40:47
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Option to output polygons
ilto:mkgmap-dev-boun...@lists.mkgmap.org.uk>>
im Auftrag von Ticker Berkin
mailto:rwb-mkg...@jagit.co.uk>>
Gesendet: Sonntag, 24. Juli 2016 20:23:41
An: mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
Betreff: Re: [mkgmap-dev] Option to output polygons in s
---
> *Von:* mkgmap-dev im Auftrag von
> Ticker Berkin
> *Gesendet:* Sonntag, 24. Juli 2016 20:23:41
> *An:* mkgmap-dev@lists.mkgmap.org.uk
> *Betreff:* Re: [mkgmap-dev] Option to output polygons in size order
>
> Hi Gerd
>
> Looking at the meaning o
little
for a patch .
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Sonntag, 24. Juli 2016 20:23:41
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Hi Gerd
Looking at the meaning of the sub-division, this looks like just
Hi Gerd
Looking at the meaning of the sub-division, this looks like just the
place to try and order the polygons by size! What governs the order
they appear in at the moment? The size should be the full size of the
individual polygon.
Concerning the new thread "Why do we render place=island polyg
ta integrity than it is about
> rendering a map. So I am not sure if it fits within the mkgmap remit.
>
> Regards
>
> Gary
>
>
>
>
> From: mkgmap-dev on behalf
> of Ticker Berkin
> Sent: 23 July 2016 19:44
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re
Hi Ticker,
Ticker Berkin wrote
> I'd understood and hoped that, for areas with the same level it
> rendered areas in file order, and I see on my device it overwriting,
> sometimes woods with island, sometimes the other way around, depending
> on, I presumed, the input ordering. I see the exactly t
mkgmap-dev on behalf of Ticker
Berkin
Sent: 23 July 2016 19:44
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Option to output polygons in size order
Hi Gary
Experimenting with my device, using the in-build area representations
(ie no TYP section in my map) it seems as if diffe
t; one sub area
> overlaps polygons in other sub areas. I assume that the order in
> which these
> sub areas are rendered depends on the direction you are moving.
>
> Gerd
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Samstag, 23. Juli 2016 22:00:12
&g
on: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Samstag, 23. Juli 2016 22:00:12
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Option to output polygons in size order
Hi Gerd
I don't understand how multi-polygon processing works, but was
presuming that, if my idea wo
etmap, to make it an inner polygon. when i download the
> > new OSM data I expect it to work correctly.
> >
> > if the polygons are set correctly on openstreetmap, then draw order
> > will will as you expect.
> >
> > Gary
> >
> > From: mkgmap-dev
you mean by splitter delaying things.
>
> Gary
>
> From: mkgmap-dev on behalf
> of Ticker Berkin
> Sent: 23 July 2016 18:42
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Option to output polygons in size order
>
> Hi
>
> I'm sure
treff: Re: [mkgmap-dev] Option to output polygons in size order
Hi
I'm sure that the order in the map has some effect on the Legend; as I
zoom in or scroll across areas with greenery they appear briefly and
are then cleared, by the island polygon that covers everything, as it
starts drawin
correct draw order works fine.
Not sure what you mean by splitter delaying things.
Gary
From: mkgmap-dev on behalf of Ticker
Berkin
Sent: 23 July 2016 18:42
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Option to output polygons in size ord
to handle the draw order is to use a typ file, not
> sure
> if this works on your device, but it seems to work well for others.
>
> Gerd
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Samstag, 23. Juli 2016 18:45:59
> An: mkgmap development
> Betreff: [
tmap, then draw order will will
as you expect.
Gary
From: mkgmap-dev on behalf of Gerd
Petermann
Sent: 23 July 2016 17:05
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] Option to output polygons in size order
Hi Ticker,
are you sure that the ord
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Samstag, 23. Juli 2016 18:45:59
An: mkgmap development
Betreff: [mkgmap-dev] Option to output polygons in size order
Hi
I'm using splitter-r437/mkgmap-r3676 to make a map for Etrex Legend
from british-isles-latest.os
Hi
I'm using splitter-r437/mkgmap-r3676 to make a map for Etrex Legend
from british-isles-latest.osm.pbf from geofabric.de.
Using "default" style and not using a TYP file, no land features
(woods,marsh,green) show because an island polygon for "British Isles"
is rendered near the end, on top of e
46 matches
Mail list logo
