This hosted feature layer is provided by the USDA FPAC-BC-GEO and shows image acquisition dates for 2023 National Agriculture Imagery Program (NAIP) imagery for Massachusetts. This date index is state based and contains a polygon for each exposure used in the creation of the imagery. Click on a polygon to find out more information about any area on the image. Attribute information includes the following: IDATE - Image acquisition date SDATE - Polygon start date/time - local 24 hour clock. The start/end time will be for the collection of the individual polygon (will be the same for frame based systems)EDATE - Polygon end date/time - local 24 hour clock. The start/end time will be for the collection of the individual polygon (will be the same for frame based systems)BCON - Color type - possible values are NC (natural color), CIR (color infrared), and M4B (4-band)CAM_TYPE - Camera type (Digital or film)CAM_MAN - Camera ManufacturerCAM_MOD - Camera modelHARD_FIRM - Camera HW and FW version which provides top level information specific to the camera systemSENSNUM - Sensor or lens serial numberAC_TYPE - Aircraft type - ICAO designation (i.e. C441 for a Cessna 441 Conquest II), airborne platforms only blank attribute for space-based systemsACTAILNUM - Aircraft tail number - airborne platforms only a blank attribute for space-based systemsSHAPE_AREA - Polygon area (square meters)RED_RNGE - Red electromagnetic spectrum - spectrum range in nano meters (604-664)GREEN_RNGE - Green electromagnetic spectrum - spectrum range in nano meters (533-587)BLUE_RNGE - Blue electromagnetic spectrum - spectrum range in nano meters (420-492)NIR_RNGE - Near infrared electromagnetic spectrum - spectrum range in nano meters (683-920)

DPH note about change from 7-day to 14-day metrics: As of 10/15/2020, this dataset is no longer being updated. Starting on 10/15/2020, these metrics will be calculated using a 14-day average rather than a 7-day average. The new dataset using 14-day averages can be accessed here: https://data.ct.gov/Health-and-Human-Services/COVID-19-case-rate-per-100-000-population-and-perc/hree-nys2

As you know, we are learning more about COVID-19 all the time, including the best ways to measure COVID-19 activity in our communities. CT DPH has decided to shift to 14-day rates because these are more stable, particularly at the town level, as compared to 7-day rates. In addition, since the school indicators were initially published by DPH last summer, CDC has recommended 14-day rates and other states (e.g., Massachusetts) have started to implement 14-day metrics for monitoring COVID transmission as well.

With respect to geography, we also have learned that many people are looking at the town-level data to inform decision making, despite emphasis on the county-level metrics in the published addenda. This is understandable as there has been variation within counties in COVID-19 activity (for example, rates that are higher in one town than in most other towns in the county).

This dataset includes a weekly count and weekly rate per 100,000 population for COVID-19 cases, a weekly count of COVID-19 PCR diagnostic tests, and a weekly percent positivity rate for tests among people living in community settings. Dates are based on date of specimen collection (cases and positivity).

A person is considered a new case only upon their first COVID-19 testing result because a case is defined as an instance or bout of illness. If they are tested again subsequently and are still positive, it still counts toward the test positivity metric but they are not considered another case.

These case and test counts do not include cases or tests among people residing in congregate settings, such as nursing homes, assisted living facilities, or correctional facilities.

These data are updated weekly; the previous week period for each dataset is the previous Sunday-Saturday, known as an MMWR week (https://wwwn.cdc.gov/nndss/document/MMWR_week_overview.pdf). The date listed is the date the dataset was last updated and corresponds to a reporting period of the previous MMWR week. For instance, the data for 8/20/2020 corresponds to a reporting period of 8/9/2020-8/15/2020.

Notes: 9/25/2020: Data for Mansfield and Middletown for the week of Sept 13-19 were unavailable at the time of reporting due to delays in lab reporting.

This file contains the arrival and departure events for buses up to the most recent completed month of 2025. Due to data collection issues, data is not guaranteed to be complete for any stop or date.Data Dictionary:

NameDescriptionData TypeExampleservice_dateDate on which the trip took place. Service dates run from around 2:00AM - 1:59:59AMDate2019-12-31route_idRoute IdString01direction_idIdentifies whether the trip is traveling inbound or outboundStringInboundhalf_trip_idIdentification for the one way tripInteger40836717stop_idGTFS-compatible stopInteger75time_point_idThe code for the timepointStringmittime_point_orderThe order of this timepoint in the tripInteger4point_typeIdentifies whether the stop is the starting point, midpoint, or endpoint for the tripStringMidpointstandard_typeIdentifies whether the trip should be evaluated on the scheudle standard or headway standard.StringHeadwayscheduledThe time the trip was scheduled to depart the stop. The scheduled time should not be used to evaluated reliability if this trip is evaluated on the headway standard. Only the headway and run time should be used per the Service Delivery Policy.Time12:30 AMactualThe time the trip actually departed the timepoint.Time12:29 AMscheduled_headwayThe scheduled time between the trip and the previous trip at the stop, in seconds. NULL if this trip is evaluated on the schedule standard.Integer1200headwayThe actual time between the trip and the previous trip at the stop, in seconds. NULL if this trip is evaluated on the schedule standard or if this is the last stop on the trip (endpoint). Endpoints are evaluated by whether the trip runtime is within 120% of the scheduled run time.Integer1163MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

This dataset is no longer being updated as of 11/24/2022. It is being retained on the Open Data Portal for its potential historical interest.

The data represented in this graph are dynamic and may change over time.

Since March 20, the Cambridge Public Health Department (CPHD) has provided data regarding COVID-19 case counts based on the date that the Massachusetts Public Health Department (MDPH) reported the case to CPHD (known as report date).

Beginning March 31, 2020, CPHD began providing COVID-19 case counts based on the onset time -- the date of a positive diagnosis -- which is preferable for studying disease patterns over time. Both sets of data provide the same number of total cases. CPHD often receives onset time (positive COVID-19 diagnosis) after the report date. Thus, the graph displaying onset time is recommended as a representation of the case counts per day.

Daily case counts reflect the total number of cases to date, including active and recovered individuals.

This file contains the arrival and departure events for buses for calendar year 2018. Due to data collection issues, data is not guaranteed to be complete for any stop or date.Data Dictionary:

Name
Description
Data Type
Example


service_date
Date on which the trip took place. Service dates run from around 2:00AM - 1:59:59AM 
Date
2019-12-31


route_id
Route Id
String
01


direction_id
Identifies whether the trip is traveling inbound or outbound
String
Inbound


half_trip_id
Identification for the one way trip
Integer
40836717


stop_id
GTFS-compatible stop
Integer
75


time_point_id
The code for the timepoint
String
mit


time_point_order
The order of this timepoint in the trip
Integer
4


point_type
Identifies whether the stop is the starting point, midpoint, or endpoint for the trip 
String
Midpoint


standard_type
Identifies whether the trip should be evaluated on the scheudle standard or headway standard. 
String
Headway


scheduled
The time the trip was scheduled to depart the stop. The scheduled time should not be used to evaluated reliability if this trip is evaluated on the headway standard. Only the headway and run time should be used per the Service Delivery Policy.
Time
12:30 AM


actual
The time the trip actually departed the timepoint.
Time
12:29 AM

Integer
-60


scheduled_headway
The scheduled time between the trip and the previous trip at the stop, in seconds. NULL if this trip is evaluated on the schedule standard.

Integer
1200


headway
The actual time between the trip and the previous trip at the stop, in seconds. NULL if this trip is evaluated on the schedule standard or if this is the last stop on the trip (endpoint). Endpoints are evaluated by whether the trip runtime is within 120% of the scheduled run time.

Integer
1163

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

This file contains the arrival and departure events for buses for calendar 2019. Due to data collection issues, data is not guaranteed to be complete for any stop or date.Data Dictionary:

Name
Description
Data Type
Example


service_date
Date on which the trip took place. Service dates run from around 2:00AM - 1:59:59AM 
Date
2019-12-31


route_id
Route Id
String
01


direction_id
Identifies whether the trip is traveling inbound or outbound
String
Inbound


half_trip_id
Identification for the one way trip
Integer
40836717


stop_id
GTFS-compatible stop
Integer
75


time_point_id
The code for the timepoint
String
mit


time_point_order
The order of this timepoint in the trip
Integer
4


point_type
Identifies whether the stop is the starting point, midpoint, or endpoint for the trip 
String
Midpoint


standard_type
Identifies whether the trip should be evaluated on the scheudle standard or headway standard. 
String
Headway


scheduled
The time the trip was scheduled to depart the stop. The scheduled time should not be used to evaluated reliability if this trip is evaluated on the headway standard. Only the headway and run time should be used per the Service Delivery Policy.
Time
12:30 AM


actual
The time the trip actually departed the timepoint.
Time
12:29 AM


scheduled_headway
The scheduled time between the trip and the previous trip at the stop, in seconds. NULL if this trip is evaluated on the schedule standard.

Integer
1200


headway
The actual time between the trip and the previous trip at the stop, in seconds. NULL if this trip is evaluated on the schedule standard or if this is the last stop on the trip (endpoint). Endpoints are evaluated by whether the trip runtime is within 120% of the scheduled run time.

Integer
1163

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

The protected and recreational open space datalayer contains the boundaries of conservation lands and outdoor recreational facilities in Massachusetts. The associated database contains relevant information about each parcel, including ownership, level of protection, public accessibility, assessor’s map and lot numbers, and related legal interests held on the land, including conservation restrictions. Conservation and outdoor recreational facilities owned by federal, state, county, municipal, and nonprofit enterprises are included in this datalayer. Not all lands in this layer are protected in perpetuity, though nearly all have at least some level of protection.

Definitions of "Level of Protection" In Perpetuity (P)- Legally protected in perpetuity and recorded as such in a deed or other official document. Land is considered protected in perpetuity if it is owned by the town’s conservation commission or, sometimes, by the water department; if a town has a conservation restriction on the property in perpetuity; if it is owned by one of the state’s conservation agencies (thereby covered by article 97); if it is owned by a non-profit land trust; or if the town received federal or state assistance for the purchase or improvement of the property.Private land is considered protected if it has a deed restriction in perpetuity, if an Agriculture Preservation Restriction has been placed on it, or a Conservation Restriction has been placed on it.Temporary (T) - Legally protected for less than perpetuity (e.g. short term conservation restriction), or temporarily protected through an existing functional use. For example, some water district lands are only temporarily protected while water resource protection is their primary use.These lands could be developed for other uses at the end of their temporary protection or when their functional use is no longer necessary. These lands will revert to unprotected status at a given date unless protection status is extended.Limited (L) - Protected by legal mechanisms other than those above, or protected through functional or traditional use.These lands might be protected by a requirement of a majority municipal vote for any change in status. This designation also includes lands that are likely to remain open space for other reasons (e.g. cemeteries and municipal golf courses).None (N) - Totally unprotected by any legal or functional means. This land is usually privately owned and could be sold without restriction at any time for another use (e.g. scout camps, private golf course, and private woodland).More details...Feature layer is also available.

Petition subject: Court cases Original: http://nrs.harvard.edu/urn-3:FHCL:13906013 Date of creation: 1740-05-28 Petition location: Boston Selected signatures:Nathaniel Cunningham Actions taken on dates: 1740-05-31,1740-06-03,1740-06-06,1740-06-14 Legislative action: Received in the House on May 31, 1740 and read and ordered and sent for concurrence and received in the Council on June 3, 1740 and read and concurred and received in the Council on June 6, 1740 and read and ordered and sent for concurrence and received in the House on June 14, 1740 and read and concurred Total signatures: 1 Legislative action summary: Received, read, ordered, sent, received, read, concurred, received, read, ordered, sent, received, read, concurred Legal voter signatures (males not identified as non-legal): 1 Female only signatures: No Identifications of signatories: merchant Prayer format was printed vs. manuscript: Manuscript Additional archivist notes: Nathaniel Cunningham, George Hewes, Robert Hewes, Cato, Nero, Quagno, Scipio, Mr. Trumball of Lebanon, Joseph Barnard of Hartford, William Nicholls, John Read, John Ryall, John Walley, Mr. Barker, Mr. Gooch, [additional documents in volumes] Location of the petition at the Massachusetts Archives of the Commonwealth: Massachusetts Archives volume 59, pages 316-320 Acknowledgements: Supported by the National Endowment for the Humanities (PW-5105612), Massachusetts Archives of the Commonwealth, Radcliffe Institute for Advanced Study at Harvard University, Center for American Political Studies at Harvard University, Institutional Development Initiative at Harvard University, and Harvard University Library.

This volume's release consists of 143321 media files captured by autonomous wildlife monitoring devices under the project, Massachusetts Wildlife Monitoring Project. The attached files listed below include several CSV files that provide information about the data release. The file, "media.csv" provides the metadata about the media, such as filename and date/time of capture. The actual media files are housed within folders under the volume's "child items" as compressed files. A critical CSV file is "dictionary.csv", which describes each CSV file, including field names, data types, descriptions, and the relationship of each field to fields in other CSV files. Some of the media files may have been "tagged" or "annotated" by either humans or by machine learning models, identifying wildlife targets within the media. If so, this information is stored in "annotations.csv" and "modeloutputs.csv", respectively. To protect privacy, all personally identifiable information (PII) have been removed, locations have been "blurred" by bounding boxes, and media featuring sensitive taxa or humans have been omitted. To enhance data reuse, the sbRehydrate() function in the AMMonitor R package will download files and re-create the original AMMonitor project (database + media files). See source code at https://code.usgs.gov/vtcfwru/ammonitor.

Petition subject: Slaves Original: http://nrs.harvard.edu/urn-3:FHCL:13905997 Date of creation: 1703-06-01 Petition location: Massachusetts Selected signatures:John Saffin Actions taken on dates: 1703-06-01,1703-06-03,1703-06-03,1703-06-03 Legislative action: Received in the House and read on June 1, 1703 and read on June 3, 1703 and ordered that the petitioner have a hearing before this court on the 2nd Wednesday of the next session and sent for concurrence and received in Council on June 3, 1703 and read and not agreed to and ordered that the matter be heard before the next Court of General Sessions of the Peace of Suffolk and received in the House on June 3, 1703 and read and agreed Total signatures: 1 Legislative action summary: Received, read, read, ordered, sent, received, read, not agreed, ordered, received, read, agreed Legal voter signatures (males not identified as non-legal): 1 Female only signatures: No Prayer format was printed vs. manuscript: Manuscript Additional archivist notes: Adam, Isaac Addington, Samuel Converse, Boston, England, smallpox Location of the petition at the Massachusetts Archives of the Commonwealth: Massachusetts Archives volume 9, page 152 Acknowledgements: Supported by the National Endowment for the Humanities (PW-5105612), Massachusetts Archives of the Commonwealth, Radcliffe Institute for Advanced Study at Harvard University, Center for American Political Studies at Harvard University, Institutional Development Initiative at Harvard University, and Harvard University Library.

The political boundary datalayer is a polygon representation of town boundaries created from arcs developed from survey coordinates extracted from the 68-volume Harbor and Lands Commission Town Boundary Atlas for the 351 communities (cities and towns) in Massachusetts. The Atlas was published in the early 1900's and is maintained by the Survey Section of Massachusetts Highway Department. For communities with a coastal boundary, MassGIS has collaborated with Massachusetts Water Resources Authority and the Department of Environmental Protection to complete a 1:12000 scale coastline. The boundary for the coastline was defined as being the upland side of tidal flats and rocky inter-tidal zones. Note that the 351 communities are the official municipal names, not including "villages" or other sections of towns.This datalayer was created for the purposes of providing an up-to-date polygon version of the town boundaries for the 351 cities and towns of the Commonwealth of Massachusetts. The legislative intent for some boundaries could not be mapped. Boundaries where that is true are identified in the attribute information. This layer contains multi-part polygons, one for each municipality. The coastline on this layer has been generalized for small-scale cartography and faster display in web map services.See the layer metadata for details.

Crime incident reports are provided by Boston Police Department (BPD) to document the initial details surrounding an incident to which BPD officers respond. This is a dataset containing records from the new crime incident report system, which includes a reduced set of fields focused on capturing the type of incident as well as when and where it occurred. Records in the new system begin in June of 2015.

The Analyze Boston Data Exports posted now are the updated incident data from the Mark43 RMS Database which launched in September of 2019 and is complete through present with the exclusion of data that falls under MGL ch.41 s.98f. The 2019 data that was originally posted contained combined exports from the Intergraph RMS and the Mark43 RMS during 2019 but the Extract/Transfer/Load process was not updated during the transition.

This layer contains block level 2020 Decennial Census redistricting data as reported by the U.S. Census Bureau for the state of Massachusetts. The attributes come from the 2020 Public Law 94-171 (P.L. 94-171) tables.Data download date: August 12, 2021Census tables: P1, P2, P3, P4, H1, P5, HeaderDownloaded from: Census FTP siteProcessing Notes:Data was downloaded from the U.S. Census Bureau FTP site, imported into SAS format and joined to the 2020 TIGER boundaries. Boundaries are sourced from the 2020 TIGER/Line Geodatabases. Boundaries have been projected into Web Mercator and each attribute has been given a clear descriptive alias name. No alterations have been made to the vertices of the data.Each attribute maintains it's specified name from Census, but also has a descriptive alias name and long description derived from the technical documentation provided by the Census. For a detailed list of the attributes contained in this layer, view the Data tab and select "Fields". The following alterations have been made to the tabular data:Joined all tables to create one wide attribute table:P1 - RaceP2 - Hispanic or Latino, and not Hispanic or Latino by RaceP3 - Race for the Population 18 Years and OverP4 - Hispanic or Latino, and not Hispanic or Latino by Race for the Population 18 Years and OverH1 - Occupancy Status (Housing)P5 - Group Quarters Population by Group Quarters Type (correctional institutions, juvenile facilities, nursing facilities/skilled nursing, college/university student housing, military quarters, etc.)HeaderAfter joining, dropped fields: FILEID, STUSAB, CHARITER, CIFSN, LOGRECNO, GEOVAR, GEOCOMP, LSADC.GEOCOMP was renamed to GEOID and moved be the first column in the table, the original GEOID was dropped.Placeholder fields for future legislative districts have been dropped: CD118, CD119, CD120, CD121, SLDU22, SLDU24, SLDU26, SLDU28, SLDL22, SLDL24 SLDL26, SLDL28.P0020001 was dropped, as it is duplicative of P0010001. Similarly, P0040001 was dropped, as it is duplicative of P0030001.In addition to calculated fields, County_Name and State_Name were added.The following calculated fields have been added (see long field descriptions in the Data tab for formulas used): PCT_P0030001: Percent of Population 18 Years and OverPCT_P0020002: Percent Hispanic or LatinoPCT_P0020005: Percent White alone, not Hispanic or LatinoPCT_P0020006: Percent Black or African American alone, not Hispanic or LatinoPCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or LatinoPCT_P0020008: Percent Asian alone, Not Hispanic or LatinoPCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or LatinoPCT_P0020010: Percent Some Other Race alone, not Hispanic or LatinoPCT_P0020011: Percent Population of Two or More Races, not Hispanic or LatinoPCT_H0010002: Percent of Housing Units that are OccupiedPCT_H0010003: Percent of Housing Units that are VacantPlease note these percentages might look strange at the individual block level, since this data has been protected using differential privacy.**To protect the privacy and confidentiality of respondents, data has been protected using differential privacy techniques by the U.S. Census Bureau. This means that some individual blocks will have values that are inconsistent or improbable. However, when aggregated up, these issues become minimized. The pop-up on this layer uses Arcade to display aggregated values for the surrounding area rather than values for the block itself.Additional links:U.S. Census BureauU.S. Census Bureau Decennial CensusAbout the 2020 Census2020 Census2020 Census data qualityDecennial Census P.L. 94-171 Redistricting Data Program

Petition subject: School discrimination Original: http://nrs.harvard.edu/urn-3:FHCL:25500550 Date of creation: (unknown) Petition location: Malden Legislator, committee, or address that the petition was sent to: Edward M. Flanagan, Malden; committee on education Selected signatures:John P. Donnelly Actions taken on dates: 1969-01-01,1969-01-01 Legislative action: Received in the House on January 1, 1969 and referred to the committee on education and sent for concurrence and received in the Senate on January 1, 1969 and concurred Total signatures: 1 Legislative action summary: Received, referred, sent, received, concurred Legal voter signatures (males not identified as non-legal): 1 Female only signatures: No Identifications of signatories: citizens, Massachusetts Mayors Association Prayer format was printed vs. manuscript: Printed Additional non-petition or unrelated documents available at archive: additional documents available Additional archivist notes: for an investigation by a special commission including members of the General Court relative to the financing by the Commonwealth of elementary and secondary public school education, includes address Location of the petition at the Massachusetts Archives of the Commonwealth: Resolves 1969, c.61, passed August 4, 1969 Acknowledgements: Supported by the National Endowment for the Humanities (PW-5105612), Massachusetts Archives of the Commonwealth, Radcliffe Institute for Advanced Study at Harvard University, Center for American Political Studies at Harvard University, Institutional Development Initiative at Harvard University, and Harvard University Library.

Petition subject: Military service Original: http://nrs.harvard.edu/urn-3:FHCL:13909102 Date of creation: 1781-02-24 Petition location: Boston Selected signatures:Alexander Hodgdan Actions taken on dates: 1781-03-15 Legislative action: Received in the Council on March 15, 1781 and read and advised Total signatures: 1 Legislative action summary: Received, read, advised Legal voter signatures (males not identified as non-legal): 1 Female only signatures: No Identifications of signatories: committee appointed by the town of Boston to inlist their quota of men Prayer format was printed vs. manuscript: Manuscript Additional archivist notes: [with list of men enlisted before January 31, 1781, including Bristol Ballard] Location of the petition at the Massachusetts Archives of the Commonwealth: Massachusetts Archives volume 177, pages 348-349 Acknowledgements: Supported by the National Endowment for the Humanities (PW-5105612), Massachusetts Archives of the Commonwealth, Radcliffe Institute for Advanced Study at Harvard University, Center for American Political Studies at Harvard University, Institutional Development Initiative at Harvard University, and Harvard University Library.

This file contains the arrival and departure events for buses between January and December 2020. Due to data collection issues, data is not guaranteed to be complete for any stop or date.Data Dictionary:

Name
Description
Data Type
Example


service_date
Date on which the trip took place. Service dates run from around 2:00AM - 1:59:59AM 
Date
2019-12-31


route_id
Route Id
String
01


direction_id
Identifies whether the trip is traveling inbound or outbound
String
Inbound


half_trip_id
Identification for the one way trip
Integer
40836717


stop_id
GTFS-compatible stop
Integer
75


time_point_id
The code for the timepoint
String
mit


time_point_order
The order of this timepoint in the trip
Integer
4


point_type
Identifies whether the stop is the starting point, midpoint, or endpoint for the trip 
String
Midpoint


standard_type
Identifies whether the trip should be evaluated on the scheudle standard or headway standard. 
String
Headway


scheduled
The time the trip was scheduled to depart the stop. The scheduled time should not be used to evaluated reliability if this trip is evaluated on the headway standard. Only the headway and run time should be used per the Service Delivery Policy.
Time
12:30 AM


actual
The time the trip actually departed the timepoint.
Time
12:29 AM


scheduled_headway
The scheduled time between the trip and the previous trip at the stop, in seconds. NULL if this trip is evaluated on the schedule standard.

Integer
1200


headway
The actual time between the trip and the previous trip at the stop, in seconds. NULL if this trip is evaluated on the schedule standard or if this is the last stop on the trip (endpoint). Endpoints are evaluated by whether the trip runtime is within 120% of the scheduled run time.

Integer
1163

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

Petition: Military service Original: http://nrs.harvard.edu/urn-3:FHCL:13909084 Date of creation: 17770000 Petition location: Ipswich Top signatures:Joshua Giddings Actions taken on dates: 1777-08-16 Legislative action: Received in the Council on August 12, 1777 and ordered and read and accepted Total signatures: 1 Legislative action summary: Received, ord ered, read, accepted Legal voter signatures (males not identified as non-legal): 1 Identifications of signatories: NA Prayer format was printed vs. manuscript: Manuscript Additional archivist notes: Fortune Ellery, John Cushing, Captain Robert Dodge, [“…he was at great expence in hiring said Fortune to engage in the public service to which services he was not obliged being a black man…”] Acknowledgements: Supported by the National Endowment for the Humanities (PW-5105612), Massachusetts Archives of the Commonwealth, Radcliffe Institute for Advanced Study at Harvard University, Center for American Political Studies at Harvard University, Institutional Development Initiative at Harvard University, and Harvard University Library.

It includes all heavy rail and light rail rapid transit lines. These travel times are calculated from the departure time at the origin stop to the arrival time at the destination stop. Due to track circuit or other data issues, data is not guaranteed to be complete for any origin-destination pair or date.Data Dictionary:NameDescriptionData TypeExampleservice_dateDate for which travel times should be returned.Date43830route_idGTFS-compatible route for which travel times should be returned.StringOrangedirection_idGTFS-compatible direction for which travel times should be returned.Integer0from_stop_idGTFS-compatible stop representing the origin stop in a pair.String70205to_stop_idGTFS-compatible stop representing the destination stop in a pair.String70154start_time_secProperty of “Travel Times”. Expressed in "seconds after midnight." The time associated with the departure event of the vehicle from the origin stop of the pair.Integer45763end_time_secProperty of “Travel Times”. Expressed in "seconds after midnight." The time associated with the arrival event of the vehicle to the destination stop of the pair.Integer46411travel_time_secProperty of “Travel Times”. Difference between start_time_sec and end_time_sec. The actual travel time between the origin stop and the destination stop, in seconds.Integer648MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

View arrest details and search by State Police division, date, location, type of offense, and more.

Petition subject: Support for individuals Original: http://nrs.harvard.edu/urn-3:FHCL:13448066 Date of creation: 1862-01-13 Petition location: Boston Legislator, committee, or address that the petition was sent to: H. Augustus Lothrop, Sharon; committee on claims Selected signatures:Sally Burr Actions taken on dates: 1862-01-15,1862-01-16 Legislative action: Received in the House on January 15, 1862 and referred to the committee on claims and sent for concurrence and received in the Senate on January 16, 1862 and concurred Total signatures: 1.0 Legislative action summary: Received, referred, sent, received, concurred Females of color signatures: 1.0 Female only signatures: Yes Identifications of signatories: a member of the Ponkapog tribe of Indians, [females of color] Prayer format was printed vs. manuscript: Manuscript Native American tribe: Massachusetts, Ponkapoag Acknowledgements: Supported by the National Endowment for the Humanities (PW-5105612), Massachusetts Archives of the Commonwealth, Radcliffe Institute for Advanced Study at Harvard University, Center for American Political Studies at Harvard University, Institutional Development Initiative at Harvard University, and Harvard University Library. Additional non-petition or unrelated documents available at archive: additional documents available Additional archivist notes: James Burr, son, invalid, maintenance, assistance, Indian guardians, Ponkapoag tribe Location of the petition at the Massachusetts Archives of the Commonwealth: Resolves 1862, c.34, passed March 27, 1862