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.

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 Address Ranges Relationship File (ADDR.dbf) contains the attributes of each address range. Each address range applies to a single edge and has a unique address range identifier (ARID) value. The edge to which an address range applies can be determined by linking the address range to the All Lines Shapefile (EDGES.shp) using the permanent topological edge identifier (TLID) attribute. Multiple address ranges can apply to the same edge since an edge can have multiple address ranges. Note that the most inclusive address range associated with each side of a street edge already appears in the All Lines Shapefile (EDGES.shp). The TIGER/Line Files contain potential address ranges, not individual addresses. 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. 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.

A Home for Everyone is the City of Boise’s (city) initiative to address needs in the community by supporting the development and preservation of housing affordable to residents on Boise budgets. A Home for Everyone has three core goals: produce new homes affordable at 60% of area median income, create permanent supportive housing for households experiencing homelessness, and preserve home affordable at 80% of area median income. This dataset includes information about all homes that count toward the city’s Home for Everyone goals.

While the “produce affordable housing” and “create permanent supportive housing” goals are focused on supporting the development of new housing, the preservation goal is focused on maintaining existing housing affordable. As a result, many of the data fields related to new development are not relevant to preservation projects. For example, zoning incentives are only applicable to new construction projects.

Data may be unavailable for some projects and details are subject to change until construction is complete. Addresses are excluded for projects with fewer than five homes for privacy reasons.

The dataset includes details on the number of “homes”. We use the word "home" to refer to any single unit of housing regardless of size, type, or whether it is rented or owned. For example, a building with 40 apartments counts as 40 homes, and a single detached house counts as one home.

The dataset includes details about the phase of each project when a project involves constructing new housing. The process for building a new development is as follows: First, one must receive approval from the city’s Planning Division, which is also known as being “entitled.” Next, one must apply for and receive a permit from the city’s Building Division before beginning construction. Finally, once construction is complete and all city inspections have been passed, the building can be occupied.

To contribute to a city goal, homes must meet affordability requirements based on a standard called area median income. The city considers housing affordable if is targeted to households earning at or below 80% of the area median income. For a three-person household in Boise, that equates to an annual income of $60,650 and monthly housing cost of $1,516. Deeply affordable housing sets the income limit at 60% of area median income, or even 30% of area median income. See Boise Income Guidelines for more details.Project Name – The name of each project. If a row is related to the Home Improvement Loan program, that row aggregates data for all homes that received a loan in that quarter or year. Primary Address – The primary address for the development. Some developments encompass multiple addresses.Project Address(es) – Includes all addresses that are included as part of the development project.Parcel Number(s) – The identification code for all parcels of land included in the development.Acreage – The number of acres for the parcel(s) included in the project.Planning Permit Number – The identification code for all permits the development has received from the Planning Division for the City of Boise. The number and types of permits required vary based on the location and type of development.Date Entitled – The date a development was approved by the City’s Planning Division.Building Permit Number – The identification code for all permits the development has received from the city’s Building Division.Date Building Permit Issued – Building permits are required to begin construction on a development.Date Final Certificate of Occupancy Issued – A certificate of occupancy is the final approval by the city for a development, once construction is complete. Not all developments require a certificate of occupancy.Studio – The number of homes in the development that are classified as a studio. A studio is typically defined as a home in which there is no separate bedroom. A single room serves as both a bedroom and a living room.1-Bedroom – The number of homes in a development that have exactly one bedroom.2-Bedroom – The number of homes in a development that have exactly two bedrooms.3-Bedroom – The number of homes in a development that have exactly three bedrooms.4+ Bedroom – The number of homes in a development that have four or more bedrooms.# of Total Project Units – The total number of homes in the development.# of units toward goals – The number of homes in a development that contribute to either the city’s goal to produce housing affordable at or under 60% of area median income, or the city’s goal to create permanent supportive housing for households experiencing homelessness. Rent at or under 60% AMI - The number of homes in a development that are required to be rented at or below 60% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details. Boise defines a home as “affordable” if it is rented or sold at or below 80% of area median income.Rent 61-80% AMI – The number of homes in a development that are required to be rented at between 61% and 80% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details. Boise defines a home as “affordable” if it is rented or sold at or below 80% of area median income.Rent 81-120% AMI - The number of homes in a development that are required to be rented at between 81% and 120% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details.Own at or under 60% AMI - The number of homes in a development that are required to be sold at or below 60% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details. Boise defines a home as “affordable” if it is rented or sold at or below 80% of area median income.

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 shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).

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. The Address Ranges Relationship File (ADDR.dbf) contains the attributes of each address range. Each address range applies to a single edge and has a unique address range identifier (ARID) value. The edge to which an address range applies can be determined by linking the address range to the All Lines Shapefile (EDGES.shp) using the permanent topological edge identifier (TLID) attribute. Multiple address ranges can apply to the same edge since an edge can have multiple address ranges. Note that the most inclusive address range associated with each side of a street edge already appears in the All Lines Shapefile (EDGES.shp). The TIGER/Line Files contain potential address ranges, not individual addresses. 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. 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. 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 dataset was developed by Dillon Isaacson for use with the Esri Police Transparency Solution. This a redacted version of the RMS Charge dataset, which is an internal BPD dataset coming from the New World Law Enforcement Records Management System (LERMS) and consists of one count per charge per case/incident. A case/incident is the report that a crime took place, either reported via the public or witnessed by an officer. The Charge(s) in a case reflect what laws were broken in commission of a crime. This data is created as one point per charge. Locations of crimes have been moved to the nearest Ada County street centerline from where the incident occurred. Crimes of a sexual nature have had their locations and address information removed to protect the privacy of the victims. These records still have Patrol Area and Reporting District attributes, so the general locations and trends for these crimes can still be determined. This dataset is designed to reflect a rolling 5-6 year period. Crimes occurring in the last 9 days are withheld from the data because these data are preliminary and very likely to change. Therefore, the time range of the data will be from January 1st of the calendar year 5 years ago, up to 10 days before today’s date. For example, if you are viewing the data on September 10th, 2023, the range of data will be January 1st, 2018, to August 31st, 2023. On the first day of each year, the oldest year of records will be removed from this dataset, although it can still be requested via a Public Records Request.Field Descriptions:ChargeID - Unique identifier for charges in a case. Populated by New World Law Enforcement Records Management System (LERMS).DRNumber - Case Number, can have multiple charges per case.IncidentType - The type of incident that occurred for a caseCrimeCode - Alphanumeric code crime codeCrimeCodeDescription - OffenseCrimeCodeGroup - A grouping of crimes based on Offense codes, found starting on page 10 of the UCR Manual.CrimeType - Impact of crime, options include Person, Property, or Society Crimes.IncidentAddress - Address where incident occurred. Specific addresses have been replaced with block-level addresses or street intersections.City - City where Incident OccurredDistrict - BPD Reporting District where the crime occurred. Police reporting districts are the smallest division of territorial boundaries used by law enforcement to deploy manpower, organize officers below their senior commanders, and to track reported crimes, accidents, and calls for service. Reporting districts typically encompass a few square blocks.PatrolArea - BPD Patrol Areas where the crime occurred. Police areas are the second to largest division of territorial boundaries used by law enforcement to deploy manpower, organize officers below their senior commanders, and to track reported crimes, accidents, and calls for service.LocationScene - Type of location where incident occurred. Examples include Gym, Residence/Home, Hotel/Motel.ChargeGroup - Link created between Statute/Charge and NIBRS Crime CodesChargeSubGroup - Subgrouping for things like Domestic Assault or Commercial TheftChargeDescription - Descriptions of Charge Code that aligns with statute.ChargeCode - Statute Code of crime committed.Severity - Severity of crime committed such as Felony or Misdemeanor.OccurredDateTime - Datetime when the incident of the case occurred.Occurred_DW - Day of the Week from OccurredDateTimeOccurred_HR - Numeric Hour from OccurredDateTimeOccurred_MO - Numeric Month from OccurredDateTimeOccurred_DM - Numeric Day of Month from OccurredDateTimeOccurred_YR - Numeric Year from OccurredDateTime

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 shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).

Thumbnail image by Tony Moody.This dataset includes all housing developments approved by the City of Boise’s (“city”) Planning Division since 2020 that are known by the city to have received or are expected to receive support or incentives from a government entity. Each row represents one development. Data may be unavailable for some projects and details are subject to change until construction is complete. Addresses are excluded for projects with fewer than five homes for privacy reasons.

The dataset includes details on the number of “homes” in a development. We use the word "home" to refer to any single unit of housing regardless of size, type, or whether it is rented or owned. For example, a building with 40 apartments counts as 40 homes, and a single detached house counts as one home.

The dataset includes details about the phase of each project. The process for build a new development is as follows: First, one must receive approval from the city’s Planning Division, which is also known as being “entitled.” Next, one must apply for and receive a permit from the city’s Building Division before beginning construction. Finally, once construction is complete and all city inspections have been passed, the building can be occupied.

The dataset also includes data on the affordability level of each development. To receive a government incentive, a developer is typically required to rent or sell a specified number of homes to households that have an income below limits set by the government and their housing cost must not exceed 30% of their income. The federal government determines income limits based on a standard called “area median income.” The city considers housing affordable if is targeted to households earning at or below 80% of the area median income. For a three-person household in Boise, that equates to an annual income of $60,650 and monthly rent or mortgage of $1,516. See Boise Income Guidelines for more details.Project Address(es) – Includes all addresses that are included as part of the development project.Address – The primary address for the development.Parcel Number(s) – The identification code for all parcels of land included in the development.Acreage – The number of acres for the parcel(s) included in the project.Planning Permit Number – The identification code for all permits the development has received from the Planning Division for the City of Boise. The number and types of permits required vary based on the location and type of development.Date Entitled – The date a development was approved by the City’s Planning Division.Building Permit Number – The identification code for all permits the development has received from the city’s Building Division.Date Building Permit Issued – Building permits are required to begin construction on a development.Date Final Certificate of Occupancy Issued – A certificate of occupancy is the final approval by the city for a development, once construction is complete. Not all developments require a certificate of occupancy.Studio – The number of homes in the development that are classified as a studio. A studio is typically defined as a home in which there is no separate bedroom. A single room serves as both a bedroom and a living room.1-Bedroom – The number of homes in a development that have exactly one bedroom.2-Bedroom – The number of homes in a development that have exactly two bedrooms.3-Bedroom – The number of homes in a development that have exactly three bedrooms.4+ Bedroom – The number of homes in a development that have four or more bedrooms.# of Total Project Units – The total number of homes in the development.# of units toward goals – The number of homes in a development that contribute to either the city’s goal to produce housing affordable at or under 60% of area median income, or the city’s goal to create permanent supportive housing for households experiencing homelessness.Rent at or under 60% AMI - The number of homes in a development that are required to be rented at or below 60% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details. Boise defines a home as “affordable” if it is rented or sold at or below 80% of area median income.Rent 61-80% AMI – The number of homes in a development that are required to be rented at between 61% and 80% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details. Boise defines a home as “affordable” if it is rented or sold at or below 80% of area median income.Rent 81-120% AMI - The number of homes in a development that are required to be rented at between 81% and 120% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details.Own at or under 60% AMI - The number of homes in a development that are required to be sold at or below 60% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details. Boise defines a home as “affordable” if it is rented or sold at or below 80% of area median income.Own 61-80% AMI – The number of homes in a development that are required to be sold at between 61% and 80% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details. Boise defines a home as “affordable” if it is rented or sold at or below 80% of area median income.Own 81-120% AMI - The number of homes in a development that are required to be sold at between 81% and 120% of area median income. See the description of the dataset above for an explanation of area median income or see Boise Income Guidelines for more details.Housing Land Trust – “Yes” if a development receives or is expected to receive this incentive. The Housing Land Trust is a model in which the city owns land that it leases to a developer to build affordable housing.City Investment – “Yes” if the city invests funding or contributes land to an affordable development.Zoning Incentive - The city's zoning code provides incentives for developers to create affordable housing. Incentives may include the ability to build an extra floor or be subject to reduced parking requirements. “Yes” if a development receives or is expected to receive one of these incentives.Project Management - The city provides a developer and their design team a single point of contact who works across city departments to simplify the permitting process, and assists the applicants in understanding the city’s requirements to avoid possible delays. “Yes” if a development receives or is expected to receive this incentive.Low-Income Housing Tax Credit (LIHTC) - A federal tax credit available to some new affordable housing developments. The Idaho Housing and Finance Association is a quasi-governmental agency that administers these federal tax credits. “Yes” if a development receives or is expected to receive this incentive.CCDC Investment - The Capital City Development Corp (CCDC) is a public agency that financially supports some affordable housing development in Urban Renewal Districts. “Yes” if a development receives or is expected to receive this incentive. If “Yes” the field identifies the Urban Renewal District associated with the development.City Goal – The city has set goals to produce housing affordable to households at or below 60% of area median income, and to create permanent supportive housing for households experiencing homelessness. This field identifies whether a development contributes to one of those goals.Project Phase - The process for build a new development is as follows: First, one must receive approval from the city’s Planning Division, which is also known as being “entitled.” Next, one must apply for and receive a permit from the city’s Building Division before beginning construction. Finally, once construction is complete and all city inspections have been passed, the building can be occupied.

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 dataset provides information about the number of properties, residents, and average property values for Neptune Place cross streets in Boise, ID.

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 Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).

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 dataset provides information about the number of properties, residents, and average property values for Wadsworth Drive cross streets in Boise, ID.

This dataset provides information about the number of properties, residents, and average property values for Aldape Cove cross streets in Boise, ID.

This is a polygon data set representing planning projects or applications and their associated parcels. In cases where a permit involves more than one parcel, parcels are merged together to create one project extent. An active planning permit could be a planning project (PLN) that has completed the concept review phase and has not yet been entitled, canceled, withdrawn, and denied. It also includes planning applications that are currently under review by the planning staff and have not yet been issued or withdrawn. PLNs associated with active applications will appear on the map. This data was created by the City of Boise. This data is updated daily. It is current to the date of publication.

Field Descriptions:

Record ID

– The unique identifier assigned by the permit system.

Parent Record ID

– The PLN case associated with the application.

Record Name

– The name of the permit entered in the permit system.

Status

– The current state of the permit within the permitting workflow.

Accepted - The permit has been though the prescreening process and it has been paid for. It is ready for review.

Appealed - A member of the public has applied to have a decision to issue an application related to the permit reversed.

Applicant upload - Partial permit application has been received by PDS and is awaiting more plan information.

Applications in Review - Applications associated with the PLN permit are being reviewed by the planning department.

In Review - The permit is currently being reviewed by planners or a regulatory body.

Interdepartmental Review - The PLN is in the process of being review by different departments and is not yet ready to have application related to it.

Neighborhood Meeting - The PLN is in being reviewed in a neighborhood meeting.

Project Entitled - An application under the PLN had been entitled and the project can now legally apply for building permits.

Received - Complete permit application has been received by PDS and is ready to begin prescreening.

Returned to Applicant - The application is incomplete or inaccurate and has been returned to the applicant for corrections.

AddToTrackerDate

– The date when the PLN case completes concept review or when an application is received. This is a datetime field stored in Universal Coordinated Time (UTC).

RecordType

– The type of planning permit.

Administrative Approval - Permits that can be approved by the planning staff without review by a higher authoritative regulatory body.

Annexation-Rezone - Permits requesting to change the boundary of the city or change the zoning district of a parcel(s).

Comprehensive Plan Amendment - A permit to amend Blueprint Boise, the city’s comprehensive plan, in order to address changes within the community since its adoption.

Conditional Use - A permit in which a use is reviewed for compliance with the comprehensive plan, availability of services, compatibility, and possible adverse impacts upon neighboring properties.

Design Review-Historic - A permit to review new construction and exterior alterations to a building or site located within the city’s Design Review and Downtown Design Review Overlay zones.

Floodplain-Hillside - A permit that ensures development of sloped and/or flood-prone land occurs in a manner consistent with the Comprehensive Plan.

Planned Unit Development - A permit that provides opportunities for creative land development that preserves natural features, allows efficient provision of services, and provides common open spaces or other amenities not found in traditional lot-by-lot development.

Project - A permit that tracks the preliminary steps before planning applications are applied for. Their record later will become the parent record ID of the related applications. The first three letter of the record ID are PLN.

Subdivision - A permit that creates and records legal division of land.

Subdivision Other Stuff - Other permits related to subdivisions, including vacation of easement and/or plat note, subdivision ordinance waiver, or street name change.

Variance - A permit to request relief form a dimensional standard withing the Zoning Ordinance based on a hardship with a property, or an exceptional circumstance related to the use of the property.

Comprehensive Planning Area

– The comprehensive planning area the location of the planning permit would fall in.

Neighborhood Association Name

– The neighborhood association the location of the planning permit would fall in.

Property Address

– The street address of the property the permit is related to.

ReviewAuthority

– The highest authoritative regulatory body that needs to approve permit.

City Council - The legislative body for Boise City with policy setting a budgetary authority.

Planning & Zoning Commission - A group of people appointed to deal with a broad array of issues such as making recommendations and decisions on land use applications and dealing with the long-term issues of planning for the future growth and development of the community.

Administrative - A planning employee of Planning and Development Services.

Design Review Committee - A group of people appointed to accept and review applications for design review permits which have been developed to protect property rights and values, enhance important environmental features, and ensure orderly and harmonious development within the community.

Historic Preservation Commission - A group of people appointed to promote, preserve, and protect the historic buildings, structures, sites, monuments, streets, and neighborhoods which serve as visible reminders of Boise’s historical, archaeological, architectural, educational, and cultural heritage.

Website

– A link to the public Accela permitting and licensing system website for the specific permit.

Next Hearing Date

– The date of the next public hearing where the application will be reviewed. This is a datetime field stored in Universal Coordinated Time (UTC).

Hearing Body

– The regulatory body that will preside over the next hearing date.

City Council - The legislative body for Boise City with policy setting a budgetary authority.

Planning & Zoning Commission - A group of people appointed to deal with a broad array of issues such as making recommendations and decisions on land use applications and dealing with the long-term issues of planning for the future growth and development of the community.

Design Review Committee - A group of people appointed to accept and review applications for design review permits which have been developed to protect property rights and values, enhance important environmental features, and ensure orderly and harmonious development within the community.

Historic Preservation Commission - A group of people appointed to promote, preserve, and protect the historic buildings, structures, sites, monuments, streets, and neighborhoods which serve as visible reminders of Boise’s historical, archaeological, architectural, educational, and cultural heritage.

ZoningCode

– The zoning code which regulates the planning permit.

Pre-2023 Code - Permit is regulated under the zoning code in use before December 1st, 2023.

MZC 2023 - Permit is regulated under the Modern Zoning Code adopted on December 1st, 2023.

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 Relationship File (ADDR.dbf) contains the attributes of each address range. Each address range applies to a single edge and has a unique address range identifier (ARID) value. The edge to which an address range applies can be determined by linking the address range to the All Lines Shapefile (EDGES.shp) using the permanent topological edge identifier (TLID) attribute. Multiple address ranges can apply to the same edge since an edge can have multiple address ranges. Note that the most inclusive address range associated with each side of a street edge already appears in the All Lines Shapefile (EDGES.shp). The TIGER/Line Files contain potential address ranges, not individual addresses. 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. 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 point data set representing the locations where City of Boise Risk Management and Safety Services has placed automated external defibrillators (AED) for use, if needed, by Boise City staff or the public. An AED is a portable electronic device, that automatically diagnoses potentially life threatening cardiac arrhythmias in a patient, and is able to treat them through defibrillation (the application of electrical therapy which stops the arrhythmia, allowing the heart to reestablish an effective rhythm). Some locations have an AED placed there seasonally, while other locations have AEDs year round, as noted in the attributes. Only those AEDs positioned for use by general staff and/or the public are recorded in this data set; AEDs not available for use are not included. The data is a snapshot of AED locations current to the last periodic update. The dataset is maintained by City of Boise GIS under direction from the Boise City’s Risk Management and Safety Services staff.For more information, please contact City of Boise Risk Management and Safety Services.