Description: This data set has been updated with the latest new traffic signals information.Important to note that the data contains (12) retired records (flagged under “Condition” column as “Retired”). Nevertheless, these retired records cannot be deleted from the GIS dataset because CityWorks consumes GIS data and work orders are tied to them. Deleting any GIS points will impact CityWorks workflow resulting in losing access to the work order (historical) records. When issuing work orders to the signal locations for electrical works, repairs require to have GIS point representation for work order tie to.FILTER OUT NEEDED RECORDSTo location inactive signalized intersections, apply the following filter:CONDITION <> “Retired”To locate all signalized intersections disregard if any controller controls more than one intersectionSTATUS = ' ' OR STATUS IS NULL OR STATUS <> 'X'To location the numbers of controllers, use the following filter expression. (note: this helps to address the fact that controllers in a few locations control more than one intersection signals)STATUS = ' ' OR STATUS IS NULL OR STATUS = 'M'ABOUT RCORDS WITH RETIRED STATUSRecord flagged as “retired” are invalid feature representations. Some of the are warning lights for ped or fire engines. Some is valid traffic signal representation such as FID 619 but is located outside the City of Oakland and thus should not be included in the data. Some of them are invalid because they are the duplicated representations of already exist feature in the data.MORE DETAILS1) 26 new records were added to the GIS layer for new trafficsignals 2) Identify and eliminate points that are not traffic lights based TSD data, consulted with traffic engineers. They are not traffic signals (just warning lights or crosswalks). 3) Clean-up GIS geometries for overlapping points or duplicated records. 4) Corrected misplaced GIS points by relocating them to the correct geo-locations. 5) Comprehensive attribute updates on attributes per TSD traffic signal records6) Added a new numeric field FID_IN_NUM for easy numeric sorting.7) Added a new field MODIFIED to indicate what modifications made to the records.8) Added a new field UPDATE_DATE for the date of updates.9) Added a new field OLD_FAC_ID for holding original FID value before adding new records - can be removed if needed 10) Added two new fields for server link for staff have access rights to the folder for as-built drawings 11) Added 4 new fields for traffic signal group (COORDGROUP). 12) Added a new field for BUS-ONLY for the newly added AC Transit Bus-only lanes.13) New entries to traffic controller domain values (Hawk 170 E & Hawk 2070 E).FIELD LENGTH EXTENDEDRECONCILENOTES, TEXT, to 150NEW FIELDS ADDEDCOORDGROUP, TEXT, 50COORDAM, TEXT, 10COORDMID, TEXT, 10COORDPM, TEXT, 10COORDOFF, TEXT, 10BUS_ONLY, TEXT, 50FID_IN_NUM, SHORTDOT_TSDDB_NO, SHORTMOIFIED, TEXT, 15UPDATE_DATE, DATELINK1, TEXT, 255LINK2, TEXT, 255OLD_FAC_ID TEXT, 30 - for holding original FID value before adding new records - can be removed if needed EXPLANATIONS COORDGROUP – Traffic Signal Group Name: New, added for traffic signal group name. COORDAM – Cycle Length AM: New, added field for attribute belongs to traffic signal group.COORDMID – Cycle Length MID: New, added field for attribute belongs to traffic signal group.COORDOFF – Cycle Length OFF:New, added field for attribute belongs to traffic signal group.FID_IN_NUM – New, enable numeric (sequential) sort on Facility ID.DOT_TSDDB – New, for cross-reference to DOT TSD ID (internal traffic signals data).MODIFIED – New, what has been updated to the record.UPDATE_DATE – New, date of edit/updates made.LINK1 – New, holding server link to As-built drawing.LINK2 – New, holding server link to folder containing technical drawings for staff who has access.Historical NotesNoushin Adabi: 5/7/2013 I exported the then-current GIS data (from Earth ArcSDE Geodatabase), which had 1220 records, exactly half of which were duplicates. First, I deleted duplicate records. Then I compared the GIS data with an Access database from Transportation Services, comparing the tabular data and working with Mohamed Alaoui.Where the Transportation Services database had a traffic signal that was not in GIS, it was added to GIS. I then gave a list to Mohamed for those traffic signals that have different facility ids than in the Transportation Services database; we are keeping the faculty id that is in GIS.I also added all the Traffic Signals that Electrical Services had previously identified as missing (as had been previously communicated in Cityworks or emails).