On Sat, 4 May 2019 at 08:47, Paul Allen wrote:
>
> Former quay side.
>
Thanks! So just a spot for a few 00 people to all sit at once & look at the
River - must be very pretty :-)
> Remodelled to achieve whatever it was the architect was trying to achieve.
>
& Architect Astronauts, creating fa
On Fri, 3 May 2019 at 23:14, Graeme Fitzpatrick
wrote:
On Sat, 4 May 2019 at 02:22, Paul Allen wrote:
>
>>
>> You will note that there are narrow, normal-size steps within big steps.
>>
>
> That strikes me almost like a forum or similar?
> https://images.app.goo.gl/VwCPYybjcqrBiSp66
>
> Fish mar
On Sat, 4 May 2019 at 02:22, Paul Allen wrote:
>
> You will note that there are narrow, normal-size steps within big steps.
>
That strikes me almost like a forum or similar?
https://images.app.goo.gl/VwCPYybjcqrBiSp66
Fish market perhaps?
Thanks
Graeme
Hi there,
Definition: A tag to mark the possibility to change the baby's nappy
Author: Valor Naram
the discussion has been closed by me and we can vote on my proposal.
Please give me your voice at https://wiki.openstreetmap.org/wiki/Propos
ed_features/changing_table so we can get rid of the `di
I guess one problem has been fixed, but many still remain.
Vr gr Peter Elderson
Op vr 3 mei 2019 om 19:04 schreef Paul Allen :
> On Fri, 3 May 2019 at 17:39, Sarah Hoffmann wrote:
>
> Most editors are quite good at keeping route order these days (iD has
>> looong ago been fixed).
>>
>
> How lo
On Fri, May 3, 2019 at 12:39 PM Sarah Hoffmann wrote:
> Please note the statistics at the end of the post. I actually
> did bother to observe the state of affairs and I found that a
> majority of routes in fact _are_ already sorted. The numbers
> are from before waymarkedtrails stopped sorting rou
If you want a routing app to navigate you along an OSM route (using gpx as
intermediate), or a comparable dat use of OSM routes, the route must be
ordered correctly or it simply won't work. If 65% of the routes is ordered,
that means 35% is not and you can't rely on it for routing or profiling. I
w
On Fri, 3 May 2019 at 17:39, Sarah Hoffmann wrote:
Most editors are quite good at keeping route order these days (iD has
> looong ago been fixed).
>
How long ago is looong? Because 3 or 4 months ago I used iD to make a
minor change to a
sorted bus route and it scrambled the order. Yes, it was
On Friday 03 May 2019, Tobias Knerr wrote:
>
> So I finally got around to building that prototype to test my idea.
> The code only needs a highway=step way and an area:highway polygon as
> input, and produces sensible results for common shapes of straight
> stairways. I'm pretty happy with the resu
Hi,
On Fri, May 03, 2019 at 01:24:49PM +0100, Andy Townsend wrote:
> Seriously, hoever wrote that section of that wiki page
> https://wiki.openstreetmap.org/w/index.php?title=Relation:route&action=history
> must have done so out of their _desire_ that relations are kept ordered in
> OSM, not out
On Fri, 3 May 2019 at 16:51, Martin Koppenhoefer
wrote:
>
> Can it cope with cases like these?
>
Or this https://goo.gl/maps/TxVMau8EBrLUAaeU6 Sorry it's a google thingy
but I don't have a
good photo of it. I would, of course, take several photos myself if I were
going to map it, but
since we
On Fri, May 3, 2019 at 4:25 AM Nita Rae Sanders wrote:
> Please read the Wikipedia article again. While the name of an ED
> implies Emergency care, and they certainly do provide it, less than
> 20% result in inpatient admission. The vast majority are treat and
> release. In the majority of cases,
Am Fr., 3. Mai 2019 um 17:20 Uhr schrieb Tobias Knerr :
> On 11.04.19 23:28, Tobias Knerr wrote:
> So I finally got around to building that prototype to test my idea. The
> code only needs a highway=step way and an area:highway polygon as input,
> and produces sensible results for common shapes of
On 11.04.19 23:28, Tobias Knerr wrote:
> A decent heuristic is to connect each node from the upper border to the
> closest point (not necessarily a node) on the lower border, and vice
> versa. Then you place steps at regular intervals along these connections.
>
> For common step shapes, this shoul
Hm... it's a different subject... but it's much, much more than ordering.
Edits to ways: splitting, lengthening, shortening, combining, adding and
removing, can destroy many routes of different kinds, not only unordering
them but making them unorderable because of duplicate ways, branch ways,
inter
I prefer that those complete newbies get to mess with only 1 or 2
members of route relations, at the relatively small price of ordering.
Peter Elderson skrev den 03.05.2019 16:12:
> You prefer routes to stay unordered? Or that edits damage routes?
>
> Vr gr Peter Elderson
>
> Op vr 3 mei 2019
You prefer routes to stay unordered? Or that edits damage routes?
Vr gr Peter Elderson
Op vr 3 mei 2019 om 16:08 schreef :
>
> >>> For a non-roundtrip route consiting of two consecutive ways the route
> >>> direction can be deduced from the order of the ways in the relation.
> >>
> >> That's ass
Indeed. So at a given point, it's the oneway on the way that decides if you
can go in, not the route relation. This means oneway tag can be used on the
relation. Of course, for vehicles it would be wise to add only ways that
are legally allowed in the same direction as the route is intended.
Vr g
For a non-roundtrip route consiting of two consecutive ways the route
direction can be deduced from the order of the ways in the relation.
That's assuming the ways are ordered at all. I've cleaned up hundreds
of routes (most created by Potlatch users though) and my advice is: do
not rely on
cycle.travel appears to try to follow cycle routes as much as possible.
It respects road attributes
Peter Elderson skrev den 03.05.2019 15:13:
> This one seems to map routes to ways, and it knows the attributes of the ways.
> Are you saying it ignores oneway tags on the individual ways? I wonder
Also, it does route to produce a track, but then to use it for navigation
you transfer the gpx to your device, which then does the actual routing.
Vr gr Peter Elderson
Op vr 3 mei 2019 om 15:13 schreef Peter Elderson :
> This one seems to map routes to ways, and it knows the attributes of the
>
This one seems to map routes to ways, and it knows the attributes of the
ways.
Are you saying it ignores oneway tags on the individual ways? I wonder, if
I feed it a route that goes over a oneway street and then reverse the
direction, would it allow that in the navigation? Could be dangerous if it
On 03/05/2019 13:36, Peter Elderson wrote:
Routers look at the ways, not the routes.
Immediately I can think of at least one major exception for that
(cycle.travel). I suspect that there are others too.
Best Regards,
Andy
___
Tagging mailing
*Oneway or not?*
*oneway=yes* is the simplest and already most used way to indicate that a
route is oneway. It does not matter if that's legal, customary, by design
or recommended. For ways, oneway is a legal thing; for routes it is not.
Routers look at the ways, not the routes. No clash there. It
On 03/05/2019 13:05, Hufkratzer wrote:
If some editors damage the order in the relations this is a bug that
should be fixed anyway.
As ever I'm sure that pull requests would be welcome.
Seriously, hoever wrote that section of that wiki page
https://wiki.openstreetmap.org/w/index.php?title
On 03.05.2019 12:56, o...@hjart.dk wrote:
Hufkratzer skrev den 02.05.2019 12:11:
On 30.04.2019 21:05, Kevin Kenny wrote:
On Tue, Apr 30, 2019 at 2:19 PM s8evq wrote:
Personally, I like signed_direction=yes. It's simple and avoids
using the word oneway.
Also, using the value forward|backward
On 03/05/2019 12:21, s8evq wrote:
But what's the alternative then?
Explicit start and/or finish nodes?
As previously mentioned, you simply can't rely on route ways being ordered.
Best Regards,
Andy
___
Tagging mailing list
Tagging@openstreetma
On Fri, 03 May 2019 12:56:34 +0200, o...@hjart.dk wrote:
> That's assuming the ways are ordered at all. I've cleaned up hundreds of
> routes (most created by Potlatch users though) and my advice is: do not
> rely on routes being ordered.
But what's the alternative then?
- Using CW CCW? How wo
+1
Id and Potlach edits damage routes. JOSM edits damage the routes as well,
but JOSM allows the user to prevent/detect/analyse/repair the damage while
editing. Still, it's a shaky system, can't rely on it for data use.
Op vr 3 mei 2019 om 12:59 schreef :
>
>
> Hufkratzer skrev den 02.05.2019 12:
Hufkratzer skrev den 02.05.2019 12:11:
On 30.04.2019 21:05, Kevin Kenny wrote:
On Tue, Apr 30, 2019 at 2:19 PM s8evq wrote:
Personally, I like signed_direction=yes. It's simple and avoids using
the word oneway.
Also, using the value forward|backward might not be necessary, as
it's possible
Am Fr., 3. Mai 2019 um 10:44 Uhr schrieb Peter Elderson :
> I would not map a noise level value for any surface. a. It's not the
> surface that produces the noise; b. it's a relative value, but compared to
> what? You would need/assume a standard regular noise value for comparison;
> c. the stand
2 May 2019, 21:55 by amilopow...@u-cloud.ch:
> surface=whispering_asphalt or surface=silent_asphalt
>
Please avoid fragmenting surface tag.
> Then I found on Overpass-Turbo someone that tagged "asphalt:type=porous".
>
Something like that would be preferable if it is mappable.
In general, intr
I would not map a noise level value for any surface. a. It's not the
surface that produces the noise; b. it's a relative value, but compared to
what? You would need/assume a standard regular noise value for comparison;
c. the standard will change over time, making all mapped values wrong.
I'm at
On 5/2/19, Graeme Fitzpatrick wrote:
> On Fri, 3 May 2019 at 06:44, Nita Rae Sanders wrote:
>
>> I am envisioning something where all ED's will be designated as such,
>> even
>> those embedded within the hospital.
>> It is an attempt to provide a common tagging system, exactly for the
>> purpose
sent from a phone
> On 2. May 2019, at 23:11, Florian Lohoff wrote:
>
> I'd rather propose surface=asphalt asphalt=whisper or the like.
>
> asphalt:type would also be okay with me. There are more likely 100s of types
> of asphalt.
I also would not introduce a new surface value, it is still
35 matches
Mail list logo