Hi Henning,
looking at your files, I see that small rectangles are forced by
overlapping areas.
I think restriction for poly are the same as for option --polygon-file,
quote from doc: "If the polygon area(s) describe(s) a rectilinear area
with no more than 40 vertices, splitter will try to
On 13.01.2018 00:43, Andrzej Popowski wrote:
> Is it this right-angled shape of polys required?
I'm not 100% sure, but somehow I remember Gerd told me it needs to be
rectangle shaped.
Hening
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Small tiles are mainly caused by not well aligned polygons. I attached
you kmz with my splitter result. You can compare them for example in
josm. I just have realized the small tiles while testing in beginning of
DEM-support. While checking for broken img-files with 0kb I found
several others with
Hi Henning,
you are right, using splitter is a valid alternative to my process.
Is it this right-angled shape of polys required? And where are created
small tiles, around any border or only on overlapping areas?
--
Best regards,
Andrzej
___
Hi Andrzej
For Africa it can be useful, as areas with drive on left /right are at
least roughly horizontal and vertical. Also you don't need overlapping
for this use case.
In general I also think, as soon as mkgmap can support non-rectangle
tiles, it will be better obsolete. Using non-rectangle
Hi Henning,
> --polygon-desc-file=filename.osm
Thanks for info. That's very interesting. Actually I would like similar
processing for mkgmap, since I'm satisfied with standard splitting.
But I see a good uses for this feature. I can create polygons for drive
on left and drive on right
Oh, forgotten to mention:
--polygon-desc-file=filename.osm you need to use for splitter.
Henning
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Something similar is already possible with splitter. You can create an
*.osm file with many polygons inside, each with tags name=* and mapid=*
(see attachment). splitter will give you tiles with 6234 and per
polygon a .args with list of necessary data tiles per map. That
args-file you can hand
Hi Henning,
> you should be able to split Europe once and then just let mkgmap
> calculate all the country maps based on the boundary polygons
I'm doing something similar for my maps. I create a map of a continent,
for example Africa and then I execute mkgmap with list of img to create
Hi Gerd,
ok, maybe I was too fast. ;-)
I just tried to understand your Bremen example. You have splitted Lower
Saxony (Niedersachsen) into 15 tiles. Based on these 15 tiles you want
to let mkgmap create a map of Bremen by using a map polygon, which is
not following any of the splitted tiles. Lets
and <o...@hscholland.de>
Gesendet: Freitag, 12. Januar 2018 14:31:59
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] The 0x4b background polygon in the overview map
So your idea was basically:
User has splitted a data file covering city A in the upper part and city
B in the lower pa
___
> Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von
> Henning Scholland <o...@hscholland.de>
> Gesendet: Freitag, 12. Januar 2018 13:16:19
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] The 0x4b backg
Hi Gerd,
using poly to clip background could be a way to create irregular maps.
There are some caveats.
Background doesn't clip map data, they will be still visible. The proper
way would be to clip data too.
Detailed tiles and overview map have different resolution and usually
their edges
9
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] The 0x4b background polygon in the overview map
Hi Gerd,
I probably didn't got your issue.
So far I understand I gave mkgmap a list of data tiles or already
compiled map tiles. based on this mkgmap creates a complete map. A
uftrag von
> Henning Scholland <o...@hscholland.de>
> Gesendet: Freitag, 12. Januar 2018 12:35:04
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] The 0x4b background polygon in the overview map
>
> Hi Gerd,
>
> I think this would be best and additionall
r 2018 12:35:04
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] The 0x4b background polygon in the overview map
Hi Gerd,
I think this would be best and additionally I would suggest to make the
polygon defined by user (as suggested in DEM-poly and precomp-sea
thread). As default I
Hi Gerd,
I think this would be best and additionally I would suggest to make the
polygon defined by user (as suggested in DEM-poly and precomp-sea
thread). As default I would limit overview map to the map tiles. Maybe
then we should name the parameter --overview-map-polygon=filename
I'm not
Hi all,
up to now mkgmap always creates a rectangular 0x4b polygon for the overview
map. I wonder
if I should change that so that the 0x4b polygons of the sub tiles are used.
This seems to be the better way if we start using non-rectangular 0x4b polygons?
Gerd
18 matches
Mail list logo
