Common use of GIS SUBMISSION REQUIREMENTS AND STANDARDS Clause in Contracts

GIS SUBMISSION REQUIREMENTS AND STANDARDS. All ROW Mapping project work authorizations are subject to the following submission requirements and standards: a. The required geo-referenced parcel data (features) must be submitted in ArcGIS 10 format or the current version in use by the State and in the format of the current ROW Geo-Database Template, which shall be provided by the State. b. The template is available for download from the ROW Division’s webpage on the State’s internet site (▇▇▇▇▇.▇▇▇), along with more detailed requirements. c. The template’s Coordinate System is Geographic coordinates (longitude and latitude), North American Datum of 1983 in Decimal Degrees (8 or more place after the decimal point). d. The data must be geospatially correct and submitted to the State in the exact format of the template. DocuSign Envelope ID: B8B3CD6B-A26C-4D40-A13B-9771D9AA4591 8. ELECTRONIC RIGHT-OF-WAY MAPPING STANDARDS The primary purpose of this section is to provide instructions for the graphics standards, file management structure, and naming conventions, for right-of-way mapping electronic deliverables submitted to the State’s Right-of-Way Division by the Districts, other Divisions, and Consultants, as an integral part of the right-of-way mapping package. The software, file types and file formats must be compatible with those used by the District/Division Design for Schematics and PS&E (e.g., native MicroStation V8i files for graphics, Microsoft Office Word 2010 for metes and bounds descriptions). a. MicroStation V8i b. Level Library Files The Surveyor shall use the State’s current MicroStation V8i Level Library Files for right-of-way mapping. The files contain all the predefined levels that will normally be needed for right-of-way mapping and to show existing utilities. c. Separate DGN Files for Each Map Sheet The Surveyor shall provide one DGN file for each map sheet so that each right-of-way map sheet is spatially correct (snapping on elements gives correct coordinate values), This allows multiple users to work on different sheets at the same time from a server in production, with all the sheets utilizing the same master reference files. (Note: It is possible to have all the sheets in one DGN, but only one person at a time would be able to work on the project.) The sheet file naming convention is “ROW CSJ_Sheet Number.dgn”, with an example as follows: “212104065_S01.dgn” In the example above, the first nine (9) numbers “212104065” is the right-of-way CSJ for the project and “S01” is the sheet number, beginning with number 1 as the cover sheet. DocuSign Envelope ID: B8B3CD6B-A26C-4D40-A13B-9771D9AA4591 d. Format of the MDF/MRF (Master Design File or Master Right-of- Way Files) DGN Reference Files and Map Sheet Naming Conventions The recommended naming prefix for design files is MDF (Master Design File). Therefore, the prefix must be different for the right-of- way files because the location of the existing and proposed right-of- way in the design files from the schematic will change to some degree after an on the ground survey is made for right-of-way mapping. Therefore, the prefix could be MRF for Master Right-of- Way File. The corrected Master Right-of-Way Files shall be given to the design engineer to be used in the final PS&E so that all features of construction and the relocation of utilities shall be correctly placed in relation to the highway right-of-way and the right-of-way of cross streets or roadways. The Master Right-of-Way File naming convention is: “MRF ROW CSJ_Logical Name.dgn”, with examples as follows: MRF212104065_Schematic90.dgn (Schematic layout 90% submittal); MRF212104065_Schematic100.dgn (Schematic layout 100% submittal); MRF212104065_SchemApprov.dgn (Final Approved [State & FHWA] Schematic); MRF212104065_PSEDesign.dgn (Final P.S.&E. Design); MRF212104065_ExROW.dgn (Existing right-of-way determined by RPLS); MRF212104065_PropROW.dgn (Proposed right-of-way of final design); MRF212104065_DeedPlot.dgn (Deed Record); MRF212104065_Planimetric.dgn (Aerial mapping topography); MRF212104065_ROWTopo.dgn (Improvements data collection); MRF212104065_DesignTopo.dgn (Design level data collection topography); MRF212104065_ExUtil.dgn (Existing utilities), etc. All sheet files with a plan view must have the MRF referenced to allow more than one sheet file to be worked on at the same time. e. File Structure of Master and Reference DGN Files If possible, the file structure will not have any subfolders, to allow better transfer of data to different PC or server drive names or DocuSign Envelope ID: B8B3CD6B-A26C-4D40-A13B-9771D9AA4591 CD/DVD’s without path problems to reference files when the sheet files are opened. f. Lines Weights, Line Styles, Colors, Text Size, Text Fonts, Scale, and Annotations Legibility is the primary concern when choosing the scale, line weights and text size. Not only must the sheets be legible at full scale sheet size (22 inches x 34 inches), they must be completely legible at half scale sheet size (11 inches x 17 inches). Even if the originals or first generation plots are legible, the reproductions (copies) must also be legible. The normal scales for the full scale sheet size must be 1 inch = 50 feet (urban) and 1 inch = 100 feet (rural), which shall be 1 inch = 100 feet and 1 inch = 200 feet, respectively, when plotted or reduced to the half scale sheet size. Minimum line weights, text size and text font are dictated by legibility at half scale sheet size (11 inches x 17 inches). Even if the originals or first generation plots are legible, the reproductions (copies) must also be legible. Standard cell library: TxdotSurv_04.cel or current State cell files; Standard Font: 1 ▇▇▇▇▇; and standard State color tables: V256COLR.ctb or Txgpk.ctb. The Surveyor shall use the State’s current GEOPAK Survey SMD file that sets up new feature codes in SMD file for alignment chains, parcel chains and survey chains that can be drawn by GEOPAK Survey from the GPK file with the correct line styles, colors and weights to the designated levels loaded into the dgn by the State’s current level library files. The Surveyor shall use MicroStation Packager for the submission of electronic deliverables, which would capture any non-State standard rsc, cel, text, etc. files that were used in the mapping that look and plot differently in the State’s MicroStation® V8i workspace. g. Text and Line Colors When Using Color Digital Orthoimagery in the Background The predominate colors of the digital orthoimagery (greens, browns, etc) dictate which line and text colors stand out and are legible. Some degree of trial and error is sometimes needed. DocuSign Envelope ID: B8B3CD6B-A26C-4D40-A13B-9771D9AA4591 h. Required Data in the GEOPAK Right-of-Way GPK File Alignments, chains of proposed and existing right-of-way lines, parent tracts and taking parcels, and all otherpoints collected in the field (start with schematic or design GPK file) are required. If the design GPK file is too detailed for right-of-way use, input files can be created for the information sought from the design GPK file to load into the right-of-way GPK file. i. Surface Coordinate and the ROW GIS Geo-Database Surface adjustment factors and basis of datum must be well documented in the electronic deliverables “file structure/deliverables read me” file. j. Requirements for Electronic Deliverables Native MicroStation V8i DGN files (reference files, sheets files, and parcel plats files); GEOPAK Survey GPK files; Separate comma delimited point files (ASCII file) and .csv file in the following types of coordinates: Surface or Projected Coordinates, Grid Coordinates (Texas Coordinate System of 1983 in U.S. Survey feet) and Geographic Coordinates (WGS-84 in decimal degrees) in the following format: point number, northing or latitude, easting or longitude, elevation, feature code, description. Text/.csv point file naming convention is: ROWCSJ_Type of Coordinates.csv (Example: 212101065_Surface.csv, 212101065_Grid.csv, and 212101065_WGS84.csv); PDF’s created in MicroStation V8i of Map Sheets (both 22 inches x 34 inches and 11 inches x 17 inches, one set in black and white and another set in color if there is orthoimagery for the background; PDF’s of signed and sealed Property Descriptions, Parcel Plats, and the Surveyor Reports and Microsoft Office Word 2010 documents of Property Descriptions and Surveyor’s Reports; Raw and processed GPS files including adjustment reports. DocuSign Envelope ID: B8B3CD6B-A26C-4D40-A13B-9771D9AA4591

GIS SUBMISSION REQUIREMENTS AND STANDARDS. All ROW Mapping project work authorizations are subject to the following submission requirements and standards: a. The required geo-referenced parcel data (features) must be submitted in ArcGIS 10 format or the current version in use by the State and in the format of the current ROW Geo-Database Template, which shall be provided by the State. b. The template is available for download from the ROW Division’s webpage on the State’s internet site (▇▇▇▇▇.▇▇▇), along with more detailed requirements. c. The template’s Coordinate System is Geographic coordinates (longitude and latitude), North American Datum of 1983 in Decimal Degrees (8 or more place after the decimal point). d. The data must be geospatially correct and submitted to the State in the exact format of the template. DocuSign Envelope ID: B8B3CD6B9A5E574C-A26C-4D40F6F1-A13B-9771D9AA4591 4EA5-A0CA-CDE46BF87198 Contract No. 02-6IDP1010 8. ELECTRONIC RIGHT-OF-WAY MAPPING STANDARDS The primary purpose of this section is to provide instructions for the graphics standards, file management structure, and naming conventions, for right-of-way mapping electronic deliverables submitted to the State’s Right-of-Way Division by the Districts, other Divisions, and Consultants, as an integral part of the right-of-way mapping package. The software, file types and file formats must be compatible with those used by the District/Division Design for Schematics and PS&E (e.g., native MicroStation V8i files for graphics, Microsoft Office Word 2010 for metes and bounds descriptions). a. MicroStation V8i b. Level Library Files The Surveyor shall use the State’s current MicroStation V8i Level Library Files for right-of-way mapping. The files contain all the predefined levels that will normally be needed for right-of-way mapping and to show existing utilities. c. Separate DGN Files for Each Map Sheet The Surveyor shall provide one DGN file for each map sheet so that each right-of-way map sheet is spatially correct (snapping on elements gives correct coordinate values), This allows multiple users to work on different sheets at the same time from a server in production, with all the sheets utilizing the same master reference files. (Note: It is possible to have all the sheets in one DGN, but only one person at a time would be able to work on the project.) The sheet file naming convention is “ROW CSJ_Sheet Number.dgn”, with an example as follows: “212104065_S01.dgn” In the example above, the first nine (9) numbers “212104065” is the right-of-way CSJ for the project and “S01” is the sheet number, beginning with number 1 as the cover sheet. DocuSign Envelope ID: B8B3CD6B9A5E574C-A26C-4D40F6F1-A13B-9771D9AA45914EA5-A0CA-CDE46BF87198 Contract No. 02-6IDP1010 d. Format of the MDF/MRF (Master Design File or Master Right-of- Way Files) DGN Reference Files and Map Sheet Naming Conventions The recommended naming prefix for design files is MDF (Master Design File). Therefore, the prefix must be different for the right-of- way files because the location of the existing and proposed right-of- way in the design files from the schematic will change to some degree after an on the ground survey is made for right-of-way mapping. Therefore, the prefix could be MRF for Master Right-of- Way File. The corrected Master Right-of-Way Files shall be given to the design engineer to be used in the final PS&E so that all features of construction and the relocation of utilities shall be correctly placed in relation to the highway right-of-way and the right-of-way of cross streets or roadways. The Master Right-of-Way File naming convention is: “MRF ROW CSJ_Logical Name.dgn”, with examples as follows: MRF212104065_Schematic90.dgn (Schematic layout 90% submittal); MRF212104065_Schematic100.dgn (Schematic layout 100% submittal); MRF212104065_SchemApprov.dgn (Final Approved [State & FHWA] Schematic); MRF212104065_PSEDesign.dgn (Final P.S.&E. Design); MRF212104065_ExROW.dgn (Existing right-of-way determined by RPLS); MRF212104065_PropROW.dgn (Proposed right-of-way of final design); MRF212104065_DeedPlot.dgn (Deed Record); MRF212104065_Planimetric.dgn (Aerial mapping topography); MRF212104065_ROWTopo.dgn (Improvements data collection); MRF212104065_DesignTopo.dgn (Design level data collection topography); MRF212104065_ExUtil.dgn (Existing utilities), etc. All sheet files with a plan view must have the MRF referenced to allow more than one sheet file to be worked on at the same time. e. File Structure of Master and Reference DGN Files If possible, the file structure will not have any subfolders, to allow better transfer of data to different PC or server drive names or DocuSign Envelope ID: B8B3CD6B9A5E574C-A26C-4D40F6F1-A13B-9771D9AA4591 4EA5-A0CA-CDE46BF87198 Contract No. 02-6IDP1010 CD/DVD’s without path problems to reference files when the sheet files are opened. f. Lines Weights, Line Styles, Colors, Text Size, Text Fonts, Scale, and Annotations Legibility is the primary concern when choosing the scale, line weights and text size. Not only must the sheets be legible at full scale sheet size (22 inches x 34 inches), they must be completely legible at half scale sheet size (11 inches x 17 inches). Even if the originals or first generation plots are legible, the reproductions (copies) must also be legible. The normal scales for the full scale sheet size must be 1 inch = 50 feet (urban) and 1 inch = 100 feet (rural), which shall be 1 inch = 100 feet and 1 inch = 200 feet, respectively, when plotted or reduced to the half scale sheet size. Minimum line weights, text size and text font are dictated by legibility at half scale sheet size (11 inches x 17 inches). Even if the originals or first generation plots are legible, the reproductions (copies) must also be legible. Standard cell library: TxdotSurv_04.cel or current State cell files; Standard Font: 1 ▇▇▇▇▇; and standard State color tables: V256COLR.ctb or Txgpk.ctb. The Surveyor shall use the State’s current GEOPAK Survey SMD file that sets up new feature codes in SMD file for alignment chains, parcel chains and survey chains that can be drawn by GEOPAK Survey from the GPK file with the correct line styles, colors and weights to the designated levels loaded into the dgn by the State’s current level library files. The Surveyor shall use MicroStation Packager for the submission of electronic deliverables, which would capture any non-State standard rsc, cel, text, etc. files that were used in the mapping that look and plot differently in the State’s MicroStation® V8i workspace. g. Text and Line Colors When Using Color Digital Orthoimagery in the Background The predominate colors of the digital orthoimagery (greens, browns, etc) dictate which line and text colors stand out and are legible. Some degree of trial and error is sometimes needed. DocuSign Envelope ID: B8B3CD6B9A5E574C-A26C-4D40F6F1-A13B-9771D9AA45914EA5-A0CA-CDE46BF87198 h. Required Data in the GEOPAK Right-of-Way GPK File Alignments, chains of proposed and existing right-of-way lines, parent tracts and taking parcels, and all otherpoints collected in the field (start with schematic or design GPK file) are required. If the design GPK file is too detailed for right-of-way use, input files can be created for the information sought from the design GPK file to load into the right-of-way GPK file. i. Surface Coordinate and the ROW GIS Geo-Database Surface adjustment factors and basis of datum must be well documented in the electronic deliverables “file structure/deliverables read me” file. j. Requirements for Electronic Deliverables Native MicroStation V8i DGN files (reference files, sheets files, and parcel plats files); GEOPAK Survey GPK files; Separate comma delimited point files (ASCII file) and .csv file in the following types of coordinates: Surface or Projected Coordinates, Grid Coordinates (Texas Coordinate System of 1983 in U.S. Survey feet) and Geographic Coordinates (WGS-84 in decimal degrees) in the following format: point number, northing or latitude, easting or longitude, elevation, feature code, description. Text/.csv point file naming convention is: ROWCSJ_Type of Coordinates.csv (Example: 212101065_Surface.csv, 212101065_Grid.csv, and 212101065_WGS84.csv); PDF’s created in MicroStation V8i of Map Sheets (both 22 inches x 34 inches and 11 inches x 17 inches, one set in black and white and another set in color if there is orthoimagery for the background; PDF’s of signed and sealed Property Descriptions, Parcel Plats, and the Surveyor Surveyor’s Reports and Microsoft Office Word 2010 documents of Property Descriptions and Surveyor’s Reports; Raw and processed GPS files including adjustment reports. DocuSign Envelope ID: B8B3CD6B9A5E574C-A26C-4D40F6F1-A13B-9771D9AA45914EA5-A0CA-CDE46BF87198 The Surveyors shall prepare and submit the following: • An Abstract Map (Working Sketch) of the current record title holders. • A Preliminary Map showing the proposed schematic and existing right-of- way. • A Right-of-Way map for the project limits under cover of Title Sheet, Index Sheet, Control Data Sheet, and Exhibits of the property descriptions and parcel plats. • Documentation stating that the appropriate monuments were set on the proposed right-of-way lines at intersecting property lines, and at all PCs, PTs, angle points, intersecting right-of-way lines of side streets, and at 1,500 foot stations. • Documentation stating that the appropriate monuments were set on the existing right-of-way lines in areas of no acquisition at all PCs, PTs, angle points, and 1,500 foot stations, and as directed by the State. • The Surveyor’s report, outlining the approach, reasons or basis for the existing right-of-way determination, and conclusions made. • A copy of the State’s right-of-way mapping check list, signed by the Surveyor. A. Design Surveys and Construction Surveys

GIS SUBMISSION REQUIREMENTS AND STANDARDS. All ROW Mapping project work authorizations are subject to the following submission requirements and standards: a. The required geo-referenced parcel data (features) must be submitted in ArcGIS 10 format or the current version in use by the State and in the format of the current ROW Geo-Database Template, which shall be provided by the State. b. The template is available for download from the ROW Division’s webpage on the State’s internet site (▇▇▇▇▇.▇▇▇), along with more detailed requirements. c. The template’s Coordinate System is Geographic coordinates (longitude and latitude), North American Datum of 1983 in Decimal Degrees (8 or more place after the decimal point). d. The data must be geospatially correct and submitted to the State in the exact format of the template. DocuSign Envelope ID: B8B3CD6BA1F83282-A26C-4D4027A1-A13B-9771D9AA4591 4756-AFA4-EB689A1E9938 Contract No. 36-6IDP1443 8. ELECTRONIC RIGHT-OF-WAY MAPPING STANDARDS The primary purpose of this section is to provide instructions for the graphics standards, file management structure, and naming conventions, for right-of-way mapping electronic deliverables submitted to the State’s Right-of-Way Division by the Districts, other Divisions, and Consultants, as an integral part of the right-of-way mapping package. The software, file types and file formats must be compatible with those used by the District/Division Design for Schematics and PS&E (e.g., native MicroStation V8i files for graphics, Microsoft Office Word 2010 for metes and bounds descriptions). a. MicroStation V8i b. Level Library Files The Surveyor shall use the State’s current MicroStation V8i Level Library Files for right-of-way mapping. The files contain all the predefined levels that will normally be needed for right-of-way mapping and to show existing utilities. c. Separate DGN Files for Each Map Sheet The Surveyor shall provide one DGN file for each map sheet so that each right-of-way map sheet is spatially correct (snapping on elements gives correct coordinate values), This allows multiple users to work on different sheets at the same time from a server in production, with all the sheets utilizing the same master reference files. (Note: It is possible to have all the sheets in one DGN, but only one person at a time would be able to work on the project.) The sheet file naming convention is “ROW CSJ_Sheet Number.dgn”, with an example as follows: “212104065_S01.dgn” In the example above, the first nine (9) numbers “212104065” is the right-of-way CSJ for the project and “S01” is the sheet number, beginning with number 1 as the cover sheet. DocuSign Envelope ID: B8B3CD6BA1F83282-A26C-4D4027A1-A13B-9771D9AA45914756-AFA4-EB689A1E9938 Contract No. 36-6IDP1443 d. Format of the MDF/MRF (Master Design File or Master Right-of- Way Files) DGN Reference Files and Map Sheet Naming Conventions The recommended naming prefix for design files is MDF (Master Design File). Therefore, the prefix must be different for the right-of- way files because the location of the existing and proposed right-of- way in the design files from the schematic will change to some degree after an on the ground survey is made for right-of-way mapping. Therefore, the prefix could be MRF for Master Right-of- Way File. The corrected Master Right-of-Way Files shall be given to the design engineer to be used in the final PS&E so that all features of construction and the relocation of utilities shall be correctly placed in relation to the highway right-of-way and the right-of-way of cross streets or roadways. The Master Right-of-Way File naming convention is: “MRF ROW CSJ_Logical Name.dgn”, with examples as follows: MRF212104065_Schematic90.dgn (Schematic layout 90% submittal); MRF212104065_Schematic100.dgn (Schematic layout 100% submittal); MRF212104065_SchemApprov.dgn (Final Approved [State & FHWA] Schematic); MRF212104065_PSEDesign.dgn (Final P.S.&E. Design); MRF212104065_ExROW.dgn (Existing right-of-way determined by RPLS); MRF212104065_PropROW.dgn (Proposed right-of-way of final design); MRF212104065_DeedPlot.dgn (Deed Record); MRF212104065_Planimetric.dgn (Aerial mapping topography); MRF212104065_ROWTopo.dgn (Improvements data collection); MRF212104065_DesignTopo.dgn (Design level data collection topography); MRF212104065_ExUtil.dgn (Existing utilities), etc. All sheet files with a plan view must have the MRF referenced to allow more than one sheet file to be worked on at the same time. e. File Structure of Master and Reference DGN Files If possible, the file structure will not have any subfolders, to allow better transfer of data to different PC or server drive names or DocuSign Envelope ID: B8B3CD6BA1F83282-A26C-4D4027A1-A13B-9771D9AA4591 4756-AFA4-EB689A1E9938 Contract No. 36-6IDP1443 CD/DVD’s without path problems to reference files when the sheet files are opened. f. Lines Weights, Line Styles, Colors, Text Size, Text Fonts, Scale, and Annotations Legibility is the primary concern when choosing the scale, line weights and text size. Not only must the sheets be legible at full scale sheet size (22 inches x 34 inches), they must be completely legible at half scale sheet size (11 inches x 17 inches). Even if the originals or first generation plots are legible, the reproductions (copies) must also be legible. The normal scales for the full scale sheet size must be 1 inch = 50 feet (urban) and 1 inch = 100 feet (rural), which shall be 1 inch = 100 feet and 1 inch = 200 feet, respectively, when plotted or reduced to the half scale sheet size. Minimum line weights, text size and text font are dictated by legibility at half scale sheet size (11 inches x 17 inches). Even if the originals or first generation plots are legible, the reproductions (copies) must also be legible. Standard cell library: TxdotSurv_04.cel or current State cell files; Standard Font: 1 ▇▇▇▇▇; and standard State color tables: V256COLR.ctb or Txgpk.ctb. The Surveyor shall use the State’s current GEOPAK Survey SMD file that sets up new feature codes in SMD file for alignment chains, parcel chains and survey chains that can be drawn by GEOPAK Survey from the GPK file with the correct line styles, colors and weights to the designated levels loaded into the dgn by the State’s current level library files. The Surveyor shall use MicroStation Packager for the submission of electronic deliverables, which would capture any non-State standard rsc, cel, text, etc. files that were used in the mapping that look and plot differently in the State’s MicroStation® V8i workspace. g. Text and Line Colors When Using Color Digital Orthoimagery in the Background The predominate colors of the digital orthoimagery (greens, browns, etc) dictate which line and text colors stand out and are legible. Some degree of trial and error is sometimes needed. DocuSign Envelope ID: B8B3CD6BA1F83282-A26C-4D4027A1-A13B-9771D9AA45914756-AFA4-EB689A1E9938 h. Required Data in the GEOPAK Right-of-Way GPK File Alignments, chains of proposed and existing right-of-way lines, parent tracts and taking parcels, and all otherpoints collected in the field (start with schematic or design GPK file) are required. If the design GPK file is too detailed for right-of-way use, input files can be created for the information sought from the design GPK file to load into the right-of-way GPK file. i. Surface Coordinate and the ROW GIS Geo-Database Surface adjustment factors and basis of datum must be well documented in the electronic deliverables “file structure/deliverables read me” file. j. Requirements for Electronic Deliverables Native MicroStation V8i DGN files (reference files, sheets files, and parcel plats files); GEOPAK Survey GPK files; Separate comma delimited point files (ASCII file) and .csv file in the following types of coordinates: Surface or Projected Coordinates, Grid Coordinates (Texas Coordinate System of 1983 in U.S. Survey feet) and Geographic Coordinates (WGS-84 in decimal degrees) in the following format: point number, northing or latitude, easting or longitude, elevation, feature code, description. Text/.csv point file naming convention is: ROWCSJ_Type of Coordinates.csv (Example: 212101065_Surface.csv, 212101065_Grid.csv, and 212101065_WGS84.csv); PDF’s created in MicroStation V8i of Map Sheets (both 22 inches x 34 inches and 11 inches x 17 inches, one set in black and white and another set in color if there is orthoimagery for the background; PDF’s of signed and sealed Property Descriptions, Parcel Plats, and the Surveyor Surveyor’s Reports and Microsoft Office Word 2010 documents of Property Descriptions and Surveyor’s Reports; Raw and processed GPS files including adjustment reports. DocuSign Envelope ID: B8B3CD6BA1F83282-A26C-4D4027A1-A13B-9771D9AA45914756-AFA4-EB689A1E9938