Thank you once again Gerd.
On 15/09/2020 6:05 pm, Gerd Petermann wrote:
Hi Joao,
you probably have a large tile that contains rather few OSM details but a lot
of DEM data. Mongolia would be a typical candidate. With your change of the
--dem-dist option you removed several DEM levels and thus
Hi Joao,
the "fixed poly file is still wrong. The longitude value 188.1459 is not valid,
the range is from -180 to 180 for longitudes and -90 to 90 for latitudes.
I suggest to use JOSM with the poly plugin to create or modify *.poly files.
Gerd
Von:
Hi Joao,
you probably have a large tile that contains rather few OSM details but a lot
of DEM data. Mongolia would be a typical candidate. With your change of the
--dem-dist option you removed several DEM levels and thus drastically reduced
the number of bytes needed for that data.
Gerd
Hi sorry I thought I had sent a response.
I created the poly with input from:
http://geojson.io/#map=2/-1.9/-22.3
I fixed the poly by changing it to:
TITLE
1
-11.21917 45.1531
-11.62209 34.99365
1.996625 35.73983
6.106414 40.61866
53.73163 36.25641
75.16701 36.08421
114.1697 42.97197
Reporting I found a fix for this.
I stopped having the messages and being able to compile my maps after I
changed the following options:
Before:
--dem-dists=3312,3312,9942,13248,26512,44176
--overview-dem-dist=88368
After:
--overview-dem-dist=8
--dem-dists=9942
I'm not sure why some
Hi sorry I thought I had sent a response.
I created the poly with input from:
http://geojson.io/#map=2/-1.9/-22.3
I fixed the poly by changing it to:
TITLE
1
-11.21917 45.1531
-11.62209 34.99365
1.996625 35.73983
6.106414 40.61866
53.73163 36.25641
75.16701 36.08421
114.1697 42.97197
Hi sorry I thought I had sent a response.
I created the poly with input from:
http://geojson.io/#map=2/-1.9/-22.3
I fixed the poly by changing it to:
TITLE
1
-11.21917 45.1531
-11.62209 34.99365
1.996625 35.73983
6.106414 40.61866
53.73163 36.25641
75.16701 36.08421
114.1697 42.97197
Reporting I found a fix for this.
I stopped having the messages and being able to compile my maps after I
changed the following options:
Before:
--dem-dists=3312,3312,9942,13248,26512,44176
--overview-dem-dist=88368
After:
--overview-dem-dist=8
--dem-dists=9942
I'm not sure why some
I was created from data from:
http://geojson.io/#map=2/20.0/0.0
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {},
"geometry": {
"type": "Polygon",
"coordinates": [
[
[
94.921875,
Hi Joao,
how did you create this poly file? The value 189.84375 is obviously wrong and
probably mkgmap / splitter fails to recognize that.
Gerd
Von: mkgmap-dev im Auftrag von Joao
Almeida
Gesendet: Dienstag, 1. September 2020 13:34
An:
For example.
This is the poly file with the areas.
Title
1
-30.41875 45.18952
-30.20899 13.02443
-14.68754 13.38583
-7.346309 27.84205
1.043668 31.57658
0.4144224 37.2386
10.27264 38.32281
14.46764 35.3111
19.29187 39.64797
18.66261 49.64685
6.706903 48.20123
-1.473327 45.18952
-29.16025 45.79186
El 1/9/20 a las 1:39, Joao Almeida escribió:
There is however a different behaviour, this only happens if I try to
include different polygon areas, if I just try the same are by it self
it does not throw the message about map too big.
Could you explain this a little bit further?
Help please, could not find a solution that works.
I'm trying to build a map that includes DEM shading. I've tried
splitting the map with max nodes 80, 60 and this last time 40.
For some reason I always get the following message on the same tile
regardless of the split maxnodes option.
13 matches
Mail list logo
