[Tagging] departures_board vs. passenger_information_display
AgusQui has noticed that the two keys mentioned in the subject line are essentially duplicates. I think passenger_information_display is more useful, as it can include arrivals as well as departures. It also outnumbers departures_board by about six to one. The departures_board key does have a useful subkey of realtime. I would suggest adding the following multivalue options: passenger_information_display = yes/no/realtime/static ... where "static" would cover the printed versions proposed in the departures_board page. Alternatively it could be a subkey: passenger_information_display:realtime = yes/no I frankly don't find it useful to make a distinction between printed timetables with times vs. printed timetables with intervals (Paris mixes the two anyhow). If folks think this is a good idea (and making departures_board deprecated), I could write up a formal proposal. John ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] departures_board vs. passenger_information_display
Greetings! Czech railway stations have separate arrival and departure boards (and entirely separate general information boards) that can be far enough apart for the distinction being important. If you're standing in front of a departure board, finding an arrival board might not be trivial. Happy mapping! Matej On 26 February 2018 at 09:29, Johnparis wrote: > AgusQui has noticed that the two keys mentioned in the subject line are > essentially duplicates. > > I think passenger_information_display is more useful, as it can include > arrivals as well as departures. It also outnumbers departures_board by > about six to one. > > The departures_board key does have a useful subkey of realtime. I would > suggest adding the following multivalue options: > > passenger_information_display = yes/no/realtime/static > > ... where "static" would cover the printed versions proposed in the > departures_board page. Alternatively it could be a subkey: > > passenger_information_display:realtime = yes/no > > I frankly don't find it useful to make a distinction between printed > timetables with times vs. printed timetables with intervals (Paris mixes > the two anyhow). > > If folks think this is a good idea (and making departures_board > deprecated), I could write up a formal proposal. > > John > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > > ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] departures_board vs. passenger_information_display
2018-02-26 9:52 GMT+01:00 Matej Lieskovský : > Czech railway stations have separate arrival and departure boards (and > entirely separate general information boards) that can be far enough apart > for the distinction being important. > > same in Germany and Italy (although the boards are typically close to each other) ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] departures_board vs. passenger_information_display
Maybe passenger_information_display:type=arrivals/departures? or similar Agustín. El feb. 26, 2018 9:02 AM, escribió: Send Tagging mailing list submissions to tagging@openstreetmap.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.openstreetmap.org/listinfo/tagging or, via email, send a message with subject or body 'help' to tagging-requ...@openstreetmap.org You can reach the person managing the list at tagging-ow...@openstreetmap.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Tagging digest..." -- Message: 2 Date: Mon, 26 Feb 2018 09:52:25 +0100 From: Matej Lieskovský To: "Tag discussion, strategy and related tools" Subject: Re: [Tagging] departures_board vs. passenger_information_display Message-ID: Content-Type: text/plain; charset="utf-8" Greetings! Czech railway stations have separate arrival and departure boards (and entirely separate general information boards) that can be far enough apart for the distinction being important. If you're standing in front of a departure board, finding an arrival board might not be trivial. Happy mapping! Matej On 26 February 2018 at 09:29, Johnparis wrote: > AgusQui has noticed that the two keys mentioned in the subject line are > essentially duplicates. > > I think passenger_information_display is more useful, as it can include > arrivals as well as departures. It also outnumbers departures_board by > about six to one. > > The departures_board key does have a useful subkey of realtime. I would > suggest adding the following multivalue options: > > passenger_information_display = yes/no/realtime/static > > ... where "static" would cover the printed versions proposed in the > departures_board page. Alternatively it could be a subkey: > > passenger_information_display:realtime = yes/no > > I frankly don't find it useful to make a distinction between printed > timetables with times vs. printed timetables with intervals (Paris mixes > the two anyhow). > > If folks think this is a good idea (and making departures_board > deprecated), I could write up a formal proposal. > > John > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > -- Subject: Digest Footer _ ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] AutoEdit rename roof:slope:direction to roof:direction
Thank you Marc for your awesome work! It looks good and think it hasen't any objections yet :D I'll try to call taggers attention, which still use the old tag. Best regards, Rebo Am 19.02.2018 um 01:29 schrieb marc marc: the first part is done https://www.openstreetmap.org/changeset/56476192 https://www.openstreetmap.org/changeset/56476241 Regards, Marc ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
