On Fri, 5 Oct 2018 at 15:57, Graeme Fitzpatrick
wrote:
>
>
>
> I don't know how many of the 3500 worldwide are actually
> communications_towers bu that definition, but I'd guess not more than a
> dozen or 2?
>
Some more searching & this
https://en.wikipedia.org/wiki/List_of_tallest_towers says
sent from a phone
> On 5. Oct 2018, at 21:12, bkil wrote:
>
> I have yet to see a restaurant that
> declines to pack my meal for takeaway=* if I can't consume it on
> premise
I believe initially the idea of this tag was takeaway=only
then came the preset webforms.
a common combination for
sent from a phone
> On 6. Oct 2018, at 00:42, marc marc wrote:
>
> I see a tower, I tag a tower, another day someone will add his function.
It is not just the function. If you see a watch tower, you know it’s a watch
tower, there might be different types, in a prison, at a border etc. but
On Sat, 6 Oct 2018 at 07:27, André Pirard wrote:
> On 2018-10-05 20:35, Florian Lohoff wrote:
>
> Hi,
> is there a tag to ignore a roundabout flare in counting the exits?
>
> Is it a good idea for a navigator to ignore an exit and risk confusion?
>
But it's not an exit, it's only a driveway
>
Le 06. 10. 18 à 00:26, Martin Koppenhoefer a écrit :
> Why not tag man_made=observation_tower / bell_tower / etc.
do you have to be an expert in towers+telecomunication+a+b+c
to put the right tag?
or is it so disturbing to do it by successive refinement ?
I see a tower, I tag a tower, another day
sent from a phone
> On 5. Oct 2018, at 08:15, Joseph Eisenberg wrote:
>
> Sounds sensible to me. If JOSM and ID support man_made=tower +
> tower:type=communication with a preset, it won't be any more work than typing
> in a single tag.
for me it made more sense to discourage the whole
extra:
Languages - sorted by FREQ of unclear translations : ( descending )
* 61 tr
* 59 he
* 50 uk
* 40 da
* 38 it
* 36 ro
* 30 is
* 29 pl
* 27 lt
* 26 ast
* 25 ca
* 24 zh-TW
* 21 no
* 21 fi
* 20 vi
* 20 sl
* 20 ko
* 20 gl
*
On 2018-10-05 20:35, Florian Lohoff wrote:
Hi,
is there a tag to ignore a roundabout flare in counting the exits?
Is it a good idea for a navigator to ignore an exit and risk confusion?
What number should it say if that's the way to go?
We have a roundabout with a private driveway connecting
Hi,
I have created an experimental QA report about the same/unclear
translations.
and now about ~450 unclear translations pair detected.
( same translations AND different osm keys! )
if you know any language - please check!( discuss in your local osm
list! )
Current status ( you can edit
On Friday, October 5, 2018, Florian Lohoff wrote:
>
> Is there tagging to let announcements ignore that flare?
>
I think that if the driveway is tagged highway=service, this should be
enough information for the routeing engine to ignore it. Besides there
might be people that don't want the
On Friday, October 5, 2018, Graeme Fitzpatrick
wrote:
>
>
> I don't know how many of the 3500 worldwide are actually
> communications_towers bu that definition, but I'd guess not more than a
> dozen or 2?
>
There are already more than a dozen in the small country of Switzerland.
> I'd like to
> I am not sure adding drinking_water on bars or pubs would do us a favor. For
> one it might be up
> to the discretion of the current staff how they respond to your request (and
> could depend whether
> you have already consumed something there, know the barkeeper, are
> accompagnied by
Thanks for the link. The situation was the same in Hungary between
1998-2009. As of 2018, it is not a legal obligation, thus it is up to
the owner to decide whether they offer tap water for free. The
reasoning is probably that overheads, dish washing and service is not
at all free, though most
Hi,
is there a tag to ignore a roundabout flare in counting the exits?
We have a roundabout with a private driveway connecting to the
roundabout. Visually you wont actually count that service road
as a valid roundabout flare but still its a connection.
A mapper now changed to a faked topology
On 10/5/2018 1:23 PM, bkil wrote:
I agree that keeping a whole price chart up to date manually is a
tedious and error prone process yielding low added value from the
standpoint of users and OSM, so we should definitely not be doing
that. Although specifying the cost of a single representative
On Mon, Oct 1, 2018 at 11:38 AM Martin Koppenhoefer
wrote:
>> Could you please clarify what policy this would violate that makes you
>> disapprove?
>
> it is basically a way of giving a discount to customers. Would you also want
> to add special offers of your supermarket, like buy one get one
Apparently British English uses "watershed" to name the line that divides
to drainage basins, though Americans would call that a "divide":
I looked up natural=divide on Overdrive Turbo. I didn't find any uses in
Europe. In North America there were two places where the tag has been used:
the
Two weeks have passed since the RFC, all problems are solved and the
proposal can finally be voted:
https://wiki.openstreetmap.org/wiki/Proposed_features/assembly_point:purpose
The goal is to specify which emergency an emergency=assembly_point is
designed for.
Cheers
--
Daniele Santini
On 05/10/18 17:31, Lionel Giard wrote:
I also support this simplification of definition and tags.
Is there a possibility to indicate that a tower is specifically a
landmark with a tag of some sort without knowing the height (most of
them are not publicly known around here) ? Because some are
I think a 'watershed' is an area describing the catchment area that drains to
one point.
A 'divide' is a single line that describes the division between 2 or more
watersheds.
You are right in that they are all water related.
On 05/10/18 17:20, Philip Barnes wrote:
You seem to be describing
I also support this simplification of definition and tags.
Is there a possibility to indicate that a tower is specifically a landmark
with a tag of some sort without knowing the height (most of them are not
publicly known around here) ? Because some are really useful for navigation
(visible from
You seem to be describing a watershed, which was recently discussed.
https://lists.openstreetmap.org/pipermail/tagging/2018-September/039026.html
Phil (trigpoint)
On 4 October 2018 15:46:19 BST, Kevin Kenny wrote:
>In some maps that I render, I want to show the divide between a couple
>of
On Fri, 5 Oct 2018 at 16:17, Joseph Eisenberg
wrote:
> Sounds sensible to me. If JOSM and ID support man_made=tower +
> tower:type=communication with a preset, it won't be any more work than
> typing in a single tag.
>
Can confirm that it's preset in iD, as I've just mapped one (a mobile phone
Sounds sensible to me. If JOSM and ID support man_made=tower +
tower:type=communication with a preset, it won't be any more work than
typing in a single tag.
Does this require a proposal process? How does something become officially
deprecated?
On Fri, Oct 5, 2018 at 2:59 PM Graeme Fitzpatrick
24 matches
Mail list logo
