A recent 911 call in Boston had responders head to the right address, but in the wrong neighborhood of the city. [Corrected to reflect that the error did not result in a fatality, as I originally suggested. 3/18] Boston has neighborhoods - they are formal, with real known boundaries - but still such things happen. So, until the whole thing is straightened out, when a "serious emergency" (crime in progress or act of violence) call comes in, responders will be dispatched to every such address in every neighborhood.
The event that triggered the change:
The caller told a 911 operator Sunday morning that the homicide occurred at 689 Washington St. Instead of sending police to Dorchester, the operator gave them the same address in Downtown Crossing. Officers ended up at a Malaysian restaurant two blocks from Boston Common and about 7 miles from the scene of the homicide.
The
article in the Boston Globe suggests that the phone company did not code the wired line phone to the neighborhood and perhaps should. It further notes that ZIP Codes and exchanges (the second three numbers in the full phone number) can identify neighborhoods.
Comments
May 8
THANK GOD!!!
Christina de Barros about AOL Sues NavQuest Over Similarity to MapQuest
May 8
There is no confusion. One is boat [...]
Kirk about Ben Bernanke: Geographer
May 8
Are we seeing a new meaning for the term [...]
Archie Belaney about CNN Exemplifies Problems with Static Web Services in Election Coverage
May 7
Curious. ESRI builds the maps...it's not [...]
Allen Zwetschkenbaum about AOL Sues NavQuest Over Similarity to MapQuest
May 7
It's about time the small person has a [...]
Allan Doyle about Was Autodesk the first public company to bring an open source geo product to market?
May 6
BBN was owned by GTE from 1997-2000. We [...]
Jan about AOL Sues NavQuest Over Similarity to MapQuest
May 6
Criminally prosecuted is a bit much. I [...]