Good idea - I've added a pull request to Osmose
https://github.com/osm-fr/osmose-backend/pull/714 - please take a look and
weigh in if you think it could be improved.
On Wed, Dec 18, 2019 at 4:47 PM Ken Kilfedder
wrote:
> Is it worth adding this to Osmose and the other QA tools?
>
> ---
>
Hi Edward,
On 18/12/2019 16:31, Edward Catmur via Talk-GB wrote:
Further to this - if you want to look for barrier=kerb +
highway=crossing nodes in your area, which may be disrupting routing,
the Overpass query is node["barrier"="kerb"]["highway"="crossing"] :
It sounds like traffic_calming=table
(not 100% sure).
18 Dec 2019, 17:20 by talk-gb@openstreetmap.org:
> Returning to the original issue, I think I've worked out what the problem is.
> It's that on a crossing node, kerb=* is fine (it describes the
> presence/attributes of the kerb on the
On 18/12/2019 16:26, David Woolley wrote:
> On 18/12/2019 15:59, Robert Skedgell wrote:
>> It's parking a car on a
>> footway which is illegal in London (an offence which is only subject to
>> civil enforcement), unless explicitly allowed by the local authority.
>
> It's potentially a criminal
Is it worth adding this to Osmose and the other QA tools?
---
https://hdyc.neis-one.org/?spiregrain
spiregrain_...@ksglp.org.uk
On Wed, 18 Dec 2019, at 4:31 PM, Edward Catmur via Talk-GB wrote:
> Further to this - if you want to look for barrier=kerb + highway=crossing
> nodes in your area,
Thank you Edward
Found one in Leicester, maproulette seagull adds barrier=kerb to
crossing=toucan / kerb=lowered.
Will fix.
Cheers
Phil (trigpoint)
On Wednesday, 18 December 2019, Edward Catmur wrote:
> Further to this - if you want to look for barrier=kerb + highway=crossing
> nodes in your
Further to this - if you want to look for barrier=kerb + highway=crossing
nodes in your area, which may be disrupting routing, the Overpass query
is node["barrier"="kerb"]["highway"="crossing"] :
https://overpass-turbo.eu/s/P5Y
On Wed, Dec 18, 2019 at 4:20 PM Edward Catmur
wrote:
> Returning to
On 18/12/2019 15:59, Robert Skedgell wrote:
It's parking a car on a
footway which is illegal in London (an offence which is only subject to
civil enforcement), unless explicitly allowed by the local authority.
It's potentially a criminal offence anywhere see sub-paragraph 17 of
Returning to the original issue, I think I've worked out what the problem
is. It's that on a crossing node, kerb=* is fine (it describes the
presence/attributes of the kerb on the subsidiary highway) but barrier=kerb
should *not* be used.
Combining kerb=* with highway=crossing is blessed by Wiki:
On 18/12/2019 15:36, Philip Barnes wrote:
> On Wednesday, 18 December 2019, David Woolley wrote:
>> On 18/12/2019 13:31, Edward Catmur via Talk-GB wrote:
>>> That said, the same goes for cars - other than the lowest bodied sports
>>> cars, pretty much all motor vehicles are capable of taking a
On Wednesday, 18 December 2019, David Woolley wrote:
> On 18/12/2019 13:31, Edward Catmur via Talk-GB wrote:
> > That said, the same goes for cars - other than the lowest bodied sports
> > cars, pretty much all motor vehicles are capable of taking a kerb at low
> > speed.
>
> Although raised
On 18/12/2019 13:31, Edward Catmur via Talk-GB wrote:
That said, the same goes for cars - other than the lowest bodied sports
cars, pretty much all motor vehicles are capable of taking a kerb at low
speed.
Although raised kerbs are generally there to stop that happening and the
resultant
I think your new mapping is correct, as it reflects reality - which is what
most matters. You could improve it by curving the cycle path/sidewalk up to
the crossing and aligning the kerb nodes to the aerial photo, but that's
nitpicking.
That said, there's still a problem in that at least one
Hi,
After investigating two reports of OSRM routing failures around North
Tyneside, the common factor I can see is barrier=kerb tags added to
highway=crossing nodes intersecting highway=tertiary and
highway=cycleway/ footway ways.
Here are links to the two map note reports:
14 matches
Mail list logo
