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.
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.
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
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
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
So what is wrong with ele=* on the stations and the topography of the
line? Completely (for OSM purposes) objective and uncontroversial. The
data consumer/renderer can make their own mind up about nomenclature.
Many of these lifts go up to go down, or go down to go up, as they cross
ridges and
sent from a phone
> On 12. Aug 2020, at 21:39, Yves wrote:
>
> Alexey, you're right, anyway physical properties like incline are better
> tagged on way than on relations.
and horizontal aerialways aren’t completely unheard of either. The incline
solution works only for a subset of
Alexey, you're right, anyway physical properties like incline are better tagged
on way than on relations.
Yves ___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
My imagination draws an aerialway that goes over a hill, with or without a mid-station at the top. So, potentially incline is not even a property of a route=aerialway relation, but of an aerialway way segment. 12.08.2020, 18:57, "Kevin Broderick" :In the case of Gaislachkoglbahn, it appears to be
There are 2 lines of the Metrocable gondola system in Medellín, Colombia
which have 4 stations each (one has 5 stations, but that actually appears
to be 2 different cable loops)
https://en.wikipedia.org/wiki/Metrocable_(Medell%C3%ADn)
The variety of different types of "aerialway" is quite large,
In the case of Gaislachkoglbahn, it appears to be two separate tramways
(and tagged as such), with adjacent terminals. If the carriers (gondola
cabins, tram cars, chairs, etc) don't continue through the station, I think
it would be a drive or return terminal, not a mid-station; that particular
If the concern is for routing, that's a slightly bigger challenge—some
tramways load only at one end, some load at both (e.g. the gondola
linked above), others load primarily at one end with limited loading
at the other in various special conditions, sometimes event-specific,
and often with
>From an 'information about aerial tramways" standpoint, I believe that it
would be preferable to label the drive, midstation, and return terminals as
such. While they are often for vertical-oriented transport, aerialways are
sometimes used for horizontal transport, e.g.
Hi,
1) maybe "station=lower_station" would be clearer
2) I couldn't find any real-world example
3) Probably this would be the definition of a mid-station.
Interesting example:
https://www.openstreetmap.org/node/1613091788
Here within the same building we have "Talstation" ("valley station")
1) is bottom station always in valley?
(This should be fixable)
2) is there case of 2 and more middle
stations?
3) is there case of one station being both
top and bottom station at once?
Also, it uses single known tag, not
new discussion purpose ones.
Though, yes processing would be
much more
Am 12.08.2020 um 16:28 schrieb Niels Elgaard Larsen:
dktue:
Hi,
I was wondering why there's no way to distinguish valley and upper stations of
aerialways in OpenStreetMap.
Usually an aerialway consists of
* one valley station
* zero or more mid stations
* one upper station (or
dktue:
> Hi,
>
> I was wondering why there's no way to distinguish valley and upper stations of
> aerialways in OpenStreetMap.
>
> Usually an aerialway consists of
>
> * one valley station
> * zero or more mid stations
> * one upper station (or "mountain station")
>
> What do you think you
Hi,
I was wondering why there's no way to distinguish valley and upper
stations of aerialways in OpenStreetMap.
Usually an aerialway consists of
* one valley station
* zero or more mid stations
* one upper station (or "mountain station")
What do you think you tagging this information
18 matches
Mail list logo
