Hi ... map data sets contain x/y variables that define polygons (map areas ... zips, states, counties, countries, whatever). SASHELP.ZIPCODE contains x/y variables that just identify the centroid of a zip code. There's only one x/y coordinate per zip ... not enough to draw a polygon !!! Since SAS/Graph will work with any set of x/y variables, it will actually draw a map of NYS using SASHELP.ZIPCODE. However, since there's only one point per zip in the data set, you cannot draw zip polygons, but you can have GMAP just "connect the centroids" of a state map ... data nys; set sashelp.zipcode; where state eq 36; keep state zip x y; run; proc gproject data=nys out=pnys eastlong degrees; id state; run; proc gmap data=pnys map=pnys; id state; choro zip / nolegend; run; quit; That SAS code produced the attached NYS_SASHELP_ZIPCODE map ... not what you want. If you go back to the example I posted, I said that ... " I got the shapefile from ... http://www.census.gov/cgi-bin/geo/shapefiles2010/main " If I use it with this SAS code ... * ZCTA shapefile import for New York; proc mapimport datafile='z:\tl_2010_36_zcta510.shp' out=nyzip; select zcta5ce10; rename zcta5ce10=zip; run; * ZCTA data set contains unprojected X/Y coordinates ... project them; proc gproject data=nyzip out=pnyzip degrees eastlong; id zip; run; * create a dummy response data set ... one observation per areacode; proc sql; create table dummy as select distinct zip, 1 as var from pnyzip; quit; goptions reset=all; * make a map; proc gmap map=pnyzip data=dummy; id zip; choro var / discrete nolegend; run; quit; I get a real zip code map ... attached as NYS_ZIP ... it has some flaws, but those flaws are in the shapefile. Hopefully that helps you understand that SASHELP.ZIPCODE cannot be used to create a map and that you can get free shapefiles and create maps with PROC GMAP
... View more
