<?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 Segmentation Error in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343765#M63433</link>
    <description>&lt;P&gt;When you get a segmentation violation (which is basically a memory-related access error and signals a bug), you should put this immediately to the attention of SAS technical support.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Mar 2017 16:10:03 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2017-03-23T16:10:03Z</dc:date>
    <item>
      <title>Proc Geocode Segmentation Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343756#M63430</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to geocode a large number of addresses at once using proc geocode. SAS sometimes gets hung up trying to geocode a single address that is overly general (made up example=&amp;nbsp;&lt;SPAN&gt;311 N.E. with a valid city, state and zip) and stops the entire geocoding proccess by producing the error below.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This makes it really difficult to geocode a lot of addresses at once because the geocoding program stops entirely. Is there a way to:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) keep this error from happeining&lt;/P&gt;&lt;P&gt;Or&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2) get sas to continue where it left off once it encounters the error&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;NOTE: The map data sets in library MAPSGFK are based on the digital maps from GfK GeoMarketing and are covered by their Copyright. 
      For additional information, see http://support.sas.com/mapsonline/gfklicense.
NOTE: Address data set had only 1 observations. Intermediate progress times not output.
ERROR:  An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
 
The SAS task name is [GEOCODE ]
Segmentation Violation
 
Traceback of the Exception:
2                                                          The SAS System                             10:11 Thursday, March 23, 2017

 
ERROR:  An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
 
The SAS task name is [GEOCODE ]
Segmentation Violation&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is an example of my geocode program:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;PROC GEOCODE
METHOD=STREET /* Geocoding method */
DATA=work.tmp_geocode1 /* Input address data */
OUT=GeoData.tmp_geocode_outputTEST1 /* Output data set */
lookupstreet=SASHELP.USM /*needs to point at USM dataset downloaded from SAS*/
attribute_var=(tract block);
RUN; &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have SAS 9.3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2017 15:30:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343756#M63430</guid>
      <dc:creator>TB2</dc:creator>
      <dc:date>2017-03-23T15:30:02Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Geocode Segmentation Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343765#M63433</link>
      <description>&lt;P&gt;When you get a segmentation violation (which is basically a memory-related access error and signals a bug), you should put this immediately to the attention of SAS technical support.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2017 16:10:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343765#M63433</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-03-23T16:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Geocode Segmentation Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343766#M63434</link>
      <description>&lt;P&gt;This might help, although it says it's for 9.4:&amp;nbsp;&lt;A href="http://support.sas.com/kb/48/454.html" target="_blank"&gt;http://support.sas.com/kb/48/454.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Art, CEO, AnalystFinder.com&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2017 16:10:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343766#M63434</guid>
      <dc:creator>art297</dc:creator>
      <dc:date>2017-03-23T16:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Geocode Segmentation Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343787#M63437</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/73766"&gt;@TB2&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This makes it really difficult to geocode a lot of addresses at once because the geocoding program stops entirely. Is there a way to:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1) keep this error from happeining&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Pre-validate your data (data check) that all of your addresses have required elements. And yes I know all too well that some folks address data is very messy.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2017 17:29:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343787#M63437</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2017-03-23T17:29:30Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Geocode Segmentation Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343852#M63445</link>
      <description>&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;Worked with open source R ggmap

311 N E, Washington, DC 20002


%utl_submit_r64('
source("c:/Program Files/R/R-3.3.2/etc/Rprofile.site",echo=T);
library("ggmap");
lonlat_sample &amp;lt;- as.numeric(geocode("311 N E, Washington, DC 20002"));
class(lonlat_sample);
lonlat_sample;
res &amp;lt;- revgeocode(lonlat_sample, output="more");
res$postal_code;
res$neighborhood;
');

[1] "numeric"
[1] -77.00153  38.89586
[1] 20002
Levels: 20002
[1] Northeast Washington
Levels: Northeast Washington


&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 23 Mar 2017 20:24:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Geocode-Segmentation-Error/m-p/343852#M63445</guid>
      <dc:creator>rogerjdeangelis</dc:creator>
      <dc:date>2017-03-23T20:24:09Z</dc:date>
    </item>
  </channel>
</rss>

