A. SUMMARY This dataset contains the list of intersecting Analysis Neighborhoods and ZIP Codes for the City and County of San Francisco. It can be used to identify which ZIP codes overlap with Analysis Neighborhoods and vice verse. B. HOW THE DATASET IS CREATED The dataset was created with a spatial join between the Analysis Neighborhoods and ZIP codes. C. UPDATE PROCESS This is a static dataset D. HOW TO USE THIS DATASET This dataset is a many-to-many relationship between analysis neighborhoods and ZIP codes. A single neighborhood can contain or intersect with multiple ZIP codes and similarly, a single ZIP code can be in multiple neighborhoods. This dataset does not contain geographic boundary data (i.e. shapefiles/ GEOMs). The datasets below containing geographic boundary data should be used for analysis of data with geographic coordinates. E. RELATED DATASETS Analysis Neighborhoods San Francisco ZIP Codes Supervisor District (2022) to ZIP Code Crosswalk Analysis Neighborhoods - 2020 census tracts assigned to neighborhoods

Abstract

A crosswalk dataset matching US ZIP codes to corresponding census tracts

Documentation

The denominators used to calculate the address ratios are the ZIP code totals. When a ZIP is split by any of the other geographies, that ZIP code is duplicated in the crosswalk file.

**Example: **ZIP code 03870 is split by two different Census tracts, 33015066000 and 33015071000, which appear in the tract column. The ratio of residential addresses in the first ZIP-Tract record to the total number of residential addresses in the ZIP code is .0042 (.42%). The remaining residential addresses in that ZIP (99.58%) fall into the second ZIP-Tract record.

So, for example, if one wanted to allocate data from ZIP code 03870 to each Census tract located in that ZIP code, one would multiply the number of observations in the ZIP code by the residential ratio for each tract associated with that ZIP code.

https://redivis.com/fileUploads/4ecb405e-f533-4a5b-8286-11e56bb93368%3E" alt="">(Note that the sum of each ratio column for each distinct ZIP code may not always equal 1.00 (or 100%) due to rounding issues.)

Census tract definition

A census tract, census area, census district or meshblock is a geographic region defined for the purpose of taking a census. Sometimes these coincide with the limits of cities, towns or other administrative areas and several tracts commonly exist within a county. In unincorporated areas of the United States these are often arbitrary, except for coinciding with political lines.

Further reading

The following article demonstrates how to more effectively use the U.S. Department of Housing and Urban Development (HUD) United States Postal Service ZIP Code Crosswalk Files when working with disparate geographies.

Wilson, Ron and Din, Alexander, 2018. “Understanding and Enhancing the U.S. Department of Housing and Urban Development’s ZIP Code Crosswalk Files,” Cityscape: A Journal of Policy Development and Research, Volume 20 Number 2, 277 – 294. URL: https://www.huduser.gov/portal/periodicals/cityscpe/vol20num2/ch16.pdf

Contact information

Questions regarding these crosswalk files can be directed to Alex Din with the subject line HUD-Crosswalks.

Acknowledgement

This dataset is taken from the U.S. Department of Housing and Urban Development (HUD) office: https://www.huduser.gov/portal/datasets/usps_crosswalk.html#codebook

Abstract

A crosswalk matching US ZIP codes to corresponding CBSA (core-based statistical area)

Documentation

The denominators used to calculate the address ratios are the ZIP code totals. When a ZIP is split by any of the other geographies, that ZIP code is duplicated in the crosswalk file.

**Example: **ZIP code 03870 is split by two different Census tracts, 33015066000 and 33015071000, which appear in the tract column. The ratio of residential addresses in the first ZIP-Tract record to the total number of residential addresses in the ZIP code is .0042 (.42%). The remaining residential addresses in that ZIP (99.58%) fall into the second ZIP-Tract record.

So, for example, if one wanted to allocate data from ZIP code 03870 to each Census tract located in that ZIP code, one would multiply the number of observations in the ZIP code by the residential ratio for each tract associated with that ZIP code.

https://redivis.com/fileUploads/4ecb405e-f533-4a5b-8286-11e56bb93368%3E" alt="">(Note that the sum of each ratio column for each distinct ZIP code may not always equal 1.00 (or 100%) due to rounding issues.)

CBSA definition

A core-based statistical area (CBSA) is a U.S. geographic area defined by the Office of Management and Budget (OMB) that consists of one or more counties (or equivalents) anchored by an urban center of at least 10,000 people plus adjacent counties that are socioeconomically tied to the urban center by commuting. Areas defined on the basis of these standards applied to Census 2000 data were announced by OMB in June 2003. These standards are used to replace the definitions of metropolitan areas that were defined in 1990. The OMB released new standards based on the 2010 Census on July 15, 2015.

Further reading

The following article demonstrates how to more effectively use the U.S. Department of Housing and Urban Development (HUD) United States Postal Service ZIP Code Crosswalk Files when working with disparate geographies.

Wilson, Ron and Din, Alexander, 2018. “Understanding and Enhancing the U.S. Department of Housing and Urban Development’s ZIP Code Crosswalk Files,” Cityscape: A Journal of Policy Development and Research, Volume 20 Number 2, 277 – 294. URL: https://www.huduser.gov/portal/periodicals/cityscpe/vol20num2/ch16.pdf

Contact authors

Questions regarding these crosswalk files can be directed to Alex Din with the subject line HUD-Crosswalks.

Acknowledgement

This dataset is taken from the U.S. Department of Housing and Urban Development (HUD) office: https://www.huduser.gov/portal/datasets/usps_crosswalk.html#codebook

View the 2022 Zip Code to Supervisor District Crosswalk: https://data.sfgov.org/Geographic-Locations-and-Boundaries/Supervisor-District-2022-to-ZIP-Code-Crosswalk/2x22-z5j6 Lists intersecting Supervisor Districts and ZIP Codes for City and County of San Francisco.

A. SUMMARY This dataset contains the list of intersecting 2022 Supervisor Districts and ZIP Codes for the City and County of San Francisco. It can be used to identify which ZIP codes overlap with Supervisor Districts (2022) and vice verse. B. HOW THE DATASET IS CREATED The dataset was created with a spatial join between the 2022 Supervisor districts and ZIP codes. C. UPDATE PROCESS This is a static dataset D. HOW TO USE THIS DATASET This dataset is a many-to-many relationship between supervisor districts and ZIP codes. A single supervisor district can contain or intersect with multiple ZIP codes and similarly, a single ZIP code can be in multiple supervisor districts. This dataset does not contain geographic boundary data (i.e. shapefiles/ GEOMs). The datasets below containing geographic boundary data should be used for analysis of data with geographic coordinates. E. RELATED DATASETS Supervisor Districts (2022) San Francisco ZIP Codes Supervisor District (2012) to ZIP Code Crosswalk Analysis Neighborhoods - 2020 census tracts assigned to neighborhoods

Researchers have long been able to analyze crime and law enforcement data at the individual agency level and at the county level using data from the Federal Bureau of Investigation's Uniform Crime Reporting (UCR) Program data series. However, analyzing crime data at the intermediate level, the city or place, has been difficult, as has merging disparate data sources that have no common match keys. To facilitate the creation and analysis of place-level data and linking reported crime data with data from other sources, the Bureau of Justice Statistics (BJS) and the National Archive of Criminal Justice Data (NACJD) created the Law Enforcement Agency Identifiers Crosswalk (LEAIC). The crosswalk file was designed to provide geographic and other identification information for each record included in the FBI's UCR files and Bureau of Justice Statistics' Census of State and Local Law Enforcement Agencies (CSLLEA). The LEAIC records contain common match keys for merging reported crime data and Census Bureau data. These linkage variables include the Originating Agency Identifier (ORI) code, Federal Information Processing Standards (FIPS) state, county and place codes, and Governments Integrated Directory government identifier codes. These variables make it possible for researchers to take police agency-level data, combine them with Bureau of the Census and BJS data, and perform place-level, jurisdiction-level, and government-level analyses.

Crosswalk numbers for the city of Boston. Generated in July 2008 from original maps dated 1951-1962 and related sketches. Placed using centerlines from Water and Sewer as well as block defintions. Shapefiles for individual districts were merged into this one file but do not have an active connection. Some discrepency between centerlines and earlier maps was allowed, though obvious problems were marked in red. The legend is consistent between all districts, except for Roxbury where the map did not distinguish mid-block or school crosswalks.

This is the road facility (crosswalk) information provided by the Living Safety Map (https://www.safemap.go.kr) operated by the Ministry of the Interior and Safety, and the crosswalk layer information of the National Geographic Information Institute is collected, and each facility can be identified through the legend in the Living Safety Map. It provides all information composed of crosswalks on major roads and within specific facilities, and the corresponding API provides both XML and WMS. In the case of XML, only information on each city and county is provided, and coordinate and location information are not provided.

Intersection markings including crosswalk and stop line locations and information.

This is the MnDOT user-accepted version of the state boundary. It is a composite of all of the county boundaries, as accepted by MnDOT for general purpose use. This boundary represents a pre-1947 state boundary as it does not recognize the 1947 states compact signed between Wisconsin, Michigan, and Minnesota, which defined the boundary/boundaries within Lake Superior. This boundary measures approximately 84,365 square miles, and excludes the portion of Lake Superior that is legally defined as part of the state of Minnesota.

This medium-scale (nominally 1:24,000) dataset represents the boundaries of Cities in Minnesota. It is derived from CTU dataset where the feature type is a City (does not include townships or unorganized territories). The Minnesota Geospatial Information Office created the initial CTU dataset by updating a municipal boundary file maintained by the Minnesota Department of Transportation (MnDOT). Update information was gathered primarily from annexation and detachment records maintained by the Office of Administrative Hearings, Municipal Boundary Adjustment Unit. MnDOT has maintained the file since 2014.

This medium-scale (nominally 1:24,000) dataset represents the boundaries of cities, townships, and unorganized territories (CTUs) in Minnesota. The Minnesota Geospatial Information Office created the initial CTU dataset by updating a municipal boundary file maintained by the Minnesota Department of Transportation (MnDOT). Update information was gathered primarily from annexation and detachment records maintained by the Office of Administrative Hearings, Municipal Boundary Adjustment Unit. MnDOT has maintained the file since 2014.

This dataset represents the county boundaries, as recognized by the Minnesota Department of Transportation. There are 87 counties in Minnesota.

The adjusted urban boundaries from the 2010 U.S. census.

Jurisdictional crosswalk is a combination of data from federal sources and legacy MnDOT data. It creates a crosswalk or translation between various ID systems for city, township, and unorganized territories within the State of Minnesota.

Tribal Government boundaries is a layer that contains the Minnesota interpretation of the federally recognized tribal boundaries within Minnesota. For the Federal interpretation see the US senses TIGER files.

Check other metadata records in this package for more information on boundaries of jurisdictions.