A little more feedback. I was talking to one of the city councilors yesterday evening who is on the Ottawa informatics sub-committee. Apparently they have decide to release data under the opendata side but his thoughts were that it was a list of swimming lessons and their times and not much else.
However since it appears to have been released to Google there is a very good chance I can get what ever we require the question then becomes what exactly do we want? It started out as GTFS, Google transit whatever but has now been amended to General Transit whatever. We have a few bus stops in Ottawa already mapped but what we don't have is the four digit bus stop number that allows you to phone and see when the next bus is, nor do me have the official locations that are displayed on the bus GPS as the bus approaches the stops. I assume this information would be useful. Previously I have suggested wiping data already in OSM where it is either wrong or incomplete and been cried down because people have spent time entering the data. In this case bus tops missing the metadata of the official location or the four digit number is far less valuable than just knowing where the bus stop is. Route information can be tied to physical bus stops but gets amended twice a year. Thoughts please. Thanks John On 21 April 2010 16:02, Sam Vekemans <acrosscanadatra...@gmail.com> wrote: > There is also the talk-tran...@opentstreetmap.org discussion list, the > folks who are subscribed would be interested to hear your methods/ideas > about this. Just cc: that list in your discussions :) > > http://lists.openstreetmap.org/listinfo/talk-transit > > BTW, once the licence is correct, just simply convert the data to .osm > format and make it available to the community (via this list & making a > wiki page). & Remind people to only copy in those stops in a small area > (that they know of) and can handle on their own. > Splitting the .osm file into geographical areas small as possible would > really help, or even breaking it down into different types of bus stops (if > that information is available) would certainly help. (quad-tree tiling) > > This method, when combined with other methods, ie. WMS layer maptile > overlay / OpenJUMP automatch Diff files. Is the ideal solution, as it can > involved the greater community, who has varying levels of technical > ability. The source data doesn't need to be changed, but it can be > enhanced (externally) by adding in the OSM NODE ID, into the source > database. So then it can be cross-referenced to ensure quality control. > > > Cheers, > Sam > > > Twitter: @Acrosscanada > Blogs: http://acrosscanadatrails.posterous.com/ > http://Acrosscanadatrails.blogspot.com > Facebook: http://www.facebook.com/sam.vekemans > Skype: samvekemans > OpenStreetMap IRC: http://irc.openstreetmap.org > @Acrosscanadatrails > > > > On Wed, Apr 21, 2010 at 11:41 AM, Robert Damphousse <rjdam...@gmail.com>wrote: > >> GTFS is a format that Google started for storing information about public >> transit systems: >> >> http://code.google.com/transit/spec/transit_feed_specification.html >> >> If you have specific questions about the format that are not addressed by >> the documentation, you can try the transit developers group: >> >> http://groups.google.com/group/transit-developers/ >> >> Keep in mind that the format is far from being a "standard", and nearly >> every transit agency has something in their GTFS dataset which is not part >> of the current specification. There are also a few tools for importing GTFS >> data into a SQL database, this may help you take a better look at what is in >> the data. Here is one such tool: >> >> http://cbick.github.com/gtfs_SQL_importer/html/index.html >> >> Cheers, >> Robert >> >> On Wed, Apr 21, 2010 at 11:29 AM, Thomas Cort <linuxg...@gmail.com>wrote: >> >>> The coordinates don't appear to be very accurate. I tried plotting a >>> few points on a map. They are pretty close sometimes, but not dead on >>> (maybe I just picked the few inaccurate ones to test). The bus stop >>> number (asset_ref in OSM / stop_code in GTFS) is not present in >>> stops.txt. There are already a number of OC Transpo stops in OSM, so >>> any import would have to check for nearby duplicates. Lastly and most >>> importantly, there is no license information* and it isn't marked on >>> the GTFS exchange site as official. >>> >>> * Note, I'm one of the organizers of Open Data Ottawa >>> (opendataottawa.ca). The city is likely going to be opening up some >>> data sets soon. The motion has passed the IT sub comittee and just has >>> a couple of more steps to go. Hopefully that will clear up the license >>> uncertainty and give the public an official OC Transpo data set. I'll >>> keep you posted. >>> >>> -Tom >>> >>> >>> >>> On Wed, Apr 21, 2010 at 1:45 PM, Richard Weait <rich...@weait.com> >>> wrote: >>> > On Wed, Apr 21, 2010 at 1:30 PM, john whelan <jwhelan0...@gmail.com> >>> wrote: >>> >> There seems to be a collection of bus stop data here for different >>> cities >>> >> including Ottawa. Any idea who is putting it up or if there are any >>> scripts >>> >> for import etc? >>> > >>> > How is that data licensed? >>> > >>> > _______________________________________________ >>> > Talk-ca mailing list >>> > Talk-ca@openstreetmap.org >>> > http://lists.openstreetmap.org/listinfo/talk-ca >>> > >>> >>> _______________________________________________ >>> Talk-ca mailing list >>> Talk-ca@openstreetmap.org >>> http://lists.openstreetmap.org/listinfo/talk-ca >>> >> >> >> _______________________________________________ >> Talk-ca mailing list >> Talk-ca@openstreetmap.org >> http://lists.openstreetmap.org/listinfo/talk-ca >> >> >
_______________________________________________ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
