Posts
-
When some data is better than no data
-
Loops and cards and taps, oh my!
-
Python context managers for CFFI resource management
-
Legacy AVL system? It's okay, join the club.
-
Reprogramming a u-blox MAX-7Q in-situ on a Raspberry Pi
-
How should transit agencies make their GTFS available?
-
Apps ≇ frequency
-
Why "they're not on NextBus" isn't the problem it sounds like
-
Synoptic first!
-
Traction motor, HVAC unit, AVL system?
-
Building Momentum with open data, open source, and open architecture
-
What's wrong with the NextBus API?
-
Passively open, actively closed
-
GTFS-realtime for WMATA buses
-
Open standards are a force multiplier for civic software
-
Bringing OpenTripPlanner and OneBusAway to DC to improve rider experience
-
Journey history as open data, and cooperation with developers
-
Celebrating regional mobility
-
Automating transit alert selection using fare collection data
-
Context-free trip planning
-
WMATA's open data efforts are good, but could be better
-
Taming MTA New York City Transit's bus GTFS feeds
-
Announcing htmlbib, a tool for rendering BibTeX files as interactive HTML
-
It's 2011. Do you know where your buses are?
-
Human factors in rail signalling accidents, and the role of backup systems
-
Using the Common Alerting Protocol for transit alerts
-
Does Twitter provide a good substitute for costly SMS services?
-
27 hours on the IRT: visualizing ATS data
-
Making transit alert feeds effective
-
Maryland's new 511 system falls short of expectations
-
Do-it-yourself WMATA train arrival display
-
More on social media for transit agencies
-
Google Apps Script: like AppleScript for the Web
-
41 of the top 50 transit agencies use Twitter. Does yours?
-
What can we do with station subtitles?
-
What role do developers play in open payment?
-
Heritage trains and CBTC
-
Metro Forward: how you turn a transit agency around
-
Sustaining signage systems
-
How do we show the value of HSR?
-
Tar River Transit: not the 'alternative'
-
WMATA releases NextBus predictions; introduces another proprietary format
-
Locational privacy in open payment
-
More weekend closures, less single-tracking for Metrorail
-
Station names are about system usability, not neighborhood identity
-
Using shortDOIs automatically in BibDesk
-
GTFS direction_id on loops
-
Updates to tph.py
-
Announcing aerodb
-
Rider feedback for transit systems: the good and the bad
-
Looking at PATH's service with GTFS data
-
A Python script for visualizing GTFS data
-
Visualizing transit service levels using GTFS data
-
Passenger information systems for consolidated bus terminals
-
Notes on bi-directional signalling
-
Kermit: more than a file transfer program, a tangible link to the past
-
Where does Chromaroma's data come from?
-
Fare policy ≠ fare collection equipment
-
Verifone: Square's not the problem, but EMV is the solution
-
Your smartphone is not an AVL solution
-
Documentation for geolucidate
-
Transparency in artificial intelligence
-
FareBot: reading ORCA cards on Android
-
What can you do in 300 ms?
-
MultiStreamer, a work in progress
-
Software package updates
-
Metrorail station codes
-
Starbucks mobile payment: neat, but not novel
-
The case of the not-so-electronic application
-
First airports, now airlines
-
More free airport data
-
Cheap airport data
-
BBC transport article ignores the facts
-
Librelist: where ideology trumps usability
-
A novel method for inserting elements in text with lxml
-
Reviewing WMATA’s Transparent Metro Data Sets initiative
-
Updates to geolucidate
-
XML misconceptions harm interoperability
-
A tool for evaluating academic programs
-
Notes on the design of student information systems
-
Announcing geolucidate
subscribe via RSS