Description: <p>The Design Files Water Structures layer contains water utility structures originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Type: Only found on the point layers. Identifies type of structure within the utility. Null values allowed.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files TV Structures layer contains television utility structures originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format. </p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p><span style="background-color:rgb(255,255,255); color:rgb(74,74,74); font-family:"Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><span style="display:inline !important; float:none; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; letter-spacing:normal; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; word-spacing:0px;">Please see the feature service description for additional information about the data processing.</span></span></p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Type: Only found on the point layers. Identifies type of structure within the utility. Null values allowed.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Telephone Structures layer contains telephone utility structures originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Type: Only found on the point layers. Identifies type of structure within the utility. Null values allowed.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Storm Structures layer contains stormwater utility structures originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p><span style="background-color:rgb(255,255,255); color:rgb(74,74,74); font-family:"Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;"><span style="display:inline !important; float:none; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; letter-spacing:normal; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; word-spacing:0px;">Please see the feature service description for additional information about the data processing.</span></span></p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Type: Only found on the point layers. Identifies type of structure within the utility. Null values allowed.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Sewer Structures layer contains sewer utility structures originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Type: Only found on the point layers. Identifies type of structure within the utility. Null values allowed.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Power Structures layer contains power/electrical utility structures originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Type: Only found on the point layers. Identifies type of structure within the utility. Null values allowed.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Gas Structures layer contains gas utility structures originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the <span style="font-family:"Aptos",sans-serif; font-size:12.0pt;"><span style="line-height:115%;">feature service description</span></span> for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Type: Only found on the point layers. Identifies type of structure within the utility. Null values allowed.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Water Pipes layer contains water utility pipes originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the overall service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files TV Lines layer contains television lines originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Telephone Lines layer contains telephone lines originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Storm Pipes layer contains stormwater pipes originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Sewer Pipes layer contains sewer lines originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Right of Way Line layer contains right of way lines originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Power Lines layer contains power/electrical lines originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p><p><strong>Field Descriptions</strong></p><p>ObjectID: Unique integer field within each feature class. It is system generated.</p><p>GlobalID: 128-bit string that is unque across geodatabases. It is system generated.</p><p>Associated CAD Annotation: String value calculated from the utility annotation layer based on proximity.</p><p>Location Accuracy: Default value is “Unknown”. Can be used to filter out features that have been assigned a value of “Low.”</p><p>ProjectID: ProjectID value from the original CAD dataset.</p><p>Let Date: Let Date assigned based on the ProjectIDs.</p><p>Design File Status: Indicates the originating CAD data source ("existing" or “proposed”.)</p>
Description: <p>The Design Files Gas Lines layer contains gas lines originally captured in CAD design files submitted for project advertisement by NCDOT between 2012 and 2022. These do not represent as-built conditions. NCDIT-T GIS Unit coordinated the conversion of the files from CADD to GIS format.</p><p>Within the original data structure, utilities were classified as either “existing” or “proposed.”</p><ul><li><i>Existing utilities</i> represented conditions at the time the design file was submitted.</li><li><i>Proposed utilities</i> reflected potential modifications or new infrastructure related to planned DOT roadway projects at the time the design file was submitted.</li></ul><p>Existing utilities and proposed utilities were combined into one dataset with the distinction preserved in the dataset’s <strong>Design File Status </strong>field.</p><p>It is important to note that these layers should not be considered authoritative or fully accurate. They are provided as a reference to help identify potential utility conflicts that may require further investigation. Users should confirm the data by consulting other reliable sources (such as utility provider datasets) and through field verification.</p><p>Please see the feature service description for additional information about the data processing.</p>