CSV Table. This table includes coded descriptions for Property Class Codes in the St. Louis County, Missouri Parcel dataset. Property Class Codes are the Tax Subclass Codes for a property. Please see field PROPCLASS in the Parcel dataset. Link to Metadata.

This dataset contains model-based ZIP Code Tabulation Area (ZCTA) level estimates in GIS-friendly format. PLACES covers the entire United States—50 states and the District of Columbia—at county, place, census tract, and ZIP Code Tabulation Area levels. It provides information uniformly on this large scale for local areas at four geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. PLACES was funded by the Robert Wood Johnson Foundation in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates are Behavioral Risk Factor Surveillance System (BRFSS) 2022 or 2021 data, Census Bureau 2020 population counts, and American Community Survey (ACS) 2018–2022 estimates. The 2024 release uses 2022 BRFSS data for 36 measures and 2021 BRFSS data for 4 measures (high blood pressure, high cholesterol, cholesterol screening, and taking medicine for high blood pressure control among those with high blood pressure) that the survey collects data on every other year. These data can be joined with the Census 2021 ZCTA boundary file in a GIS system to produce maps for 40 measures at the ZCTA level. An ArcGIS Online feature service is also available for users to make maps online or to add data to desktop GIS software. https://cdcarcgis.maps.arcgis.com/home/item.html?id=3b7221d4e47740cab9235b839fa55cd7

The City of Tempe ZIP Codes feature class is from Maricopa County GIS Open Data and is intended to show the USPS ZIP Code boundaries within Tempe, Arizona.

This data represents five-digit ZIP Code areas used by the U.S. Postal Service. This is an ArcGIS Online item directly from Esri. For more information see https://www.arcgis.com/home/item.html?id=8d2012a2016e484dafaac0451f9aea24.

This feature class was created by exporting the Census Zip Code features from the 2020 TIGER/Line Geodatabase.TIGER Geodatabases are spatial extracts from the Census Bureau’s MAF/TIGER database. These files do not include demographic data, but they contain geographic entity codes that can be linked to the Census Bureau’s demographic data.

This dataset demarcates the zip code boundaries that lie within Allegheny County.If viewing this description on the Western Pennsylvania Regional Data Center’s open data portal (http://www.wprdc.org), this dataset is harvested on a weekly basis from Allegheny County’s GIS data portal (http://openac.alcogis.opendata.arcgis.com/). The full metadata record for this dataset can also be found on Allegheny County’s GIS portal. You can access the metadata record and other resources on the GIS portal by clicking on the “Explore” button (and choosing the “Go to resource” option) to the right of the “ArcGIS Open Dataset” text below.Category: Civic Vitality and GovernanceOrganization: Allegheny CountyDepartment: Geographic Information Systems Group; Department of Administrative ServicesTemporal Coverage: currentData Notes: Coordinate System: Pennsylvania State Plane South Zone 3702; U.S. Survey FootDevelopment Notes: noneOther: noneRelated Document(s): Data Dictionary (none)Frequency - Data Change: As neededFrequency - Publishing: As neededData Steward Name: Eli ThomasData Steward Email: gishelp@alleghenycounty.us

This dataset contains model-based ZIP Code tabulation Areas (ZCTA) level estimates for the PLACES project 2020 release in GIS-friendly format. The PLACES project is the expansion of the original 500 Cities project and covers the entire United States—50 states and the District of Columbia (DC)—at county, place, census tract, and ZIP Code tabulation Areas (ZCTA) levels. It represents a first-of-its kind effort to release information uniformly on this large scale for local areas at 4 geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. The project was funded by the Robert Wood Johnson Foundation (RWJF) in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates include Behavioral Risk Factor Surveillance System (BRFSS) 2018 or 2017 data, Census Bureau 2010 population estimates, and American Community Survey (ACS) 2014-2018 or 2013-2017 estimates. The 2020 release uses 2018 BRFSS data for 23 measures and 2017 BRFSS data for 4 measures (high blood pressure, taking high blood pressure medication, high cholesterol, and cholesterol screening). Four measures are based on the 2017 BRFSS data because the relevant questions are only asked every other year in the BRFSS. These data can be joined with the census 2010 ZCTA boundary file in a GIS system to produce maps for 27 measures at the ZCTA level. An ArcGIS Online feature service is also available at https://www.arcgis.com/home/item.html?id=8eca985039464f4d83467b8f6aeb1320 for users to make maps online or to add data to desktop GIS software.

This data set is intended for use as a reference map layer for GIS maps and applications. Tax codes are used to calculate the assessor's taxing rate on a specific parcel based on the taxing districts that represent it. In GIS, this dataset is used to create Fire District boundaries, School District boundaries, and City Limits. These data are continually being updated by County Cartography.

MassGIS had received quarterly updates of these data as part of its license for the HERE (Navteq) core map release (streets and related data); however, that license has expired. These ZIP Code boundaries are aligned to the street centerlines of the Q2 2018 HERE product (with a release date of April 1, 2018) and use a then-recent USPS source file.In March 2024, MassGIS modified the boundaries for all ZIP Code areas in Boston based on the U.S. Postal Service's ZIP Code Look Up by Address website. MassGIS also added polygons for ZIP Codes 02199 and 02203.Five-digit ZIP Codes were developed by the USPS and first introduced in 1963 for efficient mail delivery (the term ZIP stands for Zone Improvement Plan) but are difficult to map with complete certainty. In most cases, addresses in close proximity to each other are grouped in the same ZIP Code, which gives the appearance that ZIP Codes are defined by a clear geographic boundary. However, even when ZIP Codes appear to be geographically grouped, a clear ZIP Code boundary cannot always be drawn because ZIP Codes are only assigned to a point of delivery and not the spaces between delivery points. In areas without a regular postal route or no mail delivery, ZIP Codes may not be defined or have unclear boundaries.The USPS does not maintain an official ZIP Code map. The Census Bureau and many other commercial services will interpolate the data to create polygons to represent the approximate area covered by a ZIP code, but none of these maps are official or entirely accurate. Please see this good discussion of the issues of mapping ZIP Codes.See full metadata.Map service also available.

Count and percentage of county residents by age groups. Data are summarized at county, city, zip code and census tract of residence. Data are presented for zip codes (ZCTAs) fully within the county. Source: U.S. Census Bureau, 2016-2020 American Community Survey 5-year estimates, Table B01001; data accessed on April 11, 2022 from https://api.census.gov. The 2020 Decennial geographies are used for data summarization.METADATA:notes (String): Lists table title, notes, sourcesgeolevel (String): Level of geographyGEOID (Numeric): Geography IDNAME (String): Name of geographyt_pop (Numeric): Total populationt0_4 (Numeric): Population count ages less than 5 yearst5_14 (Numeric): Population count ages 5 to 14 yearst15_24 (Numeric): Population count ages 15 to 24 yearst25_34 (Numeric): Population count ages 25 to 34 yearst35_44 (Numeric): Population count ages 35 to 44 yearst45_54 (Numeric): Population count ages 45 to 54 yearst55_64 (Numeric): Population count ages 55 to 64 yearst65over (Numeric): Population count ages 65 years and olderp_0_4 (Numeric): Percent of people ages less than 5 yearsp_5_14 (Numeric): Percent of people ages 5 to 14 yearsp_15_24 (Numeric): Percent of people ages 15 to 24 yearsp_25_34 (Numeric): Percent of people ages 25 to 34 yearsp_35_44 (Numeric): Percent of people ages 35 to 44 yearsp_45_54 (Numeric): Percent of people ages 45 to 54 yearsp_55_64 (Numeric): Percent of people ages 55 to 64 yearsp_65over (Numeric): Percent of people ages 65 years and older

This dataset represents an ongoing effort to approximate the geographic extents of 5 digit zip codes. The dataset was produced using a combination of methods and is based on several sets of source data. Methods include: 1) using local zip code polygon data obtained from counties and cities contained within these counties; 2) Identifying place locations (city, town, places) from the postal service website and address information system (AIS) and as a last result, building theissen polygons around usps places in unpopulated areas; and 3) editing line work using the 2000 Census TIGER line file's zip code attributes. In addition, AGRC has used the locations of mailing addresses known to be valid to fine tune this dataset.

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. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2020 Census.

ArcGIS tool and tutorial to convert the shapefiles into network format. The latest version of the tool is available at http://csun.uic.edu/codes/GISF2E.htmlUpdate: we now have added QGIS and python tools. To download them and learn more, visit http://csun.uic.edu/codes/GISF2E.htmlPlease cite: Karduni,A., Kermanshah, A., and Derrible, S., 2016, "A protocol to convert spatial polyline data to network formats and applications to world urban road networks", Scientific Data, 3:160046, Available at http://www.nature.com/articles/sdata201646

Overview

This dataset contains all DOMI Street Closure Permit data in the Computronix (CX) system from the date of its adoption (in May 2020) until the present. The data in each record can be used to determine when street closures are occurring, who is requesting these closures, why the closure is being requested, and for mapping the closures themselves. It is updated hourly (as of March 2024).

Preprocessing/Formatting

It is important to distinguish between a permit, a permit's street closure(s), and the roadway segments that are referenced to that closure(s).

• The CX system identifies a street in segments of roadway. (As an example, the CX system could divide Maple Street into multiple segments.)

• A single street closure may span multiple segments of a street.

• The street closure permit refers to all the component line segments.

• A permit may have multiple streets which are closed. Street closure permits often reference many segments of roadway.

The roadway_id field is a unique GIS line segment representing the aforementioned segments of road. The roadway_id values are assigned internally by the CX system and are unlikely to be known by the permit applicant. A section of roadway may have multiple permits issued over its lifespan. Therefore, a given roadway_id value may appear in multiple permits.

The field closure_id represents a unique ID for each closure, and permit_id uniquely identifies each permit. This is in contrast to the aforementioned roadway_id field which, again, is a unique ID only for the roadway segments.

City teams that use this data requested that each segment of each street closure permit be represented as a unique row in the dataset. Thus, a street closure permit that refers to three segments of roadway would be represented as three rows in the table. Aside from the roadway_id field, most other data from that permit pertains equally to those three rows. Thus, the values in most fields of the three records are identical.

Each row has the fields segment_num and total_segments which detail the relationship of each record, and its corresponding permit, according to street segment. The above example produced three records for a single permit. In this case, total_segments would equal 3 for each record. Each of those records would have a unique value between 1 and 3.

The geometry field consists of string values of lat/long coordinates, which can be used to map the street segments.

All string text (most fields) were converted to UPPERCASE data. Most of the data are manually entered and often contain non-uniform formatting. While several solutions for cleaning the data exist, text were transformed to UPPERCASE to provide some degree of regularization. Beyond that, it is recommended that the user carefully think through cleaning any unstructured data, as there are many nuances to consider. Future improvements to this ETL pipeline may approach this problem with a more sophisticated technique.

Known Uses

These data are used by DOMI to track the status of street closures (and associated permits).

Further Documentation and Resources

An archived dataset containing historical street closure records (from before May of 2020) for the City of Pittsburgh may be found here: https://data.wprdc.org/dataset/right-of-way-permits

This is an exercise on the use of Postal Code Conversion Files (PCCF) with GIS. (Note: Data associated with this exercise is available on the DLI FTP site under folder 1873-299.)

Land use codes assigned to parcels by the San Juan County WA Assessor's OfficeField DefinitionsUse Code - The first two digits represent the land use codes in WAC 458-53-030(5). The third and fourth digits are used internally by the San Juan County Assessor's Office to identify specific primary use or uses on a parcel.Description - Text that describes the Use Code.ABS Code - Abstract category of Use Code as seen in WAC 458-53-050.

TIGER road data for the MSA. When compared to high-resolution imagery and other transportation datasets positional inaccuracies were observed. As a result caution should be taken when using this dataset. TIGER, TIGER/Line, and Census TIGER are registered trademarks of the U.S. Census Bureau. ZCTA is a trademark of the U.S. Census Bureau. The Census 2000 TIGER/Line files are an extract of selected geographic and cartographic information from the Census TIGER data base. The geographic coverage for a single TIGER/Line file is a county or statistical equivalent entity, with the coverage area based on January 1, 2000 legal boundaries. A complete set of census 2000 TIGER/Line files includes all counties and statistically equivalent entities in the United States, Puerto Rico, and the Island Areas. The Census TIGER data base represents a seamless national file with no overlaps or gaps between parts. However, each county-based TIGER/Line file is designed to stand alone as an independent data set or the files can be combined to cover the whole Nation. The Census 2000 TIGER/Line files consist of line segments representing physical features and governmental and statistical boundaries. The boundary information in the TIGER/Line files are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement. The Census 2000 TIGER/Line files do NOT contain the Census 2000 urban areas which have not yet been delineated. The files contain information distributed over a series of record types for the spatial objects of a county. There are 17 record types, including the basic data record, the shape coordinate points, and geographic codes that can be used with appropriate software to prepare maps. Other geographic information contained in the files includes attributes such as feature identifiers/census feature class codes (CFCC) used to differentiate feature types, address ranges and ZIP Codes, codes for legal and statistical entities, latitude/longitude coordinates of linear and point features, landmark point features, area landmarks, key geographic features, and area boundaries. The Census 2000 TIGER/Line data dictionary contains a complete list of all the fields in the 17 record types.

   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists.

Users are encouraged to refer to the U.S. Census website for more information on ZCTAs: https://www.census.gov/programs-surveys/geography/guidance/geo-areas/zctas.html
and to the U.S. Postal Service for more information on ZIP Codes: https://faq.usps.com/

This CSV contains the code definitions for the "CODE" attribute of the Utah Dominant Vegetation layer in the SGID. These data were collected by the Utah Division of Wildlife Resources.

This feature layer contains records of code complaints in the City of Tempe. Records are updated Tuesday through Saturday..Please note that there may be multiple complaint records associated with a single address point. When viewing these data using GIS software, multiple records per address result in stacked points on the map. Data are provided in this exploded format to make it easier for users.The data found here are displayed at https://gis.tempe.gov/codecompliance albeit in a non-exploded form where points aren't stacked.Contact EmailLink: www.tempe.gov/codeData Source: AccelaData Source Type: GeospatialPublish Frequency: WeeklyPublish Method: Automatic (via ETL)