ArcGIS REST Services Directory Login | Get Token
Home > services > Traffic > traffic (FeatureServer) > MTA.signs API Reference
JSON

Layer: MTA.signs (ID: 6)

View In:   ArcGIS Online Map Viewer

Name: MTA.signs

Display Field: ASSET_NAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 7 0;"><SPAN>| A. METHODOLOGY | Sign shop assets are manually added and updated via the Sign Shop Web Map Editor: https://sfgov.maps.arcgis.com/apps/webappviewer/index.html?id=a28072f040a84754a56163003e2b1fc2 </SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>| B. UPDATE FREQUENCY | Multiple times per day, Monday through Friday 7am to 5pm</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN>| C. OTHER CRITICAL INFO | Delineators and bike racks use the "NUM_OF_ASSETS" field to indicate how many assets are represented by a single point. Use values of 5 and 10 where possible. New are located along the curb. Old assets will be gradually moved to the curb. The 'zero point' of the blockface (where measurements begin) needs further SFMTA internal discussion and alignment. Currently, the MTA.curb layer sourced from SFGIS in 2017/18 uses the intersection of property lines to splice the curb into blockfaces and curb returns. Traffic Engineering uses a different methodology reliant on the location of the crosswalk.</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN>| D. ATTRIBUTES |</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN>OBJECTID_1: System (ArcGIS) generated unique identifier;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>ASSET_ID: Unique ID generated by HxGN EAMS and synced back to ArcGIS via Logic Apps. Does not populate for 'cancelled' features;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_CODE: Alphanumeric value associated with unique combination of LEGEND and SIGN_SIZE. Uses domain EAMS_Signshop_SignCode. Domain created from table MTA.signshop_domain_signcode;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>LEGEND: Text that appears on the sign, or if not a sign, a brief description of asset type. Populated via Logic App which uses the MTA.signshop_contingent_reference table to look up the value based on the sign code;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_SIZE: Dimensions of the sign. Populated via Logic App which uses the MTA.signshop_contingent_reference table to look up the value based on the sign;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>STREET_ADDRESS_RANGE: Lowest to highest address number and name of street asset is located on. Null for intersection assets;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_SUPPORT: Type of structure sign is affixed to. Uses domain EAMS_Signshop_SignSupport. Domain created from table MTA.signshop_domain_signsupport;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>FROM_ST: For assets on blockfaces/street segments, street name of first intersecting street. Based on CNN street segments, is not directional. For 3+ way intersections, street name(s) of intersecting street(s);</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>TO_ST: For assets on blockfaces/street segments, street name of second intersecting street. Based on CNN street segments, is not directional. Null for intersection assets;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>INTERSECTION: Street names of two intersecting streets. Null for assets on street segment / blockface;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>CORNER_SIDE_FACING: Description of where asset is located in an intersection. Somewhat legacy field from previous tabular database architecture. Uses domain EAMS_Signshop_SideFacing. Domain created from table MTA.signshop_domain_sidefacing;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>ARROW_DIR: Direction of arrow for signs with arrows, such as ONE WAY. Uses domain EAMS_Signshop_ArrowDirection. Domain created from table MTA.signshop_domain_arrowdir;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>BAPA: Whether asset requires Breakaway Pole Assembly;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>BOOM_TRUCK: Whether the asset requires a boom truck to install;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>CLEARANCE_PERMIT: Whether the asset requires a clearance permit;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>NUM_OF_ASSETS: Number of assets, such as in the case of delineators and bike racks. Should use value of 5 or 10;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>CONDITION: Condition of the asset. Uses domain EAMS_Signshop_Condition. Domain created from table MTA.signshop_domain_condition;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>ORIG_INSTALL_DATE: Date of original installation;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>REPLACEMENT_DATE: Replacement date;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_SUPERVISOR: Which sign supervisor district the asset is in;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SF_SUP_DISTRICT: Which SF Supervisor district the asset is in;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SHEETING: Type of sheeting. Uses domain EAMS_Signshop_Sheeting. Domain created from table MTA.signshop_domain_sheeting;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>STATUS_CODE: Status of asset, such as Pending Installation, In Service, Retired, or Withdrawn. Uses domain EAMS_Signshop_SignStatus. Domain created from table MTA.signshop_domain_status;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>NEW_SIGN_CODE: Alphanumeric value for new sign codes. Manually entered by Sign Shop supervisors;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>NEW_SIGN_LEGEND: Text for new legends. Manually entered by Sign Shop Supervisors;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>NEW_SIGN_SIZE: Dimensions of sign for new sign codes. Uses domain EAMS_Signshop_NewSignSize. Domain created from table MTA.signshop_domain_signsize;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_CATEGORY: Name of category. Uses domain EAMS_Signshop_SignCategory. Domain created from table MTA.signshop_domain_category;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>SIGN_CLASS: Name of sign class. Uses domain EAMS_Signshop_SignClass. Domain created from table MTA.signshop_domain_class;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>PURPOSE: For what purpose sign is for, according to planners. Uses domain EAMS_Signshop_Purpose. Domain created from table MTA.signshop_domain_purpose;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>GISOBJID: Unique ID generated by Logic App, set equal to OBJECTID_1, populated in HxGN EAMS then synced back to GIS. Does not populate for 'cancelled' features. Required field for HxGN EAMS;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN>CANCEL: If asset created in error, user will populate this field with "cancel' to flag it for removal;</SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN /></P><P STYLE="margin:0 0 0 24;"><SPAN /></P></DIV></DIV></DIV>

Copyright Text: | A. CUSTODIAN | Contact steph.nelson@sfmta.com, Spatial Data Store DBA | B. CREATED | 20230703, Mallik Budhavarapu and Steph Nelson imported from Spears/SHOPS database | C. VERSIONS | 20230703

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

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