ArcGIS REST Services Directory
JSON

Layer: Jobs Census Block 24-inches (ID:11)

View In:   Map Viewer

Name: Jobs Census Block 24-inches

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The consequence indicators chosen to measure impact to PDAs include 2040 job spaces, 2040 residential units, projected growth in job spaces 2010-2040, and projected growth in residential units 2010-2040. The years and units reflect the parcel-level regional projections produced by Plan Bay Area’s Urban Sim model. Residential units are essentially households, but they refer to the physical space that can accommodate a household, not the people. Similarly, a job space is the physical space that accommodates a job, not the job itself. A development with 50 apartments has 50 residential units and an office building with space for 100 desks has 100 job spaces. Note that while PDAs are located in areas that are currently developed, they represent only the portion of developed area where increased density or transit investment is beneficial to regional land use and transportation objectives. PDAs were nominated by elected officials of local jurisdictions and approved by the ABAG Executive Board as part of Plan Bay Area 204056. The Consequence Analysis did not consider impacts to residential units or job spaces outside of PDA boundaries. Th PMT decided to use 2040 projections over 2010 values for both indicators because the impacts of sea level rise will be experienced in the future. This is the only indicator in the entire analysis for which robust future projections were readily available. The team decided to include projected growth in both job spaces and residential units as additional indicators in order to highlight PDAs where sea level rise will impact developments that have not yet been constructed. It is important to make this distinction because it is possible to intervene or modify designs for future developments. To calculate consequence, a key assumption made in this analysis is that once a parcel is exposed to flooding, even marginally, the entire number of residential unit in that parcel is considered impacted. This assumption reflects a conservative understanding that flooding has many direct and indirect impacts for a person’s ability to enjoy their home. Indirect impacts such as flooding of walkways, foundations, electrical systems may all contribute to an individual or family being displaced. Since we don’t have data to reflect these indirect impacts, we maintain the assumption that any flooding to a parcel impacts all the people living in it. This assumption works well for small parcels, but for large parcels this assumption serves as a limitation to the analysis. Large undeveloped parcels (e.g. former military lands) that have large projected growth for 2040, show high numbers of residential units impacted when exposed to flooding, despite the fact that the flooding may not be in the location where future development may occur. A related but separate limitation of this analysis is the existence of parcel boundaries that extend bayward of the MHHW line. These parcel boundaries intersect even small amounts of flooding despite the fact that no buildings exist in these parts of the parcel and inaccurately indicate impacted residential units. Future efforts should be made to refine parcel boundaries to both current and future developed areas on the shoreline. All data is in projected coordinate system NAD 1983 UTM Zone 10N. Please refer to the geodatabase metadata for more information. Read more about data sources and methods here: http://www.adaptingtorisingtides.org/wp-content/uploads/2020/03/ARTBayArea_Appendix_Final_March2020_ADA.pdf .

Copyright Text: This work was supported by SF Bay Conservation and Development Commission, Natural Capital Project, AECOM, and Silvestrum. BCDC (2020). Adapting To Rising Tides Bay Area Housing Jobs Consequence Analysis; SF Bay [spatial data file]. SF Bay Conservation and Development Commission. Accessed at https://explorer.adaptingtorisingtides.org/download .

Min. Scale: 0

Max. Scale: 0

Default Visibility: false

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:
Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 2/11/2022 6:47:30 PM

Schema Last Edit Date: 2/11/2022 6:47:30 PM

Data Last Edit Date: 2/11/2022 6:47:30 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat