| ArcGIS REST Services Directory |
| Home > services > Map2 (FeatureServer) > All Layers and Tables | | API Reference |
This statewide dataset contains a combination of land cover mapping from 2016 aerial imagery and land use derived from standardized assessor parcel information for Massachusetts.
Each location in this layer is associated with a land cover class value as well as a parcel use code
Although both land cover and land use information are included, each of these aspects can be accessed independently, or in interesting and useful combinations with one another. For instance, a user can simply display impervious surfaces (land cover), or commercial parcels (land use). In combination, it is possible to display and measure the portions of the commercial parcels that are covered by impervious surfaces or the portions of residential parcels used as developed open space.
This layer is the result of a cooperative project between MassGIS and the National Oceanic and Atmospheric Administration’s (NOAA) Office of Coastal Management (OCM). Funding was provided by the Mass. Executive Office of Energy and Environmental Affairs.
MassGIS stores the data as a single statewide polygon feature class named LANDCOVER_LANDUSE_POLYin the spatial reference of NAD_1983_Contiguous_USA_Albers (EPSG: 5070).
Data development
The following sections describe the development and features of the two components, land cover and land use, as well as the final combined dataset.
Land cover
The thematic land cover dataset was created in raster format by NOAA's Coastal Change Analysis Program (C-CAP). C-CAP has produced numerous standardized land cover products which are included in the National Land Cover Database. These products are used in numerous ways to assess urban growth, inventory wetlands, coastal intertidal areas, and adjacent uplands, and delineate wildlife habitat to monitor changes in these areas. This information helps in the understanding of the landscape's response to natural and human-caused changes. OCM worked in close coordination with MassGIS to produce the land cover. OCM delivered the data to MassGIS in an Albers projection.
2016 NAIP imagery This 2016 land cover information was initially developed as a 1-meter, 6-category draft raster derived from 2016 USDA National Agricultural Imagery Program (NAIP) aerial multispectral imagery. Classes were impervious, bare, grass, shrub, tree, and water. Additional reference data were used to create this 19-class version, including: 2016 WorldView multispectral satellite imagery, lidar-based terrain elevation data, 2016-era 2D structures data, and other ancillary data such as MassDOT Roads, MassDEP Wetlands, etc. The wetlands in the final land cover product are exclusively from the C-CAP program and will differ from the MassDEP Wetlands data.
The land cover information in this product is consistent with C-CAP’s High-Resolution Land Cover Classification Scheme (PDF). Also see General information about C-CAP High-Resolution Land Cover.
Land use
The land use component of the data layer is represented by the Property Type Classification Code associated with each parcel in MassGIS' Standardized "Level 3" Parcels layer. These "use codes" come from the Mass. Department of Revenue Division of Local Services (DLS), along with custom use codes some municipalities include in their parcel data.
For this project, MassGIS created a parcel layer using data deliverables as close as possible to the time of the 2016 NAIP imagery used for the land cover. Since parcel data complying with Level 3 of the MassGIS standard was not available from every municipality for the year 2016, some information was selected from a different year to use data as close to 2016 as possible, with the following rules:
If Fiscal Year (FY) 2016 data was available, it was used. Otherwise, data was used from other years in the following order: 2017 (+1), 2015 (-1), 2018 (+2), 2014 (-2), 2013 (-3), 2012 (-4), 2011 (-5). Fiscal year values were retained in the final product to help indicate relative reliability of the USECODE.
MassGIS merged these parcel data into one feature class and dissolved them based on these fields:
USE_CODE: Use code from DOR DLS, along with custom use codes some municipalities include in their parcel data.
FY: Fiscal year
POLY_TYPE: Parcel type (FEE, TAX, ROW, WATER, PRIV_ROW, RAIL_ROW)
TOWN_ID: Town ID (1-351)
GEN_CODE: Generalized use code chosen by MassGIS for this project to simplify the 1,600+ USE_CODEs for map display.
Combined Land Cover – Land Use Data
For efficient processing and distribution, MassGIS split up the statewide land cover raster into 291 smaller, regularly sized and spaced tiles, each 10km by 10km (10,000 x 10,000 pixels).
The Create Fishnet tool produced a polygon index that precisely fit the tiles. The tiles were identified with a TILENAME value based on row and column position. For example, TILENAME “R07C17” identifies the tile in row 7, column 17. The index is named LANDCOVER_USE_INDEX_POLY. Aside from TILENAME, the other field is SHP_LINK, which stores a link to download a zipped land cover-land use shapefile for each tile.
Each land cover image was converted to a polygon shapefile using a Raster to Shapefile model in ERDAS IMAGINE. This method preserves the thematic attributes and simplifies the polygons very slightly.
MassGIS carried out the following steps in ArcGIS 10.6.1:
Reprojected the land use polygons from Massachusetts State Plane to the same Albers projection of the land cover.
Used the Identity tool to geometrically combine the land cover polygons with the dissolved parcel data to produce a land cover-land use feature class for each tile.
Checked and repaired the geometry of the Identity output.
Converted all multipart polygons to single-part polygons in the Identity output.
The Identity created numerous very small polygons because the two components (land cover and land use) were not spatially correlated. To preserve the input data, MassGIS decided not to eliminate polygons or perform any other cartographic refinement at this point. Users can easily perform these operations if desired.
As part of final QA, MassGIS modified the attributes of a small number of polygons with erroneous land cover or generalized land use codes, including a few right-of-way polygons in Boston that did not have the correct USEGENCODE of 55.
The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.
This layer is the official state-maintained street transportation dataset available from MassGIS and represents all the public and a good portion of the private roadways in Massachusetts, including designations for Interstate, U.S. and State highways. Formerly known as the Massachusetts Highway Department (MHD) Roads, then the Executive Office of Transportation - Office of Transportation Planning (EOT-OTP) Roads, The MassDOT roads layer includes linework from the 1:5,000 road and rail centerlines data that were interpreted as part of the Black and White Digital Orthophoto project. The Massachusetts Department of Transportation - Office of Transportation Planning, which maintains this layer, continues to add linework from municipal and other sources and update existing linework using the most recent color orthophoto imagery as a base. In addition to the new linework, the attribute table includes all "road inventory" items maintained in MassDOT's linear referencing system.
The layer is up-to-date through December 31, 2013.
In ArcSDE this layer is named EOTROADS_ARC.