I'd try something similar to this example:
access:conditional=destination @ (weight>5.5)
So in your case you would have
maxspeed:advisory:conditional=18 @ (weight>=37.5)
maxspeed:advisory:conditional=22 @ (weight>=35 AND weight<37.5)
maxspeed:advisory:conditional=26 @ (weight>=32.5 AND weight<35
I suppose, given that they all have the same tag, that the values would
need to be concatenated with semicolons:
maxspeed:advisory:conditional=18 @ (weight>=37.5);22 @ (weight>=35 AND
weight<37.5);26 @ (weight>=32.5 AND weight<35);37 @ (weight>=30 AND
weight<32.5)
On Thu, Apr 25, 2019 at 10:28 A
The water flowing through it is still river water.
On 24/04/2019 20:47, François Lacombe wrote:
Hi Dave
I'm happy to tag as canal the man_made space between two lock gates.
This is often concrete lined and sized accordingly to allow boats to pass
through.
The main difference with rivers going
DaveF wrote:
> The water flowing through it is still river water.
The water flowing down lots of canals is ultimately river water :) - the
Llangollen Canal is fed by the River Dee, the Mon & Brec by the Usk, and so
on.
Generally, where a lock has been built, this is in an artificial cut
slightly
On 25/04/2019 11:25, Richard Fairhurst wrote:
DaveF wrote:
The water flowing through it is still river water.
The water flowing down lots of canals is ultimately river water :) - the
Llangollen Canal is fed by the River Dee, the Mon & Brec by the Usk, and so
on.
In the case of the Llangollen
On 25/04/2019 11:25, Richard Fairhurst wrote:
DaveF wrote:
The water flowing through it is still river water.
The water flowing down lots of canals is ultimately river water :) - the
Llangollen Canal is fed by the River Dee, the Mon & Brec by the Usk, and so
on.
In the case of the Llangollen
Have these diversions been given a 'XYZ Canal' name? if not then it's a
river.
I think the duck test needs to be applied.
DaveF
On 25/04/2019 11:25, Richard Fairhurst wrote:
DaveF wrote:
The water flowing through it is still river water.
The water flowing down lots of canals is ultimately r
Even shorter, because if there are conflicting rules in the conditional, the
last one is taken, says the wiki. (Not sure if this is really implemented in
applications that work with that data though):
maxspeed:advisory:conditional=37 mph @ (weight>=6 lbs);26 mph @
(weight>=65000 lbs);22 mph
On Thu, 25 Apr 2019 at 13:00, Dave F via Tagging
wrote:
> Have these diversions been given a 'XYZ Canal' name? if not then it's a
> river.
>
> I think the duck test needs to be applied.
>
So does the presence of ducks make it a river and the absence of ducks make
it a canal?
--
Paul
__
DaveF wrote:
> Have these diversions been given a 'XYZ Canal' name? if not then
> it's a river.
hahahahaha
cheers
Richard
--
Sent from: http://gis.19327.n8.nabble.com/Tagging-f5258744.html
___
Tagging mailing list
Tagging@openstreetmap.org
https://
On Thursday, 25 April 2019, Paul Allen wrote:
> On Thu, 25 Apr 2019 at 13:00, Dave F via Tagging
> wrote:
>
> > Have these diversions been given a 'XYZ Canal' name? if not then it's a
> > river.
> >
> > I think the duck test needs to be applied.
> >
>
> So does the presence of ducks make it a
Le jeu. 25 avr. 2019 à 12:03, Dave F via Tagging
a écrit :
> The water flowing through it is still river water.
>
Many artificial man made infrastructure involve natural water taken from
rivers and streams.
The point of waterway isn't only to tag water but the kind of way it is
flowing in (witho
Hi all,
I wrote this proposal focused on power conversion in traction substations.
https://wiki.openstreetmap.org/wiki/Proposed_features/Traction_substations_extension
It is proposed to use a new key conversion=* to indicate which kind of
power conversion operates inside a substation.
As explaine
Going back to the original example, I would say, not only the lock but the
entire cut, in particular way https://www.openstreetmap.org/way/24335
should be tagged as waterway=canal. This scheme applies to most river-lock
arrangements, the "cuts" are nearly almost artificial canals.
At least this
On Wed, 24 Apr 2019 at 20:47, François Lacombe
wrote:
> The main difference with rivers going through cities is it's often the
> original natural course.
The River Tame, in North Birmingham and in the urban areas north of
the city, has several sections, some concrete-sided and some looking
entir
Le jeu. 25 avr. 2019 à 18:49, Andy Mabbett a
écrit :
> The River Tame, in North Birmingham and in the urban areas north of
> the city, has several sections, some concrete-sided and some looking
> entirely natural, that are nowhere near its original course.
>
Ok this is a good point
Despite wate
There's no discussion concerning the proposal of "baby changing table" anymore. What's happening? Should I start the voting process? Are all words said?Answer "no" (with or without any reason) and I won't start the voting.CheersSören alias Valor Naram Original Message Subject: [Tagg
On Wednesday, 24 April 2019, Warin wrote:
> On 25/04/19 04:39, Dave F wrote:
> >
> >
> > On 21/04/2019 01:12, Warin wrote:
> >>
> >>
> >> I am all for the introduction of the key education=*
> >>
> >>
> >> It makes sense, adds detail - improves the map data base.
> >
> > True.
> >
> > The one that
25 Apr 2019, 19:03 by fl.infosrese...@gmail.com:
> To me, current tagging is defined as follow:
> waterway=river/stream => "natural" water course
> waterway=canal => artificial water channel for a given purpose
> waterway=drain => useless water evacuation (mainly rain)
>
I would use river/stream n
sent from a phone
> On 22. Apr 2019, at 01:49, marc marc wrote:
>
> I know the tag description, thanks :)
> the question is "can we expect to have changing tables on a regular
> basis that are different from what we can expect with other tags,
> which would justify encouraging people to put a
sent from a phone
> On 25. Apr 2019, at 18:45, Volker Schmidt wrote:
>
> The Rhine downstream from Basel and to Bingen has been re-bedded nearly
> completely (see https://en.wikipedia.org/wiki/Upper_Rhine) and, by the above
> arguments, should be re-tagged as canal, which seems absurd.
> So
Getting away from the discussion of river v canal & back to the original
problem pictured
https://www.openstreetmap.org/way/347369154 , why is it "River Wey
Navigation" while the river itself is just "Wey"
https://www.openstreetmap.org/way/243353339#map=16/51.2572/-0.5605?
Shouldn't they both eithe
On 26/04/19 04:10, Philip Barnes wrote:
On Wednesday, 24 April 2019, Warin wrote:
On 25/04/19 04:39, Dave F wrote:
On 21/04/2019 01:12, Warin wrote:
I am all for the introduction of the key education=*
It makes sense, adds detail - improves the map data base.
True.
The one that irks me i
On Thu, 25 Apr 2019 at 22:16, Graeme Fitzpatrick
wrote:
> Getting away from the discussion of river v canal & back to the original
> problem pictured
> https://www.openstreetmap.org/way/347369154 , why is it "River Wey
> Navigation" while the river itself is just "Wey"
>
Canals, when used for bo
Le 25.04.19 à 22:52, Martin Koppenhoefer a écrit :
> I don’t mind encouraging or not a description, as long as it is in the wiki
> alone it won’t change anything
for those who read the wiki, I think the tags listed there have
an influence, it's supposed to be the ones someone has expressed
an int
no:) (or more exactly: it has been said but I say it again
in case you missed it)
I notice that the page has almost doubled in size :(
I wonder if you shouldn't split the proposal into two:
a minimalist proposal that takes the rela data from the diaper=* tag
and provides a better schema to encode
sent from a phone
> On 23. Apr 2019, at 09:45, Lionel Giard wrote:
>
> There isn't any EU police or military force (that's still a political
> discussion but there is none at the moment). The only existing thing is the
> international cooperation that is increased between neighboring countri
I have created 2 proposal pages for natural=mesa and natural=butte
A mesa is defined as "A flat-topped elevated landform surrounded by
cliffs". A mesa may also be known as a table or tableland, potrero or
tepui. See http://en.wikipedia.org/wiki/en:mesa
A butte is defined as "a hill with a flat to
It has been over 2 weeks since the RFC for
https://wiki.openstreetmap.org/wiki/Proposed_features/Key:golf_cart
This key is already in use over 16,000 times to define access
restrictions for golf carts on highway ways (especially highway=path
and highway=service), highway=crossing and amenity=parki
I'm afraid that using camp_site=camp_pitch as a subtag on
tourism=camp_site features, and using "tourism=pitch" for separate
tagging would combine the same disadvantages as using
camp_site=camp_pitch as an independent feature, plus the disadvantages
of adopting a new tag under the tourism key.
You
On 26/04/19 11:48, Joseph Eisenberg wrote:
I have created 2 proposal pages for natural=mesa and natural=butte
A mesa is defined as "A flat-topped elevated landform surrounded by
cliffs". A mesa may also be known as a table or tableland, potrero or
tepui. See http://en.wikipedia.org/wiki/en:mesa
I've already made a suggestion to split the wiki pages into two parts:The first one describes the key "changing_table" as a replacement for "diaper". This section will compare the old tagging with the new tagging without introducing new subkeys.The second one describes the extensions (adding of mor
On Thu, Apr 18, 2019 at 5:13 PM Joseph Eisenberg
wrote:
> Fri, Apr 19, 2019 at 7:.
>
>> I was wondering about leaving them all under peak?
>>
>> natural=peak
>> peak=hill/mountain/plateau/butte/mesa
>>
>> Would that work?
>>
>
> A peak is well defined as the local high point. A Mesa or butte will
33 matches
Mail list logo
