Civil 3D 2016 Project Data Workflow Map - Wisconsin WisDOT Macros > SRV to PNT/FLT 3 Survey PDF...

download Civil 3D 2016 Project Data Workflow Map - Wisconsin WisDOT Macros > SRV to PNT/FLT 3 Survey PDF Civil

of 15

  • date post

    16-Apr-2020
  • Category

    Documents

  • view

    0
  • download

    0

Embed Size (px)

Transcript of Civil 3D 2016 Project Data Workflow Map - Wisconsin WisDOT Macros > SRV to PNT/FLT 3 Survey PDF...

  • WisDOT Macros > SRV to PNT/FLT

    copy valid breaklines and final boundary to create verification surface

    copy valid breaklines and final boundary to create verification surface

    Import XML into SDB

    export files to LandXML

    Add obscured area hide boundaries

    WORKING FOLDER N:\PDS\C3D

    DATA SHORTCUT FOLDER DESIGN PROJECT ID (Example: 12345678)

    FDM 15-5-3.1.1

    BaseData

    Files in this folder should only be created and edited by the Survey Data Coordinator responsible for documenting existing conditions.

    Existing Topography Name: Topo-Ex.dwg [DT2] Desc: Base file used in plan production

    Existing Utilities Name: Uti-Ex.dwg [DT2] Desc: Base file used in plan production

    Survey Database Queries (Predefined)

    UtilityFigures1

    UtilityFigures2

    UtilityPoints1

    UtilityPoints2

    Existing Surface Name: Surf-Ex.dwg [DT2] Desc: Base file used in design and plan production

    SURFACES

    Existing Surface Name: Exist

    Definition

    Boundaries

    Data Clip boundary = polyline around proposed construction limits Hide boundary = obscure areas

    Breaklines

    EXIST.flt

    Point Files

    EXIST.pnt

    Edits

    Field Survey Existing Surface Name: Exist-Survey

    BOUNDARIES

    Definition

    Boundaries

    Breaklines

    EXIST-bldg.flt

    EXIST-obsc.flt

    EXIST-weak.flt

    EXIST-ewboundary.flt

    EXIST-ew.flt

    EXIST-disc.flt

    Imagery

    Mapping

    EXIST.SRV

    EXIST.pnt

    EXIST.flt

    EXIST-bldg.flt

    EXIST-ew.flt

    EXIST-ewboundary.flt

    EXIST-disc.flt

    EXIST-obsc.flt

    EXIST-weak.flt

    Orig

    Existing Mapping Topo Name: M (flight).dwg [DT3]

    Raster

    Other

    GIS data, USGS DEM, As-built data, pipe network of existing facilities

    Survey

    Field survey text file Name: --.pac

    Field survey text file Name: --.xml

    Project Survey Database Name: SD--.sdb

    Survey Database Queries (Predefined)

    Centerlines

    Control Points

    SurfaceFigures1

    SurfaceFigures2

    SurfacePoints1

    SurfacePoints2

    SurfacePoints3

    TopoFigures1

    TopoFigures2

    TopoPoints1

    TopoPoints2

    TopoPoints3

    UtilityFigures1

    UtilityFigures2

    UtilityPoints1

    UtilityPoints2

    multiple survey databases may exist with the project survey database

    Field survey edit file Name: SurveyEdits.dwg [DT2] Desc: file used for checking

    This is a working file only used by a survey data coordinator to review and rectify field survey data. Survey queries are inserted as needed for the review process.

    Existing Survey Topo Name: Topo-Ex-Survey.dwg [DT2]

    This file is the complete collection of all field survey data for the project that will be used in design and plans production.

    Survey Database Queries (Predefined)

    TopoFigures1

    TopoFigures2

    TopoPoints1

    TopoPoints2

    TopoPoints3

    Existing Survey Surface Name: Surf-Ex-Survey.dwg [DT1]

    SURFACES

    Field Survey Existing Surface Name: Exist-Survey

    Definition

    Boundaries

    Field Survey Boundary polyline (Data Clip)

    Breaklines

    Point Files

    Point Survey Database Queries (Predefined)

    SurfacePoints1

    SurfacePoints2

    SurfacePoints3

    Figure Survey Database Queries (Predefined)

    Centerlines

    SurfaceFigures1

    SurfaceFigures2

    Field Control Data Name: SurvCtrl.dwg [DT2] Desc: Control points used for field survey

    Survey Database Queries (Predefined)

    Control Points

    Geodetic Reference Documentation Name: -DT1773.docx Desc: Datum and Coordinate information

    Orig

    Design

    AliProf

    Proposed Alignments and Profiles Name: AliProf--.dwg [DT1]

    XREF

    Topo-Ex.dwg

    Uti-Ex.dwg

    ALIGNMENTS

    Roadway reference lines and profiles

    Project-wide roadway features and profiles

    - Generally roadway reference lines are kept in the AliProf.dwg file. If corridor-specific reference line alignment layout or superelevation design is iterative with the corridor design, it is acceptable to keep the alignment in the corridor file.

    - The Offset and Miscellaneous alignments that are kept in the AliProf.dwg are those that will be data referenced into multiple corridor dwg files for other purposes, such as targeting.

    - Alignments created as Offset Alignments can be created as Miscellaneous Alignments, but not all Miscellaneous Alignments can be created as Offset Alignments. User/Project preferences dictate how these alignments are created.

    - Only Centerline and Offset alignments provide for superelevation control.

    - It is recommended to create the side road profile in the Corridor dwg.

    CORRIDOR

    Setup Corridor(s)

    - For downstream use in multiple corridor files - Example Use: Edge of Traveled Way for Intersections

    SURFACES

    Exist Surf-Ex.dwg

    Setup Corridor Surface(s) Name: Crdr-Setup

    - For downstream use in multiple corridor files - Example Use: Edge of Traveled Way for Intersections

    Corridors

    Roadway Corridor(s) Name: Crdr--.dwg [DT1]

    XREF

    Topo-Ex.dwg

    Uti-Ex.dwg

    ALIGNMENTS

    Corridor-specific roadway features and profiles - not used project-wide

    - Offset and Miscellaneous alignments can be created in a corridor drawing when they are to be used exclusively by that corridor dwg.

    - Alignments created as Offset Alignments can be created as Miscellaneous Alignments, but not all Miscellaneous Alignments can be created as Offset Alignments. User/Project preferences dictate how these alignments are created.

    - Only Centerline and Offset alignments provide for superelevation control.

    - It is recommended to create the side road profile in the Corridor dwg.

    Roadway reference lines and profiles

    Project-wide roadway features and profiles

    SITES

    Grading groups may be saved in the corridor file or separate grading file. Create grading surfaces in the Crdr.dwg if a dynamic connection to a corridor feature line is desired. Example Use: Bridge Abutments, Ponds, Berms, Etc.

    CORRIDORS

    Setup Corridor(s)

    Example Uses: - EdgeofTraveledWay Setup- - CurbReturn Setup-

    Rdwy

    INTERSECTION

    Geometry Priority Objects (Intersection objects for tying alignments and profiles)

    SURFACES

    Exist

    Crdr-Setup

    Crdr-Setup

    Example Uses: - EdgeofTraveledWay Setup- - CurbReturn Setup-

    Crdr--Datum

    Datum surface extends to subgrade shoulder point.

    Crdr--Top

    Top surface extends to slope intercepts.

    Crdr--Subg-Impr

    Crdr--Subbase

    Crdr--BaseCourseXS

    Surface to be used for section views and quantities

    Crdr-Pavt.dwg [DT1]

    Crdr-Pavt is a copy of the Crdr.dwg file after the design is finalized and before Contractor Data Packet is created.

    CORRIDORS

    Pavt

    SURFACES

    Crdr--Pavement

    Corridor Pavement Surface with increased frequency - See FDM 15-5-7 Table 7.1

    Crdr--BaseCourse

    Only the upper base layer needs to be derived from the pavement corridor. Lower layers can be derived from primary corridor

    Corridor Base Course Surface with increased frequency - See FDM 15-5-7 Table 7.1

    Edgelines

    Proposed Pavements Name: Pavt.dwg [DT1]

    ALIGNMENTS

    Project-wide roadway features

    Corridor-specific roadway features

    Plan production offsets.

    The offset and miscellaneous alignments data referenced into the Pavt dwg are used to create additional offset alignments used for plans production (example: curb face).

    Proposed slope intercepts Name: SI.dwg [DT1]

    SURFACES

    Rfnt-All-Top Surf-Rfnt-All-Top.dwg

    Extract surface boundary. Update extracted boundary based on Rfnt-All-Top surface.

    Pavement Marking Name: PM.dwg [DT1]

    Surfaces

    Rfnt Top Step 1: Create Rfnt Surface Name: Surf-Rfnt-All-Top.dwg [DT1]

    SURFACES

    Rfnt-All-Top

    Use Surfaces Crdr-Top or Rfnt-Top for Pavement Grades. Frequencies should be set for grade locations.

    Crdr--Top Crdr-Rdwy.dwg

    Grading Surfaces

    Rfnt Top Step 2: Extract Breaklines Name: Surf-Rfnt-All-Top-RawData.dwg

    breaklines found by Design Surface Data Extractor tool

    Rfnt Top Step 3: Create verification surface from extracted breaklines Name: Surf-Rfnt-All-Top-Verification.dwg [DT1]

    SURFACES

    Volume Surface: Rfnt-All-Top-Verification

    Rfnt-All-Top (Base Surface)

    Surf-Rfnt-All-Top.dwg

    Rfnt-All-Top-FromBreaklines (Comparison Surface)

    Rfnt Datum Step 1: Create Rfnt Surface Name: Surf-Rfnt-All-Datum.dwg [DT1]

    SURFACES

    Rfnt-All-Datum

    Rfnt-All-Top

    Crdr--Datum Crdr-Rdwy.dwg

    Grading Surfaces

    Rfnt Datum Step 2: Extract Breaklines Name: Surf-Rfnt-All-Datum-RawData.dwg

    breaklines found by Design Surface Data Extractor tool

    Rfnt Datum Step 3: Create verification surface from extracted breaklines Name: Surf-Rfnt-All-Datum-Verification.dwg [DT1]

    SURFACES

    Volume Surface: Rfnt-All-Datum-Verification

    Rfnt-All-Datum (Base Surface)

    Surf-Rfnt-All-Datum.dwg

    Rfnt-All-Datum-FromBreaklines (Comparison Surface)

    Surf-Rfnt-All-.dwg [DT1]

    SURFACES

    Rfnt-All-

    Crdr--

    Surface Type: Subgrade Improvement, Subbase Crdr-Rdwy.dwg