<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN STYLE="font-weight:bold;">1970</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using US Department of Commerce, Bureau of the Census data, developed the digital 1970 Census Boundaries/Population data file containing easily accessible population and housing counts for the state of North Carolina.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">1980</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using US Department of Commerce, Bureau of the Census data, developed the GIS data set, 1980 Census Boundaries/Population,  containing easily accessible population and housing counts for the state of North Carolina.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">1990</SPAN><SPAN>:  Census block and block group. TIGER/Line feature classes can be used to join demographic data from the 1990 census for use in a GIS.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">2000</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using TIGER/line  2000 files and statistics from the US Department of Commerce/Bureau of the Census, developed the GIS 2000 Census Tract, Block Group, and Block data sets for each of the 100 counties in North Carolina and combined the data into one  statewide coverage.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">2010</SPAN><SPAN>:  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.  Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads.  Census blocks are relatively small in area; for example, a block in a city bounded by streets.  However, census blocks in remote areas are often large and irregular and may even be many square miles in area.  A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks.  As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas.  Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands).  Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census.  A block may consist of one or more faces.    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.    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.  Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program.  The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate.  The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses.  Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people.  When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions.  The spatial size of census tracts varies widely depending on the density of settlement.  Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions.  In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline.  Census tract boundaries generally follow visible and identifiable features.  They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses.  State and county boundaries always are census tract boundaries in the standard census geographic hierarchy.  In a few rare instances, a census tract may consist of noncontiguous areas.  These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.  For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.    Census Urban Areas:  The Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the "urban footprint." There are two types of urban areas: urbanized areas (UAs) that contain 50,000 or more people and urban clusters (UCs) that contain at least 2,500 people, but fewer than 50,000 people (except in the U.S. Virgin Islands and Guam which each contain urban clusters with populations greater than 50,000). Each urban area is identified by a 5-character numeric census code that may contain leading zeroes.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN STYLE="font-weight:bold;">1970</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using US Department of Commerce, Bureau of the Census data, developed the digital 1970 Census Boundaries/Population data file containing easily accessible population and housing counts for the state of North Carolina.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">1980</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using US Department of Commerce, Bureau of the Census data, developed the GIS data set, 1980 Census Boundaries/Population,  containing easily accessible population and housing counts for the state of North Carolina.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">1990</SPAN><SPAN>:  Census block and block group. TIGER/Line feature classes can be used to join demographic data from the 1990 census for use in a GIS.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">2000</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using TIGER/line  2000 files and statistics from the US Department of Commerce/Bureau of the Census, developed the GIS 2000 Census Tract, Block Group, and Block data sets for each of the 100 counties in North Carolina and combined the data into one  statewide coverage.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">2010</SPAN><SPAN>:  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.  Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads.  Census blocks are relatively small in area; for example, a block in a city bounded by streets.  However, census blocks in remote areas are often large and irregular and may even be many square miles in area.  A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks.  As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas.  Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands).  Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census.  A block may consist of one or more faces.    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.    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.  Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program.  The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate.  The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses.  Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people.  When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions.  The spatial size of census tracts varies widely depending on the density of settlement.  Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions.  In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline.  Census tract boundaries generally follow visible and identifiable features.  They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses.  State and county boundaries always are census tract boundaries in the standard census geographic hierarchy.  In a few rare instances, a census tract may consist of noncontiguous areas.  These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.  For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.    Census Urban Areas:  The Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the "urban footprint." There are two types of urban areas: urbanized areas (UAs) that contain 50,000 or more people and urban clusters (UCs) that contain at least 2,500 people, but fewer than 50,000 people (except in the U.S. Virgin Islands and Guam which each contain urban clusters with populations greater than 50,000). Each urban area is identified by a 5-character numeric census code that may contain leading zeroes.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
[]
{'Title': 'NC1Map_Census', 'Author': '', 'Comments': '<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN STYLE="font-weight:bold;">1970</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using US Department of Commerce, Bureau of the Census data, developed the digital 1970 Census Boundaries/Population data file containing easily accessible population and housing counts for the state of North Carolina.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">1980</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using US Department of Commerce, Bureau of the Census data, developed the GIS data set, 1980 Census Boundaries/Population,  containing easily accessible population and housing counts for the state of North Carolina.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">1990</SPAN><SPAN>:  Census block and block group. TIGER/Line feature classes can be used to join demographic data from the 1990 census for use in a GIS.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">2000</SPAN><SPAN>:  The NC Center for Geographic Information and Analysis, using TIGER/line  2000 files and statistics from the US Department of Commerce/Bureau of the Census, developed the GIS 2000 Census Tract, Block Group, and Block data sets for each of the 100 counties in North Carolina and combined the data into one  statewide coverage.    </SPAN></P><P><SPAN STYLE="font-weight:bold;">2010</SPAN><SPAN>:  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.  Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads.  Census blocks are relatively small in area; for example, a block in a city bounded by streets.  However, census blocks in remote areas are often large and irregular and may even be many square miles in area.  A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks.  As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas.  Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands).  Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census.  A block may consist of one or more faces.    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.    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.  Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program.  The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate.  The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses.  Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people.  When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions.  The spatial size of census tracts varies widely depending on the density of settlement.  Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions.  In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline.  Census tract boundaries generally follow visible and identifiable features.  They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses.  State and county boundaries always are census tract boundaries in the standard census geographic hierarchy.  In a few rare instances, a census tract may consist of noncontiguous areas.  These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.  For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.    Census Urban Areas:  The Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the "urban footprint." There are two types of urban areas: urbanized areas (UAs) that contain 50,000 or more people and urban clusters (UCs) that contain at least 2,500 people, but fewer than 50,000 people (except in the U.S. Virgin Islands and Guam which each contain urban clusters with populations greater than 50,000). Each urban area is identified by a 5-character numeric census code that may contain leading zeroes.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>', 'Subject': 'This map displays various census related data: population and housing (1970, 1980); Blocks, Block Groups and Tracts (1990, 2000, and 2010).', 'Category': '', 'AntialiasingMode': 'Fast', 'TextAntialiasingMode': 'Force', 'Version': '2.9.0', 'Keywords': 'NC,North Carolina,Department of Information Technology,DIT,Center for Geographic Information and Analysis,CGIA,NC OneMap,OneMap,census,block,block group,tract,population,housing,boundaries,society'}
[{'geoTransforms': [{'wkid': 108001, 'latestWkid': 1241, 'transformForward': True, 'name': 'NAD_1927_To_NAD_1983_NADCON'}]}, {'geoTransforms': [{'wkid': 108001, 'latestWkid': 1241, 'transformForward': False, 'name': 'NAD_1927_To_NAD_1983_NADCON'}]}]
nan