SCAG UrbanFootprint Scenario Planning Model (SPM)

SCAG UrbanFootprint
Scenario Planning Model (SPM)
Draft User Manual for Data Review and Editing
The data review and editing framework within SCAG UrbanFootprint SPM provides the user with a
number of data management and data review options. Using attribute query and map selector tools,
the user can explore data, summarize attributes, and edit configured layers. This documentation
covers basic SPM functionality for data review and editing.
Rev September 2014
Table of Contents
I.
Introduction................................................................................2-3
II. Data Management Framework – Site Map ......................... 4
III. User Interface Overview ..................................................... 5-13
1. Layer Management Window ............................................... 5
2. Map Tool Bar .........................................................................5-6
3. Explore Window ............................................................... 7-12
4. Edit Window .................................................................... 12-13
Appendix A – Data Dictionary .............................................. 14-19
Appendix B – Editable Fields ....................................................... 20
Appendix C – SCAG Land Use Codes .................................. 21-24
1|P a g e
I.
Introduction
SCAG UrbanFootprint-based Scenario Planning Model (SPM) is a land use planning,
modeling, and data management tool that is undergoing development to facilitate more
informed and collaborative planning by local jurisdictions and other stakeholders. Built on a
web-based geospatial platform with full co-benefit analysis capacity, the SPM allows
planners to develop future scenarios for land use, transportation infrastructure, and socioeconomic growth distribution.
The UrbanFootprint model, an Open Source software product being customized and
enhanced for use by California Metropolitan Planning Organizations (MPOs), serves as the
platform for the SPM. Currently, SCAG, Sacramento Area Council of Governments (SACOG),
and San Diego Association of Governments (SANDAG) are all contributing to the effort to
customize UrbanFootprint, and enhancements will be shared by all users and ultimately
made available to local jurisdictions across Southern California.
This pilot process is intended to demonstrate how local and regional data can be served to
local jurisdictions via the SPM web-based user interface, and to test initial functions focused
primarily on data review and editing. The data review and editing framework within SPM
provides the user with a number of data management and data review options. Using
attribute query and map selector tools, the user can explore data, summarize attributes, and
edit configured layers. This documentation covers basic SPM functionality for data
review and editing.
Ultimately, the SPM once completed will bring robust scenario-development functionality to
local jurisdictions across the SCAG region. For more information, please visit our website at
http://sp.scag.ca.gov.
System Requirements
The SPM is accessed via a web page. Ultimately, any web browser will be able to access the
system effectively, as will nearly all desktops, laptops, and tablets. For access to the pilot
site, there are some more refined, through fairly minimal, requirements:
-
A relatively recent (purchased in last 5 years) desktop or laptop computer running
the Windows, Mac OSX, or Linux operating systems. The current system has not
been optimized for tablet or touchscreen operating systems or interfaces.
-
Current version of Google Chrome web browser. Chrome is available via free
download at https://www.google.com/intl/en/chrome/browser/
2|P a g e
-
Mouse, track-ball, or trackpad-based input device (essentially all desktop or laptop
computers have this capability).
Note: If you experience difficulties in performing feature editing (e.g., feature selection,
querying, etc.) while being able to view maps on the SPM, first check your internet firewall
configuration with the local IT support. The URL of the SPM data management site should
be added to the trust list of firewall configuration in order to avoid block access by web
filters set up locally.
3|P a g e
II.
Data Management Framework - Site Map
3
2
4
1
1: Layer Management Window
2: Map Toolbar
3: Explore Window
4: Edit Window
5: Map Area
5
Figure 1: SPM Data Management Framework User Interface
4|P a g e
III.
User Interface Overview
1. Layer Management Window
The Layer Management window on the left side of the SPM user
interface displays layers that have been preloaded into the SPM,
and that can be turned on for display and activated for selection,
editing, and queries. See Appendix A for descriptions of the data
available via the SPM.
The user can select an active layer by clicking on the layer name
and the active layer will be highlighted in blue.
Important: Any map selection, attribute query, export
layer, export csv initiated by the user will occur on the
active layer regardless of it is visible or not.
Figure 2: Layer Management
Editable Layer: Any layer with the pencil icon next to it contains editable fields by the user.
See Appendix B for the list of editable fields.
Exporting Active Layer: The user can export the
Active Layer to a geodatabase (.gdb) by clicking on
the layers button on the Layers Tool Bar. The user
can initiate exporting by clicking ‘OK’ on a window
that opens up (see Figure 3) once the user clicks on
the ‘Export Active Layer – to gdb’ button. By
default, the exported layer is saved to the Windows
Figure 3: Layer Export
default Download folder.
Reordering Map Layers: The user can re-order layers on the
map by clicking on the arrow button on the right side of the
Layers Tool Bar. This button will open a window where the
user can order the layers by clicking on the layer name and
dragging it into the order the user prefers within the visible
list. This order corresponds to the layer order on the map.
Figure 4: Re-Order Layers
2. Map Tool Bar
Clicking on an icon on the map tool bar
allows the user to zoom and navigate around
Figure 5: Map Tool Bar
the map as well as select and identify map
5|P a g e
features. The user can hover their pointer to get the ‘tool tip’ to identify what button corresponds
with each selector.
Zoom to Project Extent: This tool allows the user to zoom the current map to the project
map extent. The project in the SPM refers to a local jurisdiction or County.
Zoom to Selection Extent: This tool allows the user to zoom the current map to the extent
of selected features of the Active Layer.
Clear Selection: This tool clears the selected features of the Active Layer.
Navigate: This tool allows the user to navigate around the map by clicking and dragging on
the map. The user can hold ‘Shift’ and drag to create zoom extent.
Point Selector: The point selector selects the feature that intersects with a point where the
user clicks on the map.
Rectangle Selector: The rectangle selector selects the feature that intersects with a
rectangle formed by the user clicking and dragging across the map.
Polygon Selector: The polygon selector selects the feature that intersects with a user
defined polygon shape formed by the user defining each node of the polygon by clicking on
the map. Double clicking will stop forming the polygon selection.
Identify: This tool is activated when a feature is selected. The Identify tool opens a
moveable summary window where the user can view the attributes of the selected feature.
Query: The Query tool opens a moveable query window where the user can access the SPM
attribute querying functionality. See Attribute Query section for more detail.
Figure 6: Query via pop-up window
6|P a g e
3. Explore Window
The Explore Window allows the user to toggle between Scenario Manager, Attribute Query,
Attribute Aggregation, and Approval/Merge options. By clicking on the ‘Explore’ button on the top
of the screen, the map selection will resize and default to the Scenario Manager screen. See Figure 7
below.
Figure 7: Manage Scenario via Explore top section
On the left of the Explore Window, the user can toggle between the following options:
-
Scenario Manager: The user can switch between Master and Draft Scenarios
and see metadata about the active scenario.
Attribute Query: The user can define attribute queries and join tables to explore
the data.
Attribute Aggregation: The user can define aggregate queries to summarize the
data.
Approval/Merge: The user who has a manager level or director level permission can
approve edits and merge those edits into mater versions of the editable layers.
3-1 Scenario Manager
This screen allows the user to view and change the
active scenario (layer group) and to view top-level
demographic characteristics of the current data. By
default, when a user logs in, the active scenario is the
Draft scenario.
Note: A Scenario in the SPM consists
of a group of layers and specific user
metadata associated with those layer
versions.
7|P a g e
-
Draft and Master Scenario
The current system gives the user an option to switch between a Draft Scenario and a
Master Scenario by clicking on the ‘Draft’ or ‘Master’.
Important: Layers are only
Both contain the same layers, but store those layers
directly editable via the edit
as different versions. In the Draft Scenario, the user
can edit, approve, and merge changes to the editable screen when the user is working
in a Draft Scenario.
layers. The Master Scenario contains all the
approved and merged updates from the Draft
Scenario.
The user cannot directly edit layers in a Master Scenario. Any edits to a layer must be made
in the Draft Scenario and then approved and merged into the Master Scenario through the
Approval/Merge interface (see following section for documentation on Approval and
Merging). While in the scenario top section, the user can see high level summary statistics of
the active scenario.
3-2 Attribute Query
The attribute query functionality and the map selector tools in the SPM are linked by default.
When a user selects features on the map with the map selector tools, the attributes will
populate in the query window. If the user inputs an attribute query with no map selection, the
map will show the features selected from the attribute query. The user also has the option to
use attribute selections and map selections in combination.
SPM attribute query functionality can also be accessed by clicking on the ‘Query’ button in the
Map Tool bar. Each option provides the same functionality but provides a different layout to
accommodate user preference and varying work flows.
-
Querying Attributes: SPM attribute querying functionality utilizes SQL syntax to tell the
database what features the user would like to select. The user can select attribute names
from a drop down list by clicking on the arrow button next to the ‘Where’ clause or type
them in.
The following comparison/equality operators are supported:
Greater than : >
Less than : <
Greater than or equal to : >=
Less than or equal to : <=
Equals : =
Not equal: !=
Figure 8: Query Window
8|P a g e
For querying strings, the following syntax can be used (must be capitals):
BEGINS_WITH : String begins with a certain letter or group of letters
ENDS_WITH : String ends with a certain letter or group of letters
CONTAINS: String contains a certain letter or group of letters
Multiple attribute queries are supported using the following syntax (must be capitals):
AND : SQL ‘and’ syntax, attributes must meet both query requirements
OR : SQL ‘or’ syntax, attributes must meet either query requirements
Query Examples:
Example 1: Returns all rows with land use code 1200 with a dwelling
unit count greater than 2
lu12 = 1200 AND du>=2
Example 2: Returns all parcels with an apn that begins with 580 or an
apn that begins with 104
apn BEGINS_WITH ‘580’ OR apn BEGINS_WITH ‘104’
*Any string query must have quotation marks around values.
-
Joining Tables: SPM allows the user to seamlessly join and query spatial tables of different
geography types and geographic scales. Each layer in the system is tagged with a join type
when it is imported. The join types include attribute joins, polygon to polygon, polygon to
centroid, and centroid to polygon joins. This processing is handled ‘behind the scenes’ in the
system.
The user utilizes these pre-defined join
tables by selecting the desired table from
the drop down button in the query
window. Having selected a table to join,
the user will have access to all fields in
that join table. Any query making use of
join fields will utilize the pre-defined
spatial or attribute relationship.
Figure 9: Join drop-down view
9|P a g e
Important: If the user is querying a field from the join table that has the
same name as a field in the source table, the system defaults to the
source table field. To query the join table field, the user must write the
name_of_join_table.field_name or select it from a drop down list by
clicking the arrow next to the ‘Where’ clause in the Query window.
-
Query Options: The user has a number of
options to form their query and to show
helpful information in the user interface:
Figure 10: Query Toggles/Buttons
Limit Results to Selected Area: If the user has selected features with a map selector tool
and input an attribute query, they have the option to limit the query result to the map
selection or apply them to the whole dataset.
Show Selection Shape on Map: The user can toggle on and off the map selection shape
Clear Button: Clears the selection
Query Button: Executes the query
3-3 Attribute Aggregation
Similar to querying syntax, aggregation syntax
makes use of the SQL database language. The
user has options to aggregate any field in the
active table and any field in a table that has
been joined. Aggregation includes both
aggregation operators and ‘group by’ results.
The user can also decide whether to aggregate
within the active map selection or from the
Figure 11: Aggregation window
entire dataset.
-
Aggregate: The following aggregation operators are active in SPM:
SUM(field_name): Sum of the values of the assigned field
COUNT(field_name): Count the number rows from the assigned field
AVG(field_name): Average of the values of the assigned field
MAX(field_name): Maximum value in the assigned field
MIN(field_name): Minimum value in the assigned field
Multiple fields can be aggregated at the same time by separating the aggregation functions
with commas. An example of this syntax is as follows:
SUM(field_name), AVG(field_name2), COUNT(field_name3), SUM(field_name4)
10 | P a g e
-
Group By: SPM allows the user to specify one or more group by fields. ‘Group By’ allows the
user to summarize fields by categorical variables. A common group by field is a parcel land
use code column, but any categorical variable can be used. If a group by column is specified,
aggregations will return values for each distinct value in the group by column.
Aggregation/Group By Example:
Example 1: Sum all the Year 2012 employment from the TAZ record by
unique TAZ id and to count the number of parcels within each TAZ
from the parcel data set. Limit the results to a painted selection.
3-4 Approval/Merging
The Approval/Merging interface is accessible to users with manager or director level
permissions. The approval interface allows data managers to review and approve/reject edits
made by any user. Through easy to use drop-down queries, edited features can be reviewed,
approved or rejected, and merged into the master version.
Figure 12: Approval Interface
11 | P a g e
-
Approving/Rejecting Edits: The approval interface acts
on the active layer. When a data manager is ready to
approve or reject edits, they can load all pending edited
rows (needing approval) by selecting the correct query
form the drop down list. If the user would like to review
previously approved or rejected features, the system
provides those options as well.
Figure 13: Approval Query Options
Once the data has loaded, the user can highlight a given row (or group of rows by holding
down CTRL) to see the location on the map. The user can
approve or reject the highlighted rows by pushing the
corresponding “Approve” and “Reject” buttons. If the user
would like to simply approve or reject all edits, toggling
‘Select All’ will highlight all rows. Once highlighted, all rows
can then be approved or rejected. Once rows have been approved or rejected, the user must
save their edits. Any approval or rejections that are not saved will be ignored.
-
Merging: Once features have been reviewed and edits
approved, the data manager can merge all approved
features into the Master version of the layer. Within the
approval interface, the user can toggle the Merge screen.
This will provide the user with the option to merge
approved features. After clicking on the Merge button, a
backend process will handle filtering and merging data
tables.
4. Edit Window
The Edit Window allows the user to edit or comment upon select layer attributes. Currently attribute
editing requires custom edit forms to be made specifically for configured layers in SPM; any layer
not configured for editing is not editable (see Appendix B for the list of editable layers). If a layer
has been configured, when that layer is active in the layer manager, the user can open an edit
window by clicking on the ‘Edit’ button on the right side of the screen to view and edit specific
attributes. See Figure 14 below.
The editor operates on the currently selected features of the active layer. If there is more than one
feature selected, any changes made in the editor window will populate all rows with those values
unless the layer is configured to only allow editing of one row at a time.
In case where a layer is configured to only allow editing of one row at a time,
following message will be displayed indicating that only one record at a time
can be edited.
12 | P a g e
To save changes to edited attributes the user must push the save button when
finished editing. If the user changes the selected features without saving changes,
those changes will not be saved.
Figure 14: Attribute editing window
13 | P a g e
Appendix A - Data Dictionary
Background Imagery
This group of layers features recent, high-resolution imagery and street maps where users
can select as a base or background layer and identify street and road network with street
names and address search. These layers as ‘served’ directly from commercial or related
services into the SPM system.
Google Map
Google’s streets and related labels on a standard (non-aerial) map. This map includes
Google’s depiction of fixed rail and other major transit lines.
Google Aerial
Google’s aerial imagery along with street, building, and other useful labels.
Google Labels
Google’s streets and related labels, without any imagery.
Open Street Map
Streets and related labels on a standard map served by OpenStreetMap.
Draft/Master
The following layers grouped under Draft or Master present jurisdictional level land use
and administrative or planning boundaries, some of which include editable fields. Only
authorized users with permissions to approve or reject changes made on Draft layers have
access to Master layers (see Approval/Merging section for more detail).
General Plan, zoning, and existing land use data are shown at the parcel level. Because
SCAG’s parcel level database does not support multiple uses on a single parcel, data may be
generalized in some areas. Due to this limitation, if site specific data is necessary, users
should always reference a local agency’s adopted documents or field surveys to determine
actual land use designations.
2012 Existing Land Use Parcels
The base year of the 2016-2040 RTP/SCS is 2012. To develop the base year
existing land use data, SCAG used property land use information acquired
from Digital Map Products (DMP) and SCAG’s 2008 existing land use data. DMP land use
codes were converted to SCAG’s standardized Existing Land Use code system. For detailed
information on the Existing Land Use codes, please refer to Table B1 in Appendix B.
14 | P a g e
Beginning in August 2013, the 2012 existing land use maps were reviewed by local
jurisdictions and revised based on the local input and comments. The information available
via SPM reflects the local inputs received by August 22, 2014.
General Plan Parcels
The general plan and zoning documents, maps, and/or GIS shapefiles collected
from local jurisdictions were coded into GIS shapefiles at the parcel level.
Parcel boundary data were acquired from DMP. The General Plan Parcels layer is prepared
with SCAG’s standardized General Plan codes. For detailed information on the standardized
general plan codes, please refer to Table B2 in Appendix B. The information available via
SPM reflects the local inputs received by August 22, 2014. Scenario Planning Zones
Scenario Planning Zone (SPZ) is a spatial boundary that SCAG developed as the minimum
unit of scenario planning and analysis for the SPM. It was developed by grouping parcels of
uniform or compatible land uses while maintaining manageable size for capturing local land
use benefits on transportation, varied by development density and intensity. The SPZs
maintain a nesting relationship with existing boundaries such as parcel, Tier 2/3 TAZ,
Community Planning Area, City, Subregion, and County.
Jurisdiction Boundary and Sphere of Influence
Jurisdiction boundary and Sphere of Influence information are from each
County’s Local Agency Formation Commissions (LAFCO). The information
included here are as of July 2012. SCAG uses the data directly from LAFCO as the legitimate
source based on the legal requirement of SB385. For inaccuracy or changes in jurisdiction
boundaries or sphere of influences, local jurisdictions need to contact LAFCO to reflect the
most accurate boundaries.
Tier2 TAZ
SCAG developed the Transportation Analysis Zones (TAZ) for the SCAG Region,
based on the 2010 Tiger Census Block. This is used to facilitate Travel Demand
and Land Use Modeling needs at SCAG.
County
This group of countywide layers includes: (1) resource areas and farmland1 information in
the region obtained from state and federal data sources; (2) information related to a transit
priority project compiled pursuant to Government Code Section 65080(b)(2)(H); and (3)
boundaries of administrative district and Census geography.
1
See Government Code section 65080.01 for definitions of “resource areas” and “farmland.”
15 | P a g e
Farmland
Farmland information was obtained from the Farmland Mapping &
Monitoring Program (FMMP) in the Division of Land Resource Protection in
the California Department of Conservation. The FMMP is to provide consistent and
impartial data and analysis of agricultural land use and land use changes throughout the
State of California. SCAG obtains the Important Farmland Map created by FMMP. The study
area is in accordance to the soil survey developed by National Resources Conservation
Service (NRCS) in the United States Department of Agriculture. Important Farmland Map is
biennially updated based on a computer mapping system, aerial imagery, public review, and
field interpretation. The minimum land use mapping unit is 10 acres. The classification
system of farmland (column “polygon_fy”) was developed by combing technical soil rating
and current land use, as shown in Table A4. The information available via SPM reflects the
local inputs received by August 22, 2014.
Table B1: Definition of Types of Farmland (polygon_fy)
Symbol
Value
Prime Farmland (P)
Farmland of Statewide
Importance (S)
UNIQUE FARMLAND (U)
Farmland of Local
Importance (L)
Grazing Land (G)
Urban and Built-up
Land (D)
Other Land (X)
Water (W)
Definition
Farmland with the best combination of physical and chemical
features able to sustain long term agricultural production. This land
has the soil quality, growing season, and moisture supply needed to
produce sustained high yields. Land must have been used for
irrigated agricultural production at some time during the four years
prior to the mapping date.
Farmland similar to Prime Farmland but with minor shortcomings,
such as greater slopes or less ability to store soil moisture. Land must
have been used for irrigated agricultural production at some time
during the four years prior to the mapping date.
Farmland of lesser quality soils used for the production of the state's
leading agricultural crops. This land is usually irrigated, but may
include non-irrigated orchards or vineyards as found in some
climatic zones in California. Land must have been cropped at
some time during the four years prior to the mapping date.
Land of importance to the local agricultural economy as
determined by each county’s board of supervisors and a local
advisory committee.
Land on which the existing vegetation is suited to the grazing of
livestock. This category was developed in cooperation with the
California Cattleman’s Association, University of California
Cooperative Extension, and other groups interested in the extent of
grazing activities. The minimum mapping unit for Grazing Land is 40
acres.
Land occupied by structures with a building density of at least 1 unit
to 1.5 acres, or approximately 6 structures to a 10-acre parcel. This
land is used for residential, industrial, commercial, institutional,
public administrative purposes, railroad and other transportation
yards, cemeteries, airports, golf courses, sanitary landfills, sewage
treatment, water control structures, and other developed purposes.
Land not included in any other mapping category. Common
examples include low density rural developments; brush, timber,
wetland, and riparian areas not suitable for livestock grazing;
confined livestock, poultry or aquaculture facilities; strip mines,
borrow pits; and water bodies smaller than 40 acres. Vacant and
nonagricultural land surrounded on all sides by urban development
and greater than 40 acres is mapped as Other Land.
Perennial water bodies with an extent of at least 40 acres.
16 | P a g e
Large government land holdings, including National Parks, Forests,
and Bureau of Land Management holdings are not included in
FMMP’s survey area.
Not Surveyed (Z)
CPAD Holdings
California Protected Area Database (CPAD) is a GIS inventory of all publicly
owned protected open space lands in the State of California through fee
ownership. GreenInfo Network has prepared CPAD by aggregating and cross-checking
various open space data from state, local and other agencies.
The “protected” status in CPAD does not refer to a specific level of conservation for
biodiversity values, but a general commitment to maintain the property for open space uses.
The lands in CPAD are defined based on the agencies that own the fee title to the property,
not the managing parties. Also, CPAD is not the database of all public lands, but that of all
“publicly owned” open space. The owning agencies include public and non-profits, but
currently the private owners and properties under the use of easements are excluded.
The data available via SPM is presented by ownership (column “LAYER”) and reflects the
local inputs received by August 22, 2014.
Table B2: CPAD Holdings by Ownership – Legend
Symbol
Value
US Forest Service
US Bureau of Land Management
National Park Services
US Fish and Wildlife Service
Other Federal
California Department of Parks and Recreation
California Department of Fish and Wildlife
Other State
County
City
Non-Governmental Organization
Special District
US Military/Defense
Habitat Conservation Areas
This data set is from the Natural Community Conservation Planning (NCCP)
program of California Department of Fish and Wildlife. The primary objective
of the NCCP program is to conserve natural communities at the ecosystem
17 | P a g e
level, while accommodating compatible land use. By considering the long-term stability of
wildlife and plant communities, and including key interests in the planning process, it aims
at anticipating and preventing the controversies in the surrounding areas of the species.
A local agency is in charge of monitoring the development of a conservation plan in
cooperation with landowners, environmental organizations and other interest parties. The
Department of Fish and Wildlife provides necessary support, direction, and guidance to
NCCP participants.
Endangered Species
SCAG obtained the California Natural Diversity Database (CNDDB) July 2013
version developed by the California Department of Fish and Wildlife’s
Biogeographic Data Branch (BDB). The CNDDB is a library of the location and
condition of species of rate and sensitive plants, animals, and natural communities in
California. It is updated on a continuous basis to be consistent and current, but cannot be an
exhaustive and comprehensive inventory of rare species and natural communities. Field
verification for the absence and presence of sensitive species is required by the end users.
The types of elements (column “ELMTYPE”) are specified as four categories of plant, animal,
terrestrial community, and aquatic community, as shown in the Table A3.
Table B3: Definition of Types of Elements (ELMTYPE)
Symbol
Value
Definition
1
Plant (ELMCODEs beginning with “P” or “N”)
2
Animal (ELEMCODEs beginning with “A” or “I”)
3
4
Terrestrial community (ELMCODEs beginning with “CT”)
Aquatic community (ELMCODEs beginning with ”CA”, “CE”, CL”, “CM” or “CR”
The precision or accuracy level (ACC_CLASS) represents spatial uncertainty on a scale of
one to ten, indicating both accuracy type and accuracy value.
Table B4: Definition of Precision or Accuracy Level (ACC_CLASS)
Value
Definition
80 meters
1: Specific bounded area with an 80 meter radius
Specific
2: Specific bounded area
Nonspecific
3: Non-specific bounded area
1/10 mile
4: Circular feature with a 150 meter radius (1/10 mile)
1/5 mile
5: Circular feature with a 300 meter radius (1/5 mile)
2/5 mile
6: Circular feature with a 600 meter radius (2/5 mile)
3/5 mile
7: Circular feature with a 1,000 meter radius (3/5 mile)
4/5 mile
8: Circular feature with a 1,300 meter radius (4/5 mile)
1 mile
9: Circular feature with a 1,600 meter radius (1 mile)
5 mile
10: Circular feature with a 8,000 meter radius (5 miles)
18 | P a g e
Flood Zones
The flood zones data is based on the Digital Flood Insurance Rate Map
(DFIRM), obtained from Federal Emergency Management Agency (FEMA) in
October 2013. The DFIRM Database is a digital version of the FEMA Flood Insurance Rate
Maps (FIRM) that is designed for use with digital mapping and analysis software. The FIRM
is created by FEMA for the purpose of floodplain management, mitigation, and insurance
activities for the National Flood Insurance Program (NFIP).
The FIRM includes data on the 100-year (1% annual chance of occurring) and 500-year (0.2%
annual chance of occurring) floodplains (column “flood_zone”). This data set included in the
SPM is prepared at the county level for better presentation of the flood areas, which is
normally not constrained to city limits.
Major Transit Stops
The Major Transit Stop information is extracted from 2035 planned year data in the 20122035 RTP/SCS Amendment #1. It is defined as a site containing a rail transit station, a ferry
terminal served by either a bus or rail transit service, or the intersection of two or more
major bus routes with a frequency of service interval of 15 minutes or less during the
morning and afternoon peak commute periods (CA Public Resource Code Section 21064.3).
It also includes major transit stops that are included in the applicable regional
transportation plan.
High Quality Transit Corridors
The High Quality Transit Corridors information is extracted from 2035
planned year data in the 2012-2035 RTP/SCS Amendment #1. It is defined as
a corridor with fixed route bus service with service intervals no longer than 15 minutes
during peak commute hours.
High Quality Transit Areas
An area within one-half-mile of either a major transit stop or a high quality
transit corridor, extracted from 2035 planned year data in the 2012-2035
RTP/SCS Amendment #1.
Transit Priority Areas
An area within one-half mile of a major transit stop that is existing or planned,
if the planned stop is scheduled to be completed within the planning horizon
included in a Transportation Improvement Program adopted pursuant to
Section 450.216 or 450.332 of Title 23 of the Code of Federal Regulations. To assist in
identifying the transit priority areas, this data layer identifies the major transit stops and
their surrounding areas in one-half mile radius distance. Please note that this layer is still in
draft form and may undergo changes as SCAG continues to update its transportation
network. Updates to this information will be forthcoming as information becomes available.
19 | P a g e
Appendix B – Editable Fields by Data Layer
Table A1: Editable Fields by Data Layer
Layer
Field Name
density
General Plan Parcels
General Plan Densities: Lower End
high
General Plan Densities: Higher End
zone_code
scag_gp_code
comments
Scenario Planning Zones
Tier2 TAZ
Zone Code
City General Plan Code
2012 SCAG Land Use Code and Description
User Comments
pop12
2012 Total Population
hh12
2012 Total Households
emp12
2012 Total Employees
pop20
2020 Total Population
hh20
2020 Total Households
emp20
2020 Total Employees
pop35
2035 Total Population
hh35
2035 Total Households
emp35
2035 Total Employees
pop40
2040 Total Population
hh40
2040 Total Households
emp40
2040 Total Employees
comments
User Comments
comments
User Comments
pop12
2012 Tier2 TAZ Population
hh12
2012 Tier2 TAZ Households
emp12
2012 Tier2 TAZ Employees
pop20
2020 Tier2 TAZ Population
hh20
2020 Tier2 TAZ Households
emp20
2020 Tier2 TAZ Employees
pop35
2035 Tier2 TAZ Population
hh35
2035 Tier2 TAZ Households
emp35
2035 Tier2 TAZ Employees
pop40
2040 Tier2 TAZ Population
hh40
2040 Tier2 TAZ Households
emp40
2040 Tier2 TAZ Employees
comments
Existing Land Use Parcels
General Plan Densities: Density
low
city_gp_code
Jurisdiction Boundary
Description
lu12
comments
User Comments
2012 SCAG Existing Land Use Code
User Comments
20 | P a g e
Appendix C - SCAG Land Use Codes
Table C1:2012 SCAG Existing Land Use Codes – Legend
Legend
Land Use Description
Single Family Residential
Multi-Family Residential
Mobile Homes and Trailer Parks
Mixed Residential
Rural Residential
General Office
Commercial and Services
Facilities
Education
Military Installations
Industrial
1110 Single Family Residential
1111 High-Density Single Family Residential
1112 Low-Density Single Family Residential
1120 Multi-Family Residential
1121 Mixed Multi-Family Residential
1122 Duplexes, Triplexes and 2- or 3-Unit Condominiums and
Townhouses
1123 Low-Rise Apartments, Condominiums, and Townhouses
1124 Medium-Rise Apartments and Condominiums
1125 High-Rise Apartments and Condominiums
1130 Mobile Homes and Trailer Parks
1131 Trailer Parks and Mobile Home Courts, High-Density
1132 Mobile Home Courts and Subdivisions, Low-Density
1140 Mixed Residential
1100 Residential
1150 Rural Residential
1210 General Office Use
1211 Low- and Medium-Rise Major Office Use
1212 High-Rise Major Office Use
1213 Skyscrapers
1200 Commercial and Services
1220 Retail Stores and Commercial Services
1221 Regional Shopping Center
1222 Retail Centers (Non-Strip With Contiguous Interconnected
Off-Street Parking)
1223 Retail Strip Development
1230 Other Commercial
1231 Commercial Storage
1232 Commercial Recreation
1233 Hotels and Motels
1240 Public Facilities
1241 Government Offices
1242 Police and Sheriff Stations
1243 Fire Stations
1244 Major Medical Health Care Facilities
1245 Religious Facilities
1246 Other Public Facilities
1247 Public Parking Facilities
1250 Special Use Facilities
1251 Correctional Facilities
1252 Special Care Facilities
1253 Other Special Use Facilities
1260 Educational Institutions
1261 Pre-Schools/Day Care Centers
1262 Elementary Schools
1263 Junior or Intermediate High Schools
1264 Senior High Schools
1265 Colleges and Universities
1266 Trade Schools and Professional Training Facilities
1270 Military Installations
1271 Base (Built-up Area)
1272 Vacant Area
1273 Air Field
1274 Former Base (Built-up Area)
1275 Former Base Vacant Area
1276 Former Base Air Field
1300 Industrial
1310 Light Industrial
1311 Manufacturing, Assembly, and Industrial Services
1312 Motion Picture and Television Studio Lots
1313 Packing Houses and Grain Elevators
1314 Research and Development
1320 Heavy Industrial
1321 Manufacturing
1322 Petroleum Refining and Processing
21 | P a g e
Transportation, Communications,
and Utilities
1323 Open Storage
1324 Major Metal Processing
1325 Chemical Processing
1330 Extraction
1331 Mineral Extraction - Other Than Oil and Gas
1332 Mineral Extraction - Oil and Gas
1340 Wholesaling and Warehousing
1400 Transportation, Communications, and Utilities
1410 Transportation
1411 Airports
1412 Railroads
1413 Freeways and Major Roads
1414 Park-and-Ride Lots
1415 Bus Terminals and Yards
1416 Truck Terminals
1417 Harbor Facilities
1418 Navigation Aids
1420 Communication Facilities
1430 Utility Facilities
1431 Electrical Power Facilities
1432 Solid Waste Disposal Facilities
1433 Liquid Waste Disposal Facilities
1434 Water Storage Facilities
1435 Natural Gas and Petroleum Facilities
1436 Water Transfer Facilities
1437 Improved Flood Waterways and Structures
1438 Mixed Utilities
1440 Maintenance Yards
1441 Bus Yards
1442 Rail Yards
1450 Mixed Transportation
1460 Mixed Transportation and Utility
Mixed Commercial and Industrial
1500 Mixed Commercial and Industrial
Mixed Residential and Commercial
1600 Mixed Residential and Commercial
Open Space and Recreation
Agriculture
Vacant
Water
1800
1810
1820
1830
1840
1850
1860
1870
1880
2000
2100
2200
2300
2400
2500
2600
2700
3000
3100
3200
3300
3400
1900
4000
4100
4200
4300
4400
4500
Open Space and Recreation
Golf Courses
Local Parks and Recreation
Regional Parks and Recreation
Cemeteries
Wildlife Preserves and Sanctuaries
Specimen Gardens and Arboreta
Beach Parks
Other Open Space and Recreation
Agriculture
Cropland and Improved Pasture Land
2110 Irrigated Cropland and Improved Pasture Land
2120 Non-Irrigated Cropland and Improved Pasture Land
Orchards and Vineyards
Nurseries
Dairy, Intensive Livestock, and Associated Facilities
Poultry Operations
Other Agriculture
Horse Ranches
Vacant
Vacant Undifferentiated
Abandoned Orchards and Vineyards
Vacant With Limited Improvements
Beaches (Vacant)
Urban Vacant
Water
Water, Undifferentiated
Harbor Water Facilities
Marina Water Facilities
Water Within a Military Installation
Area of Inundation (High Water)
Under Construction
1700 Under Construction
Undevelopable or Protected Land
8888 Undevelopable or Protected Land
Unknown
9999 Unknown
22 | P a g e
Table C2: 2012 SCAG General Plan Land Use Codes – Legend
Legend
Land Use Description
Single Family Residential
1110 Single Family Residential
Multi-Family Residential
1120 Multi-Family Residential
Mobile Homes and Trailer Parks
1130 Mobile Homes and Trailer Parks
Mixed Residential
1140 Mixed Residential
1100 Residential
Rural Residential
1150 Rural Residential
General Office
1210 General Office Use
Commercial and Services
1200
1220
1221
1230
1233
Facilities
1240 Public Facilities
1250 Special Use Facilities
Education
1260 Education – K-12
1265 Education – College
Military Installations
1270 Military Installations
General Commercial
Retail and Commercial and Services
Regional Shopping Center
Other Commercial
Hotels and Motels
Transportation, Communications, and
Utilities
1300
1310
1311
1320
1321
1340
1410
1420
1430
Mixed Commercial and Industrial
1500 Mixed Commercial and Industrial
Mixed Residential and Commercial
1600 Mixed Residential and Commercial
Open Space and Recreation
1810
1820
1830
1840
1850
1860
1870
1880
Vacant
1900 Urban Vacant
3000 Vacant
Agriculture
2000 Agriculture
Water
4000 Water
Industrial
General Industrial
Light Industrial
Light Manufacturing, Assembly, and Industrial Services
Heavy Industrial
Heavy Manufacturing
Wholesaling and Warehousing
Transportation
Communication Facilities
Utility Facilities
Golf Courses
Local Parks and Recreation
State and National Parks and Recreation
Cemeteries
Wildlife Preserves and Sanctuaries
Specimen Gardens and Arboreta
Beach Parks
Other Open Space and Recreation
23 | P a g e
Specific Plan
7777 Specific Plan
Undevelopable or Protected Land
8888 Undevelopable or Protected Land
Unknown
9999 Unknown
24 | P a g e