<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Data Interop Ext - Parsing a String Name in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/data-interop-ext-parsing-a-string-name/m-p/603499#M34004</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We are building a series of spatial ETL tools to help our clean up some of the data we have been receiving. I have run into a problem where each road segment name takes the following form:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;"1500 W Saint George St"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"1400 W Saint George St"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"1300 W Saint George St"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Using the string seacher I am able to identify all the names that begin with a numeric character using ^[0-9]. The problem is when the matched names are retured (those starting with a numeric value), I am unable to retain the later portion of the string from the end of the numeric variable forward.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In addition to this, the numbers are not always in the same format, for example some street names are listed as such:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;"-1 George St."&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"500-600 George St"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"Nanaimo Ave"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My idea is to combine a series of string searchers to ensure that I capture all the variables that begin with symbols or numbers and then use the space following those features to seperate the name out.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unfourtunately I have been unsucessfull in doing so.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks in advance,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Nelson&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Jul 2010 12:35:36 GMT</pubDate>
    <dc:creator>NelsonDe_Miranda</dc:creator>
    <dc:date>2010-07-30T12:35:36Z</dc:date>
    <item>
      <title>Data Interop Ext - Parsing a String Name</title>
      <link>https://community.esri.com/t5/data-management-questions/data-interop-ext-parsing-a-string-name/m-p/603499#M34004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We are building a series of spatial ETL tools to help our clean up some of the data we have been receiving. I have run into a problem where each road segment name takes the following form:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;"1500 W Saint George St"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"1400 W Saint George St"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"1300 W Saint George St"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Using the string seacher I am able to identify all the names that begin with a numeric character using ^[0-9]. The problem is when the matched names are retured (those starting with a numeric value), I am unable to retain the later portion of the string from the end of the numeric variable forward.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In addition to this, the numbers are not always in the same format, for example some street names are listed as such:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;"-1 George St."&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"500-600 George St"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"Nanaimo Ave"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My idea is to combine a series of string searchers to ensure that I capture all the variables that begin with symbols or numbers and then use the space following those features to seperate the name out.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unfourtunately I have been unsucessfull in doing so.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks in advance,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Nelson&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jul 2010 12:35:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/data-interop-ext-parsing-a-string-name/m-p/603499#M34004</guid>
      <dc:creator>NelsonDe_Miranda</dc:creator>
      <dc:date>2010-07-30T12:35:36Z</dc:date>
    </item>
    <item>
      <title>Re: Data Interop Ext - Parsing a String Name</title>
      <link>https://community.esri.com/t5/data-management-questions/data-interop-ext-parsing-a-string-name/m-p/603500#M34005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Nelson&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Welcome to the arcane world of regular expressions!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You are going to need to build a more complex regular expression definition to pick up the address components.&amp;nbsp; For example this pattern parses the case "500-600 George St":&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;([0-9]+)(-*)([0-9]*) ([a-z ][A-Z ]+)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You will then need to grab the parts from the resulting matched_parts list:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;`_matched_parts{0}' has value `500'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;`_matched_parts{1}' has value `-'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;`_matched_parts{2}' has value `600'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;`_matched_parts{3}' has value `George St'&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Aug 2010 15:10:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/data-interop-ext-parsing-a-string-name/m-p/603500#M34005</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2010-08-02T15:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: Data Interop Ext - Parsing a String Name</title>
      <link>https://community.esri.com/t5/data-management-questions/data-interop-ext-parsing-a-string-name/m-p/603501#M34006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Perfect!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I tried some regular expressions and couldn't get them to return what I wanted. Now I see what I was doing wrong.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- Nelson&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Aug 2010 11:57:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/data-interop-ext-parsing-a-string-name/m-p/603501#M34006</guid>
      <dc:creator>NelsonDe_Miranda</dc:creator>
      <dc:date>2010-08-03T11:57:18Z</dc:date>
    </item>
  </channel>
</rss>

