On 8/13/20 23:55, Peter Elderson wrote:
> I can see how an area such as a parking, a churchyard or pedestrian area
> can be tree lined. A node feature, not so much.
For example, A parking area mapped as only a node for the center could
still have this attribute.
--
Shawn K. Quinn
http://www.ra
I can see how an area such as a parking, a churchyard or pedestrian area
can be tree lined. A node feature, not so much.
Best, Peter Elderson
Op vr 14 aug. 2020 om 01:08 schreef Martin Koppenhoefer <
dieterdre...@gmail.com>:
> I’ve set up an initial documentation page for the tree_lined attribu
I’ve set up an initial documentation page for the tree_lined attribute (used
mainly in conjunction with highways and waterways) and welcome comments for it:
https://wiki.openstreetmap.org/wiki/Key:tree_lined
This used to be a redirect to natural=tree_row (which is a different tag, as it
is for
On 2020-08-13 19:41, Yves wrote:
> If top, middle, bottom have a meaning for the OP, I'm not sure it's really
> general, counter-examples have been given.
It's not the OP's private project, there is a reason why this is being
debated in public.
> To avoid confusion with elevation, what would be
If top, middle, bottom have a meaning for the OP, I'm not sure it's really
general, counter-examples have been given.
To avoid confusion with elevation, what would be another way to tag them?
Motor position have been given, but it is not really relevant for the common
user.
For routing aerialway
On 2020-08-13 18:35, Werner.Haag@leitstelle.tirol wrote:
> Hi,
>
> in my opinion (i think dktue is right there) it should be easy for a user to
> distinguish or extract (overpass query) the upper, mid and lower stations.
> That´s not possible at the moment in OSM. Elevation (ele tag) may be us
On Thu, Aug 13, 2020 at 9:22 AM Colin Smale wrote:
> Despite the minimal difference the website does indicate that one side is
> the "top station" and the other side is the "bottom station", but that's
> probably not a valid source. Anyway, suppose they were both at exactly the
> same altitude. W
Hi,in my opinion (i think dktue is right there) it should be easy for a user to distinguish or extract (overpass query) the upper, mid and lower stations.That´s not possible at the moment in OSM. Elevation (ele tag) may be useful, but does not indicate whether a station is the lower or upper one.On
I definitely agree: If the tunnel (or more often used: the bridge) is a
separate object (e.g. man_made=bridge), then the tunnel's or bridge's
name should go in the name-tag.
But my impression is that if it's the same object as the highway (or
railway or waterway) itself then "tunnel:name" or "
sent from a phone
> On 13. Aug 2020, at 14:12, dktue wrote:
>
> the wiki states since more than eight years that there's a debate about
> wether one should tag "tunnel:name" or "name". [1]
>
> Is there any new opinion in the community on this topic that has not been
> documented in the wiki
On 2020-08-13 14:49, dktue wrote:
> I think it's easy for a mapper to determine if a station is a bottom_station
> or a upper_station even if he doesn't know the exact elevation.
I would advise against such generalisations - it depends so much on the
circumstances and the mapper in question. OSM
Here's an example [1] where the name of the tunnel seems to be tagged as
"name". I'm not sure what the roads name is (might be Schlossbergtunnel,
Hegelstraße or Rheinlandstraße). Tagging it to tunnel:name would
definitely clarify on this.
So is there a consensus that one should tag "tunnel:nam
On 13/08/2020 08.10, dktue wrote:
the wiki states since more than eight years that there's a debate about
wether one should tag "tunnel:name" or "name". [1]
Is there any new opinion in the community on this topic that has not
been documented in the wiki?
How is the tunnel tagged? If it's a h
I think it's easy for a mapper to determine if a station is a
bottom_station or a upper_station even if he doesn't know the exact
elevation.
Am 13.08.2020 um 14:28 schrieb Colin Smale:
On 2020-08-13 14:07, dktue wrote:
I think that it's quite hard for data consumers (again: think of an
over
On 2020-08-13 14:07, dktue wrote:
> I think that it's quite hard for data consumers (again: think of an
> overpass-query to find all mid-stations) to determine which role a station
> has. Like Martin said: Why not just solve the (huge!) special case of
> mountain aerialways where we really have
Hi,
the wiki states since more than eight years that there's a debate about
wether one should tag "tunnel:name" or "name". [1]
Is there any new opinion in the community on this topic that has not
been documented in the wiki?
Cheers
dktue
[1] https://wiki.openstreetmap.org/wiki/Key:tunnel
I think that it's quite hard for data consumers (again: think of an
overpass-query to find all mid-stations) to determine which role a
station has. Like Martin said: Why not just solve the (huge!) special
case of mountain aerialways where we really have one bottom_station,
zero or more mid_stat
Aug 13, 2020, 01:33 by lisbe...@gmx.us:
> Isthere any situation where both should be expected, yet >
> healthcare> should have higher priority than > shop> ?
>
> Or is there another side I'm missing?
>
>
This is decision made by renderer/data user.
If more than one of amenity/shop/tour
18 matches
Mail list logo
