Does not work if only geocoding City and State places

[jneedle79]

If there is not a value in Address 1 field the tool will not work. In the unmatched log it shows the addresses matched 100% but they are still not populated in the FC. If the same dataset is run with the same locator in ArcGIS Pro all locations appear in the FC.

[jneedle79]

Does anyone check these issue posts??

[cosbyr]

@jneedle79

Sorry for the delay. Yes the tool is designed to work with records that have street address information, not just City and State place information. I've looked into the tool a little further to see if we could get it to work with just City and State Information:

• In my tests, I found like you that the tool would create an output log that shows a 100% match for addresses with City and State information only, however it was not adding the geocoded records to the output target feature class. If your process was similar to mine here is an example of record in the output log:

• The key word above is the word "Locality", this is the addr_type of the geocoded record: https://developers.arcgis.com/rest/geocode/api-reference/geocoding-service-output.htm#GUID-D8DE94E9-5E2E-480D-9DE3-2212B9D7350D

• The Import Records tool accepts the following addr_types for matches: "AddrPoint", "StreetAddr", "BldgName", "Place", "POI", "Intersection", "PointAddress", "StreetAddress", "SiteAddress","Address", "StreetAddressExt", "StreetInt". The tool was designed this way because it was meant to primarily deal with local address type records at parcels.

• If you look at line 47 in the "import_records.py" python script that comes with tool you should see the following:

  # Accepted levels of geolocation
  addrOK = ["AddrPoint", "StreetAddr", "BldgName", "Place", "POI", "Intersection", "PointAddress", "StreetAddress", "SiteAddress","Address", "StreetAddressExt", "StreetInt"]

  You can modify this line to allow it match other addr_types such as Locality by doing this:

# Accepted levels of geolocation
addrOK = ["AddrPoint", "StreetAddr", "BldgName", "Place", "POI", "Intersection", "PointAddress", "StreetAddress", "SiteAddress","Address", "StreetAddressExt", "StreetInt", "Locality"]

You may need to add other addr_type aside from "Locality" to the list above to bring in all the records you are trying to import.

After I made this change and saved the import_records.py file, I was able to successfully add "City, State" addresses to my target features when running the Import Records tool.

Hope this helps!

[jneedle79]

Thanks for your help, that worked!!

Jake Needle, GISP GIS Program Manager Woodard & Curran 980 Washington Street, Suite 325N Dedham, Massachusetts 02026 p: 800.446.5518 x2546 | p: 781.613.0277 (Direct) e: jneedle@woodardcurran.commailto:jneedle@woodardcurran.com

From: Ryan Cosby notifications@github.com Sent: Monday, June 8, 2020 11:45 AM To: Esri/incident-import-tools incident-import-tools@noreply.github.com Cc: Jake Needle jneedle@woodardcurran.com; Mention mention@noreply.github.com Subject: Re: [Esri/incident-import-tools] Does not work if only geocoding City and State places (#17)

@jneedle79https://github.com/jneedle79

Sorry for the delay. Yes the tool is designed to work with records that have street address information, not just City and State place information. I've looked into the tool a little further to see if we could get it to work with just City and State Information:

• In my tests, I found like you that the tool would create an output log that shows a 100% match for addresses with City and State information only, however it was not adding the geocoded records to the output target feature class. If your process was similar to mine here is an example of record in the output log: [image]https://user-images.githubusercontent.com/11748268/84050227-4e135380-a962-11ea-993a-9c536db2cfa6.png
• The key word above is the word "Locality", this is the addr_type of the geocoded record: https://developers.arcgis.com/rest/geocode/api-reference/geocoding-service-output.htm#GUID-D8DE94E9-5E2E-480D-9DE3-2212B9D7350D
• The Import Records tool accepts the following addr_types for matches: "AddrPoint", "StreetAddr", "BldgName", "Place", "POI", "Intersection", "PointAddress", "StreetAddress", "SiteAddress","Address", "StreetAddressExt", "StreetInt". The tool was designed this way because it was meant to primarily deal with local address type records at parcels.
• If you look at line 47 in the "import_records.py" python script that comes with tool you should see the following:

Accepted levels of geolocation

addrOK = ["AddrPoint", "StreetAddr", "BldgName", "Place", "POI", "Intersection", "PointAddress", "StreetAddress", "SiteAddress","Address", "StreetAddressExt", "StreetInt"]

You can modify this line to allow it match other addr_types such as Locality by doing this:

Accepted levels of geolocation

addrOK = ["AddrPoint", "StreetAddr", "BldgName", "Place", "POI", "Intersection", "PointAddress", "StreetAddress", "SiteAddress","Address", "StreetAddressExt", "StreetInt", "Locality"]

You may need to add other addr_type aside from "Locality" to the list above to bring in all the records you are trying to import.

After I made this change and saved the import_records.py file, I was able to successfully add "City, State" addresses to my target features when running the Import Records tool.

Hope this helps!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/Esri/incident-import-tools/issues/17#issuecomment-640711077, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANULMZSTEMRYX6HJFYYXMGDRVUBQFANCNFSM4NE7ZMEQ.