ArcGIS REST Services Directory Login | Get Token
JSON

Layer: MTA.signals (ID: 7)

View In:   ArcGIS Online Map Viewer

Name: MTA.signals

Display Field: CNN

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: | A. PURPOSE | This dataset serves as an inventory of traffic signal and related equipment.| B. METHODOLOGY | N/A| C. UPDATE FREQUENCY | Signals Access database updated regularly (weekly, or quarterly) based on SRC work orders returned to date. GIS file updated quarterly. | D. OTHER CRITICAL INFO | Attribute data primarily maintained in the Access database. Spatial data exports are sourced from the Access database. To query for TSP (Transit Signal Prioritization), load this query into the "Definition Query" tab under Properties: \\mtanas\sfmtagis\04_GeoTools\Queries\TSP.exp| E. ATTRIBUTES |CNN: San Francisco’s street centerline network unique ID If there is more than one type of equipment at an intersection or mid-block segment, the unique ID will be based on the CNN plus 1 or 2;STREET1: Cross street #1;STREET2: Cross street #2;STREET3: Cross street #3;STREET4: Cross street #4;SUP_DIST: Supervisorial district(s);SIG_NUM: Maintenance field for Traffic Signal Shop;TYPE: Type of equipment present at this location--SIGNAL-Traffic signal,FLASHER- Traffic signal that is always on flashing mode,BEACON-Flashing yellow warning light,PENDING- Pending signal location, programmed and/or under construction,FUTURE- Candidate intersection for new signals contract, not yet funded,CALTRANS- Traffic Signal maintained and operated by the State,Others- DALY CITY, LIGHTED CROSSWALK, MESSAGE SIGN, LANE CONTROL, MASTER, NEW BEACON;IC_MAKE: Manufacturer of traffic signal controller;MODEL: Model of traffic signal controller;CABINET_SI: Size and type of traffic signal controller cabinet;SYSTEM_NUM: Number indicating to which system a signal belongs;MASTER: Identifies location of system master or TBC system reference intersection;BBS: Indicates presence of battery backup system (BBS);VEH_ACTUATED: Indicates presence and type of vehicle detection;PED_SIGNAL: Indicates presence of pedestrian signals--ALL- Pedestrian signals for all open crosswalks,SOME PHASES- pedestrian signals only across some crosswalks,NONE- no pedestrian signals for any crosswalks,PENDING- pending additional pedestrian signals to be installed as part of a signal project (upgrade, modification, or new signals) which is under design or construction and not yet completed;APS: Indicates presence and model of accessible pedestrian signal (APS) push buttons as well as which project the APS units were installed by;PED_ACTUATED: “YES” if intersection is pedestrian actuated either by conventional push buttons or by buttons integrated in APS units;MANUAL_CONTROL: Unknown field;TBC: Indicates presence and type of time based clock (TBC);INTERCONNECT: Type of traffic signal interconnect used for coordination;PREEMPT_PR: Indicates presence and order of priority of traffic signal preempts, including TSP (Transit Signal Prioritization);DETECTION: Type of detection used to activate traffic signal preempt;D_ATE2070: Date when traffic signal controller was upgraded to type 2070;PROJECT_NEW: Most recent project (new signals, modifications, or full upgrade) planned, pending, or under construction;PROJECT_OLD: Previous signal contract (new signals, modifications, or full upgrade) which has already been completed;YR_OF_CONTRACT: Approximate date of UPGRADED contract certification;LAST_UPGRADE: Year intersection was last upgraded (since 1990);NEW_SIGNALS: Field indicates project status for new signals project--FUTURE-Candidate intersection for new signals project, not yet funded,PENDING- Intersection under design or construction as part of new signals project, not yet completed,DONE- Construction at intersection as part of new signals project has been completed. Please note that only intersections included as part of contracts completed after 1990 are noted as “DONE”,NONE- No new signals project planned; MOD _PROJECT: Field indicates project status for signal modifications project--FUTURE- Candidate intersection for signal modifications project, not yet funded,PENDING- Intersection under design or construction as part of signal modifications project, not yet completed,DONE- Construction at intersection as part of signal modifications project has been completed. Please note that only intersections included as part of contracts completed after 1990 are noted as “DONE”,NONE- No signal modifications project planned;FULL_UPGRADE _PROJECT: Field indicates project status for full upgrade project--FUTURE- Candidate intersection for full upgrade project, not yet funded,PENDING- Intersection under design or construction as part of full upgrade project, not yet completed,DONE- Construction at intersection as part of full upgrade project has been completed. Please note that only intersections included as part of contracts completed after 1990 are noted as “DONE”, NONE- No full upgrade project planned; BEACON_FLASHER: Field indicates project status for installation of beacons and flashers--FUTURE- Candidate intersection for beacon and flashers contract, not yet funded,PENDING- Intersection under design or construction as part of beacon and flashers contract, not yet completed,DONE- Construction at intersection as part of beacon and flashers contract has been completed. Please note that only intersections included as part of contracts completed after 1990 are noted as “DONE”,NONE- No beacon and flashers contract planned;FUNDING: Source of funds used to pay for signal contract;RLCAM: “YES” if intersection has red light camera system;STARTYEAR: Year equipment (traffic signal) began operation if known;CALTRANS_ROUTE: Caltrans highway route number if applicable; CALTRANS: “X” if signals are maintained in full or in part by Caltrans;PERCENT_C: Percent of maintenance paid by Caltrans;SF: “X” if signals are maintained in part by City of San Francisco;PERCENT_SF: Percent of maintenance paid by City of San Francisco;PERCENT_PORT: Percent of maintenance paid by Port of San Francisco;LAMP_ASSGN: Maintenance field for Traffic Signal Shop;LAMP_SORT: Maintenance field for Traffic Signal Shop;SORT_ME: Maintenance field for Traffic Signal Shop

Copyright Text: | A. CUSTODIAN | Jarrett Hornbostel, jarrett.hornbostel@sfmta.com, SFMTA, Sustainable Streets, Transportation Engineering | B. CREATED | Unknown | C. VERSIONS | 20161222, Jarrett Hornbostel, quarterly update 201605, Jarrett Hornbostel, quarterly update, prep for MTA spatial data store 20150611, Jarrett Hornbostel, quarterly update, prep for MTA spatial data store

Default Visibility: false

MaxRecordCount: 10000

MaxSelectionCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields: Templates:
Capabilities: Query

Sync Can Return Changes: false

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Edit Fields Info:
Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:

Supported Operations:   Query   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata   Update Metadata