From OpenStreetMap Wiki
Jump to: navigation, search

The Massachusetts Department of Transportation (massDOT) and its Office of Transportation Planning (Planning) maintains the state road inventory. The successor to the EOT whose road inventory was uploaded to OSM in 2007. Planning is working with OpenStreetMap to import more data and upload more. Data imported from them uses the massdot_import_* tag

Right to Use

All of this data is in the public domain, attribution is appreciated, but not obligatory.


MBTA Bus Stops

The Data is based on MBTA GTFS File and the .osm file was created 8/12/11 (download). The .osm file containing this data merged with existing nodes can be downloaded here.

Tags Notes
name=* name of the stop
ref=* the "stop_id" from the stop.txt file full documentation here(pdf).
highway=bus_stop based on usage found at that page
network=MBTA See Their Website
operator=MBTA See Their Website
attribution=massDOT MBTA is part of massDOT
source=massdot_import_081211 I'm numbering my imports based on date

Non-MBTA Bus Stops

Same source as above, except the 13 RTA files. Same Tags as above as well, except network=MBTA replaced by the name of the network, and operator=* omitted unless there was a single and obvious Operator for the network. The 2 MiB osm is available here.

Road Inventory

A database of ALL the public roads and "a good portion" of the private ones, a version was uploaded to OpenStreetMap in 2007. There is a version posted annually at our website here. As the internal file is updated on a daily basis I've made a more up to date version available (100MB zipped shapefile updated 8/05/22).

There is a data dictionary available (pdf 154 KiB) as shapefiles have a limit on field lengths there is a conversion table (pdf 8 KiB) that lists the different field names. Chris Schmidt created an MassGis_to_OSM_Attribute_Map during the original upload.

This data, along with all massDOT data is in the "NAD 1983 StatePlane Massachusetts Mainland FIPS 2001" coordinate system, WKID: 26986.


While most of the fields are either self explanatory some are not or require explanation.

AssignedLength & AssignedLengthSource
Be wary of these, especially the Odometer ones, their accuracy is questioned.
Anytime a number is used to represent a city or town, they are numbered alphabetically with 1= Abington & 351 = Yarmouth but with Aquinnah numbered as if it was still Gay head. Massgis has a reference chart.
City and Town in Massachusetts are specific terms that relate to the form of government a municipality has. It has nothing to do with size or even what the town calls itself sometimes.
This refers to who owns a given road, i.e. if you see a pothole, who should you complain to. Note the difference between Private and Unaccepted by city or town. A private road is a road owned by a non-governmental entity. An Unaccepted road is not owned by anyone.
If Jurisdiction is blank, it's not really a road (bike path, trail, or quite a few other things). Querying those out are a good first step.
Attributes relating to the sidewalk, shoulder, median, curbs, width, and speed limit.
These are very out of date (think decades), but we are in the process of updating them, so each future dump will be much more accurate. But we are only doing this for the ones we (massDOT) own, roads with different Jurisdiction will be hit or miss depending on who has jurisdiction (mostly miss).
Values relating to pavement quality. For roads massDOT owns they are no more then 3 years old.
There are a few other codes that sometimes show up besides these three. Querying for only values with a 3 here is a good idea.


Two different types of Route data, these are included in the annual road inventory file or updated ones are available for Road Inventory Routes (20MB zipped shapefile updated 8/05/22) and Road Inventory Equation Routes (11MB zipped shapefile updated 8/05/22). I am not personally familiar with these files but this is the definition we have on our website:

Road Inventory Routes
contains the linear referenced spatial linework for the numbered routes plus "N" routes with the primary direction (north and east) beginning at zero and the opposing direction (south and west) also beginning at zero. This file is designed to match the numbered routes as one would drive them from beginning to end primarily for pavement management purposes. For example, I-91 north begins at zero at the Connecticut border and ends at just over 54 at the Vermont border, while I-91 south begins at zero at the Vermont border and ends just over 54 at the Connecticut border.
Road Inventory Equation Routes
contains the linear referenced spatial linework for the numbered routes plus the "N" routes with the primary and opposing direction matched to the mileposts in the field. The primary direction begins at zero, while the opposing direction begins at the primary direction ending value. For example, I-91 north begins at zero at the Connecticut border and ends at just over 54 at the Vermont border, while I-91 south begins at just over 54 at the Vermont border and ends at zero at the Connecticut border, matching the milepost signs along the highway. In addition, if either the primary or opposing direction extends for a longer distance, than a milepost adjustment will adjust the shorter direction to match the longer direction using an equation.

Mile Posts

Not previously available stand alone you can get the file here (2MB zipped shapefile updated 8/05/22), it has mile posts every tenth mile and is based of the Equation Routes file so they should (hopefully) match up with what is in the field.

Toll Booths

The toll booth layer is all the current toll booths in Massachusetts, currently in addition to the meta tages there is barrier=toll_booth, TOWN=*, LOCATION=MassPike Exit #, & ROUTES=#/#. The last 3 are placeholders.