Mark,
Sorry for the misunderstanding. Without looking, I assumed the SEVERE
error had been introduced by your patch, while it was probably somewhere
between r1127 and r1131 (not sure, did not look again). Without your
patch, the same errors show up.
However, experimenting a bit with the
v3
This patch is getting serious!
To reduce the number of short arcs that are being generated at tile
boundaries, this now clips the ways before the short arc removal is
done. However, it isn't a perfect solution because some map data is
very hard to deal with:
a - If a way crosses a tile
Hi Valentijn,
Thanks for the feedback.
I have now posted a new patch that should fix the majority of the short
arcs introduced by the clipping. It's not perfect but (I hope) a step
in the right direction.
My own testing shows that the presence of a short arc does not
guarantee that the routing
On Wed, Aug 12, 2009 at 8:01 PM, Thilo Hannemannthann...@gmx.de wrote:
I'm currently working on it. Have you tried the patch together with
routing? In my trials the routing was completely broken after applying
the patch.
I have tried this with routing, but not yet noticed a significant
Good Day,
is mkgmap able to handle inverse oneways (oneway=-1) correctly
(routing opposite to the ways direction) ?
Chris
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Chris,
is mkgmap able to handle inverse oneways (oneway=-1) correctly
(routing opposite to the ways direction) ?
Yes, that has been implemented.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi list, hello Steve,
I made a mistake in my options file, thinking the overview-mapname made
it to the Garmin screen (which is a bit stupid, now I think about it).
Anyway, here's the revised options patch.
Valentijn
--- options 2009-08-12 11:09:48.0 +0200
+++ options.new 2009-08-13
Carlos Dávila schrieb:
A bit of a strange thing: my Garmin mkgmap maps ask the provincie
(Province? State? County? Whatever you guys call it over there ;) when I
want to route to an address.
I have the same problem on a Nüvi 250. Maps build with the
--road-name-pois option. On my etrex this
Blast, just discovered that clipping all ways before doing short arc
removal breaks polygons that straddle tile boundaries. The problem is
that at the time the clipping is done, it is not known whether the way
is a line or a polygon. Oh well, back to square one.
I found two strange things:
- if you don't set --overview-mapname, the tdbfile will have the name of
the overview-mapnumber, 6324.tdb, (instead of OSM_map). The source
reads OSM_map, so I can't find where it goes wrong.
- the --description option seems not to work, there must be something
On Thu, Aug 13, 2009 at 10:47:07AM +0800, maning sambale wrote:
What would be the best and more efficient way to enable address info
in the POIs?
I've been assigning the addr:* tags to all POIs recently. And phone, url,
opening_hours, name, name:* (for multilingual names) where applicable and
It does work, you have to set all 3: series-name (mapset name in Mapsource),
family-name (mapset name on GPS), description -- name for the individual map
tiles - the only of the three that is written directly to the individual
tiles, the both other are written to tdb/overview image.
2009/8/13
Valentijn Sessink wrote:
I found two strange things:
- if you don't set --overview-mapname, the tdbfile will have the name of
the overview-mapnumber, 6324.tdb, (instead of OSM_map). The source
reads OSM_map, so I can't find where it goes wrong.
- the --description option seems not to
Steve Ratcliffe wrote:
Hi
So test 3 still fails, even after applying the patch, or did I do
something wrong applying the patch?
No test 3 still failing was a known problem, there are still cases where
it was known not to work.
..Steve
I had disappointing results when I tried
v4
I have gone back to the original ordering of doing short arc removal
before clipping as the previous version of this patch badly broke
polygons
As for arcs whose length is less 5m, I am not convinced they are
actually a problem as far as routing is concerned as my tests show that
mapsource
2009/8/13 Mark Burton ma...@ordern.com
v4
I have gone back to the original ordering of doing short arc removal
before clipping as the previous version of this patch badly broke
polygons
As for arcs whose length is less 5m, I am not convinced they are
actually a problem as far as routing
Valentijn Sessink wrote:
Hi,
Are you confusing this with the series-name option which assigns the
map name in the Select a Product drop down list in mapsource?
What I'm trying to achieve is a change in my Garmin Nuvi map selection
menu. It is currently saying:
[X] --family-name
Felix Hartmann schreef:
it's --family-name that you want to use.
See above example. Family name is the generic map family name.
description should show up at the place where it says OSM Map, but
it did not - so far. A hard coded description did, however.
The source code just says:
It would be good if people who have been obliged to use a minimum arc
length of 0 would provide examples of where the routing is broken.
i.e. without using this patch, find an example which doesn't route when
--remove-short-arcs is specified but will route when
--remove-short-arcs=5 is
Felix Hartmann escribió:
Valentijn Sessink wrote:
Hi,
Are you confusing this with the series-name option which assigns the
map name in the Select a Product drop down list in mapsource?
What I'm trying to achieve is a change in my Garmin Nuvi map selection
menu. It is currently
Hi Valentijn,
I've only just seen your hex patch sorry, it looks good and I've just checked
it in.
Can you please give me an example of the action='deleted' tag you're talking
about? Do you mean the action='delete' attribute specified in the JSOM file
format?
Dear Steve,
I just tried the patch. Apart from test 3 not working, the modified
PolygonSplitterBase seems not to improve the flooded island problem.
Best wishes
Christian
Steve Ratcliffe schrieb:
Hi
So test 3 still fails, even after applying the patch, or did I do
something wrong
Version 1132 was commited by steve on 2009-08-13 21:13:32 +0100 (Thu, 13 Aug
2009)
Documentation update for overview-mapname.
- Valentijn Sessink
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Version 1133 was commited by steve on 2009-08-13 23:57:39 +0100 (Thu, 13 Aug
2009)
Rounding fixes when placing points on lines
within a subdivision.
Also a small fix to rounding in the subdivision width/height calculation.
-Elrond
___
mkgmap-dev
Marko,
Thanks! These are very helpful.
On 8/13/09, Marko Mäkelä marko.mak...@iki.fi wrote:
On Thu, Aug 13, 2009 at 10:47:07AM +0800, maning sambale wrote:
What would be the best and more efficient way to enable address info
in the POIs?
I've been assigning the addr:* tags to all POIs
25 matches
Mail list logo
