Hi Valentijn, Paul, all,
On Sat, Aug 29, 2009 at 07:29:08AM +0200, Valentijn Sessink wrote:
Paul Johnson schreef:
Routing involving cycleways (by bicycle or by car) makes me wonder why
nobody's bothered getting Garmin's SDK and create new software for those
units...
http://onroute.nl/
Marko Mäkelä schreef:
On Sat, Aug 29, 2009 at 07:29:08AM +0200, Valentijn Sessink wrote:
http://onroute.nl/
Can you please explain how that link is relevant to the Garmin SDK?
It probably isn't. I know them for making a cycle map for the
Netherlands. But they could be using anything to build
On Sat, 2009-08-29 at 07:29 +0200, Valentijn Sessink wrote:
Paul Johnson schreef:
Routing involving cycleways (by bicycle or by car) makes me wonder why
nobody's bothered getting Garmin's SDK and create new software for those
units...
http://onroute.nl/
What is it? (I don't speak Dutch
It's nothing special. They are using standard garmin tools AFAICanTell. They
learned from our maps that proper bicycle/topo maps will only provide good
routing if preference is given in general for bicycleroutes.
The autorouting is pretty good for cyclists, however because of 2 reasons:
1. their
Hi list, hi Mark,
First, a remark. Since the oneway=yes/cycleway=opposite roads have
(cycleway) attached to their names, a GPS unit will randomly show
either the regular name, or the (cycleway) name. Which isn't too bad for
testing, I'd suggest you leave it this way until we're set and done with
Hi Valentijn,
First, a remark. Since the oneway=yes/cycleway=opposite roads have
(cycleway) attached to their names, a GPS unit will randomly show
either the regular name, or the (cycleway) name. Which isn't too bad for
testing, I'd suggest you leave it this way until we're set and done with
Mark,
Mark Burton schreef:
http://www.yournavigation.org/?flat=52.392997flon=4.871082tlat=52.391864tlon=4.87679v=motorcarfast=1layer=mapnik
Any ideas? (I'll recheck the routing later on, to see if this will also
happen with positions further away in one-way-streets).
I think that (at least
Hi V,
Yes, using mapsource, if the cycleway=opposite tag is present it will
route a car into the last segment of Hembrugstraat using the cycleway
but if the destination is not the last segment of that road or the
cycleway tag is not present, it will route the car correctly.
Experimentally, I
I think the condition precedent you're thinking about is wrong here.
The name that shows up in the routing does not have to be the street
that is routed on. At least I see that behaviour quite frequently. How
can I be sure? I use many non routable overlays and they have different
naming.
Hi Mark,
Without the all-cycleways option, it behaves normally. There must be
some sort of Garmin rule in action here. I'll check if there's a better
way (haha) to build the cycleway.
Valentijn
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Mark,
I've tried a couple of different methods to build opposite-cycleways,
namely forbid all motoring traffic, make a real cycleway, but all of
them make the Garmin turn to the last part of the oneway Hembrugstraat.
So I conclude it's a Garmin issue. I'm sure we could come up with all
sorts of
Valentijn,
I've tried a couple of different methods to build opposite-cycleways,
namely forbid all motoring traffic, make a real cycleway, but all of
them make the Garmin turn to the last part of the oneway Hembrugstraat.
So I conclude it's a Garmin issue. I'm sure we could come up with all
Mark,
I think the following could be what happens. The GPS unit tries to route
you to $dest, which is on a non accessible road. As non accessible has
no access, it makes no sense trying other directions.
If there's a crossing, that's a reason to try other directions so the
oneway street will
13 matches
Mail list logo
