{"text_format":"1","workbook":"xlsx","n_sheets":5,"sheets":["INSTRUCTIONS","CHECKLIST","ORD","COMMENTS","QAQC STATEMENT"],"not_rendered":{"charts":0,"images":4,"macros":1,"external_links":0,"defined_names":4,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"INSTRUCTIONS","index":0,"n_rows":37,"n_cols":1,"rows_kept":37,"cut":false,"hidden":false,"merged":[[0,0,5,0],[31,0,34,0],[36,0,38,0],[28,0,29,0],[7,0,11,0],[13,0,26,0]]}
["This QA/QC Checklist workbook has a customizable checklist that can be adjusted to show only items that the Survey PM is requiring the Survey Consultant to deliver for a particular project.  It is intended that this QA/QC Checklist be included with the MDOT Request for Survey Consultant Servicesso that the Survey Consultant is aware from the beginning of the contracting process of all of the items they must deliver.  There are some cases in which files or items are shown but end-up not being required.  This list should greatly reduce the amount of \"n/a\" comments."]
[]
[]
[]
[]
[]
[]
["This workbook contains multiple sheets: INSTRUCTIONS, CHECKLIST, ORD, COMMENTS and QA/QC STATEMENT.  Once the checklist has been customized for your project, you can either print each sheet separately to a PDF and then combine them manually, or print the entire workbook to a PDF and manually delete the Instructions page.  We are looking into a \"Print\" macro that will print all sheets except the Instructions sheet to one PDF."]
[]
[]
[]
[]
[]
["The CHECKLIST sheet contains two categories, files to be uploaded to ProjectWise and items to be included in the Survey Portfolio PDF.  Each category is separated into sections.  For the ProjectWise category, the heading of each section begins with PWISE- and is shaded gray.  Following PWISE- is the name of the folder in ProjectWise (the first section is for files that go directly into the main project folder, not a sub-folder like the rest of the sections).  For the Survey Portfolio PDF category, the heading of each section begins with SURVEY PORTFOLIO PDF- and is shaded blue.  Following  SURVEY PORTFOLIO PDF- is the name of the bookmark section within the PDF.  To select the files and items you want included as a deliverable, simply place an \"x\" in that row in column \"D\".  Once you have an \"x\" next to all the items you want, click the \"Filter\" button (cell G1) and all rows with no \"x\" will be hidden.  To show all rows again, click the \"Show All\" (cell F1) button.  Due to the size of some of the rows, there are often page formatting issues once the checklist is filtered.  At this time, you must manually adjust  the page break locations to avoid having partially filled pages.  Go to the print preview and look at each page, if any page breaks need to be adjusted go back to the Checklist sheet, make sure the view is set to \"Page Break Preview\".  Navigate to the page break that needs to be adjusted, and then click and drag the page break to the desired location.  This may be an iterative process.   "]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
["The ORD sheet contains the QC items required for the CAD deliverables.  This checklist can also be filtered, but since the fully expanded list fits all on one page, no page break formatting is required."]
[]
[]
["The COMMENTS sheet provides a place for the Survey Consultant to add any comments they have for the files or items that are included in the checklists.  Each item has an \"Item #\" which is in row \"A\" of the Checklist and ORD sheets.  This number goes in the \"Item #\" column and the corresponding comment goes in the \"Comment\" column.  "]
[]
[]
[]
[]
["The QA/QC STATEMENT contains the QA/QC Compliance Statement that is required to be signed & sealed by the QA/QC officer for the Survey Consultant.  This page will typically not be modified and only needs to be included with the PDF."]

{"sheet":"CHECKLIST","index":1,"n_rows":201,"n_cols":6,"rows_kept":201,"cut":false,"hidden":false,"merged":[[1,8,3,8],[199,1,199,3],[161,1,161,3],[165,1,165,3],[172,1,172,3],[190,1,190,3],[197,1,197,3],[100,1,100,3],[106,1,106,3],[117,1,117,3],[126,1,126,3],[149,1,149,3],[36,1,36,3],[49,1,49,3],[72,1,72,3],[88,1,88,3],[98,1,98,3],[8,1,8,3],[12,1,12,3],[16,1,16,3],[24,1,24,3],[29,1,29,3],[4,4,5,4],[6,5,7,5],[6,3,7,3],[6,1,7,1],[0,1,0,3],[1,1,1,3],[6,2,7,2]]}
[null,"Michigan Department of Transportation"]
[null,"Survey QA/QC Checklist"]
[]
[]
[null,null,"Revision Date:","2023-10-26","Required Item"]
[]
[null,"Item #","QA/QC Review\nby Consultant","MDOT Survey Project Manager:________________\nConsultant Firm:____________________                           Consultant Project Manager:_______________\nMDOT Job Number:____________________                                       Control Section:_______________\nDesign Project Manager (if sub):_________________"]
[]
[null,"PWISE - MAIN PROJECT FOLDER",null,null,"x"]
[null,1,null,"XXXXXX_MDOT_0222_20YY-MM-DD.pdf\nMDOT Form 222 (5/01) Survey Notes Receipt and Transmittal filled out with pertinent information and signed\n(e-signature is acceptable).  Once all files are uploaded to ProjectWise, change state to ‘Next’ and send the\nauto-generated e-mail to the MDOT Survey PM.","x"]
[null,{"$f":"B10+1","v":2},null,"XXXXXX_Align_ROW_Portfolio_20YY-MM-DD.pdf\nBookmarked Adobe PDF of of Surveyor's Alignment & ROW Report and pertinent alignment/ROW documents (See end of this document for items to be included in the portfolio):","x"]
[null,{"$f":"B11+1","v":3},null,"XXXXXX_Survey_Portfolio_20YY-MM-DD.pdf\nBookmarked Adobe PDF of Surveyor's Project Report and pertinent administrative, control, mapping, LiDAR, structure, hydraulic and miscellaneous project documents (See end of this document for items to be included in the portfolio):","x"]
[null,"PWISE - ALIGNMENT & ROW FOLDER",null,null,"x"]
[null,{"$f":"B12+1","v":4},null,"XXXXXX_Prop_20YY-MM-DD.doc\nA Microsoft Word document containing all property corners found / located in the field with the Northing, Easting, description of the corner location and monument, station and offset.The header should outline the company name, month and year of property corner location. Witnesses of individual property corners are not required.","x"]
[null,{"$f":"B14+1","v":5},null,"XXXXXX_Prop_20YY-MM-DD.txt\nText document containing all found property/ROW monumentation in comma separated file in the following format: Point Number,Northing,Easting,Elevation,Description.","x"]
[null,{"$f":"B15+1","v":6},null,"XXXXXX_Images_ROW.zip\nDigital photos relating to ROW/property monumentation.  The name of each file should relate to the property/controlling corner being photographed when possible.  All files are to be saved in one zip file.","x"]
[null,"PWISE - CONTROL FOLDER",null,null,"x"]
[null,{"$f":"B16+1","v":7},null,"XXXXXX_MDOT_Monument_monument number.doc\nMDOT Monument Establishment Data Sheets of all Primary Control Points established and or used as part of this project.  This form is available at: http://mdotwiki.state.mi.us/design/index.php/Chapter_10_-_Deliverables"]
[null,{"$f":"B18+1","v":8},null,"XXXXXX_Images_Control.zip\nDigital photos relating to site control.  The name of each file should relate to the control point being photographed.  All files are to be saved in one zip file.","x"]
[null,{"$f":"B19+1","v":9},null,"Total Station RAW Data\nRAW data pertaining to Primary and Intermediate Control","x"]
[null,10,null,"GPS RAW Data\nRAW data pertaining to Primary and Intermediate Control","x"]
[null,11,null,"GPS RINEX Data\nGPS RAW data pertaining to Primary and Intermediate Control converted to RINEX format","x"]
[null,12,null,"MSRN RINEX Data\nThe RINEX files for the MSRN stations used by OPUS","x"]
[null,13,null,"Vertical RAW Data\nElectronic raw data files for all vertical control established.  ","x"]
[null,"PWISE - MAPPING FOLDER",null,null,"x"]
[null,{"$f":"B24+1","v":14},null,"XXXXXX_Struc_Inventory_20YY-MM-DD.pdf\nDrainage structure inventory report compatible with MDOT software and correlated to the \nS-XXXXXX_Survey_3D_20YY-MM-DD.dgn file in .xls spreadsheet format or MISIS output report in .pdf","x"]
[null,15,null,"XXXXXX_Images_Mapping.zip\nZIP file of all digital photos of the structure(s) and end sections or headwalls with the name of the file being the structure number. For multiple photos of a structure, add a letter to the end starting with \"A\".  The numbering shall match with the information in the Drainage Structure Inventory Report.  All files are to be saved in one .zip file.","x"]
[null,16,null,"XXXXXX_Feature_Code.txt\nIndividual utility / drainage station and offset reports generated by feature code in the .dgn drawing.","x"]
[null,17,null,"XXXXXX_Mapping_Raw.zip\nElectronic raw data files for all mapping to be contained in a subfolder titled “Mapping Raw” with each day being contained in a subfolder for that day.  Multiple instruments per day require multiple subfolders."]
[null,"PWISE - STLS (STATIC TERRESTRIAL LASER SCANNING)  FOLDER"]
[null,{"$f":"B29+1","v":18},null,"Georeferenced Registered Proprietary Database"]
[null,19,null,".LAS file (version 1.2 or later) "]
[null,20,null,".POD file(s)"]
[null,21,null,"ASCII text file "]
[null,22,null,"Check that the following items are in compliance:\n       Adjoining scans used in DTM creation have correct required point density spacing\n       Scans have Min 20% overlap\n       Distance between scan setups are less than 500 ft.\n       Registration residuals between control points of adjacent scan setups\n       Clear overlaid photography on scan points\n       Scans control points traversed, Geo-referenced to correct to state plane zone, and NAVD88 datum\n       Scan control with unique numbering from Intermediate Control\n       4 control points visible in each independent scan, and meet the requirement in Appendix C-3\n       Ground Points are monumented in accordance with Appendix C-3-f\n       Correct use of Intermediate Control as described in Appendix C-3-g"]
[null,23,null,"XXXXXX_Scanning_QA_QC_20YY-MM-DD.dgn\nA .dgn format file contains information described as “Scanning QA/QC”. The points inside are correctly coded and are the correct feature.  (is this original description from the current QA/QC sufficient?)"]
[null,"PWISE - MTL (MOBIL TERRESTRIAL LIDAR) FOLDER"]
[null,{"$f":"B36+1","v":24},null,"Point Cloud Files\nProvided on electronic media of an appropriate size to contain all project information without separating on more than one media.  Two complete (2) copies have been provided to MDOT Lansing Survey Support Unit. A third (3rd) copy has been provided for use by the MDOT Region Surveyor or Design Engineer. (See Appendix F)"]
[null,25,null,"XXXXXX_MTL_Mission_Plan.tpm and .kml / .kmz\nMTL Planning files - Trajectory plan with planned target(control and validation) files in TopoDot Mission planning format, and kml/kmz format "]
[null,26,null,"XXXXXX_MTL_Survey_3D_20YY-MM-DD.dgn\n3D MicroStation DGN file containing all mapping, meeting MDOT Cadd requirements"]
[null,27,null,"XXXXXX_MTL_ExTerrain_3D_20YY-MM-DD.dgn\n3D MicroStation DGN triangle file containing the terrain surface triangles"]
[null,28,null,"LiDAR data has been tiled and saved as colorized .POD (Point Tools/MicroStation point cloud file) files using photo images"]
[null,29,null,"XXXXXX_POD_Tile_Index_20YY-MM-DD.dgn\nDGN index file showing tile layout and naming of POD files"]
[null,30,null,"LiDAR data has been tiled and submitted in .LAS/.LAZ (version 1.2 or later) format with RGB values and intensity values (File formats XYZIRGB or XYZRGBI) colorized from photo images"]
[null,31,null,"XXXXXX_LAS_Tile_Index_20YY-MM-DD.dgn\nDGN index file showing tile layout and naming of .LAS files"]
[null,32,null,"Photo mosaic/Images along route that support the LiDAR .POD/.LAS point cloud"]
[null,33,null,"Original unedited raw LiDAR dataset in manufacturer’s file format"]
[null,34,null,"XXXXXX_CntrltoMTL_Diff_3D_20YY-MM-DD.dgn\nDGN file containing mapping locations of all Control Targets, Validation Targets, GNSS Base Stations, Primary Control points, Intermediate Control points and Benchmarks used or established for the project. The points comply with MDOT features and coding.  The DGN also contains values showing the XYZ differences to the corresponding point in the final LiDAR Point Cloud. File is named"]
[null,35,null,"XXXXXX_DTM_Compare.dgn and .kmz\n3D MicroStation DGN and KMZ file providing the graphical representation of the resulting differences between the edited project DTM surface and the targets and validation points"]
[null,"PWISE - INTERIM MTL FOLDER"]
[null,{"$f":"B49+1","v":36},null,"Processing Trajectories, Scan Line Processing and Point Cloud Registration (Workflow of tasks done prior to data extraction/mapping tasks)"]
[null,37,null,"XXXXXX_Targets.txt\nCoordinate list of the Target points used for the Mobile mapping and the adjustment reports establishing these points."]
[null,38,null,"XXXXXX_ValidationPts.txt\nCoordinate list of the Validation points used for the Mobile mapping and the adjustment reports establishing these points."]
[null,39,null,"XXXXXX_PtCloud_Compare.dgn and .kmz\n3D MicroStation DGN and a KMZ file providing the graphical representation of the resulting differences between the project Point Cloud dataset and the targets and validation points"]
[null,40,null,"XXXXXX_MTL_Interim_Report_20YY-MM-DD.pdf\nNarrative report describing the actions taken to process and refine the trajectories and the results obtained.  Including, but not limited to, the following items:"]
[null,41,null,"Smooth Best Estimated Trajectory (SBET) resulting accuracies report (precision) for Trajectories "]
[null,42,null,"Describe and show any areas of the project where the data, as collected, exceeded the maximum elapsed time or distance traveled of uncorrected IMU drift due to GNSS signal loss or obstruction."]
[null,43,null,"Total Number of all Targets/Points/Validations "]
[null,44,null,"Number of  Control Targets"]
[null,45,null,"Number of Object Points (i.e. Pick Points) "]
[null,46,null,"Number of Validation Points"]
[null,47,null,"Manufacturer/software/consultant reports and printouts showing the results of the trajectory processing and refinement and accuracy level achieved"]
[null,48,null,"Manufacturer/software/consultant reports and printouts showing the results of the scan line point cloud processing, registration to control and accuracy level achieved"]
[null,49,null,"Cloud to Target registration – Statistics and comparison of how the point cloud fit to the targets"]
[null,50,null,"Comparison of elevation data between overlapping (side lap) runs and to the project validation/control elevations located in the overlap area"]
[null,51,null,"Comparison of elevation data between overlapping (cross lap) runs and to the project validation/control elevations located in the overlap area"]
[null,52,null,"Comparison of points at the area of overlap (end lap) if more than one GNSS base is used"]
[null,53,null,"Project targets and control points have been Geo-referenced to correct Michigan State Plane Zone, vertical datum (NAVD88), utilizing GEOID____"]
[null,54,null,"Project Accuracy reports of collected GNSS data as well as PDOP and SV visibility"]
[null,55,null,"Project Accuracy reports of collected IMU data"]
[null,56,null,"Project Trajectory reports including a comparison of the forward and reverse runs as well as the combined forward/reverse run"]
[null,57,null,"Comparison spreadsheet showing the differences (fit) of the resultant combined point cloud to the validation points. This spreadsheet shall include a resultant summary in NSSDA format of all the validation points (minimum of 20 required) showing the 95% difference in horizontal X and Y, and Vertical Z for the project"]
[null,"PWISE - STRUCTURES FOLDER"]
[null,{"$f":"B72+1","v":58},null,"XXXXXX_Elevation_Sketches_structure designation.pdf\nSketch of both sides of structure in elevation view with the following information displayed: "]
[null,59,null,"Bridge Seat Elevations"]
[null,60,null,"Reference Point Elevations"]
[null,61,null,"Top of Footing Elevations"]
[null,62,null,"Underclearance Distances"]
[null,63,null,"Water Surface Elevation"]
[null,64,null,"Other Elevations ________________"]
[null,65,null,"Dimensions of Existing Substructure Elements"]
[null,66,null,"XXXXXX_Plan_Sketches_structure designation.pdf\nSketch of structure in plan view with the following information displayed: "]
[null,67,null,"Dimensions of Existing Substructure Elements"]
[null,{"$f":"B83+1","v":68},null,"Face to Face Existing Substructure Measurements"]
[null,69,null,"Reference Point Elevation, Stationing & Coordinates"]
[null,70,null,"Angle of Crossing of Existing Substructure Units with bridge Alignment"]
[null,71,null,"XXXXXX_Images_structure designation.zip\nZIP file of all digital photos of the structure.  If multiple structures, create a separate zip file for each."]
[null,72,null,"S_######_BXX_Name_of_Watercourse_Culvert_Detail_Form.pdf or S_######_BXX_Name_of_Watercourse_Structure_Detail_Sketch.pdf","x","IF XXXXXX_Elevation_Sketches_structure designation.pdf and XXXXXX_Plan_Sketches_structure designation.pdf are selected do not use"]
[null,"PWISE -HYDRO FOLDER"]
[null,{"$f":"B88+1","v":73},null,"XXXXXX_Hydraulics_20YY-MM-DD.dgn\nThis DGN is a COPY of the S-XXXXXX_Survey_3D_20YY-MM-DD.dgn file.  All levels not pertaining to items required in the Hydraulics Survey Scope should be turned off, then use the \"Save Settings\" command.  (Do Not Delete them from the .dgn)"]
[null,{"$f":"B90+1","v":74},null,"XXXXXX_Riparian_Owners.pdf\nMap of the riparian owners and addresses in the four quadrants of the structure and water course"]
[null,75,null,"XXXXXX_Hydro_Chains_20YY-MM-DD.csv\nThe HYDRO chains in specific MDOT format"]
[null,76,null,"XXXXXX_High_Pt_Chains_20YY-MM-DD.csv\nThe HIPTC chains in specific MDOT format"]
[null,77,null,"XXXXXX_RWS_Chain_20YY-MM-DD.csv\nThe RWS chains in specific MDOT format"]
[null,78,null,"XXXXXX_LWS_Chain_20YY-MM-DD.csv\nThe LWS chains in specific MDOT format"]
[null,79,null,"XXXXXX_River_HYDRO - Bank Stations Table.csv \nThe bank points of the Hydro chains csv in a specific MDOT format"]
[null,80,null,"XXXXXX_Images_Hydro_water course name.zip\nZIP file of all digital photos of the water course.  If multiple water courses, create a separate zip file for each."]
[null,81,null,"XXXXXX_Hydro_ExTerrain_20YY-MM-DD.xml\nThe 3D triangle file exported to a LandXML format, by selecting the option \"Export Both\" in the selection box for the Export Options, this will include the triangles and features of the surface within the LandXML file.  "]
[null,"PWISE - MISCELLANEOUS FOLDER",null,null,"x"]
[null,{"$f":"B98+1","v":82},null,"Data not assignable to one of the other five sections may be placed here and must be discussed in the survey report.  Examples of appropriate site specific information might be: newspaper articles, photos of the project site looking up and down the roadway, various aspects of a structure, etc. Photos shall be submitted in native format and annotated. All documents (excluding photos taken at time of survey) must be included in the Survey Portfolio PDF.","x"]
[null,"PWISE - PA 132 CERTIFIED SURVEYS FOLDER"]
[null,{"$f":"B100+1","v":83},null,"S-XXXXXX_PA132_20YY_MM_DD.dgn\nThis Georeferenced DGN is a composite drawing showing all the parent parcels affected by the proposed R.O.W. that will be submitted to design.  All information represented needs to be in it's true geographical position."]
[null,{"$f":"B102+1","v":84},null,"CS#####_ JN######_Parcel #### Survey.dgn\nThis Georeferenced DGN is the final Certified Survey drawing.  It should only containg the drawing of the surveyed Parcel with the MDOT Certified Survey boarder.  The MDOT Certified Survey boarder DGN can be downloaded from the MDOT Resources web page."]
[null,{"$f":"B103+1","v":85},null,"CS#####_JN######_Parcel #### Description.docx\nThis Word file (docx) contains the final legal descriptions, notes and witnesses with the MDOT Certified Survey boarder.  The MDOTdescription and notes Word file (docx) can be downloaded from the MDOT Resources web page."]
[null,86,null,"CS#####_ JN######_Parcel #### Survey.pdf\nThis is a Georeferenced PDF copy of the final signed and sealed Certified Survey (contains the drawing and legal descriptions, notes and witnesses)."]
[null,87,null,"CS#####_ JN######_Parcel #### Survey Recorded.pdf\nThis is a PDF copy of the recorded final signed and sealed Certified Survey (containing the Liber and Page assigned by the Register of Deeds)."]
[null,"PWISE - RID FOLDER",null,null,"x"]
[null,{"$f":"B106+1","v":88},null,"S-XXXXXX_Survey_Info_Sheet_20YY-MM-DD.doc\nThe header should outline the company name, month and year of point establishment, datum, geoid used, SPC zone, the formula to convert from grid to ground distances, average combined scale factor, and the horizontal and vertical control points held fixed in the adjustments.  This document will list all Primary Control, Intermediate Control, Benchmarks, Photogrammetry Target points, PLSS Corners, and Alignment Points.  \nHorizontal Control shall include Northing, Easting, Elevation, standard deviation (2 sigma) in each coordinate, point scale factor to 12 significant figures, description of the monument, station and offset and witnesses.  \nVertical Control  shall include Northing, Easting to the nearest foot (1.0'), elevation with standard deviation (2 sigma), point scale factor to 12 significant figures, description of the monument, station and offset and witnesses.","x"]
[null,{"$f":"B108+1","v":89},null,"S-XXXXX_ControlPts_20YY-MM-DD.txt\nA comma delimited file (ASCII text) of all the points listed above in the Survey Info Sheet.  The file shall be created in the following format:  (Point name / number, Northing, Easting, Elevation, and Description)","x"]
[null,90,null,"S-XXXXXX_Align_ROW_20YY-MM-DD.dgn and S-XXXXXX_Align_ROW_20YY-MM-DD.pdf\nAn alignment and ROW drawing (.dgn format) with:\n        Station and coordinates of the POB and POE.\n       Alignment attributes on appropriate levels.\n       Alignment annotation shall be as follows:\n          “ROADWAY + LEGAL or NON-LEGAL + (Name of alignment).”\n       An alignment key including the following:\n            Name of the Company that created the alignment\n            Job Number: XXXXXX, Control Section: XXXXX, XXXXX, Etc...\n            List of All Retraced Alignments (provided with survey deliverables):\n                       Route Name + Legal or Non-Legal + (Name of alignment) = \n                       Route Name,\n                       Origin Year,\n                       Type of Alignment \"Construction Alignment, Survey Alignment, etc.\",\n                       From Project Number XXXXXX,\n                       \"as retraced for\" Job Number XXXXXX,\n                       in \"Year of retracement (MM/DD/YYYY)\" \n                    e.g. - M-43 LEGAL CALIL = M-43, 1954 CONSTRUCTION ALIGNMENT FROM PROJECT\n                            82-24, AS RETRACED FOR JOB NUMBER 111659 IN 2011.\n            Name of Michigan Professional Surveyor responsible for new and retraced alignments provided\n            Note about the Type of ROW shown (Legal or Non-Legal)\n            Horizontal Datum: ___________________[Ex. NAD83(CORS2011) MSPC Central Zone(2112)]\n            Average Combined Scale Factor: 0.000000000000 (Must be to 12 decimal places)\n            Grid Distance/Combined Scale Factor = Ground Distance\n   ","x"]
[null,91,null,"Continued Requirements for S-XXXXXX_Align_ROW_20YY-MM-DD.dgn\nand S-XXXXXX_Align_ROW_20YY-MM-DD.pdf\n       “Survey Alignment ROW Drawing Requirements\" and alignment annotation requirements\n                       described in the document have been complied with to create both DGN and PDF files. \n                       (Click Icon at left for a copy of document.)\n                       Or see Chapter 4 Section 2.2.1 of the Survey Standards of Practice. \n                       https://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=105c56b1-a778-42f2-aa93-1b32ac1e50ce&fileName=%22Survey%20Alignment%20ROW%20Drawing%20Requirements.pdf%22\n       Complete curve data including:\n            Deflection angle (RT or LT), radius, external, tangent length\n            PC, PI and PT stations and coordinates\n       Section Corner ties annotated by bearing and distance along the section line from found PLSS corners to\n          the intersection with the alignment.\n       The location of the existing Right of Way \n       Right of Way attributes on appropriate levels.\n       Checked the Direction Ahead Bearing and Direction Back Bearing from the curve data to the Tangent\n          Bearing coming in to and out of the curve data to ensure that they are the same to prevent non-tangential\n          curves.\n       Alignments must be a complex element and the appropriate Bentley feature name and definition are applied.  \n       The DGN and PDF file must be georefenced. (https://stateofmichigan.sharepoint.com/sites/MDOT-SPC-DevelopmentGuide/SitePages/Project-PDF.aspx)","x"]
[null,92,null,"S-XXXXXX_Align_XML_20YY-MM-DD.xml\nAlignment(s) exported to a LandXML format. \nNote: Alignments must start on a tangent segment not on a curve segment. Curves containing delta’s of 180 degrees or greater must be broken into two curve segments.\n","x"]
[null,93,null,"S-XXXXXX_Survey_3D_20YY-MM-DD.dgn\n3D - Map of the project area generated from Open Roads Designer (ORD)","x"]
[null,94,null,"S-XXXXXX_Survey_2D_20YY-MM-DD.dgn\nExport out a 2D Planimetric Map from the 3D Map of the project area generated from ORD","x"]
[null,95,null,"S-XXXXXX_ExTerrain_20YY-MM-DD.dgn\n3D triangle file [(contains triangles, clip boundary(ies) and voids (i.e. - obscured areas), of all terrain models including bridge decks]","x"]
[null,96,null,"S-XXXXXX_ExTerrain_20YY-MM-DD.xml\nThe 3D triangle file exported to a LandXML format","x"]
[null,97,null,"S-XXXXXX_ExTerrain_Deck_structure designation_20YY-MM-DD.xml\n3D triangle file exported to a LandXML format of each of the individual Deck terrain models.","x"]
[null,"ALIGN ROW PORTFOLIO PDF - SURVEYORS ALIGNMENT AND ROW REPORT",null,null,"x"]
[null,{"$f":"B117+1","v":98},null,"Surveyor’s Alignment and ROW Report, Containing a complete synopsis of the alignment and ROW survey including, but not limited to: ","x"]
[null,{"$f":"B119+1","v":99},null,"Explanation of any deviation from the Scope and/or the Standards.","x"]
[null,100,null,"Provide a complete discussion of all Alignments relative to the project. Specify information and methods used to determine the location and designation of each such as accepted monumentation and documents used to support your determination.","x"]
[null,101,null,"Property boundary issues addressed, with specific information that may be useful for a surveyor to retrace or an engineer during design.  If necessary, include a summary of conversations with property owners and their concerns.","x"]
[null,102,null,"Alignment information must be certified, signed and sealed by the Professional Surveyor as described in the Alignment section of the Standards of Practice.","x"]
[null,103,null,"Research\nResearch information used to establish alignment and ROW such as (but not limited to):\n         ■   MDOT survey records/ ROW Maps\n         ■   MDOT deeds/easements, ROW releases, adjacent private land owner deeds.\n         ■   LCRCs for PLSS corners\n         ■   Recorded/Unrecorded Plats\n         ■   Recorded/Unrecorded Surveys\n         ■   Tax descriptions of adjacent properties","x"]
[null,104,null,"Tax Maps\nMark maps with location and point numbers of the property corners located in the field.","x"]
[null,105,null,"Field Notes\nScanned copies of field notes pertaining to alignment and ROW work.","x"]
[null,"SURVEY PORTFOLIO PDF - ADMINISTRATIVE SECTION",null,null,"x"]
[null,{"$f":"B126+1","v":106},null,"Vicinity Map\nScreen capture from Street Atlas, Google Maps, or some other resource with the POB and POE labeled","x"]
[null,{"$f":"B128+1","v":107},null,"Surveyor’s Project Report, divided into subsections, containing a complete synopsis of project survey including, but not limited to: ","x"]
[null,108,null,"Explanation of any deviation from the Scope and/or the Standards.","x"]
[null,109,null,"Basis of horizontal and vertical control, with specific emphasis on datum sources used (list CORS and NAVD benchmarks tied), equipment, software, methods used to establish the coordinates and methods used to detect errors and eliminate them. If RTK is used, explain the methodology, equipment and procedure used. Include a detailed explanation relating to CORS usage or site calibration (Base Station) (for level loops, Primary and Intermediate Control networks).","x"]
[null,110,null,"Indicate Geoid Model used.","x"]
[null,111,null,"Statement indicating whether Precise or Rapid ephemeris has been used to process final solutions (OPUS RS can not be used).","x"]
[null,112,null,"Statement indicating  adherence to observation procedures per Appendix B of the current version of the Standards of Practice for use of OPUS to establish the horizontal datum.","x"]
[null,113,null,"Statement indicating that OPUS elevations have not been used for determining vertical control for the project, unless approved by the Survey Project Manager.","x"]
[null,114,null,"Statement indicating that for groups of control points spaced less than 1500 feet apart, the following procedures were followed: All of the points are submitted to OPUS and the baselines between the groups of points shall be calculated using conventional post processing techniques, using the OPUS derived values as a check.\n","x"]
[null,115,null,"Statement indicating that if a mark is used in multiple lists, such as a control point and a bench mark; it shall carry the same designation in each.  All lists shall include the mark name or number, description of the monument, station and offset, and coordinates.","x"]
[null,116,null,"Mapping information for the project should be summarized per the Standards Of Practice dialog. ","x"]
[null,117,null,"Any mapping issues encountered, with specific information that may be useful for an engineer during design.","x"]
[null,118,null,"Any information obtained regarding drainage issues observed or reported by local authorities or residents should be discussed","x"]
[null,119,null,"Explanation of how the Reference Point locations were determined for Bridge Surveys."]
[null,120,null,"Discuss the contents of anything that appears in the Miscellaneous section.","x"]
[null,121,null,"The signed, sealed, and dated “PROFESSIONAL SURVEYOR’S   CERTIFICATION FOR MDOT PROJECTS” as detailed in the Standards of Practice.","x"]
[null,122,null,"MDOT Survey Project Check List\nThis Form, completed, signed & sealed, indicating that all project related items are accounted for.","x"]
[null,123,null,"QA/QC Certification\nSigned and sealed by the lead QA/QC person (See the Survey Standards of Practice (May 2014) Quality Assurance/Quality Control section – Page 27.) - NOTE: This is not the QA/QC statement from the QA/QC Checklist.","x"]
[null,124,null,"Notice of Authorization\nMDOT form 5180 Acceptance of Priced Proposal & Authorization for Consultant to Proceed attached documents as received from MDOT Contract Services Division (remove Cost Derivation pages).  This will include the MDOT authorization, Priced Proposal, Work Plan and the original Attachment \"C\".","x"]
[null,125,null,"MDOT Form 5102 - Change of Scope\nOnly required if there was an actual change of scope after initial authorization.","x"]
[null,126,null,"Work Permits Required for the Project","x"]
[null,127,null,"Correspondence\nMinutes of Meetings, phone conversations, emails and any other project related correspondence.","x"]
[null,"SURVEY PORTFOLIO PDF - CONTROL SECTION",null,null,"x"]
[null,{"$f":"B149+1","v":128},null,"MDOT Monument Establishment Sheet\nAll Primary Control Points established and or used as part of this project (contact Lansing survey Support Office for template).","x"]
[null,{"$f":"B151+1","v":129},null,"NGS Data Sheets.","x"]
[null,130,null,"NGS Mark Recovery Forms.","x"]
[null,131,null,"GPS v EDM Control Comparison\nInclude a table of GPS and EDM observations for Primary Control showing: Average Combined Scale Factor, Measured GPS Grid Distance, Calculated GPS Ground Distance, Measured EDM Ground Distance and Δ Distance (GPS Ground – EDM Ground).","x"]
[null,132,null,"Field Notes\nScanned copies of field notes pertaining to control work.","x"]
[null,133,null,"Primary Control Plot\nPlot(s) of the GPS network(s) from GPS software and sketch(s) or plot(s) of network or traverse with legible point numbers for Primary Control.","x"]
[null,134,null,"Intermediate Control Plot\nPlot(s) of the GPS network(s) from GPS software and sketch(s) or plot(s) of network or traverse with legible point numbers for Intermediate Control.","x"]
[null,135,null,"Reports for Primary Control horizontal adjustments including: (Check all that apply).\n            Minimally                   Fully\n          Constrained            Constrained\n                                                                input parameters, a-priori, centering error, etc\n                                                                raw unadjusted closures \n                                                                final coordinates with standard deviations (2 sigma)\n                                                                vector input data and analysis.  \n                                                                histograms  \n                                                                error ellipses  \n                                                                traverse closures  \n                                                                statistical test results  \n                                                                horizontal and vertical datums, ellipsoid, SPC zone and units (IF)\n                                                                name of the adjustment program used with \n                                                                      version or release. \n           OR supply all written calculations to support the final results.  \n          Only Non-trivial vectors used \n","x"]
[null,136,null,"Reports for Intermediate Control horizontal adjustments including: (Check all that apply).\n            Minimally                   Fully\n          Constrained            Constrained\n                                                                input parameters, a-priori, centering error, etc\n                                                                raw unadjusted closures \n                                                                final coordinates with standard deviations (2 sigma)\n                                                                vector input data and analysis  \n                                                                histograms  \n                                                                error ellipses  \n                                                                traverse closures  \n                                                                statistical test results  \n                                                                horizontal and vertical datums, ellipsoid, SPC zone and units (IF)\n                                                                name of the adjustment program used with \n                                                                      version or release. \n           OR supply all written calculations to support the final results.  \n          Only Non-trivial vectors used \n","x"]
[null,137,null,"OPUS Requirements\nStation Observation Sheets and copies of the OPUS Extended Output files.","x"]
[null,138,null,"Reports for Vertical adjustments including: (Check all that apply).\n            Minimally                   Fully\n          Constrained            Constrained\n                                                                input parameters\n                                                                raw unadjusted closures \n                                                                final elevations with standard deviations (2 sigma)\n                                                                loop closures  \n                                                                statistical test results.  \n                                                                horizontal and vertical datums, ellipsoid, SPC zone and units (IF)\n                                                                name of the adjustment program used with version or release. \n           OR supply all written calculations to support the final results.","x"]
[null,"SURVEY PORTFOLIO PDF - MAPPING SECTION",null,null,"x"]
[null,{"$f":"B161+1","v":139},null,"Research\nResearch information related to project mapping such as (but not limited to):\n         ■   Old MDOT plans (only include pertinent pages)\n         ■   Aerial photos/images\n         ■   Plans/Maps from local agencies","x"]
[null,{"$f":"B163+1","v":140},null,"Field Notes\nScanned copies of field notes pertaining to mapping.","x"]
[null,141,null,"Calculations\nOnly relative to mapping such as temporary Control Points/Benchmarks.","x"]
[null,"SURVEY PORTFOLIO PDF - STATIC TERESTRIAL LASER SCANNING (STLS) SECTION"]
[null,{"$f":"B165+1","v":142},null,"Scanning Report\nMust contain all of minimum requirements of Appendix C-1-b items."]
[null,{"$f":"B167+1","v":143},null,"Sketch of scanning setups and target locations"]
[null,144,null,"Scanning Control Point list"]
[null,145,null,"Registration residuals"]
[null,146,null,"QA/QC spreadsheet for check shots"]
[null,147,null,"Field Notes\nScanned copies of field notes pertaining to STLS."]
[null,"SURVEY PORTFOLIO PDF - MOBILE TERESTRIAL LiDAR (MTL) SECTION"]
[null,{"$f":"B172+1","v":148},null,"Location map\nShowing the MDOT project limits area, coverage of the MTL acquisition and the locations of GNSS base stations and CORS used."]
[null,{"$f":"B174+1","v":149},null,"MTL Final Report\nSpecifically describes the Mobile LiDAR project and includes the following:"]
[null,150,null,"Final version of Interim Report developed in the Processing Trajectories, Scan Line Processing and Point Cloud Registration section prepared for the interim early delivery to MDOT - may be exact copy of original submittal OR be revised to discuss any adjustments required from the review of the interim deliverables."]
[null,151,null,"Planning, acquisition, processing, and point cloud preparation"]
[null,152,null,"Describes, at a minimum, how the requirements of Appendix D were met"]
[null,153,null,"Describes how the MTL acquisition was controlled, whether via use of CORS (list CORS used and distances from project) or via local GNSS base station(s) (and methods used to establish) or some other method for tying the MTL to the project coordinates."]
[null,154,null,"Describes the limits of MTL, limits of any supplemental survey mapping and how the data was merged if required for the overall project"]
[null,155,null,"Statement that LiDAR acquisition has been done when pavement is dry. If not, explain and describe weather conditions and conditions of pavement surface"]
[null,156,null,"Statement that LiDAR acquisition settings and operating speed were done in a manner to maintain accurate data and consistent data spacing throughout the project"]
[null,157,null,"Statement that LiDAR acquisition included collection of images along the trajectory routes to colorize the point cloud"]
[null,158,null,"List the number of passes completed along each corridor or per trajectory that were used to acquire point cloud data and limit resulting obscured areas:\nNumber of Passes = _____________\n"]
[null,159,null,"List the percentage of side overlap of adjacent scan passes:  ______________%"]
[null,160,null,"Data extracted from LiDAR point clouds have been delivered with a consistent spacing used by all operators.\nList average spacing between vertices when extracting line features: ___________ feet.   \nList average spacing used in extracting spot shots (e.g. parking areas, terrain, slopes, etc.): ________ft. by ________ ft. grid.\n"]
[null,161,null,"PDF of Comparison spreadsheet showing the fit of the control points/targets to the final point cloud. This spreadsheet shall include a resultant summary in NSSDA format showing the 95% differences in horizontal X and Y, and Vertical Z for the project. (The TopoDOT Control points to point cloud analysis tool that outputs a spreadsheet and chart diagram is one accepted option.)"]
[null,162,null,"PDF of Comparison spreadsheet showing the differences (fit) of the final project DTM surface to the validation points. This spreadsheet shall include a resultant summary in NSSDA format showing the 95% differences in horizontal X and Y, and Vertical Z for the project"]
[null,163,null,"PDF of Comparison spreadsheet showing the differences (fit) of the final project DTM surface to the validation points. This spreadsheet shall include a resultant summary in NSSDA format showing the 95% differences in horizontal X and Y, and Vertical Z for the project."]
[null,164,null,"Field Notes\nScanned copies of field notes pertaining to MTL."]
[null,"SURVEY PORTFOLIO PDF - STUCTURES SECTION"]
[null,{"$f":"B190+1","v":165},null,"Elevation View Sketch\nInsert the Elevation View Sketch of the structure(s)."]
[null,{"$f":"B192+1","v":166},null,"Plan View Sketch\nInsert the Plan View Sketch of the structure(s)."]
[null,167,null,"MDOT Culvert Form(s)\nInsert the appropriate MDOT culvert form(s)"]
[null,168,null,"Field Notes\nScanned copies of field notes pertaining to structures."]
[null,169,null,"Bridge As-builts\nThe specific pages of MDOT bridge as-built plans used to calculate reference points/lines (not entire plan set)."]
[null,170,null,"S_######_BXX_Name_of_Watercourse_Culvert_Detail_Form.pdf or S_######_BXX_Name_of_Watercourse_Structure_Detail_Sketch.pdf",null,"IF Elevation view Sketch and Plan view Sketch are selected do not use"]
[null,"SURVEY PORTFOLIO PDF - HYDRAULICS SECTION"]
[null,{"$f":"B197+1","v":171},null,"Field Notes\nScanned copies of field notes pertaining to hydraulics."]
[null,"SURVEY PORTFOLIO PDF - MISCELLANEOUS SECTION",null,null,"x"]
[null,{"$f":"B199+1","v":172},null,"Documents from the Miscellaneous folder.  Photos taken during the project will not be inserted here.","x"]

{"sheet":"ORD","index":2,"n_rows":35,"n_cols":5,"rows_kept":35,"cut":false,"hidden":false,"merged":[[0,4,1,4],[0,0,1,0],[0,1,1,1],[0,2,1,2],[0,3,1,3]]}
["Item #","QA/QC Review\nby Consultant","Open Roads Designer (ORD) Files\n","Required Item","PM Notes"]
[]
[200,null,"The required DGN scale is: 1 inch = ___ feet","x"]
[{"$f":"A3+1","v":201},null,"The correct zone specific seed file was used and the Geographic Coordinate System Library Settings have been verified to ensure that the correct state plane coordinate zone is attached.","x"]
[{"$f":"A4+1","v":202},null,"Current MDOT workspace utilized. ","x"]
[203,null,"Only MDOT Feature Codes per the most current version of the MDOT survey codelist. ","x"]
[204,null,"Points and Chains must be stored in one fieldbook within the Survey database in ORD, or as discussed with the PM.  ","x"]
[205,null,"Terrain chains are defined as \"generated by point list\" within ORD, with the exception of the terrain model boundary.  ","x"]
[206,null,"The Control Point list coordinates have been compared to the coordinates in the DGN file.","x"]
[207,null,"The Benchmark list elevations have been compared to the elevations in the DGN file.","x"]
[208,null,"The Alignment Point list coordinates have been compared to the coordinates in the DGN file.","x"]
[209,null,"The PLSS Corner list coordinates have been compared to the coordinates in the DGN file.","x"]
[210,null,"All Survey Linear Features are edited; properly connected; patterns checked for proper direction, correctness, and aesthetics.","x"]
[211,null,"All Survey Linear Feature crossings resolved using the ORD Report Crossing Features tool.  ","x"]
[212,null,"Alignment and ROW data is not included in the 3D drawing.  ","x"]
[213,null,"Hydro Survey Chains checked for correct left to right direction."]
[214,null,"Hydro RWS and LWS Survey Chains checked to make sure each line is one continous linear feature with the correct code and begins at the furthest downstream end and ends at the furthest upstream end. ","x"]
[215,null,"Deck survey chain(s) for Structure(s)"]
[216,null,"Abutment survey chain(s) for Structure(s)"]
[217,null,"Wing wall survey chain(s) for Structure(s)"]
[218,null,"Terrain Model Road Project – EXRD, EXRD1, EXRD2, etc. for multiple model","x","217 and 218 can be selected together but they should not be selected with 219"]
[219,null,"Terrain Model Bridge Deck - structure designation, CS12345S01, CS12345B02NB, CS12345B02SB, CS12345X02 etc. for multiple deck models as discussed with the project manager.  ","x"]
[220,null,"Terrain Model Road & Bridge Deck Combined Project – EXRDDK, EXRDDK1, EXRDDK2, etc. for multiple models ",null,"typically used for resurfacing projects and not reconstruction of bridge structures"]
[221,null,"Terrain Model Photo Mapping – EXPHO, EXPHO1, EXPHO2",null,"future rename?"]
[222,null,"Terrain Model  Supplemental Photo Survey – EXSUP, EXSUP1, EXSUP2",null,"future rename?"]
[223,null,"Terrain Model  Merged Photo / Supplemental Survey – EXMERG, EXMERG1, EXMERG2",null,"future rename?"]
[224,null,"Terrain Model checked for invalid break lines and point data","x"]
[225,null,"Terrain Model triangles checked for spikes and dips","x"]
[226,null,"Long or invalid triangles have been obscured from Terrain Model","x"]
[227,null,"The appriopriate Terrain Model Feature Definition applied for contours:\n       E_Contours -1 & 5  \n       E_Contours -2 & 10","x"]
[228,null,"Bridge Deck removed from Terrain Model except when required for approach work"]
[229,null,"Water course removed from Terrain Model","x"]
[230,null,"Terrain surface beneath bridge decks is included in Terrain Model Road Project","x"]
[231,null,"Annotation Scale Enabled","x"]
[232,null,"The DGN files have been compressed. ","x"]

{"sheet":"COMMENTS","index":3,"n_rows":1,"n_cols":2,"rows_kept":1,"cut":false,"hidden":false,"merged":[[0,1,0,8]]}
["ITEM #","COMMENT"]

{"sheet":"QAQC STATEMENT","index":4,"n_rows":4,"n_cols":2,"rows_kept":4,"cut":false,"hidden":false,"merged":[]}
[]
[]
[]
[null,"Yes    No     Scope has been reviewed to insure compliance. (Circle one)\n\n\nI ______________________, P.S. as lead QA/QC Surveyor in charge on this contract authorization have thoroughly reviewed the survey notes and scope of work and certify that all required and requested information has been electronically submitted to MDOT and is in compliance with the MDOT Survey Standards of Practice, the Survey Scope of Work, and this QA/QC Checklist, unless otherwise noted. Any individual check box left blank or marked N/A has been explained in the Comments following the checklist.\n\n\n     \n\n\n\n                                                            _____________________________________\nSEAL                                                        Professional Surveyor signature and date\n"]