Changing from the 2015 to the 2016 primary street lookup data should not have caused a major difference. Normally a new TIGER release includes mainly new streets, although the Census Bureau does insert corrections in the TIGER/Line files on occasion.   Regarding 9.40M4 being more accurate than previous releases, that is always our goal. Unfortunately making a change to better handle some addresses can sometimes introduce undesirable effects in others. We do try to prevent that, but are not always 100% successful. We'd really like to determine why you are seeing those changes. ... View more

jerry898969,   The SASHELP.ZIPCODE data set is updated for each maintenance release. The other data sets in SASHELP used by PROC GEOCODE do not change that often as there is rarely the need. For example, the same versions of GCTYPE (July 2013) and PLFIPS (July 2010) are in both 9.40M2 and 9.40M3.   New versions of the primary street lookup data sets (USM, USS and USP) are posted to SAS MapsOnline annually with each new TIGER/Line file relesae by the Census Bureau. The newer versions do not replace the older ones but are merely added to the MapsOnline site.   Are you using the nationwide street lookup data downloaded from MapsOnline? Which version (year)? Did you change lookup data sets between your older and newer geocoding runs?    Now there was a change in PROC GEOCODE between 9.40M2 and 9.40M3, but without a specific address to run, it is not possible to see if that is the reason for the difference you are seeing. There were also code changes between 9.40M3 and 9.40M4. It would be interesting to see how one of the problematic addresses is handled in that latest release.   I wish I could be of more help. ... View more

So you geocoded the sample addresses in Cary and Katy with no crash while using the sashelp.geoexm lookup data. But your address data crashes using your USM.USM lookup data.   Your debug trace shows your address being geocoded is 2042 MOMANY ST. I searched the USM 2015 lookup data set for MOMANY streets and found two in the US: Oregon, OH 43616 Saint Joseph, MI 49085 I am not sure which state your address is in, so I geocoded MOMANY ST in both states using the same version of SAS as you and also on a 64 bit Windows platform with service pack 1. I used the USM lookup data generated from the 2015 TIGER files. I also geocoded the MOMANY ST addresses on another 64 bit Windows server also running 9.4M3 SAS. I am unable to duplicate the crash on either machine.   Please submit this code to provide details on your WORK.TEST and USM.USM data sets:   ods pdf file='c:\temp\contents2.pdf'; title 'Address Data Set'; proc contents data=work.test; run; proc print data=work.test; run; title 'USM Data Set'; proc contents data=usm.usm; run; data USMheader;   set usm.usm (firstobs=1 obs=5); run; title 'USM Header Obs'; proc print data=header; run; ods pdf close; I ran that on my PC and my output file is attached as contents1.pdf. Please upload your output file which will be c:\temp\contents2.pdf. I am wondering if there are differences in your copy of USM. ... View more

Strange that this code used to work but suddenly began crashing. Can you please: Submit '%put &sysvlong;' to get the SAS version. Submit '%put &syshostinfolong;' to output the operating system. Add 'debug=4' to your proc geocode syntax and resubmit. This will enable the program tracing code which will provide an idea of where it crashed.. Also, submit the code below using the sample lookup data in the SASHELP library. It should get one street level match and one ZIP code match. If it runs, then the problem may be related to the lookup data in your USM library. But even if that is the case, proc geocode should end gracefully and not crash:   data test;   length address $64 city $24 state $2;   infile datalines dlm=',';   input address city state zip; cards; 500 SAS Campus Dr, Cary, NC, 27513 11500 Red Rock Canyon Dr, Katy, TX, 77450 ; proc geocode debug=4 data = work.test out = work.geocoded method = street lookupstreet = /*USM.USM*/ sashelp.geoexm; run; QUIT;   Please post the results of the code submittals above. Thanks.   ... View more

SAS/GIS does have two geocoding capabilities. One is the ability to locate an address interactively in the GIS Map Window.   An example using one of the GIS maps shipped with SAS follows: Invoke SAS/GIS with the pmenu: Solutions -> Analysis -> Geographic Information System Invoke the map selector window: File -> Open Map Select the map of Wake County, NC Census Tracts: MAPS.WAKE.TRACT When the GIS Map Window opens, toggle off the STREET layer to reduce clutter by unchecking the STREET button. The attachment 'Map of Wake County.png' shows the map at this point. Open the Find Address Window with the pmenu Tools -> Address -> Find... Enter the specifics of the address. For example: Address=100 SAS Campus Drive, City=Cary, State=NC Click the Find button and a cyan colored triangle is displayed on the map at that address. The attachment 'Marker on Map.png' shows this. SAS/GIS also has a batch geocoding capability. Details on that can be found in the SAS/GIS 9.4: Spatial Data and Procedure Guide.   Note that you will have to create the SAS/GIS map of the area you wish to geocode within. The above manual also discusses how to import spatial data into SAS/GIS data sets. For geocoding you will likely wish to use free TIGER/Line data from the Census bureau. SAS Technical Support can assist with the details of that process if necessary.   But, before embarking on that process, please be aware that the SAS/GIS batch geocoder has been supplanted by the Geocode Procedure which is part of SAS/GRAPH. If you have SAS/GIS, then you will also have SAS/GRAPH at your site. The Global Forum presentation PROC GEOCODE: Finding Locations Outside the U.S. provides an overview of its capabilities. The Geocode Procedure is the recommended geocoder for SAS users as it is actively being supported. SAS/GIS has been a legacy product for several releases and is no longer being updated.   You also asked about installing SAS/GIs on a Windows Server 2008 machine. Just go through the normal SAS install process and select the SAS/GIS product to include it. If it is not one of the available products, it may not be licensed at your site. Tech Support or your SAS site rep should be able to determine its status. ... View more

If you are in a university, you can use the new University Edition: Free Statistical Software, SAS University Edition The SAS Programming I and Statistics I courses are now available free over the web: SAS Training Starting Points ... View more

If you want to connect to ArcGIS for only geocoding, have you tried the GEOCODE Procedure in SAS/GRAPH? If it meets your needs, you could do your geocoding completely within SAS. ... View more