I-110 ExpressLanes Recommendations

Should the ExpressLanes on the Interstate 110 and Interstate 10 in Los Angeles become a permanent fixture, here’s some recommendations L.A. County Metro could adopt for version 2.0.

  • An API that spits out the current price of the ExpressLanes, so that developers can integrate this into Metro’s official app, Google Maps and other applications. It would be super awesome if the API also interfaced with a predictive engine that, based off past data, showed what the price would be at various upcoming times.
  • Better signage near exits off the ExpressLanes. The left-hand exit for 39th Street/Coliseum in the northbound direction on the 110 is confusing because it comes up fast and there’s no sign saying where this exit will take you.
  • Looping in live video detection or Caltrans/CHP traffic engineers. When workers who monitor freeways via CCTV see an accident on the 110, they should immediately be able to lower the pricing for the ExpressLanes or be able to make them free. This would allow traffic to disperse over more lanes and steer further clear of the accident.
  • I think Metro should experiment with lower pricing. When I was coming on the 105 Eastbound toward the 110, I saw a price of $7 or $8 to get to the USC area and was quickly scared off. I’ve had several pleasant journeys where I saved time by paying about a $1 to use the ExpressLanes. This was the first time I was coming from the 105, and the extra money seemed pretty steep considering a long stretch of the ExpressLanes was moving at 65 mph+.
  • Decision engine. Metro may not want to get into the business of telling people what to do, but signs would be a lot smarter if they said, “$5.00 to Adams Blvd. GOOD DEAL” or “$5.00 Adams Blvd. SAVE 10 MINUTES.”
  • All Zipcars and similar “car-sharing” or “ride-sharing” vehicles should come with transponders pre-installed. Carshares should also get free ExpressLanes access even if it’s a solo driver. Zipcar could lobby for this.

Leave a Reply

Your email address will not be published. Required fields are marked *