August Release 2.0.5

Updates include:
• Renamed Geocode Address Points to Geocompare Address Points
• Renamed Check TN List to Check AT&T TN List
• Renamed Geocode Prepped TN List to Check Other TN List
• Removed Create MSAG Locator tool
• Geocode Address Points Rewrite- rewrote tool so it directly compares
the addresses to the road centerline file
• Check TN List & Geocode Prepped List Rewrite- rewrote tool so they
directly compares the addresses to the road centerline file
• Rewrite overlapping address tool, rework comparison, parse street name
on the fly
• Syntax edits for ArcPro compatibility
• Updated documentation

Doc_Online/EnhancementTools.md

@@ -30,9 +30,8 @@ road segments matching a user-provided road name.
 overlaps. Overlapping address ranges can negatively affect geocoding
 accuracy.
 
-[*Geocode Address Points*](#geocode): geocodes the address points against the road
-centerline data. This test respects exceptions created in the
-GeocodeExceptions table.
+[*Geocompare Address Points*](#geocode): compares the address points against the road
+centerline data. 
 
 [*Split Single ESB Layer*](#splitESB): splits out a single ESB layer into three separate ESB layers for EMS, FIRE and LAW
 
@@ -174,9 +173,9 @@ Running *Find Address Range Overlaps*:
     called “AddressRange\_Overlap”.
 
 <a name="geocode"></a>
-Running *Geocode Address Points*:
+Running *Geocompare Address Points*:
 
-1.	Open ArcCatalog and navigate to the toolbox called “Kansas NG911 GIS Tools” > “Enhancement Tools” > “Geocode Address Points”.
+1.	Open ArcCatalog and navigate to the toolbox called “Kansas NG911 GIS Tools” > “Enhancement Tools” > “Geocompare Address Points”.
 
 2.  In the “NG911 Geodatabase” box, select the appropriate
     NG911 geodatabase.

Doc_Online/MSAGTools.md

@@ -4,23 +4,17 @@ Description: These tools assist with verifying a PSAP’s TN list and MSAG infor
 
 *Worthwhile Information*: These tools will create a folder for all locators and geocoding output in the same folder as your NG911 geodatabase. The name of the folder will be your NG911 geodatabase name with “_TN” appended to the end. So, if your geodatabase name is “KSCO_NG911.gdb”, the folder will be named “KSCO_NG911_TN”. All geocoding working files and outputs for MSAG analysis will be inside a geodatabase in this folder.
 
-[*Check TN List*](#TNList): geocodes a list of telephone number addresses against the MSAG information in the NG911 Address Points and Road Centerlines. This tool requires a TN (telephone number) list. Directions for obtaining the TN list are found in the Downloading_TN_records_from_911Net document. Please see detailed tool instructions below for information on the geocoding results.
+[*Check AT&T TN List*](#TNList): This tool is for PSAPs who have AT&T as their provider. The tool geocodes a list of telephone number addresses against the MSAG information in the NG911 Address Points and Road Centerlines. This tool requires a TN (telephone number) list. Directions for obtaining the TN list are found in the Downloading_TN_records_from_911Net document. Please see detailed tool instructions below for information on the geocoding results.
 
-[*Create MSAG Locator*](#MSAGLoc): creates a composite locator from an address point locator and a road centerline locator using MSAGCO data. This tool is intended for users who want to manually geocode TN or MSAG data against the NG911 data.
-
-[*Geocode Prepped TN List*](#GeocodePrepped): geocodes full addresses housed in a spreadsheet against MSAG information in an NG911 geodatabase. To run this tool, the user must have a spreadsheet that has a field pre-concatenated, full addresses with a city appended to the end. Appropriate address format examples include:
-
--	1000 3RD ST, GREAT BEND, KS
-
-- 1000 3RD ST, GREAT BEND
+[*Check Other TN List*](#GeocodePrepped): This tool is intended for PSAPs who do not have AT&T as their provider. This tool geocodes full addresses housed in a spreadsheet against MSAG information in an NG911 geodatabase. 
 
 [*MSAG NG911 Comparison*](#https://github.com/kansasgis/NG911/tree/master/Doc_Online/MSAG_NG911_comparison.pdf): see link for full tool documentation
 
 <a name="TNList"></a>
-Running *Check TN List*:
-This tool requires a telephone number list to be extracted as a spreadsheet. Directions for obtaining the TN list are found in the Downloading_TN_records_from_911Net document.
+Running *Check AT&T TN List*:
+This tool requires a telephone number list to be extracted as a spreadsheet from AT&T. Directions for obtaining the TN list are found in the Downloading_TN_records_from_911Net document.
 
-  1.	Open ArcCatalog and navigate to the toolbox called “Kansas NG911 GIS Tools” > “MSAG Tools” > “Check TN List”.
+  1.	Open ArcCatalog and navigate to the toolbox called “Kansas NG911 GIS Tools” > “MSAG Tools” > “Check AT&T TN List”.
 
   2.	In the “TN Spreadsheet” input box, select the TN Spreadsheet provided by the telephone company.
 
@@ -32,56 +26,29 @@ This tool requires a telephone number list to be extracted as a spreadsheet. Dir
 
   6.	Your TN list spreadsheet is copied in the geodatabase as TN_List_YYYYMMDD with one column added called NGTNID for a unique ID. If you had columns for NPA, NXX and PHONELINE, the unique ID is a concatenation of these columns to form the phone number. If the ID is the phone number, this ID is persistent throughout all of your MSAG reviewing and editing. If the ID is not a phone number, then the ID has been randomly generated and is persistent for this single geocoding session.
 
-  7.	All results from the geocoding operation will be found in TN_GC_Output_YYYYMMDD. This feature class can be brought into ArcMap and viewed as a normal point file. The geocoding status for each record can be found in the “Status” column. M = Matched, T = Tied, U = Unmatched.
-
-  8.	TN_Geocode_Results_YYYYMMDD contains a full report of all tied and unmatched records. These are referenced by NGTNID. Please see notes under #6 for details regarding the unique ID.
-
-  9.	To review TN_Geocode_Results_YYYYMMDD against the TN_List_YYYYMMDD, bring both tables into ArcMap and create a join from TN_List_YYYYMMDD to TN_Geocode_Results_YYYYMMDD based on the NGTNID.
-
-<a name="MSAGLoc"></a>  
-Running *Create MSAG Locator*:
-
-  1.	Open ArcCatalog and navigate to the toolbox called “Kansas NG911 GIS Tools” > “MSAG Tools” > “Create MSAG Locator”.
-
-  2.	In the “NG911 Geodatabase” box, select the appropriate NG911 geodatabase.
-
-  3.	Run the tool.
-
-  4.	This tool will create three locators in a folder that sits next to your NG911 geodatabase. The name of the folder will be your NG911 geodatabase name with “_TN” appended to the end. If your geodatabase name is “KSCO_NG911.gdb”, the folder will be named “KSCO_NG911_TN”.
-
-  5.	The locators will be called: AddressLocator, Composite Loc, and RoadLocator.
-
-  6.	For comprehensive geocoding, please use the CompositeLoc since it is a combination of the AddressLocator and RoadLocator.
+  7.	All results from the geocoding operation will be found in TN_List_YYYYMMDD. This table can be brought into ArcMap and viewed as a normal point file. The geocoding status for each record can be found in the “MATCH” column. M = Matched, T = Tied, U = Unmatched.
 
 <a name="GeocodePrepped"></a>  
-Running *Geocode Prepped TN List*:
+Running *Check Other TN List*:
 
-1.	Open ArcCatalog and navigate to the toolbox called “Kansas NG911 GIS Tools” > “MSAG Tools” > “Geocode Prepped TN List”.
+1.	Open ArcCatalog and navigate to the toolbox called “Kansas NG911 GIS Tools” > “MSAG Tools” > “Check Other TN List”.
 
 2.	In the “NG911 Geodatabase” box, select the appropriate NG911 geodatabase.
 
 3.	In “Excel Spreadsheet”, select your TN extract spreadsheet.
 
-4.	In “Full Address Field”, select the proper full address field from the dropdown. This field needs to have pre-concatenated, full addresses with a city appended to the end. Appropriate address format examples include:
-
-  a.	1000 3RD ST, GREAT BEND, KS
-
-  b.	1000 3RD ST, GREAT BEND
+4.	For the various fields outlined in the tool, fill in all fields that are in your spreadsheet. The more fields you can fill in, the more accurate the results will be. Several fields are required like House Number, Road Name, and Community.
 
 5.	Run the tool.
 
 6.	The results will be contained in a folder that sits next to your NG911 geodatabase. The name of the folder will be your NG911 geodatabase name with “_TN” appended to the end. If your geodatabase name is “KSCO_NG911.gdb”, the folder will be named “KSCO_NG911_TN”. Inside this folder will be a geodatabase called “TN_Working.gdb”. In this geodatabase, you will find two tables and a feature class with the day’s date appended to the end.
 
-7.	Your TN list spreadsheet is copied in the geodatabase as TN_List_YYYYMMDD with one column added called NGTNID for a unique ID. If you had columns for NPA, NXX and PHONELINE, the unique ID is a concatenation of these columns to form the phone number. If the ID is the phone number, this ID is persistent throughout all of your MSAG reviewing and editing. If the ID is not a phone number, then the ID has been randomly generated and is persistent for this single geocoding session.
-
-8.	All results from the geocoding operation will be found in TN_GC_Output_YYYYMMDD. This feature class can be brought into ArcMap and viewed as a normal point file. The geocoding status for each record can be found in the “Status” column. M = Matched, T = Tied, U = Unmatched.
-
-9.	TN_Geocode_Results_YYYYMMDD contains a full report of all tied and unmatched records. These are referenced by NGTNID. Please see notes under #8 for details regarding the unique ID.
+7.	Your TN list spreadsheet is copied in the geodatabase as TN_List_YYYYMMDD with one column added called NGTNID for a unique ID. If you defined a Phone Number field when running the tool, the phone number is the unique ID. If the ID is the phone number, this ID is persistent throughout all of your MSAG reviewing and editing. If the ID is not a phone number, then the ID has been randomly generated and is persistent for this single geocoding session.
 
-10.	To review TN_Geocode_Results_YYYYMMDD against the TN_List_YYYYMMDD, bring both tables into ArcMap and create a join from TN_List_YYYYMMDD to TN_Geocode_Results_YYYYMMDD based on the NGTNID.
+8.	All results from the geocoding operation will be found in TN_List_YYYYMMDD. This table can be brought into ArcMap. The geocoding status for each record can be found in the “MATCH” column. M = Matched, T = Tied, U = Unmatched.
 
 Support Contact:
 
 For issues or questions, please contact Kristen Jordan Koenig with the Kansas Data Access and Support Center. Email Kristen at Kristen@kgs.ku.edu 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).
 
-Disclaimer: The Kansas NG9-1-1 GIS Toolbox is provided by the Kansas 911 Coordinating Council, Kansas GIS Policy Board’s Data Access & Support Center (DASC), 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 Kansas 911 Coordinating Council, DASC, 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.
+Disclaimer: The Kansas NG9-1-1 GIS Toolbox is provided by the Kansas 911 Coordinating Council, Kansas GIS Policy Board’s Data Access & Support Center (DASC), 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 Kansas 911 Coordinating Council, DASC, 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.

Scripts/Enhancement_CheckRoadElevationDirection.py

@@ -21,17 +21,17 @@ def main():
     #set variables
     gdb_object = getGDBObject(gdb)
     roads = gdb_object.RoadCenterline
-    a = getFCObject(roads)
+    a_obj = getFCObject(roads)
 
     #userMessage
     userMessage("Comparing elevation indicators...")
 
     #limit records to those with elevation flags
-    qry = a.ELEV_F + " = 1 or " + a.ELEV_T + " = 1"
+    qry = a_obj.ELEV_F + " = 1 or " + a_obj.ELEV_T + " = 1"
 
     #set up search cursor
     roadFullDict = {}
-    fields = (a.UNIQUEID, a.LABEL, a.ELEV_F, a.ELEV_T, a.L_F_ADD)
+    fields = (a_obj.UNIQUEID, a_obj.LABEL, a_obj.ELEV_F, a_obj.ELEV_T, a_obj.L_F_ADD)
 
     with SearchCursor(roads, fields, qry) as rows:
         for row in rows:
@@ -120,11 +120,11 @@ def main():
     resultType = "fieldValues"
     today = strftime("%m/%d/%y")
     fc = "RoadCenterline"
-    report = a.ELEV_F + " and:or " + a.ELEV_T + " are not consistent with neighboring road segments"
+    report = a_obj.ELEV_F + " and:or " + a_obj.ELEV_T + " are not consistent with neighboring road segments"
 
     if len(badSegs) > 0:
         for badSeg in badSegs:
-            val = (today, report, fc, a.ELEV_F + " " + a.ELEV_T, badSeg, "Check Road Elevation Direction")
+            val = (today, report, fc, a_obj.ELEV_F + " " + a_obj.ELEV_T, badSeg, "Check Road Elevation Direction")
             values.append(val)
 
     if values != []: