Fed up of being routed in your car down city streets only to find the
way is blocked by a bollard? Well, if so, this is the patch for you.
If a way has a bollard on a point, the segments of the way that
connect to the bollard have access restrictions placed on them. By
default, a bollard
Hi Marco,
I read on wiki that cycle_barrier has no default access rule. I think you
should be more conservative and, in absence of explicit tags, let bicycles
passing through (wiki says that cycle_barrier should only imply
motor_vehicle=no)
You're right, will fix for v2.
Cheers,
Mark
--- Mar 7/7/09, Mark Burton ma...@ordern.com ha scritto:
Da: Mark Burton ma...@ordern.com
Oggetto: [mkgmap-dev] [PATCH v1] - beware of the bollards!
A: mkgmap-dev@lists.mkgmap.org.uk
Data: Martedì 7 luglio 2009, 15:30
Fed up of being routed in your car down city streets only
to find the
Hi Dermot,
I like what you're doing here, but won't that have negative impact if
the adjoining way segments are fairly long? Might it prevent you from
being routed to within, say, 200m of the bollard? Or will an
only-viable-route logic kick in here?
My testing indicates the later. If there
Steve Ratcliffe wrote:
It seems that the action rules are being used a lot more than I thought
going some way beyond what they were designed for. We need to look at what
the actions are being used for.
If it helps, I finished (\o/) the map I was working on, and have
uploaded both it and
--- Mar 7/7/09, Mark Burton ma...@ordern.com ha scritto:
Da: Mark Burton ma...@ordern.com
Oggetto: Re: R: [mkgmap-dev] [PATCH v2] - beware of the bollards!
A: mkgmap-dev@lists.mkgmap.org.uk
Data: Martedì 7 luglio 2009, 17:50
Hi Marco,
Mark, may I suggest a totally different approach?
Steve Ratcliffe schrieb:
highway=* {set tag_a=yes}
tag_a!=yes {set tag_b=yes}
tag_a=yes [0x01 resolution 20]
tag_b=yes [0x02 resolution 20]
highway=* [0x03 resolution 20]
Will all highways be converted to 0x01, 0x02 or 0x03?
My guess was 0x01. But it turns out that I was wrong :)
2009/7/7 Mark Burton ma...@ordern.com:
Fed up of being routed in your car down city streets only to find the
way is blocked by a bollard? Well, if so, this is the patch for you.
If a way has a bollard on a point, the segments of the way that
connect to the bollard have access restrictions
Hi Marco,
Mark, the wiki page about restrictions
http://wiki.openstreetmap.org/wiki/Relation:restriction
says I can put a key except with the following values/meaning:
except - psv/bicycle/hgv/motorcar - The restriction does not apply to these
vehicle types (more than one:
Hi
And I think, if I would change the second line to
highway=* tag_a!=yes {set tag_b=yes}
adding in the missing '' sign:
highway=* tag_a!=yes {set tag_b=yes}
Then that is allowed, and the result would still be that all
highways were 0x01.
it wouldn't change anything, or would it?
What
2009/7/7 Ralf Kleineisel r...@kleineisel.de
On 07/06/2009 12:57 AM, svn commit wrote:
--dem-increment Verical distance between the contour lines (default is
10m).
I have a suggestion here:
Currently I use SRTM2OSM to make the contour layers. I use two different
styles to make two SRTM
2009/7/7 Torsten Leistikow de_m...@gmx.de
Steve Ratcliffe schrieb:
highway=* {set tag_a=yes}
tag_a!=yes {set tag_b=yes}
tag_a=yes [0x01 resolution 20]
tag_b=yes [0x02 resolution 20]
highway=* [0x03 resolution 20]
Will all highways be converted to 0x01, 0x02 or 0x03?
My guess
Hi Martin,
But what about using turn restrictions instead of manipulating the
nearest segments of the ways?
See recent posts.
The reason is: if my destination is on side A of the bollard on the
restricted segment, garmin would still send me via the bollard whe
it's shorter because it
Hi
http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Cycle_map
http://svn.openstreetmap.org/applications/utils/export/garmincyclemap/network/
http://www.openstreetmap.org/user/Richard/diary/6949
Looks great! Is there anything that you would really like it to do that it
doesn't yet?
-- Mar 7/7/09, Mark Burton ma...@ordern.com ha scritto:
Da: Mark Burton ma...@ordern.com
Oggetto: Re: R: [mkgmap-dev] [PATCH v2] - beware of the bollards!
A: mkgmap-dev@lists.mkgmap.org.uk
Data: Martedì 7 luglio 2009, 18:38
Hi Marco,
Mark, the wiki page about restrictions
Steve Ratcliffe schrieb:
You cannot set the same tag that you are matching. (Currently there is
a bug and it will hang, but the intended result would be just that it is
ignored
as it is too late.)
All actions will be run before the final matching rule is selected and the
action rules are
v3
now adds extra points either side of the POI to reduce length of
way that has restricted access. Currently points are 25m away from the
POI. It would be nice if they were really close (like 5m) but if you
try that, the map looks crap due to the limited coordinate resolution.
So, 25m is a
Hi,
On Tue, Jul 07, 2009 at 11:03:41PM +0100, Mark Burton wrote:
[...]
diff --git a/resources/styles/default/points b/resources/styles/default/points
index 1c3ae8f..a97fc13 100644
--- a/resources/styles/default/points
+++ b/resources/styles/default/points
@@ -166,3 +166,7 @@
Nop schrieb:
Hi!
Christian Gawron schrieb:
This version of the patch (to be applied against rev. 1080) has a
HGTDEM which reads SRTM .hgt files and an optional GeoTiffDEM which
contains inner classes to read CGIAR and ASTER.
I would like to try out this patch, but first I have to ask a
I tried to run the splitter on massachusetts.osm (from cloudmade)
because my mac with a paltry 2G of ram couldn't cope in one piece. I
got an exception about bad versoin number in class file, and I wonder if
the splitter requires java 1.6? It would be nice if all the osm java
code worked with
I took the Cloudmade massachusetts.osm.bz2 from July 1st, and because I
wanted a routable map tried to make my own. I ran the splitter just
fine (mac, with java 1.6), and then ran mkgmap like this:
java -enableassertions \
-Xmx2048m \
-jar mkgmap.jar \
--tdbfile \
--gmapsupp \
try to remove option mapname. this didn't work in Mapsource.
After switching to gmapibuilder it worked without any problems in
Roadmap with my options
Also ignore-osm-bounds doesn't make sense if you split with splitter.
splitter creates aligned bounds and uses some overlaps to let mkgmap
22 matches
Mail list logo
