My feeling with the problem of flooded tiles always was that the
geofabrik extracts are to blame - they're too tight in some places, so
the coastline breaks in the extraction process already, not during the
splitting. That happens for instance in the northwest of germany around
emden and in
i think one could make 2 extra tdb files/overview maps for mapsource - 1
to bundle base/car, another to bundle base/cycle
Am 28.08.2011 18:33, schrieb Minko:
Sounds interesting, but how will you do that?
Can you give an example which I can download?
I don't see how you can tell mapsource
On Mon, Aug 29, 2011 at 08:07:04AM +0200, michael lohr wrote:
My feeling with the problem of flooded tiles always was that the
geofabrik extracts are to blame - they're too tight in some places,
so the coastline breaks in the extraction process already, not during
the splitting. That happens
Hi,
Am 29.08.2011 08:07, schrieb michael lohr:
My feeling with the problem of flooded tiles always was that the
geofabrik extracts are to blame - they're too tight in some places, so
the coastline breaks in the extraction process already, not during the
splitting. That happens for instance in
On Fri, Aug 26, 2011 at 10:51:14PM +0300, Marko Mäkelä wrote:
There should be no difference regarding address search between
revisions before and after merging the locator branch as long as you
define --location-autofill=XXX where XXX does not contain bounds.
OK, I am guilty of not defining
On Sun, Aug 28, 2011 at 11:48:09PM +0300, Bartosz Fabianowski wrote:
I keep seeing the following warning with current trunk (2018):
SEVERE (MapSplitter): 63240001.osm.pbf: Area too small to split at [...]
(reduce the density of points, length of lines, etc.)
I can confirm that the patch proposed
Version 2019 was commited by marko on 2011-08-29 08:02:35 +0100 (Mon, 29 Aug
2011)
Implement --ignore-builtin-relations.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
geofabrik extracts are to blame - they're too tight in some places, so
the coastline breaks in the extraction process already
In a sense, this is true. However, *no* polygon can ever be guaranteed
to contain enough data. Even if Geofabrik used a bounding box instead of
a bounding polygon so
It still takes a little tweaking to get the coastlines right. I have
manually chosen the tile borders so that the coastline will end outside
the tile border. Only in the Swedish/Finnish border I am using
extend-sea-sectors to make up some coastline in Sweden.
This is why I collected the
I use my own polygon file to extract germany from the european extract.
It should be sufficient to extract coastlines using that larger polygon
only. Of course once you are extracting, you can just use your own
extracts throughout. But a combination of the Geofabrik extract for map
data and
2011/08/29 09:46:03 WARNING (Subdivision): 63240010.osm.pbf: Subdivision
width is 36627 at 3231057/1236133
I guess it is time to split my tile further. But, this is not the
biggest tile:
The Subdivision class is complaining about the width of an area in
Garmin units. The area may not
fixed tiles may produce better coastlines, but you'll get map too big
at some point as the map grows. so you could either set a large safety
margin and get a lot more tiles or you'd have to fix the tiles anew more
often.
Am 29.08.2011 09:08, schrieb Bartosz Fabianowski:
It still takes a
1. I noticed that (at least for my style-file) 7500MB of RAM available
does not suffice to compile a map of Europe including index! However if
I recreate the index in another go, then it is no problem.
How comes? The index creation seems to be completly independent of the
maptiles creation. Is
fixed tiles may produce better coastlines, but you'll get map too big
at some point as the map grows.
The way I understand Marko's suggestion, you would give the splitter an
initial list of tiles (or just a region) and it would then subdivide
that into smaller tiles as it does today. The
On Mon, Aug 29, 2011 at 10:08:26AM +0300, Bartosz Fabianowski wrote:
This is why I collected the coastlines for all of Europe in a single
file. When all European coastlines are available, you no longer have to
tweak tile boundaries.
There are a few drawbacks to that approach. First, you will
Am 28.08.2011 17:15, schrieb WanMil:
Splitter is generating more than 255 tiles. But there is (or was?) a
limit of 255 tiles per pass. I am not sure if this limit is still
valid. The webpage (http://www.mkgmap.org.uk/page/tile-splitter) is a
bit out of date, e.g. does not tell about support
i'm starting to wonder if we're talking about 2 separate issues that
lead to similar outcomes.
coastlines break because:
1. they get broken in the extraction process because the poly is too tight
2. they get broken in the splitting process
a separate coastline file would quite likely mend
Am 27.08.2011 13:36, schrieb Henning Scholland:
Splitter is generating more than 255 tiles. But there is (or was?) a
limit of 255 tiles per pass. I am not sure if this limit is still
valid. The webpage (http://www.mkgmap.org.uk/page/tile-splitter) is a
bit out of date, e.g. does not tell
Hi
This looks like a bug to me. The attached patch rounds the minimum
longitude/latitude down and the maximum longitude/latitude up, making
sure that the rounded area always fully contains the original area.
Not sure that I agree. Wouldn't this mean that tile boundaries would
overlap if they
Hi Chris,
do you have set --max-areas. I found out, that it is set by default to
255, so that's why splitter uses a second run.
Henning
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi,
Am 29.08.2011 09:09, schrieb Bartosz Fabianowski:
I use my own polygon file to extract germany from the european extract.
It should be sufficient to extract coastlines using that larger polygon
only. Of course once you are extracting, you can just use your own
extracts throughout. But a
Hi,
Am 29.08.2011 01:45, schrieb Bartosz Fabianowski:
Right now, the files were generated once-off. If they are found to be
useful by others, I am happy to automate the process and make updated
coastline files available on a regular basis.
Good idea.
Josef
--
PGP Schlüssel: 311D1055
i'm starting to wonder if we're talking about 2 separate issues
Indeed, it seems so :).
1. they get broken in the extraction process because the poly is too tight
You mean the bounding polygon is so tight that it actually clips away
the coastlines? If so, the bounding polygon is simply
Wouldn't this mean that tile boundaries would overlap if they were
originally touching but not aligned?
Yes, you are right. The splitter code is not sufficiently documented to
make it clear what it is trying to achieve. After looking at the code,
it seemed to me that the goal was to expand
That's great. With this procedure I can use the german extract from
geofabrik without the missing sea near Emden.
You will still have to download all of Europe to extract the boundaries
for your larger polygon. Or alternatively you can use the extracted
boundaries I provided.
- Bartosz
First, you will have to download and process much more data than just
the country extract.
This is why I shared my extracted coastlines. The extraction has to be
done only once. Everyone else can just download the (relatively small)
coastline files.
Second, if the continent extract was
Hi,
Am 29.08.2011 17:16, schrieb Bartosz Fabianowski:
That's great. With this procedure I can use the german extract from
geofabrik without the missing sea near Emden.
You will still have to download all of Europe to extract the boundaries
for your larger polygon. Or alternatively you can
Thanks, that's one person interested in automatically updated
coastlines. I will watch the download logs over the next few days to see
whether I should start generating coastlines daily.
- Bartosz
___
mkgmap-dev mailing list
Not sure about addr:phone though - isn't this deprecated and instead
phone=* is used to fill the telephone field in the address form?
I believe that phone=* is being replaced with contact:phone, just like
url is being replaced with contact:website. I guess we should support
both.
1. I noticed that (at least for my style-file) 7500MB of RAM available
does not suffice to compile a map of Europe including index! However if
I recreate the index in another go, then it is no problem.
How comes? The index creation seems to be completly independent of the
maptiles creation.
On Mon, Aug 29, 2011 at 07:08:44PM +0300, Bartosz Fabianowski wrote:
Absolutely. What I uploaded yesterday were snapshots based on the most
recent Geofabrik Europe extract and the most recent full planet. If
these prove useful, I will make the generation a batch job so that the
coastlines
On 08/28/2011 06:33 PM, Minko wrote:
Sounds interesting, but how will you do that? Can you give an example
which I can download?
Sure. I first run mkgmap on the OSM files to generate the IMGs and the
gmapsupp.img. The config file looks somewhat like this:
gmapsupp
[more options ...]
Boundary extracts could be nice too, but I suppose that the Geofabrik
country extracts already include all the boundary=administrative
lines of the country.
This is an interesting point. The boundary files seem to be updated
about once a month right now. If there is interest in such boundary
I have just uploaded today's coastlines_europe.osm.pbf. The time stamp
matches the europe.osm.pbf file that this was created from.
Right now, I still need to manually upload and fiddle with the
timestamps. I am switching to a better hosting setup in a couple of days
that will allow me to fully
But: Each time I have created these extracts I have found several
country borders that have been broken. So I repaired them before
creating the same stuff again and ensured that the boundary extracts
were uploaded only if the country information was complete.
I am happy to devote server
Bartosz,
thanks for you detailed analysis!!
I have never seen the splitter problem you've described.
Maybe the overlap parameter of splitter prevented that because splitter
puts all points in the tile that is either contained in the bounding box
or contained in a overlap region with width
Maybe the overlap parameter of splitter prevented that because splitter
puts all points in the tile that is either contained in the bounding box
or contained in a overlap region with width overlap garmin units. If
overlap is larger than the expansion you don't see this problem.
I investigated
Version 2020 was commited by wanmil on 2011-08-29 20:46:37 +0100 (Mon, 29 Aug
2011)
Cleanup builtin-tag-list to reduce number of tags loaded by sparse styles
There are three categories of changes:
1. Address tags are now assigned dynamically by the style file. This enhances
flexibility to
2011/08/29 09:46:03 WARNING (Subdivision): 63240010.osm.pbf: Subdivision
width is 36627 at 3231057/1236133
I guess it is time to split my tile further. But, this is not the
biggest tile:
The Subdivision class is complaining about the width of an area in
Garmin units. The area may not
On 29.08.2011 20:52, WanMil wrote:
1. I noticed that (at least for my style-file) 7500MB of RAM available
does not suffice to compile a map of Europe including index! However if
I recreate the index in another go, then it is no problem.
How comes? The index creation seems to be completly
Release 2020 makes it necessary to add some rules to your style if you
want to use the address search.
From now on the address fields are composed by the mgkmap tags:
mkgmap:country
mkgmap:region
mkgmap:city
mkgmap:postal_code
(NEW) mkgmap:street
On 29.08.2011 22:21, WanMil wrote:
Release 2020 makes it necessary to add some rules to your style if you
want to use the address search.
From now on the address fields are composed by the mgkmap tags:
mkgmap:country
mkgmap:region
mkgmap:city
42 matches
Mail list logo
