The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The State Geodatabase for Indiana geodatabase contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census
        Tract, Consolidated City, County, County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. The BG boundaries in this release are
        those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        An incorporated place, or census designated place, is established to provide governmental functions for a concentration of people as opposed to a
        minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places
        always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village,
        or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated
        places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally
        incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local,
        and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP
        boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in
        an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some
        housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census
        Bureau's Boundary and Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also
        included. The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010
        Census.

        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. 

         A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have
        merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the
        county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other
        incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated
        government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places
        within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any
        other place. The boundaries of the consolidated cities are those as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey(BAS).

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of

The latest version of the geodatabase template is available here.The Infrastructure for Spatial Information in Europe (INSPIRE) is a directive passed by the European Commission, the executive body of the EU, to establish a European-wide spatial data infrastructure (SDI). An essential element of INSPIRE is the data model specification that provides a uniform way to view and download geographic datasets shared in the INSPIRE network by European Member States.The ArcGIS for INSPIRE Enterprise Geodatabase (GDB) templates implement the INSPIRE data models. The geodatabase templates implement the following themes.INSPIRE Annex ICoordinate reference systemsGeographical grid systemsGeographical names Administrative units Addresses Cadastral parcels Transport networks Hydrography Protected sitesINSPIRE Annex IILand CoverGeology (Geology application schema)INSPIRE Annex IIILand useMineral ResourcesStatistical units

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The 2015 State Geodatabase for Kentucky contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census Tract,
        Consolidated City, County, County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. The BG boundaries in this release are
        those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        An incorporated place, or census designated place, is established to provide governmental functions for a concentration of people as opposed to a
        minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places
        always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village,
        or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated
        places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally
        incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local,
        and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP
        boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in
        an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some
        housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census
        Bureau's Boundary and Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also
        included. The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010
        Census.

        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. 

         A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have
        merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the
        county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other
        incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated
        government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places
        within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any
        other place. The boundaries of the consolidated cities are those as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey(BAS).

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The State Geodatabase for Connecticut geodatabase contains multiple layers. These layers are the Block, Block Group, Census Designated Place,
        Census Tract, Consolidated City, County, County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. The BG boundaries in this release are
        those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        An incorporated place, or census designated place, is established to provide governmental functions for a concentration of people as opposed to a
        minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places
        always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village,
        or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated
        places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally
        incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local,
        and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP
        boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in
        an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some
        housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census
        Bureau's Boundary and Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also
        included. The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010
        Census.

        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. 

         A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have
        merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the
        county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other
        incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated
        government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places
        within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any
        other place. The boundaries of the consolidated cities are those as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey(BAS).

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of

This dataset was created to monitor the status, condition and trend of national BLM resources in accordance with BLM policies. It focuses on the BLM terrestrial core indicators, which include measures of vegetation and soil condition such as plant species cover and composition, plant height, and soil stability. The BLM terrestrial core indicators and methods were identified through a multi-disciplinary process and are described in BLM Technical Note 440 (https://ia800701.us.archive.org/6/items/blmcoreterrestri00mack/BlmCoreTerrestrialIndicatorsAndMethods_88072539.pdf). The Landscape Monitoring Framework (LMF) dataset was collect using the Natural Resource Conservation Services (NRCS) National Resource Inventory (NRI) methodology which mirrors the data collected by the BLM using the Monitoring Manual for Grassland, Shrubland, and Savannah Ecosystems (2nd edition; https://www.landscapetoolbox.org/methods-manuals/monitoring-manual-2nd-edition/). Specific instructions for data collectors each year the data were collected can be found at https://grazingland.cssm.iastate.edu/. Also see Interpreting Indicators of Rangeland Health (version 5; https://www.landscapetoolbox.org/manuals/iirhv5/).The monitoring locations were selected using spatially balanced, random sampling approaches and thus provide an unbiased representation of land conditions. However, these data should not be used for statistical or spatial inferences without knowledge of how the sample design was drawn or without calculating spatial weights for the points based on the sample design.General DefinitionsNoxious: Noxious status and growth form (forb, shrub, etc.) are designated for each BLM Administrative State using the state noxious list and local botany expertise often after consulting the USDA plants database. Each state’s noxious list can be found in tblStateSpecies Table, where the Noxious field is ‘YES’ and the StateSpecies field has the two letter state code for the desired state (e.g. ‘NM’).Non-Noxious: Non-Noxious status and growth form (forb, shrub, etc.) are designated for each BLM Administrative State using the state noxious list and local botany expertise often after consulting the USDA plants database. Non-Noxious status can be found in tblStateSpecies Table, where the Noxious field is ‘NO’ and the StateSpecies field has the two letter state code for the desired state (e.g. ‘NM’).Sagebrush: Sagebrush species are designated for each BLM Administrative State using local botany expertise. This list can be found for each state in in the tblStateSpecies Table, where SG_Group field is ‘Sagebrush’ and the StateSpecies field has the two letter state code for the desired state (e.g. ‘NM’).Non-Sagebrush Shrub: Non Sagebrush Shrub species are designated for each BLM Administrative State as the plants determined to be shrubs that are not also Sagebrush. This list can be found for each state in in the tblStateSpecies Table, where SG_Group field is ‘NonSagebrushShrub’ and the StateSpecies field has the two letter state code for the desired state (e.g. ‘NM’).Tall Stature Perennial Grass: Tall Stature Perennial Grasses status was determined by Sage Grouse biologist and modified slightly in each state and this list can be found in tblStateSpecies in the SG_Group field where SG_Group field is ‘TallStaturePerennialGrass’ and the StateSpecies field has the two letter state code for the desired state (e.g. ‘NM’).Short Stature Perennial Grass: Short Stature Perennial Grasses status was determined by Sage Grouse biologist and modified slightly in each state and this list can be found in tblStateSpecies in the SG_Group field where SG_Group field is ‘ShortStaturePerennialGrass’ and the StateSpecies field has the two letter state code for the desired state (e.g. ‘NM’).Preferred Forb: Preferred forb for Sage Grouse status was determined for each state by Sage Grouse biologist and other local experts and this list can be found in tblStateSpecies in the SG_Group field where SG_Group field is ‘PreferredForb’ and the StateSpecies field has the two letter state code for the desired state (e.g. ‘NM’).Live: The NRI Methods measure Live vs Dead plant cover – i.e. if a pin drop hits a plant part and that plant part is dead (even if it’s on a living plant) that hit is considered a dead hit. Any occurrence of Live Sagebrush calculations indicates that the measurement is only hits that were live plant parts. If a pin hits both a live and a dead plant part in the same pin drop – that hit is considered live.Growth Habit: The form of a plant, in this dataset the options are Forb, Graminoid, Sedge, Succulent, Shrub, SubShrub, Tree, NonVascular. The most common growth habit for each state was determined by local botany expertise often after consulting the USDA plants database. The growth habit for each species is a state can be found in tblStateSpecies in the GrowthHabitSub field. The values are used to place each plant in a Growth Habit/Duration bin such as Perennial Grass, or Annual Forb, etc.Duration: The life length of a plant. In this dataset we consider plants to be either Perennial or Annual – Biennial plants are classified as Annuals. The most common duration for each state was determined by local botany expertise often after consulting the USDA plants database. The duration for each species is a state can be found in tblStateSpecies in the Duration field. The values are used to place each plant in a Growth Habit/Duration bin such as Perennial Grass, or Annual Forb, etc.tblStateSpecies: This table in the database contains the Species Lists for each state. In the instance where a species code does not have a Growth Habit, Growth Habit Sub, or Duration – any occurrence of that code will not be included in calculations that require that information – for example a code that has NonWoody Forb but no information about annual or perennial will not be included in any of the calculations that are perennial or annual forb calculations. Most codes with no information will have the following in the notes – indicating that the only calculation it will be included in is Total Foliar which doesn’t require any growth habit and duration information – “Not used for calculations except Total Foliar.”

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esri’s ArcGIS.

        The 2015 State Geodatabase for Tennessee contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census Tract,
        Consolidated City, County, County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. The BG boundaries in this release are
        those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        An incorporated place, or census designated place, is established to provide governmental functions for a concentration of people as opposed to a
        minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places
        always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village,
        or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated
        places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally
        incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local,
        and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP
        boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in
        an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some
        housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census
        Bureau's Boundary and Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also
        included. The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010
        Census.

        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. 

         A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have
        merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the
        county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other
        incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated
        government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places
        within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any
        other place. The boundaries of the consolidated cities are those as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey(BAS).

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and

The Rare Plant Occurrences geodatabase is an element occurrence data system with about 10,000 records of rare plant observations on the 6 northernmost California Channel Islands. It is a live database created with the purpose of bringing together in one space all discoverable historic and current information on the localities of about 180 rare and sensitive plants of the northern Channel Islands, California. The list of taxa was developed from agency databases, supplemented with a 1-day workshop with area botanists in 1993; the list has been updated as new information emerges. Data records range from the late 1880s to 2019, including information from herbarium labels, published and unpublished literature, agency files, botanist field notes, incidental observations and results of targeted surveys for individual taxa. The data come from authoritative sources, but the records are of varying quality, related to the nature of the original observation. Consequently, each record contains metadata about the data source and accuracy, as well as the observation itself. The database was initiated in 1994, by Kathryn McEachern, U.S. Geological Survey (USGS) Research Ecologist, and collaborators at Channel Islands National Park and the Santa Barbara Botanic Garden. It is maintained at the co-located offices of the USGS, Western Ecological Research Center, Channel Islands Field Station and Channel Islands National Park in Ventura, California.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The 2015 State Geodatabase for Kansas contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census Tract,
        Consolidated City, County, County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. The BG boundaries in this release are
        those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        An incorporated place, or census designated place, is established to provide governmental functions for a concentration of people as opposed to a
        minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places
        always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village,
        or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated
        places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally
        incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local,
        and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP
        boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in
        an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some
        housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census
        Bureau's Boundary and Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also
        included. The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010
        Census.

        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. 

         A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have
        merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the
        county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other
        incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated
        government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places
        within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any
        other place. The boundaries of the consolidated cities are those as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey(BAS).

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

In 1986, parcel polygons [PARPOLY] were digitized from hand drawn 1:2400 half and 1:1200 quarter section maps. In 1995, the parcel data layer was converted to an ArcINFO format and held in an ArcStorm database. Parcel polygons were converted in 2005 to an ESRI ArcGIS SDE GeoDatabase; the name was changed to Parcel Components. In 2014, Ramsey County migrated to ESRI's Parcel Fabric; Conveyance Divisions were created from the Parcel Components.

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The 2015 State Geodatabase for Virginia contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census Tract,
        County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. The BG boundaries in this release
        are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        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. 

        An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD),
        which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state,
        but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have
        other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated
        to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state
        in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide
        with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial
        census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily
        have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. 

        The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also included. The boundaries
        of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include
        legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census,
        the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs
        for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical
        unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county
        subdivisions. The boundaries of most legal MCDs are as of January 1, 2013, as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). The boundaries of all CCDs, delineated in 21 states, are those as reported as part of the Census Bureau's Participant Statistical Areas
        Program (PSAP) for the 2010 Census.

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The 2015 State Geodatabase for New Jersey contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census Tract,
        County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. 

        The BG boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the
        2010 Census. 

        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. 

        An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD),
        which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state,
        but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have
        other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated
        to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state
        in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide
        with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial
        census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily
        have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. 

        The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also included. The boundaries
        of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. 

        The boundaries for counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include
        legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census,
        the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs
        for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical
        unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county
        subdivisions. The boundaries of most legal MCDs are as of January 1, 2013, as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). 

        The boundaries of all CCDs, delineated in 21 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program
        (PSAP) for the 2010 Census.

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esri’s ArcGIS.

        The 2015 State Geodatabase for New Hampshire contains multiple layers. These layers are the Block, Block Group, Census Designated Place,
        Census Tract, County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. 

        The BG boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the
        2010 Census. 

        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. 

        An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD),
        which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state,
        but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have
        other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated
        to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state
        in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide
        with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial
        census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily
        have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. 

        The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also included. The boundaries
        of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. 

        The boundaries for counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include
        legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census,
        the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs
        for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical
        unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county
        subdivisions. The boundaries of most legal MCDs are as of January 1, 2013, as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). 

        The boundaries of all CCDs, delineated in 21 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program
        (PSAP) for the 2010 Census.

Abstract

This data set holds the publicly-available version of the database of water-dependent assets that was compiled for the bioregional assessment (BA) of the Galilee subregion as part of the Bioregional Assessment Technical Programme. Though all life is dependent on water, for the purposes of a bioregional assessment, a water-dependent asset is an asset potentially impacted by changes in the groundwater and/or surface water regime due to coal resource development. The water must be other than local rainfall. Examples include wetlands, rivers, bores and groundwater dependent ecosystems.

The dataset was derived by the Bioregional Assessment Programme. This dataset was derived from multiple datasets including Natural Resource Management regions, and Australian and state and territory government databases. You can find a link to the parent datasets in the Lineage Field in this metadata statement. The History Field in this metadata statement describes how this dataset was derived. A single asset is represented spatially in the asset database by single or multiple spatial features (point, line or polygon). Individual points, lines or polygons are termed elements.

This dataset contains the unrestricted publicly-available components of spatial and non-spatial (attribute) data of the (restricted) Asset database for the Galilee subregion on 04 January 2016 (12ff5782-a3d9-40e8-987c-520d5fa366dd);. The database is provided primarily as an ESRI File geodatabase (.gdb), which is able to be opened in readily available open source software such as QGIS. Other formats include the Microsoft Access database (.mdb in ESRI Personal Geodatabase format), industry-standard ESRI Shapefiles and tab-delimited text files of all the attribute tables.

The restricted version of the Galilee Asset database has a total count of 403 918 Elements and 4 426 Assets. In the public version of the Asset GalileeGalilee database 13759 spatial Element features (~3%) have been removed from the Element List and Element Layer(s) and 352 spatial Assets (~8%) have been removed from the spatial Asset Layer(s)

The elements/assets removed from the restricted Asset Database are from the following data sources:

1) Environmental Asset Database - Commonwealth Environmental Water Office - RESTRICTED (Metadata only) (29fd1654-8aa1-4cb3-b65e-0b37698ac9a6)

2) Key Environmental Assets - KEA - of the Murray Darling Basin RESTRICTED (Metadata only) (9948195e-3d3b-49dc-96d2-ea7765297308)

3) Species Profile and Threats Database (SPRAT) - RESTRICTED - Metadata only) (7276dd93-cc8c-4c01-8df0-cef743c72112)

4) Australia, Register of the National Estate (RNE) - Spatial Database (RNESDB) (Internal 878f6780-be97-469b-8517-54bd12a407d0)

5) Communities of National Environmental Significance Database - RESTRICTED - Metadata only (c01c4693-0a51-4dbc-bbbd-7a07952aa5f6)

These important assets are included in the bioregional assessment, but are unable to be publicly distributed by the Bioregional Assessment Programme due to restrictions in their licensing conditions. Please note that many of these data sets are available directly from their custodian. For more precise details please see the associated explanatory Data Dictionary document enclosed with this dataset.

Dataset History

The public version of the asset database retains all of the unrestricted components of the Asset database for the Galilee subregion on 04 January 2016 - any material that is unable to be published or redistributed to a third party by the BA Programme has been removed from the database. The data presented corresponds to the assets published Cooper subregion product 1.3: Description of the water-dependent asset register and asset list for the Galilee subregion on 04 January 2016, and the associated Water-dependent asset register and asset list for the Galilee subregion on 04 January 2016.

Individual spatial features or elements are initially included in database if they are partly or wholly within the subregion's preliminary assessment extent (Materiality Test 1, M1). In accordance to BA submethodology M02: Compiling water-dependent assets, individual spatial elements are then grouped into assets which are evaluated by project teams to determine whether they meet materiality test 2 (M2), which are assets that are considered to be water dependent.

Following delivery of the first pass asset list, project teams make a determination as to whether an asset (comprised of one or more elements) is water dependent, as assessed against the materiality tests detailed in the BA Methodology. These decisions are provided to ERIN by the assessment team and incorporated into the AssetList table in the Asset database.

Development of the Asset Register from the Asset database:

Decisions for M0 (fit for BA purpose), M1 (PAE) and M2 (water dependent) determine which assets are included in the "asset list" and "water-dependent asset register" which are published as Product 1.3.

The rule sets are applied as follows:

M0 M1 M2 Result

No n/a n/a Asset is not included in the asset list or the water-dependent asset register

(≠ No) No n/a Asset is not included in the asset list or the water-dependent asset register

(≠ No) Yes No Asset included in published asset list but not in water dependent asset register

(≠ No) Yes Yes Asset included in both asset list and water-dependent asset register

Assessment teams are then able to use the database to assign receptors and impact variables to water-dependent assets and the development of a receptor register as detailed in BA submethodology M03: Assigning receptors to water-dependent assets and the receptor register is then incorporated into the asset database.

At this stage of its development, the for the Galilee subregion on 04 January 2016, which this document describes, does not contain any receptor information.

Dataset Citation

Bioregional Assessment Programme (2013) Asset database for the Galilee subregion on 04 January 2016 Public. Bioregional Assessment Derived Dataset. Viewed 10 December 2018, http://data.bioregionalassessments.gov.au/dataset/eb4cf797-9b8f-4dff-9d7a-a5dfbc8d2bed.

Dataset Ancestors

• Derived From QLD Dept of Natural Resources and Mines, Groundwater Entitlements 20131204

• Derived From Queensland QLD - Regional - NRM - Water Asset Information Tool - WAIT - databases

• Derived From Matters of State environmental significance (version 4.1), Queensland

• Derived From Communities of National Environmental Significance Database - RESTRICTED - Metadata only

• Derived From South Australia SA - Regional - NRM Board - Water Asset Information Tool - WAIT - databases

• Derived From National Groundwater Dependent Ecosystems (GDE) Atlas

• Derived From National Groundwater Information System (NGIS) v1.1

• Derived From Birds Australia - Important Bird Areas (IBA) 2009

• Derived From Queensland QLD Regional CMA Water Asset Information WAIT tool databases RESTRICTED Includes ALL Reports

• Derived From Asset database for the Galilee subregion on 04 January 2016

• Derived From Environmental Asset Database - Commonwealth Environmental Water Office

• Derived From National Groundwater Dependent Ecosystems (GDE) Atlas (including WA)

• Derived From QLD Dept of Natural Resources and Mines, Groundwater Entitlements linked to bores v3 03122014

• Derived From Species Profile and Threats Database (SPRAT) - Australia - Species of National Environmental Significance Database (BA subset - RESTRICTED - Metadata only)

• Derived From QLD Dept of Natural Resources and Mines, Surface Water Entitlements 131204

• Derived From Ramsar Wetlands of Australia

• Derived From Permanent and Semi-Permanent Waterbodies of the Lake Eyre Basin (Queensland and South Australia) (DRAFT)

• Derived From Asset database for the Galilee subregion on 2 December 2014

• Derived From Key Environmental Assets - KEA - of the Murray Darling Basin

• Derived From QLD Dept of Natural Resources and Mines, Groundwater Entitlements linked to bores and NGIS v4 28072014

• Derived From National Heritage List Spatial Database (NHL) (v2.1)

• Derived From Great Artesian Basin and Laura Basin groundwater recharge areas

• Derived From [QLD DNRM Licence Locations

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esri’s ArcGIS.

        The 2015 State Geodatabase for Missouri contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census Tract,
        County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. 

        The BG boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the
        2010 Census. 

        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. 

        An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD),
        which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state,
        but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have
        other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated
        to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state
        in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide
        with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial
        census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily
        have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. 

        The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also included. The boundaries
        of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. 

        The boundaries for counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include
        legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census,
        the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs
        for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical
        unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county
        subdivisions. The boundaries of most legal MCDs are as of January 1, 2013, as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). 

        The boundaries of all CCDs, delineated in 21 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program
        (PSAP) for the 2010 Census.

Abstract

The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

This database is an initial Asset database for the Central West subregion on 29 April 2015. This dataset contains the spatial and non-spatial (attribute) components of the Central West subregion Asset List as one .mdb files, which is readable as an MS Access database and a personal geodatabase. Under the BA program, a spatial assets database is developed for each defined bioregional assessment project. The spatial elements that underpin the identification of water dependent assets are identified in the first instance by regional NRM organisations (via the WAIT tool) and supplemented with additional elements from national and state/territory government datasets. All reports received associated with the WAIT process for Central West are included in the zip file as part of this dataset. Elements are initially included in the preliminary assets database if they are partly or wholly within the subregion's preliminary assessment extent (Materiality Test 1, M1). Elements are then grouped into assets which are evaluated by project teams to determine whether they meet the second Materiality Test (M2). Assets meeting both Materiality Tests comprise the water dependent asset list. Descriptions of the assets identified in the Central West subregion are found in the "AssetList" table of the database. In this version of the database only M1 has been assessed. Assets are the spatial features used by project teams to model scenarios under the BA program. Detailed attribution does not exist at the asset level. Asset attribution includes only the core set of BA-derived attributes reflecting the BA classification hierarchy, as described in Appendix A of "CEN_asset_database_doc_20150429.doc ", located in the zip file as part of this dataset. The "Element_to_Asset" table contains the relationships and identifies the elements that were grouped to create each asset. Detailed information describing the database structure and content can be found in the document "CEN_asset_database_doc_20150429.doc" located in the zip file. Some of the source data used in the compilation of this dataset is restricted.

Dataset History

This is initial asset database.

The Bioregional Assessments methodology (Barrett et al., 2013) defines a water-dependent asset as a spatially distinct, geo-referenced entity contained within a bioregion with characteristics having a defined cultural indigenous, economic or environmental value, and that can be linked directly or indirectly to a dependency on water quantity and/or quality.

Under the BA program, a spatial assets database is developed for each defined bioregional assessment project. The spatial elements that underpin the identification of water dependent assets are identified in the first instance by regional NRM organisations (via the WAIT tool) and supplemented with additional elements from national and state/territory government datasets. Elements are initially included in database if they are partly or wholly within the subregion's preliminary assessment extent (Materiality Test 1, M1). Elements are then grouped into assets which are evaluated by project teams to determine whether they meet materiality test 2 (M2) - assets considered to be water dependent.

Elements may be represented by a single, discrete spatial unit (polygon, line or point), or a number of spatial units occurring at more than one location (multipart polygons/lines or multipoints). Spatial features representing elements are not clipped to the preliminary assessment extent - features that extend beyond the boundary of the assessment extent have been included in full. To assist with an assessment of the relative importance of elements, area statements have been included as an attribute of the spatial data. Detailed attribute tables contain descriptions of the geographic features at the element level. Tables are organised by data source and can be joined to the spatial data on the "ElementID" field

Elements are grouped into Assets, which are the objects used by project teams to model scenarios under the BA program. Detailed attribution does not exist at the asset level. Asset attribution includes only the core set of BA-derived attributes reflecting the BA classification hierarchy.

The "Element_to_asset" table contains the relationships and identifies the elements that were grouped to create each asset.

Following delivery of the first pass asset list, project teams make a determination as to whether an asset (comprised of one or more elements) is water dependent, as assessed against the materiality tests detailed in the BA Methodology. These decisions are provided to ERIN by the project team leader and incorporated into the Assetlist table in the Asset database. The Asset database is then re-registered into the BA repository.

The Asset database dataset (which is registered to the BA repository) contains separate spatial and non-spatial databases.

Non-spatial (tabular data) is provided in an ESRI personal geodatabase (.mdb - doubling as a MS Access database) to store, query, and manage non-spatial data. This database can be accessed using either MS Access or ESRI GIS products. Non-spatial data has been provided in the Access database to simplify the querying process for BA project teams. Source datasets are highly variable and have different attributes, so separate tables are maintained in the Access database to enable the querying of thematic source layers.

Spatial data is provided as an ESRI file geodatabase (.gdb), and can only be used in an ESRI GIS environment. Spatial data is represented as a series of spatial feature classes (point, line and polygon layers). Non-spatial attribution can be joined from the Access database using the AID and ElementID fields, which are common to both the spatial and non-spatial datasets. Spatial layers containing all the point, line and polygon - derived elements and assets have been created to simplify management of the Elementlist and Assetlist tables, which list all the elements and assets, regardless of the spatial data geometry type. i.e. the total number of features in the combined spatial layers (points, lines, polygons) for assets (and elements) is equal to the total number of non-spatial records of all the individual data sources.

Dataset Citation

Department of the Environment (2013) Asset database for the Central West subregion on 29 April 2015. Bioregional Assessment Derived Dataset. Viewed 08 February 2017, http://data.bioregionalassessments.gov.au/dataset/5c3f9a56-7a48-4c26-a617-a186c2de5bf7.

Dataset Ancestors

• Derived From Macquarie Marshes Vegetation 1991-2008 VIS_ID 3920

• Derived From NSW Office of Water GW licence extract linked to spatial locations NIC v2 (28 February 2014)

• Derived From NSW Office of Water Surface Water Entitlements Locations v1_Oct2013

• Derived From Travelling Stock Route Conservation Values

• Derived From NSW Wetlands

• Derived From Communities of National Environmental Significance Database - RESTRICTED - Metadata only

• Derived From National Groundwater Dependent Ecosystems (GDE) Atlas

• Derived From Birds Australia - Important Bird Areas (IBA) 2009

• Derived From Environmental Asset Database - Commonwealth Environmental Water Office

• Derived From NSW Office of Water Surface Water Offtakes - NIC v1 20131024

• Derived From National Groundwater Dependent Ecosystems (GDE) Atlas (including WA)

• Derived From Species Profile and Threats Database (SPRAT) - Australia - Species of National Environmental Significance Database (BA subset - RESTRICTED - Metadata only)

• Derived From Ramsar Wetlands of Australia

• Derived From Native Vegetation Management (NVM) - Manage Benefits

• Derived From Key Environmental Assets - KEA - of the Murray Darling Basin

• Derived From National Heritage List Spatial Database (NHL) (v2.1)

• Derived From Climate Change Corridors (Dry Habitat) for North East NSW

• Derived From Great Artesian Basin and Laura Basin groundwater recharge areas

• Derived From NSW Office of Water combined geodatabase of regulated rivers and water sharing plan regions

• Derived From [New South Wales NSW Regional CMA Water Asset

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The 2015 State Geodatabase for Vermont contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census Tract,
        County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, 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. The BG boundaries in this release
        are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        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. 

        An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD),
        which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state,
        but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have
        other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated
        to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state
        in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide
        with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial
        census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily
        have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. 

        The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also included. The boundaries
        of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include
        legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census,
        the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs
        for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical
        unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county
        subdivisions. The boundaries of most legal MCDs are as of January 1, 2013, as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). The boundaries of all CCDs, delineated in 21 states, are those as reported as part of the Census Bureau's Participant Statistical Areas
        Program (PSAP) for the 2010 Census.

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public land and voluntarily provided private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastre Theme ( https://communities.geoplatform.gov/ngda-cadastre/ ). The PAD-US is an ongoing project with several published versions of a spatial database including areas dedicated to the preservation of biological diversity, and other natural (including extraction), recreational, or cultural uses, managed for these purposes through legal or other effective means. The database was originally designed to support biodiversity assessments; however, its scope expanded in recent years to include all open space public and nonprofit lands and waters. Most are public lands owned in fee (the owner of the property has full and irrevocable ownership of the land); however, permanent and long-term easements, leases, agreements, Congressional (e.g. 'Wilderness Area'), Executive (e.g. 'National Monument'), and administrative designations (e.g. 'Area of Critical Environmental Concern') documented in agency management plans are also included. The PAD-US strives to be a complete inventory of U.S. public land and other protected areas, compiling “best available” data provided by managing agencies and organizations. The PAD-US geodatabase maps and describes areas using thirty-six attributes and five separate feature classes representing the U.S. protected areas network: Fee (ownership parcels), Designation, Easement, Marine, Proclamation and Other Planning Boundaries. An additional Combined feature class includes the full PAD-US inventory to support data management, queries, web mapping services, and analyses. The Feature Class (FeatClass) field in the Combined layer allows users to extract data types as needed. A Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) facilitates the extraction of authoritative federal data provided or recommended by managing agencies from the Combined PAD-US inventory. This PAD-US Version 3.0 dataset includes a variety of updates from the previous Version 2.1 dataset (USGS, 2020, https://doi.org/10.5066/P92QM3NT ), achieving goals to: 1) Annually update and improve spatial data representing the federal estate for PAD-US applications; 2) Update state and local lands data as state data-steward and PAD-US Team resources allow; and 3) Automate data translation efforts to increase PAD-US update efficiency. The following list summarizes the integration of "best available" spatial data to ensure public lands and other protected areas from all jurisdictions are represented in the PAD-US (other data were transferred from PAD-US 2.1). Federal updates - The USGS remains committed to updating federal fee owned lands data and major designation changes in annual PAD-US updates, where authoritative data provided directly by managing agencies are available or alternative data sources are recommended. The following is a list of updates or revisions associated with the federal estate: 1) Major update of the Federal estate (fee ownership parcels, easement interest, and management designations where available), including authoritative data from 8 agencies: Bureau of Land Management (BLM), U.S. Census Bureau (Census Bureau), Department of Defense (DOD), U.S. Fish and Wildlife Service (FWS), National Park Service (NPS), Natural Resources Conservation Service (NRCS), U.S. Forest Service (USFS), and National Oceanic and Atmospheric Administration (NOAA). The federal theme in PAD-US is developed in close collaboration with the Federal Geographic Data Committee (FGDC) Federal Lands Working Group (FLWG, https://communities.geoplatform.gov/ngda-govunits/federal-lands-workgroup/ ). 2) Improved the representation (boundaries and attributes) of the National Park Service, U.S. Forest Service, Bureau of Land Management, and U.S. Fish and Wildlife Service lands, in collaboration with agency data-stewards, in response to feedback from the PAD-US Team and stakeholders. 3) Added a Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) to the PAD-US 3.0 geodatabase to facilitate the extraction (by Data Provider, Dataset Name, and/or Aggregator Source) of authoritative data provided directly (or recommended) by federal managing agencies from the full PAD-US inventory. A summary of the number of records (Frequency) and calculated GIS Acres (vs Documented Acres) associated with features provided by each Aggregator Source is included; however, the number of records may vary from source data as the "State Name" standard is applied to national files. The Feature Class (FeatClass) field in the table and geodatabase describe the data type to highlight overlapping features in the full inventory (e.g. Designation features often overlap Fee features) and to assist users in building queries for applications as needed. 4) Scripted the translation of the Department of Defense, Census Bureau, and Natural Resource Conservation Service source data into the PAD-US format to increase update efficiency. 5) Revised conservation measures (GAP Status Code, IUCN Category) to more accurately represent protected and conserved areas. For example, Fish and Wildlife Service (FWS) Waterfowl Production Area Wetland Easements changed from GAP Status Code 2 to 4 as spatial data currently represents the complete parcel (about 10.54 million acres primarily in North Dakota and South Dakota). Only aliquot parts of these parcels are documented under wetland easement (1.64 million acres). These acreages are provided by the U.S. Fish and Wildlife Service and are referenced in the PAD-US geodatabase Easement feature class 'Comments' field. State updates - The USGS is committed to building capacity in the state data-steward network and the PAD-US Team to increase the frequency of state land updates, as resources allow. The USGS supported efforts to significantly increase state inventory completeness with the integration of local parks data in the PAD-US 2.1, and developed a state-to-PAD-US data translation script during PAD-US 3.0 development to pilot in future updates. Additional efforts are in progress to support the technical and organizational strategies needed to increase the frequency of state updates. The PAD-US 3.0 included major updates to the following three states: 1) California - added or updated state, regional, local, and nonprofit lands data from the California Protected Areas Database (CPAD), managed by GreenInfo Network, and integrated conservation and recreation measure changes following review coordinated by the data-steward with state managing agencies. Developed a data translation Python script (see Process Step 2 Source Data Documentation) in collaboration with the data-steward to increase the accuracy and efficiency of future PAD-US updates from CPAD. 2) Virginia - added or updated state, local, and nonprofit protected areas data (and removed legacy data) from the Virginia Conservation Lands Database, provided by the Virginia Department of Conservation and Recreation's Natural Heritage Program, and integrated conservation and recreation measure changes following review by the data-steward. 3) West Virginia - added or updated state, local, and nonprofit protected areas data provided by the West Virginia University, GIS Technical Center. For more information regarding the PAD-US dataset please visit, https://www.usgs.gov/gapanalysis/PAD-US/. For more information about data aggregation please review the PAD-US Data Manual available at https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-manual . A version history of PAD-US updates is summarized below (See https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-history for more information): 1) First posted - April 2009 (Version 1.0 - available from the PAD-US: Team pad-us@usgs.gov). 2) Revised - May 2010 (Version 1.1 - available from the PAD-US: Team pad-us@usgs.gov). 3) Revised - April 2011 (Version 1.2 - available from the PAD-US: Team pad-us@usgs.gov). 4) Revised - November 2012 (Version 1.3) https://doi.org/10.5066/F79Z92XD 5) Revised - May 2016 (Version 1.4) https://doi.org/10.5066/F7G73BSZ 6) Revised - September 2018 (Version 2.0) https://doi.org/10.5066/P955KPLE 7) Revised - September 2020 (Version 2.1) https://doi.org/10.5066/P92QM3NT 8) Revised - January 2022 (Version 3.0) https://doi.org/10.5066/P9Q9LQ4B Comparing protected area trends between PAD-US versions is not recommended without consultation with USGS as many changes reflect improvements to agency and organization GIS systems, or conservation and recreation measure classification, rather than actual changes in protected area acquisition on the ground.