extended survey training sponsored by hq survey support

Extended Survey TrainingSponsored by HQ Survey Support

EEDS and the Surveyor

Presented by HQ CAE SupportJeff GrahamKate SeversonClint Hill

Extended Survey TrainingEEDS and the Surveyor Sept. 20, 2011

Webinar Notes

• Please mute phones unless you have a question, use the Raised Hand function to get presenters attention

• If your listening on PC speakers use the Webinar Question function to Ask Questions

• Follow along in the EEDS manual• EEDS pages references in presentation• Web address will be sent via Chat


EEDS and the Surveyor Objectives:1. Identify the purpose for EEDS2. Understand the EEDS deliverables specific to

Survey and Right of Way3. Identify the Survey folder structure4. Recognize the survey file naming conventions5. Understand project closure and transition6. Document Control Network and Topography

surveys


What is EEDS?

Electronic Engineering Data Standards A WSDOT manual that defines standards

and procedures in preparing, delivering and archiving electronic engineering data for all phases of highway projects

http://www.wsdot.wa.gov/Design/CAE/EEDS.htm





EEDS Purpose

Establishes Standards and Procedures • Promotes uniformity and consistency• Project data is managed efficiently • Adds value by making data created by

someone else easy to access and use


What does that mean to me?

• Consistency – In location and naming conventions allows others to

quickly identify and access pertinent information

• Efficiency– As a surveyor collecting information for a design

project, many groups in downstream processes depend on your data

• Documentation – Provides necessary trail to key data, decisions and

criteria, and other invaluable info to pass to customerExtended Survey TrainingEEDS and the Surveyor Sept. 20, 2011

EEDS Contents

Division 1 – DeliverablesDeliverables 1 WSDOT ResourcesDeliverables 2 Data Transfer, Review and AcceptanceDeliverables 3 Project Directory StructureDeliverables 4 File Naming ConventionsDeliverables 5 SurveyDeliverables 6 Roadway DesignDeliverables 7 Drafting and Plans Preparation

EEDS Manual Pg. 4

EEDS Contents

Division 2 – FormsForms 1 GeneralForms 2 SurveyForms 3 ProjectForms 4 InRoadsForms 5 CAD

EEDS Manual Pg. 5

EEDS Contents

Division 3 – SymbologySymbology 1 RequirementsSymbology 2 Data CollectionSymbology 3 Design StandardSymbology 4 Right of Way StandardsSymbology 5 PS&E Standards

EEDS Manual Pg. 5

WSDOT Resources

Agency Developed Software Resources– Increased efficiency for survey, drafting,

design and construction• Standard symbology• Productivity tools • Conventions

– Support Plans Preparation manual and EEDS manual

EEDS Manual Pg. D1-1

Deliverables - Suppliers Responsibility

Data Transfer– Information in electronic format – Posted on WSDOT network– Transmittal letter to the customer– Submissions shall be in accordance of EEDS– Electronic files same as “hard copy” – Files named in accordance with EEDS


Transmittal Letter

• Project Information:Name, Project Numbers, and Description

• Submission Number and Date• InRoads Location Survey Checklist• Contents Listing:

Names and Location of the Electronic Data


InRoads LocationSurvey Checklist

• Provides contact info• Use for project data contents listing• Ensures complete package

http://www.wsdot.wa.gov/publications/fulltext/design/cae/forms/InRoadsLocationSurveyChecklist.docx




Acceptance – Customers Responsibility

Review of Survey Files Verify Data

• Complies with standard field code usage• Coordinate ranges are consistent with project• Correct application of combined factor was applied



Review of Surface Models– Inconsistencies between DTM features and

MicroStation base mapping– Contours for inconsistencies or anomalies– Elements for incorrect elevations– Profiles for unusual slopes or breaks– Sections for unusual slopes or breaks– Erroneous triangles have been deleted



Review of CAD Files– Levels adhere to standards– Graphic elements conform to standards– Accuracy and consistency of tie points,

stationing and dimensions


Rejection of Electronic Data Submittals

Files that do not meet requirements are returned to the supplier for correction:

• The customer will provide written explanation of areas that do not conform

• The supplier responsibilities are:– Finding the source of the errors– Correcting the errors– Resubmitting the files


Project Directory Structure

WSDOT Standard Structure for Computer Aided Engineering (CAE) Data StorageFolder structure:

• Project stored in uniquely named folder• Contains all data files - includes all survey and

other supporting data files• Master files stored in the standard project

– Working copy may reside on local computer - surveyor’s office or field PC


Project Directory Structure

WSDOT CAE Standard Project Folders


Survey Directory Structure

All survey files are stored in the survey structure



_DeliverablesComplete-to-date survey datasets formatted for design purposes

_RequestsCopy of completed survey request form



_SurveyDocAll survey related project documentation– Survey-generated project datum calculation

reports– Audit/revision reports from processed raw

data– Survey documentation spreadsheet, etc.



\Control• Control network datasheets• Traverse analysis and adjustment reports• Other related documentation



\Monumentation• Documents for Record of Survey and

Record of Monumentation• DNR Permits and completion reports for

monumentation removal or destruction• Control network datasheets• Other related documentation



RawDataOriginal survey data files

• Field data collector files*.crd, *.rw5,*.sdr, etc.

• Scanned hard copy field notes



WorkingDataSurveyor’s working data

• \RWKsSurveyor's InRoads Project Files (*.rwk).

• \FieldbooksInRoads Survey Fieldbook (*.fwd) Files



WorkingData• \Geometry

Surveyor's InRoads Geometry Project(*.alg) Files

• \SurfacesSurveyor’s InRoads Surface (*.dtm) Files


File Naming Conventions

Standard Naming Conventions– Make data portable– Are easy to recognize– Able to use files created by others


Survey Deliverables

Data Collection and Processing– Use WSDOT standard feature codes to

identify field observations– See Symbology 2 – Data Collection for

complete code list– The raw data file must be processed and

delivered to requestor in InRoads format


Survey Deliverables

Data OrganizationAll electronic project files and data are organized as defined:

• Deliverables 3 “Project Directory Structure”• Deliverables 4 “File Naming Conventions”


Survey Deliverables

Incremental Delivery of Survey DataIncremental transfer package should include:

• Entire survey dataset (all survey points and survey chains) collected to date

• Checklist items that apply to the latest dataset


Survey Deliverables

DocumentationSurvey Request Form

• Complete surveyor’s portion• Place form in Survey\Request folder

Note: Survey Request Form is created in the Survey\Request folder when CAE Project is created.


355-001-SurveyRequest.fp7

Survey Deliverables

DocumentationInRoads Survey Documentation Spreadsheet

• Must be completed for the project• Named Projname_InRoadsSurveyDoc.xlsx• Used to document


Master_InRoadsSurveyDoc

‒Project Information‒Control Monumentation‒Alignments

‒DTM‒Survey Fieldbook

Survey Deliverables

DocumentationProject Control

• All monuments used to establishment project control network must have documentation

• Documentation will be included in the _SurveyDoc\Control folder

• Entry in InRoads Survey Documentation Spreadsheet


Survey Deliverables

DocumentationProject Control

• Must include source documentation– WSDOT Report of Survey Mark– County reports of survey documentation

• Remain in its original format• Retain its original name• Monumentation maps may be scanned

– Electronic scan treated as the source


Survey Deliverables

DocumentationSupplemental Control– Stored in Survey\_SurveyDoc\Control folder– Entry in InRoads Survey Documentation

Spreadsheet– Points must have traverse adjustment notes

documenting ties with project control


Survey Deliverables

DocumentationProject Datum

• Methodology defined in Chapter 6 of the WSDOT Highway Survey Manual

• Where multiple combined factors are required– Map of the project datum areas– Impacted control must be documented


Survey Deliverables

DocumentationProject Datum

State Plane to Project Datum conversion reportFormat ASCII Text, Microsoft Excel, or Word file formats

File name example: L1234_SPCtoPD.rptStored file in Survey\_SurveyDoc folder


Survey Deliverables

Data ProcessingFieldbooks (*.FWD)

Import raw data files or processed data file from another application

File name example: L1234_PCid_Topo.fwd

Audit files (*.log files)Document modifications and adjustments

File name example: L1234_PCid_Survey.log


Survey Deliverables

Data ProcessingGraphic Files (*.DGN)

Final survey planimetrics will be written to graphics to produce a MicroStation DGN file

File name example: L1234_PCid_Survey.dgnStored in Survey\_Deliverables folder


Survey Deliverables

Data ProcessingSurface Files (*.DTM)

•Surface DTM will be created from final survey fieldbook•Will be reviewed for accuracy

File name example: ID1234_PCid_Survey.dtmStored in Survey\_Deliverables folder


Survey Deliverables

Data ProcessingGeometry Project Files (*.ALG)

Two geometry projects will be created–project that contains the control points and monuments

File name example: L1234_PCid_Control.algStored in Survey\_Deliverables folder

–project that contains the final survey fieldbook datasetFile name example: L1234_PCid_Survey.algStored in Survey\_Deliverables folder


Survey Deliverables

Data ProcessingRaw Survey Data

All survey data collected for the project needs to be included in its raw, unedited formatAny modifications or edits prior to import into InRoads must be done on copies of the raw files and noted in the survey documentation


Survey Deliverables

Data ProcessingInRoads Survey Package Deliverables

A complete InRoads survey package consists of all the electronic data in the project’s Survey subfolderThis folder contains all files and data necessary for the requester to import and use the survey dataset in InRoads, and the supporting documentation for the survey


Survey Deliverables

The Survey\Deliverables Folder– Contains all the electronic data necessary for

designer to use the survey data with InRoads– The only data that will be used directly in the

design phase– Access to the other subfolders under the

Survey project folder is necessary for backup and overall project documentation


Survey Deliverables

Project Closure and TransitionPreparation of Deliverable Package

• General requirements for the transfer, review and acceptance of the data are detailed in Deliverables 2

• The surveyor will prepare a complete survey package and notify the requestor survey has been finalized


Survey Deliverables


Delivery accomplished by providing the requester access to the entire Survey folder if both surveyor and requester share a network resource and can both reference the same project folder


Survey Deliverables


If shared network location is not an optionSurveyor will provide a copy of the project’s Survey subfolder

This can be accomplished using any medium that can reliably contain the entire folder structure. (e.g., an email, an FTP site, a compact disk or a DVD)


Survey Deliverables

Data ArchivalWSDOT surveyor responsible for archival of the final electronic survey data per the region’s policyExternal surveyor, it is the requester who is responsible for archival of the final electronic data per the region’s policyIf no regional archival policy exists, the responsible party needs to ensure the data is appropriately archived for future reference


Survey Forms

Survey Request Form–Copied to Survey\_Requests folder when CAE project is created

–Form also available WSDOT Form CatalogInRoads Location Survey Checklist

Link on EDDS web addressInRoads Survey Location Spreadsheet

Copied to Survey\_SurveyDoc folder when CAE project is created

EEDS Manual Pg. F2-1

Symbology

Symbology 2 – Data CollectionDescribes the symbology used to identify features by survey crews, photogrammetry and other collection methods


Survey Deliverables

Symbology


Summary

EEDS project structure can be generated easily and will promote a consistent approach among projects across the state.This reduces the time taken to reverse engineer another teams data.

extended survey training sponsored by hq survey support

Documents

eeds contentsdivision

eeds manualeeds manual

wsdot manual

hq survey supporteeds

dateinroads location

surveyor objectives

cadeeds manual

eedseeds manual