🌎
ATD Geospatial
  • Table of Contents
  • Geospatial Read-Only
  • ArcGIS Online
    • Activating your ArcGIS Online account
    • Create Vector Tiles with Popups
    • ArcGIS Online Training Page
    • Updating Existing Web Style Published to AGOL
  • ArcGIS Pro
    • ArcGIS Pro Training Page
    • Working in ArcGIS Pro
  • FME
    • Getting Started
    • Working with datetime
    • Adding or Deleting columns in Socrata
  • Active Transportation
    • Bike Facilities Data Dictionary
    • Interim Projects Viewer Model
    • Strava Metro Data
    • Bike Rack Data Collection
    • Updated Bike Rack Data Collection
    • Bike Data Requests
    • Bike Route Steepness Point Generation
    • Level of Comfort Feature Service Update
    • Bike Map Processes
      • Updating Online Bike Route Vector Tiles
      • Updating Steepness Chevrons
      • Print Bike Map
      • Bike Map Data Sources/Paths
  • Arterial Management
    • Data Driven PHB Ranking
      • Data Structure
      • Attribute Schema
      • Data Collection / Processing
      • Analysis
    • School Zone Beacon Audit Map
    • Signal Intersection Aerials Map
  • Comprehensive Transportation Network
    • Active Transportation Edits to the CTN
    • CTN Data Dictionary
    • CTN Monthly Updates
      • 1. CTN Street Segment Update
      • 2. CTN Intersection Points Update
      • 3. Publishing CTN as Vector Tiles to AGOL
  • Parking Enterprise
    • Affordable Parking Program
    • Bike Parking Dashboard/Data Pull
    • Parking Inventory Management
      • Getting Started
      • Editing in MAINT
      • Relationship Classes
      • Attribute Schema
      • Domains
      • Attribute Rules
  • Signs - Markings - Banners
    • Markings GIS Maintenance
      • Getting Started
      • Standard Operating Procedure
        • Marking Types and Sub Types
        • Scenarios doing GIS QA
        • Specifications | In-House > GIS
        • Materials | In-House > GIS
        • Items | Contractor > GIS
      • Attribute Rules
        • Intersection ID
      • Domains
      • Attribute Schema
    • Signs GIS Maintenance
      • Attribute Rules
      • Attribute Schema
      • Domains
      • FGDB Topology
      • New/Removed Signs Workflow
      • Signs QC Process
  • SPEED LIMIT CHANGE PROJECT
    • Desktop App - Speed Limit Change
    • Collector App - Speed Limit Change
  • Miscellaneous
    • ArcGIS Collector App
    • Alan De Anda's G Drive
    • Capital Improvements Program (CIP) Digitization
    • Collector App Set-up - Troubleshooting
    • GIS Onboarding
    • Google Partner Account & Geodata Uploader
    • PNTS Shapefile Creation
    • Public Facing Links
    • Vision Zero Polygon Maintenance
    • TCAD/WCAD Land Values Data Process
    • ArcGIS Style Creation
  • Format Testing
    • AS
    • ZB
    • JC
    • DS
  • Special Events
    • Map Closures Project
    • SXSW GIS Support
      • Data
      • Maps
      • Spring Festival ATX Mobility Guide
      • Incident Tracking
    • AMANDA Street Events Update
    • Active Parking Permits
Powered by GitBook
On this page

Was this helpful?

  1. Signs - Markings - Banners
  2. Signs GIS Maintenance

New/Removed Signs Workflow

The steps below highlight the workflow for processing new and removed signs from AGOL Sign Work Orders to new sign dataset in Maint.

  • Make sure Austin_Daily_Progress_Master added to map

    • Run "1. Driven Street Pre-Processing" model (Creates new layer called "DrivenRoads_Actual")

      • This dataset contains dissolved driven segments with an actual date field

  • Make sure DrivenRoads_Actual and Sign Work Order data from AGOL are added to map

    • Run "2. Sign Installs and Removals" model (Creates new layer called "FeaturesAddedRemovedAfterDriven")

      • Make sure date query on "sign_Specification_acutals" layer is set with date since the last time it was ran. Should be 1 second after most recent feature in "ASSET_INSTALLATION_DATE" column in ATD_ADMIN.sign_assets Dataset

      • End result may include a Warning "No records within table, or selection set has 0 records". This is expected as not all driven segment will have sign that was installed or removed since the last model run.

  • Disable attachments from "FeaturesAddedRemovedAfterDriven"

  • CURRENT VERSION OF UPDATED PROCESS BEGINS HERE

  • Make Selection Layer of Installed signs that need to be append

    • Select by location - all new installs that do NOT intersect existing location

    • This will likely not include all signs (ie sign added to existing location)

  • Verify you are accessing Maint1 data with the ADMIN login credentials

  • Open editing window for "3. New Location Append" model

    • Click export drop down from top Ribbon and Click "Send to Python Window"

    • Run from Python window (This step is a workaround due to editing of versioned data that appears to have a bug when ran in ModelBuilder)

  • Remove Selection layer from table of contents

    • Create new selection layer by selecting all "Install - New" signs

    • Deselect any features that may not need to be appended (most likely all features will need to be appended)

  • Open editing window for "4. New Sign Append" model

    • Click export drop down from top Ribbon and Click "Send to Python Window"

    • Run from Python window (This step is a workaround due to editing of versioned data that appears to have a bug when ran in ModelBuilder)

*UPDATED PROCESS - After Model 2 in ran and attachments are disabled

  1. Once completed reverse selection on sign work order data

    -Append those features to Outlier dataset

  2. Select all removals from FeaturesAddedRemovedAfterDriven - Append to Removals dataset

  3. Query FeaturesAddedRemovedAfterDriven to include only Installs - Make selection layer of FeaturesAddedRemovedAfterDriven for new locations - Run model 3 to append locations and delete identicals - Once append is finish, select all newly added features by CreatedDate and calculate LocationStatus to Active

  4. If necessary make new selection layer for Sign Assets -Run model 4 to append all new install signs

  5. Query Sign installs to show only those created today -Select all POLE features -Select all Related location features -Clear selection of sign Assets -From Locations dataset select back all related signs (this will yeild a selection of all signs with a pole asset included) -Reverse selection (this will be all sing installs that do not include pole) -From remaining selection, select a subset of features that were appended that day. These will be pushed to Install requiring QC.

  6. Append final selection to Installs_Requiring_QC dataset

  7. Delete that same selection of features from sign_assets (this will remove all signs needed QC)

  8. Select all asset_locations that do not intersect sign_assets -Delete these locations as they do not contain sign_assets with a pole and sign combo

Additional steps for QC features (needs to be better migrated with steps above)

  1. After using model 3

    1. select all locations that were added and updated Location Status to Active (1)

  2. Run model 4

    1. select all locations that were added and updated Asset Status to Active (1)

    2. Asset Size and Asset Condition are not being Claced over -> LOOK INTO THIS

  3. Run Outlier Clean Up model

    1. This will correct fields to match domains

  4. Create Selection Layer of Outlier Poles

    1. Append poles to locations

    2. Select all outliers that intersect selected poles

    3. Append to sign_assets and update QC Status to QC Completed

    4. Append remaining outliers to sign assets and keep at QC Required

  5. Create Selection Layer of Removal Poles

    1. Append poles to locations

    2. Select all Removals that intersect selected poles

    3. Append to sign_assets and update QC Status to QC Completed and Asset Status to Inactive

    4. Append remaining outliers to sign assets and keep at QC Required and Asset Status to Inactive

  6. Append Installs_Requring_QC to sign_assets

    1. Verify Attributes

PreviousFGDB TopologyNextSigns QC Process

Last updated 2 years ago

Was this helpful?