Re: [Talk-transit] Conversation on this list (was: Proposed Feature - RFC - Public Transport)
On 12/14/2010 07:56 AM, Michał Borsuk wrote: I already told you twice to behave, you little shit. If it continues, I will have you removed from the list. That type of language and attitude is completely inappropriate. If someone needs to be removed from the list there a much better ways of handling it. --Greg ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
Re: [Talk-transit] bus stops/platforms with electronic display of when the buses pass through
Hi, For bus stops I use ticker=yes/no. I'm sure I saw that documented somewhere and didn't come up with it on my own but a fairly exhaustive wiki search to provide a link for you came up completely dry so who knows. Cheers, Greg On Fri, Oct 1, 2010 at 1:39 PM, Jo winfi...@gmail.com wrote: Hi, I didn't find a tag to use for synoptic displays indicating when buses are coming through (either as a time left to wait, or a full display of normal time+delay) at the bus stop level. And another one (at the bus_station level) with all the buses that are passing through (like the ones in train stations and airports). That one may even deserve its own node to indicate where it is and possibly even an indication in what direction it's facing. Jo ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
Re: [Talk-transit] Proposed additional tags for bus stops and an import of San Fracisco data
I would love to see GTFS data imported into OSM, especially the SF data if you can convince them to change the license. I think the street= tag is a good idea. I'm unsure of the bearing tag. If we know which street the stop is on and where the stop is the direction the bus is going follows from that. Could you provide an example of where and how that would come in useful? Or is it something that we need to know only if the imported location of the stop is not precise enough to show which side of the street it is on? How are you planning to deal with existing data? Many stops are already mapped and have more data than is in the GTFS feed. For example, does the stop have a shelter, or a ticker to show when the next bus is coming or a bench, etc. Cheers, Greg ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
Re: [Talk-transit] tagging stops served by multiple routes by more than one transit agency
When I tag bus stops with multiple operators I add the operator name to the route_ref. In the above example of HART and USF I would tag the stop as: operator=hart;usf hart_route_ref=5;12 usf_route_ref=A;C I always include route information in my bus stop tagging. I think it is more than just placeholder information. For instance, an application showing bus stops on a map should allow you to hover over the stop and see which routes it serves. If the stop doesn't include this data within its tags then you have to search through all the relations too get that data. Its simpler if the data is already in the bus stop node. Also, if you're trying to build a map of the system from the ground up instead of using an import (say, if the city in question didn't release its GTFS feed under an appropriate license) then its really a necessity to tag the stops completely to allow someone else creating the relation later to know which stops to include. Cheers, Greg ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
