ArcPy Rematch tied addresses according to a separate column value The Next CEO of Stack...

How can a day be of 24 hours?

How dangerous is XSS

How to find if SQL server backup is encrypted with TDE without restoring the backup

Could you use a laser beam as a modulated carrier wave for radio signal?

What does this strange code stamp on my passport mean?

Can a PhD from a non-TU9 German university become a professor in a TU9 university?

How should I connect my cat5 cable to connectors having an orange-green line?

Car headlights in a world without electricity

Man transported from Alternate World into ours by a Neutrino Detector

How to unfasten electrical subpanel attached with ramset

Compilation of a 2d array and a 1d array

Find a path from s to t using as few red nodes as possible

Prodigo = pro + ago?

How can I separate the number from the unit in argument?

Is it okay to majorly distort historical facts while writing a fiction story?

How do I secure a TV wall mount?

Create custom note boxes

Is there a rule of thumb for determining the amount one should accept for of a settlement offer?

Horror film about a man brought out of cryogenic suspension without a soul, around 1990

How can I prove that a state of equilibrium is unstable?

How do I keep Mac Emacs from trapping M-`?

What happens if you break a law in another country outside of that country?

Is it possible to make a 9x9 table fit within the default margins?

Is a linearly independent set whose span is dense a Schauder basis?



ArcPy Rematch tied addresses according to a separate column value



The Next CEO of Stack OverflowProgrammatically rematch unmatched addresses using a different composite locatorArcGIS10 Geocode Parser Pretype ProblemsIssue with address locator in ArcGIS 10.1How are geocoding scores calculated in ArcGIS?Missing field in address locator when geocodingHow to customize locator file to geocode unusual address?Match Button Greyed Out in Interactive Rematch WindowGeocoding: Match address is doubling up textProgrammatically rematch unmatched addresses using a different composite locatorWould a few thousand unmatched/tied NYC addresses be a source data issue?How to Geocode an address where the reference data has an address range in a single field












0















I have address data that returns many ties when geocoding using a Locator I created. The Locator uses a table that has grouped addresses based on street number ranges, e.g.



|Start_Street_Num | End_Street_Num | St_Name | Grouped_Street_Address | x | y
-----------------------------------------------------------------------------
|100 | 150 | Foo | 100 Foo | 1 | 2
|151 | 199 | Foo | 100 Foo | 3 | 4


Because of this, there are duplicates in the grouped address column, but I need to keep them because they refer to different (x,y) locations. Just for reference, the (x,y) values here refer to the midpoint of the street. I'm not allowed to consolidate the rows because there could be an intersection separating them.



The input table being geocoded has the actual address and the grouped address, e.g.



|Actual_Address_Num | Actual_Address_Name | Grouped_Address_to_Geocode
----------------------------------------------------------------------
| 123 | Foo | 100 Foo


The geocoded spits back this entry as TIED since there are two 100 Foo grouped addresses in the Locator.



Is there a way to do a rematch and have it look at the address number column to match the right range? i.e.



# psudo code logic
for row in table:
if(Actual_Address_Num >= Start_Street_Num and Actual_Address_Num <= End_Street_Num):
# match this row with the grouped address


If this is NOT possible, what is a suggested workaround / workflow change I should consider looking into?



What I've tried:




  • I found this article about attaching a new locator to the feature class resulting from a geocoding process: https://support.esri.com/en/technical-article/000003504. This seems like I would need to make a whole new Locator and run the geocoding against that Locator, but does not solve my issue with choosing the correct row for ties.

  • I see that ESRI has this Rematch function: https://pro.arcgis.com/en/pro-app/tool-reference/geocoding/rematch-addresses.htm. But there does not seem to be a way for me to specify what to rematch against as the only variables are the input FC and an SQL where clause to select the rows you want to be geocoded.

  • I saw this post: Programmatically rematch unmatched addresses using a different composite locator. But it doesn't have an answer and I am not using any of ESRI World Geocoding Services.


For Reference:




  • Python 2.7.13 win32

  • Working out of a File Geodatabase










share|improve this question



























    0















    I have address data that returns many ties when geocoding using a Locator I created. The Locator uses a table that has grouped addresses based on street number ranges, e.g.



    |Start_Street_Num | End_Street_Num | St_Name | Grouped_Street_Address | x | y
    -----------------------------------------------------------------------------
    |100 | 150 | Foo | 100 Foo | 1 | 2
    |151 | 199 | Foo | 100 Foo | 3 | 4


    Because of this, there are duplicates in the grouped address column, but I need to keep them because they refer to different (x,y) locations. Just for reference, the (x,y) values here refer to the midpoint of the street. I'm not allowed to consolidate the rows because there could be an intersection separating them.



    The input table being geocoded has the actual address and the grouped address, e.g.



    |Actual_Address_Num | Actual_Address_Name | Grouped_Address_to_Geocode
    ----------------------------------------------------------------------
    | 123 | Foo | 100 Foo


    The geocoded spits back this entry as TIED since there are two 100 Foo grouped addresses in the Locator.



    Is there a way to do a rematch and have it look at the address number column to match the right range? i.e.



    # psudo code logic
    for row in table:
    if(Actual_Address_Num >= Start_Street_Num and Actual_Address_Num <= End_Street_Num):
    # match this row with the grouped address


    If this is NOT possible, what is a suggested workaround / workflow change I should consider looking into?



    What I've tried:




    • I found this article about attaching a new locator to the feature class resulting from a geocoding process: https://support.esri.com/en/technical-article/000003504. This seems like I would need to make a whole new Locator and run the geocoding against that Locator, but does not solve my issue with choosing the correct row for ties.

    • I see that ESRI has this Rematch function: https://pro.arcgis.com/en/pro-app/tool-reference/geocoding/rematch-addresses.htm. But there does not seem to be a way for me to specify what to rematch against as the only variables are the input FC and an SQL where clause to select the rows you want to be geocoded.

    • I saw this post: Programmatically rematch unmatched addresses using a different composite locator. But it doesn't have an answer and I am not using any of ESRI World Geocoding Services.


    For Reference:




    • Python 2.7.13 win32

    • Working out of a File Geodatabase










    share|improve this question

























      0












      0








      0








      I have address data that returns many ties when geocoding using a Locator I created. The Locator uses a table that has grouped addresses based on street number ranges, e.g.



      |Start_Street_Num | End_Street_Num | St_Name | Grouped_Street_Address | x | y
      -----------------------------------------------------------------------------
      |100 | 150 | Foo | 100 Foo | 1 | 2
      |151 | 199 | Foo | 100 Foo | 3 | 4


      Because of this, there are duplicates in the grouped address column, but I need to keep them because they refer to different (x,y) locations. Just for reference, the (x,y) values here refer to the midpoint of the street. I'm not allowed to consolidate the rows because there could be an intersection separating them.



      The input table being geocoded has the actual address and the grouped address, e.g.



      |Actual_Address_Num | Actual_Address_Name | Grouped_Address_to_Geocode
      ----------------------------------------------------------------------
      | 123 | Foo | 100 Foo


      The geocoded spits back this entry as TIED since there are two 100 Foo grouped addresses in the Locator.



      Is there a way to do a rematch and have it look at the address number column to match the right range? i.e.



      # psudo code logic
      for row in table:
      if(Actual_Address_Num >= Start_Street_Num and Actual_Address_Num <= End_Street_Num):
      # match this row with the grouped address


      If this is NOT possible, what is a suggested workaround / workflow change I should consider looking into?



      What I've tried:




      • I found this article about attaching a new locator to the feature class resulting from a geocoding process: https://support.esri.com/en/technical-article/000003504. This seems like I would need to make a whole new Locator and run the geocoding against that Locator, but does not solve my issue with choosing the correct row for ties.

      • I see that ESRI has this Rematch function: https://pro.arcgis.com/en/pro-app/tool-reference/geocoding/rematch-addresses.htm. But there does not seem to be a way for me to specify what to rematch against as the only variables are the input FC and an SQL where clause to select the rows you want to be geocoded.

      • I saw this post: Programmatically rematch unmatched addresses using a different composite locator. But it doesn't have an answer and I am not using any of ESRI World Geocoding Services.


      For Reference:




      • Python 2.7.13 win32

      • Working out of a File Geodatabase










      share|improve this question














      I have address data that returns many ties when geocoding using a Locator I created. The Locator uses a table that has grouped addresses based on street number ranges, e.g.



      |Start_Street_Num | End_Street_Num | St_Name | Grouped_Street_Address | x | y
      -----------------------------------------------------------------------------
      |100 | 150 | Foo | 100 Foo | 1 | 2
      |151 | 199 | Foo | 100 Foo | 3 | 4


      Because of this, there are duplicates in the grouped address column, but I need to keep them because they refer to different (x,y) locations. Just for reference, the (x,y) values here refer to the midpoint of the street. I'm not allowed to consolidate the rows because there could be an intersection separating them.



      The input table being geocoded has the actual address and the grouped address, e.g.



      |Actual_Address_Num | Actual_Address_Name | Grouped_Address_to_Geocode
      ----------------------------------------------------------------------
      | 123 | Foo | 100 Foo


      The geocoded spits back this entry as TIED since there are two 100 Foo grouped addresses in the Locator.



      Is there a way to do a rematch and have it look at the address number column to match the right range? i.e.



      # psudo code logic
      for row in table:
      if(Actual_Address_Num >= Start_Street_Num and Actual_Address_Num <= End_Street_Num):
      # match this row with the grouped address


      If this is NOT possible, what is a suggested workaround / workflow change I should consider looking into?



      What I've tried:




      • I found this article about attaching a new locator to the feature class resulting from a geocoding process: https://support.esri.com/en/technical-article/000003504. This seems like I would need to make a whole new Locator and run the geocoding against that Locator, but does not solve my issue with choosing the correct row for ties.

      • I see that ESRI has this Rematch function: https://pro.arcgis.com/en/pro-app/tool-reference/geocoding/rematch-addresses.htm. But there does not seem to be a way for me to specify what to rematch against as the only variables are the input FC and an SQL where clause to select the rows you want to be geocoded.

      • I saw this post: Programmatically rematch unmatched addresses using a different composite locator. But it doesn't have an answer and I am not using any of ESRI World Geocoding Services.


      For Reference:




      • Python 2.7.13 win32

      • Working out of a File Geodatabase







      arcgis-desktop arcpy file-geodatabase geocoding






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 13 mins ago









      siushisiushi

      435




      435






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "79"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f317423%2farcpy-rematch-tied-addresses-according-to-a-separate-column-value%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Geographic Information Systems Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f317423%2farcpy-rematch-tied-addresses-according-to-a-separate-column-value%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Щит и меч (фильм) Содержание Названия серий | Сюжет |...

          Венесуэла на летних Олимпийских играх 2000 Содержание Состав...

          Meter-Bus Содержание Параметры шины | Стандартизация |...