495 In Atlanta at 5 PM
Sent from my SGH-T679 using Tapatalk
Sent from my SGH-T679 using Tapatalk
Worked great up until last week, when it just started sending me straight into jams. The jams are all well documented on the map though. The problem with the map in DC is not that it has not been well edited. The problem is that there are many many time based restrictions in DC. Those time based restrictions can make waze almost useless depending on your commute.bgodette wrote:So with that many users, how well does it work for rerouting, or is the map in DC still not mature enough?CBenson wrote:Over 1150 at 6:00 pm in Washington, DC yesterday.
But you shouldn't be leaving the Philadelphia–Camden–Wilmington MSA (or the Philadelphia-Reading-Camden CSA) unless you're crossing the bridge at Trenton. I suspect they're using the CSAs as 1) the numbers would be bigger (look better for marketing) and 2) I commute from the Baltimore-Columbia-Towson MSA to the Washington-Arlington-Alexandria MSA (while staying in the Washington-Baltimore-Arlington CSA) without typically seeing any changes in the numbers.WeeeZer14 wrote:NJ is split amongst a few US Census Bureau Metropolitan Statistical Areas (MSAs) and that is what the Waze areas are based off of. (Or was it is the Combined Statistical Areas, CSAs? Same impact either way.)MReiser4670 wrote:Over this past week I've been seeing 4000-5000 in Philadelphia and 9000-10,000 when I cross the bridge into New Jersey. Not sure why they're separate, but I suppose there's a reason. Either way, these numbers are basically double what they were less than a month ago, and 4x what we were seeing 9 months back.
http://en.wikipedia.org/wiki/List_of_Me ... ical_Areas
Re: Number of local Wazers at rush hour