They're already doing GTFS, maybe this isn't too much to ask?
Don/
--
karfai [AT] gmail.com
http://www.strangeware.ca
http://blog.strangeware.ca
Any idea whether the malfunction is apathy or some malicious?
Probably just apathy. I may also be doing him a disservice as he claims to be lobbying hard on the issue.
Just not sure the gtfs message is getting through.
swfiua> He claimed he was very interested in the issue and
swfiua> constantly raising at meetings with OC Transpo.
swfiua> However, when I followed up in June and asked if he had any
swfiua> update, he never replied.
swfiua> I followed up again a week ago and his assistant claimed his
swfiua> emails back to me bounced -- really not credible, as my
swfiua> gmail box is far from full.
yes, but the city of Ottawa runs Exchange ... HOSTED BY MICROSOFT, and
Exchange screws up outgoing email if DNS is particularly slow.
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] m...@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
3 months? Sometime around November then... It's good that they're on
it, I suppose. I have to ask: There was a feed (that sort of worked)
which got removed almost 8 months ago. What's so special about this
data that freeing it into a consumable format should take so long?
I look forward to seeing the new stream come online soonish. When the
realtime data was available, I didn't find it as erroneous as articles
on the subject had suggested. In fact, the only real problem I had was
the number of buses (usually locals) that indicated they weren't
transmitting adherence data (a particular field was "false").
If you're talking to the technical people involved in the feed, you
might mention that a decent time synchronization point would be an
incredibly useful addition. In the previous feed, the adherence times
were measured against some unknown time source that wasn't in sync
with network time (NTP). The same problem exists in the GTFS feed:
Arrival is measured in seconds since midnight, but after observing the
adherence time posted next to the drivers via the MK devices, I've
noticed this isn't in sync with the network time on my mobile device
and/or network server.
>
> Alternatively, or additionally, you can email the open...@ottawa.ca
> email account to register your request (again volume can be a powerful
> influencer), or register the request on the dataott.org site where
> there is a request posted which you can vote on and comment:
> http://www.dataott.org/app/need/show/4.
>
Commented with applause for the GTFS feed.
Thanks.