Graphhhopper does not update the database instantaneously. I believe you will need to wait some time before the routing matches the database: days, not hours. On Sat, Jan 12, 2019 at 9:09 AM Graeme Fitzpatrick <graemefi...@gmail.com> wrote:
> > > On Tue, 25 Dec 2018 at 09:03, Graeme Fitzpatrick <graemefi...@gmail.com> > wrote: > >> >> Guess it might be a case of suck it & see! >> > > So, after a couple of weeks of experimenting & playing with various > blocking options, then checking them with OSRM & GraphHopper (which > incidentally, brings up some pretty strange results - I'm even tempted to > ignore it's results altogether?) by attempting to route through the > roadworks area, I can report back. > > If anybody would like to experiment themselves, the spot I was using is > here: https://www.openstreetmap.org/#map=18/-28.07477/153.43936, with the > various blocks being positioned between house number 77 (Mountain View > Avenue) at the western corner Ernie Tebb Park, & the unmarked crossing / > painted island, between the Park & the lake. > > I was then attempting to route from "12, Honeyeater Drive, Miami, Gold > Coast, Queensland, 4220, Australia" to "20, Nobby Parade, Miami, Gold > Coast, Queensland, 4220, Australia", which is a very simple, quite direct > route. > > Unfortunately, when I say that GraphHopper was giving strange results, > especially for foot & bicycle, it was doing this: > https://www.openstreetmap.org/directions?engine=graphhopper_foot&route=-28.07561%2C153.43761%3B-28.07433%2C153.44100 > . > If this can't be seen, it has foot traffic walking North up Honeyeater > Drive, East down Mountain View Avenue along the road, *not* the adjacent > footpath, going the wrong way round the roundabout, continuing down & > turning South into Babbler Court, then immediately coming back West along > the Mountain View Avenue footpath till just before the roundabout, where it > crosses Mountain View Avenue at the footway=crossing + crossing=unmarked, > follows the round the corner into Nobby Parade, then crosses at another > crossing, before continuing North along the footpath to the destination. > > Bicycle routing is identical, except that it goes the correct way around > the roundabout, before getting onto the footpath! > > So FYI, the results of my testing were: > > 1. single barrier=yes (on the road - the actual marked highway=tertiary); > access=no: didn't render; doesn't stop vehicle, bike or foot access > > 2. single barrier=block (on the road); access=no: rendered as dot only; > doesn't stop vehicle, bike or foot access > > 3. row of barrier=block across both lanes; access=no; rendered as row of > dots; doesn't stop vehicle, bike or foot access > > 4. barrier=bollard (one only on road); access=no: rendered as single dot > only; doesn't stop vehicle, bike or foot access > > 5. row of barrier=bollard across both lanes; access=no; rendered as row of > dots; vehicles are blocked in OSRM, but GraphHopper still allows bike, foot > & vehicle access > > 6. single barrier=jersey_barrier (on road); access=no: rendered as dot > only; doesn't stop vehicle, bike or foot access > > 7. row of barrier= jersey_barrier across both lanes; access=no; rendered > as row of dots; doesn't stop vehicle, bike or foot access > > 8. single barrier=gate (on road); access=no: rendered as dot only; doesn't > stop vehicle, bike or foot access > > 7. barrier=fence (across full width of road); access=no: rendered on both > sides of the road, but not across the road itself; vehicles are blocked in > OSRM, but GraphHopper still allows bike, foot & vehicle access > > 8. barrier=gate in barrier=fence in middle of roadway; access=no on both; > gate didn't render, fence still only visible on both sides of the road, but > not across the road itself; vehicles are blocked in OSRM, but GraphHopper > still allows bike, foot & vehicle access > > 9. barrier=ditch (across full width of road); access=no; didn't render; > doesn't stop vehicle, bike or foot access > > 10. Least favourable option by far :-( > Split the road & cut a small (~5m) section out; shows as two road endings > actually touching; vehicles are blocked in OSRM, but GraphHopper still > allows bike, foot & vehicle access > > Increase gap to ~20m; gap shown in road; doesn't stop vehicle, bike or > foot access in either router, after a small gap did block OSRM? > > Increase road gap to ~50m by cutting it at corner of Honeyeater Drive, so > whole section of road has disappeared; everything is stopped from going > that way, including foot & bike, even though there's a marked footpath > along the side of the road? > > Unless I've been doing something wrong with the way I've been placing the > various blocks, this has got me totally confused? > > Why do we have the various blocking options if they don't actually stop > you driving through them? > > Both routers show foot traffic walking along the length of the road, not > the adjacent footpath - why? > > Anybody have any ideas, or should it all be working OK, & it's just a > peculiarity of OSRM / GraphHopper that's been throwing me out? > > Looking forward to any insights! :-) > > Thanks > > Graeme > > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
