The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent dataset, or they can be combined to cover the entire nation. The Area Hydrography Shapefile contains the geometry and attributes of both perennial and intermittent area hydrography features, including ponds, lakes, oceans, swamps (up to the U.S. nautical three-mile limit), glaciers, and the area covered by large rivers, streams, and/or canals that are represented as double-line drainage. Single-line drainage water features can be found in the Linear Hydrography Shapefile (LINEARWATER.shp). Linear water features includes single-line drainage water features and artificial path features, where they exist, that run through double-line drainage features such as rivers, streams, and/or canals, and serve as a linear representation of these features.

This maps shows City of Boise annexations since the original townsite was established in 1866 by the Idaho Territorial Legislature. Use the time-slider to watch the City grow over time. An annexation is the legal incorporation of a geographic area in to a political body. A de-annexation is the secession of a geographic area from a political body. De-annexed areas are areas that were once part of the incorporated boundaries of Boise City but have been removed from the incorporated boundaries (based on the ordinance tied to the de-annexation). The source of the data is the ordinances of annexation recorded by the Boise City Clerks' office. The map also depicts the current incorporated boundaries for cities within Ada County. The Ada County Assessor's Office maintains the city limits and impact areas datasets within Ada County. City boundaries are determined by taxcode and maintained continually, adding areas annexed to city limits by current ordinances. The impact areas dataset depicts the unincorporated areas of Ada County surrounding each city as identified in Title 9 of the Ada County Code, in accordance with Idaho Code Section 67-6526. This data is maintained by City of Boise GIS and is based on the legal descriptions contained in the ordinances. This data set is continually being updated as annexations occur. It is current to the date it was published.For more information, please contact the Ada County Assessor's Division of Land Records/GIS or the City of Boise Planning & Development Services division.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Census Bureau includes landmarks in the MTS for locating special features and to help enumerators during field operations. Some of the more common landmark types include airports, cemeteries, parks, schools, and churches and other religious institutions. The Census Bureau adds landmark features to MTS on an as-needed basis and does not ensure that all instances of a particular feature are included. The presence or absence of a landmark such as a hospital or prison does not mean that the living quarters associated with that landmark were geocoded to that census tabulation block or excluded from the census enumeration. The Area Landmark shapefile does not include military installations or water bodies because they appear in their own separate shapefiles, mil.shp and areawater.shp respectively.

Ada County Assessor's Office maintains the dataset of city limits within Ada County. It is comprised of city boundaries determined by taxcode and maintained continually, adding areas annexed to city limits by current ordinances.

Graph and download economic data for Estimate of Median Household Income for Ada County, ID (MHIID16001A052NCEN) from 1989 to 2023 about Ada County, ID; Boise City; ID; households; median; income; and USA.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

There are four entities within Ada County that assign addresses within their jurisdiction: Boise City, Ada County, Meridian, and Kuna. This dataset is an aggregation of key address data elements supplied by the four addressing entities into a single county-wide address point layer.Attribute Fields:AddPfx = Address Number Prefix: The non-integer portion of the identifier for the house, building or other feature that precedes the address number itself. Ex. 'NW'AddNum = Address Number: The numeric identifier for a land parcel, house, building or other feature. Ex. '1', '125'AddSfx = Address Number Suffix: The non-integer portion of the identifier for the house, building or other feature that follows the address number itself. Ex. '1/2'StPredMod = Street Name PreModifier: A word or phrase that precedes all other elements of the street name and modifies it, but is separated from the street name by a street name pre-directional and/or pre-type. Ex. 'Old'StPreDir = Street Name PreDirection: A word preceding the street name that indicates the directional taken by the thoroughfare from an arbitrary starting point, or the sector where it is located. Ex. 'N', 'SW'StPrefix = Street Name PreType: The element of the complete street name preceding the street name element that indicates the type of street. Ex. 'Ave', 'Blvd'StName = Street Name: Official name of a street as assigned by a local governing authority. 'Main', 'Front'StSuffix = Street Name PostType: The element of the complete street name following the street name element that indicates the type of street. Ex. 'St', 'Ln'StPostDir = Street Name PostDirection: A word following the street name that indicates the directional taken by the thoroughfare from an arbitrary starting point, or the sector where it is located. Ex. 'N', 'SW'StPostMod = Street Name PostModifier: A word or phrase that follows all other elements of the street name and modifies it, but is separated from the street name by a street name post-directional and/or post type. Ex. 'Cutoff', 'Bypass'PrUnitType = Primary Unit Type: In the case of multiple structures (generally buildings) at one street address, this describes the type of structure being addressed. Ex. 'Bldg'PrUnitID = Primary Unit Identifier: The letters, numbers, words or combination thereof used to distinguish one structure from another when several occur at the same address. Ex. 'A', 'One'SbUnitType = Sub Unit Type: In the case of multiple units per structure at one street address, this describes the type of unit being addressed. Ex. 'Apt', 'Ste'SbUnitID = Sub Unit Identifier: The letters, numbers, words or combination thereof used to distinguish one unit from another when several occur in the same building. Ex. '#10', 'A'FloorID = Floor Identifier: The letters, numbers, words or combination thereof used to distinguish one floor from another in multi-story buildings. Ex. '1', 'B', 'Mezzanine'Floors = Number of floors in a particular structure. Ex. '1', '2'CommName = City name used in a USPS mailing address for this address. 'Boise', 'Meridian'State = State abbreviation. Ex. 'ID'Zip4 = ZIP Code for an address as defined by USPS. Ex. '83702-2357', '83702'PrimStruct Used to indicate the primary structure at a particular address with many structures (i.e. a house and a barn share an address, but the house is the primary structure). Ex. 'Y', 'N'PrimAdd = Used to indicate the primary address of a structure that contains multiple addresses (i.e. an apartment building's street address). Ex. 'Y', 'N'LocalID = Address Identifier: Primary key, unique database key, etc... as assigned by each agency (i.e. that contained in the "Manager" field).GNISID = Numeric identifier for a feature in the Geographic Names Information System (GNIS).AddGrid = Reference System: Name of the address reference system (aka "grid") used to create each address. Ex. 'Kuna', 'Eagle'Manager = Address Manager: The name of the entity that currently manages this address. Ex. 'Boise', 'Ada County'Creator = Address Creator: The name of the entity that assigned this address. Ex. 'Meridian', 'Ada County'

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) contains a record for each face / area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Topological Faces Shapefile (FACES.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Area Hydrography Shapefile (AREAWATER.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces/Area Hydrography Relationship File contains a record for each face/area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up the MTS. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces/Area Hydrography Relationship File (facesah.dbf) applies can be determined by linking to the Topological Faces shapefile (faces.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces/Area Hydrography Relationship File applies can be determined by linking to the Area Hydrography shapefile (areawater.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up the MTS. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces shapefile.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) contains a record for each face / area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Topological Faces Shapefile (FACES.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Area Hydrography Shapefile (AREAWATER.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

Graph and download economic data for Resident Population in Ada County, ID (IDADAC1POP) from 1970 to 2024 about Ada County, ID; Boise City; ID; residents; population; and USA.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Range Features shapefile contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. This shapefile contains a record for each address range to street name combination. Address ranges associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that this shapefile includes all unsuppressed address ranges compared to the All Lines shapefile (edges.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefiles contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line shapefiles are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

Graph and download economic data for 90% Confidence Interval Upper Bound of Estimate of Median Household Income for Ada County, ID (MHICIUBID16001A052NCEN) from 1989 to 2023 about Ada County, ID; Boise City; ID; households; median; income; and USA.

This is a polygon data set representing fire district service areas within Ada County, Idaho. Fire districts are the administrative boundaries that define the area that a fire department, or contracted agency, is charged to provide fire suppression services for. It aggregates fire tax code area boundaries for fire districts and incorporated municipalities, as appropriate for the fire agency, to depict the service areas (a.k.a. districts) for each fire department/agency in Ada County. A fire district that annexes an area in June is responsible to serve that area even though taxation is not assigned to those properties until January the next calendar year. This data set does not represent areas of service defined through other agreements such as automatic aid, mutual aid, or other contractual agreements. This data set is not to be used to identify the tax district boundaries for any fire district/agency. The Idaho State Tax Commission publishes the official tax code area boundaries for all taxing districts (counties, cities, schools, libraries, recreation districts, fire protection, ambulance, hospital, mosquito abatement, and others) once a year (typically in March or April). This data set is maintained by Boise City GIS and is update at least twice a year (January and July). The data set is current to the date it was published. For more information, please visit City of Boise Fire Department.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

This is a polygon data set representing first due areas for stations located in Ada County. A first area is geographical area that one station is closer to than any other station. It should normally be served by the personnel and apparatus from the fire station in the event of a fire or other emergency. With today’s computer aided dispatch (CAD) systems, station first due areas are no longer used to assign an apparatus to an incident. The closest engine, no matter the district, will be assigned. We now use the first due areas to analyze if our fire fighting force is being used efficiently. We will use it to see if certain stations are busier that others and if stations have a concentration of a specific type of call in their first due area. This information will be used to make business decisions within all fire departments in Ada County. The data set was created from FireView Desktop software based on current street network, station locations, and fire district boundaries. The accuracy is unknown. This data was created by the City of Boise. This data is updated as needed. It is current to the date of publication.