This pdf document can be used to print a 32"x 21" wall map. This map also comes with street index for easy locating streets names.

City of Pittsburg (CA) boundary pre June 12th 2024. City limits have since been updated to include recent Annexations.

Pittsburgh Neighborhoods

This dataset now hosts multiple versions of the Pittsburgh Community Development Block Grant (CDBG) Census Block Group areas, obtained from the Pittsburgh GIS portal: one from 2014 and one from 2018.

The WPRDC also hosts a dataset containing CDBG Census Block Group tracts.

Files include data for bike lanes, protected bike lanes, trails, bike routes, shared lane markings, cautionary bike routes, and bridge data from the BikePGH Pittsburgh Bike Map. BikePGH developed this map in 2007 and has been publishing it both on paper and online ever since. See: http://bikepgh.org/maps for more info.

Pittsburgh Zoning Districts

This dataset includes the GIS shapefile for Pittsburgh Regional Transit's Park and Ride facilities. This layer is updated annually or on an as-needed basis as assets change.

Pittsburgh Landslide Prone Areas

Pittsburgh Public Work Environmental Service Divisions

Pittsburgh Greenways

These data were automated to provide an accurate high-resolution historical shoreline of Pittsburg to Antioch, CA suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://inport.nmfs.noaa.gov/inport/item/39808

Pittsburgh 25% Slope of Greater

Beautify The Burgh

PPA Meter Areas

City Limit Boundary for the City of Pittsburg (CA). City limits updated to reflect annexation in June 2024

Pittsburgh Bridges

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

City of Pittsburg General Plan from 2011.

Pittsburgh City Boundary

description: Pittsburgh Zoning Districts