<?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 Re: proc geocode in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/proc-geocode/m-p/43341#M11304</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PROC GEOCODE does recognize standard abbreviations for street types, e.g. Ln or Ln. for Lane. All of the supported types are in the SASHELP.GCTYPE data set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have other street types not included, you can copy SASHELP.GCTPYE to another library and add them. Just make sure to sort the updated data set by NAME and then rebuild the simple index on that variable. Then, when submitting your PROC GEOCODE run, include the TYPE= option to use your new street type data set. See the PROC GEOCODE documentation for details on this option.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Aug 2012 17:40:18 GMT</pubDate>
    <dc:creator>EdO_sas</dc:creator>
    <dc:date>2012-08-09T17:40:18Z</dc:date>
    <item>
      <title>proc geocode</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/proc-geocode/m-p/43340#M11303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does proc geocode requiere address cleaning before use?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With it correlate the same addresss but slight differences?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Say I had "123 SAS Lane, 33178" vs 123 SAS ln., 33178"?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Mar 2012 17:18:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/proc-geocode/m-p/43340#M11303</guid>
      <dc:creator>Jaime</dc:creator>
      <dc:date>2012-03-26T17:18:37Z</dc:date>
    </item>
    <item>
      <title>Re: proc geocode</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/proc-geocode/m-p/43341#M11304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PROC GEOCODE does recognize standard abbreviations for street types, e.g. Ln or Ln. for Lane. All of the supported types are in the SASHELP.GCTYPE data set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have other street types not included, you can copy SASHELP.GCTPYE to another library and add them. Just make sure to sort the updated data set by NAME and then rebuild the simple index on that variable. Then, when submitting your PROC GEOCODE run, include the TYPE= option to use your new street type data set. See the PROC GEOCODE documentation for details on this option.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Aug 2012 17:40:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/proc-geocode/m-p/43341#M11304</guid>
      <dc:creator>EdO_sas</dc:creator>
      <dc:date>2012-08-09T17:40:18Z</dc:date>
    </item>
  </channel>
</rss>

