Oklahoma NG911 Toolkit | Adjustment | Comparison | Enhancement | MSAG | Okprep | Submission | Validation

Supplementary Documentation | Examples | Generate Fishbone Analysis Tool | Topology Rules | Change Log | Error Glossary

Error Glossary

Documentation Credits

Last Revised:

June 15, 2022

Abstract

This document lists and describes the various messages written to the geoprocessing console, the TemplateCheckResults table, and the FieldValuesCheckResults table. In cases where the exact text of a message may vary, the contents of the variable part(s) are described in {curly braces}.

Errors describe issues that impede submission. Notices do not impede submission.

Template Validations

Check Layer List Ignores SUBMIT

If this check generates any errors, a console warning is printed: Not all required geodatabase datasets and/or layers are not present. See TemplateCheckResults.

Check GDB Domains Ignores SUBMIT

If this check generates any errors, a console warning is printed: Completed checking GDB domains: {#} issues found. See table FieldValuesCheckResults for results.

Check Spatial Reference Ignores SUBMIT

If this check generates any errors, the above error is also printed to the console as a warning.

Check Required Fields Ignores SUBMIT

If a required feature class does not exist inside the NG911 feature dataset, a console warning is printed: Required layer {feature class name} does not exist

If this check generates any errors, a console warning is printed: Completed check for required fields: {#} issues found. See table FieldValuesCheckResults for results.

Check Required Field Values Uses SUBMIT

If a feature class does not have a field named SUBMIT, a console warning is printed: Cannot check required field values for {feature class name}

If a feature class is missing one or more required fields, a console warning is printed: Could not check all fields in {feature class name}. Looking for: {list of required fields}

If a feature class has no features where SUBMIT is Y, a console warning is printed: {Feature class name} has no records marked for submission. Data will not be verified.

If a required feature class does not exist inside the NG911 feature dataset, a console warning is printed: Required layer {feature class name} does not exist

If this check generates any errors, a console warning is printed: Completed check for required field values: {#} issues found. See table FieldValuesCheckResults for results.

Check Submission Numbers Uses SUBMIT

If a feature class does not have a field named SUBMIT, a console warning is printed: SUBMIT field does not exist in required layer {feature class name}

If a required feature class does not exist inside the NG911 feature dataset, a console warning is printed: Required layer {feature class name} does not exist

If this check generates any errors, a console warning is printed: One or more layers had no features to submit. See table TemplateCheckResults.

Find Invalid Geometry Ignores SUBMIT

If a feature class has no NGUID field, a console warning is printed: NGUID field {field name} does not exist in {feature class name}

If a required feature class does not exist inside the NG911 feature dataset, a console warning is printed: Required layer {feature class name} does not exist

If this check generates any errors, a console warning is printed: Completed for invalid geometry: {#} issues found. See FieldValuesCheckResults.

Check Values Against Domain Uses SUBMIT

If a feature class has no features where SUBMIT is Y, a console warning is printed: No features are marked for submission in {feature class name}. Please mark records for submission by placing Y in the SUBMIT field.

If a feature class does not have a field named SUBMIT, a console warning is printed: Cannot check required field values for {feature class name} because the SUBMIT field does not exist.

If a feature class is missing one or more fields with domains, a console warning is printed: Field {field name} in feature class {feature class name} does not exist, and its values cannot be checked against domain {domain name}.

If a required feature class does not exist inside the NG911 feature dataset, a console warning is printed: Required layer {feature class name} does not exist

If this check generates any errors, a console warning is printed: Completed checking fields against domains: {#} issues found. See table FieldValuesCheckResults for results.

Check Feature Locations Uses SUBMIT

If neither DISCREPANCYAGENCY_BOUNDARY (in the NG911 feature dataset) nor COUNTY_BOUNDARY (in the OptionalLayers feature dataset) exist, a console warning is printed: Check Feature Locations could not run because the discrepancy agency and/or county boundary feature classes are absent or misnamed.

If this check generates any errors, a console warning is printed: {Feature class name}: issues with some feature locations

If this check generates any errors, a console warning is printed: Completed check on feature locations: {#} issues found. See table FieldValuesCheckResults.

Check Topology Uses SUBMIT

If this check generates any errors, a console warning is printed: Topology check complete. {#} issues found. Results in FieldValuesCheckResults.

Check Unique ID Format and Frequency Ignores SUBMIT

If a required feature class is not found, a console warning is printed: {Feature class name} does not exist

If this check generates any errors, a console warning is printed: There are {#} records in {feature class name} with null or incorrectly-formatted unique IDs.

If this check generates any errors, a console warning is printed: Checked unique ID frequency. There were {#} issues. Results are in table FieldValuesCheckResults.

Address Point Validations

If the ADDRESS_POINT feature class was not found in its expected location, a console warning is printed: Layer ADDRESS_POINT does not exist and therefore cannot be checked. This will prevent submission.

Check MSAGComm Spaces Uses SUBMIT

If this check generates any errors, a console warning is printed: Check complete. {#} issues found. See table FieldValuesCheckResults for results.

Check RCLMatch Uses SUBMIT

If the ADDRESS_POINT feature class does not have an RCLMatch field, a console warning is printed: Missing required field RCLMatch.

If this check generates any errors, a console warning is printed: Check complete. {#} issues found. See table FieldValuesCheckResults for results.

Check Frequency Uses SUBMIT

If the frequency table (AP_Freq or Road_Freq) exists and the script cannot delete it, a console warning is printed: Please manually delete {frequency table name} and then run the frequency check again.

If the Address field of the ADDRESS_POINT feature class is not of type Integer or Double, a console warning is printed: Address field of Address Points is not an integer or a double field.

If this check generates any errors, a console warning is printed: Checked frequency. There were {#} duplicate records. Individual results are in table FieldValuesCheckResults

Check ESN and Municipality Attribute Uses SUBMIT

If the ADDRESS_POINT feature class was not found in its expected location, a console warning is printed: {Input path to ADDRESS_POINT} does not exist

If the ESZ_BOUNDARY feature class was not found in its expected location, a console warning is printed: ESZ layer does not exist. Cannot complete check.

Road Centerline Validations

Check MSAGComm Spaces Uses SUBMIT

See entry in Address Point Validations section.

Check Frequency Uses SUBMIT

See entry in Address Point Validations section.

Check Cutbacks Uses SUBMIT

If the ROAD_CENTERLINE feature class was not found in its expected location, a console warning is printed: {Input path to ROAD_CENTERLINE} does not exist

If this check generates any notices, a console warning is printed: Completed check on cutbacks: {#} issues found. See FieldValuesCheckResults.

Check Directionality Uses SUBMIT

If this check generates any notices, a console warning is printed: Completed road directionality check. There were {#} issues. Results are in table FieldValuesCheckResults.

Check Address Range Overlaps Uses SUBMIT

If this check generates any notices, a console warning is printed: {#} overlapping address range segments found. Please see {full path to AddressRange_Overlap output} for overlap results.

Check Parities Uses SUBMIT

If any ROAD_CENTERLINE feature's Parity_L or Parity_R attribute is null, a console warning is printed: You have one or more parities set as null. Please populate those fields.

If this check generates any errors, a console warning is printed: Completed parity check. There were {#} issues. Results are in table FieldValuesCheckResults.


Note on Null

Where "null" is followed by an asterisk, "null" refers to any of the following: SQL NULL, Python None, a blank string (''), or a string consisting only of a single space (' ').

Support Contact

For issues or questions, please contact Emma Baker or Riley Baird with the Oklahoma Department of Transportation. Email Emma at ebaker@odot.org or Riley at rbaird@odot.org, and please include in the email which script you were running, any error messages, and a zipped copy of your geodatabase. Change the file extension from zip to piz so it gets through the email server. If there are further data transfer issues, contact Emma or Riley to make alternative data transfer arrangements.

If you have a domain issue to report, please email Emma Baker at ebaker@odot.org. Please indicate what type of domain the issue is with and the values needing corrections.

Disclaimer

The Oklahoma NG9-1-1 GIS Toolbox is provided by the Oklahoma Geographic Information (GI) Council, Oklahoma 9-1-1 Management Authority, Oklahoma Department of Transportation (ODOT), Oklahoma Office of Geographic Information (OGI) , and associated contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the Oklahoma GI Council, Oklahoma 9-1-1 Management Authority, ODOT, OGI, or associated contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.