I made up some 'data' and 'annotate' data and it worked fine.  There were 5 maps. There were several corrections I made to your program:  You were missing a semicolon here:  text="my acount information for the year 2016" The following lines were missing 'inch':  goptions horigin=4.25;  (But that shouldn't matter)   Did you create your annotate data correctly?  For MAPS.US, the data is already projected radians so you cannot project your Annotate data.     Possibly the problem is with your data which you don't provide.  I think you need to contact Tech Support and let them help you. ... View more

I agree with "ballardw".  The problem seems to be with CANADA.  For one thing, the data set is not sorted to use ID1 and you are using that for "ID".  Did you try to run the GMAP that uses CANADA without PDF?   Does GMAP produce a map?  Are you getting any errors?    BTW, there is an SGF Paper that talks about how to use MAPSGFK maps.  And there are examples that go further than the paper too.  I think this will fix at least one of your problems. The paper is at:  http://support.sas.com/resources/papers/proceedings16/. Look for a paper title: The New SAS Map Data Sets Under that title are links to the Paper and the Examples. This particular problem is described in the paper.  The following code will fix CANADA. /* Sort the map data by ID1 */ proc SORT data=mapsgfk.canada      out=smymap; by id1 id; run;   /* remove the lowest level of the map data set */ proc GREMOVE data=smymap      out=mymap; by id1; id id; run;   /* rename ID1 to ID */ data mymap (drop=id1); set mymap;      id=id1; run;   proc GMAP data=mymap map=mymap;      id id;      choro id / nolegend;  run;   ... View more

I had to change your program around to make it work.  In ALLX. you did not have Postal_Zip___Personal_Dta listed. data allx; input Postal_Zip___Personal_Dta $ statecode$ stcnt; length zip 5; zip=Postal_Zip___Personal_Dta; cards;   And in the GMAP, i had to change 'CHORO ZIP' to "CHORO STATE".  ZIP must be in the "MAP" data set.  CHORO does not work with the ANNOTATE data set.   Finally, your messages are coming out because you have Puerto Rico (PR) in your ZIP Codes and you do not have it in your map.   ... View more

I don't understand your Proc GMAP.  You have "choro zip" but I don't see where you assigned "zip" to MAP.  I put a data step above your code with the ZIP Code for SAS: data allx; Postal_Zip___Personal_Dta='27513'; output; run; And I changed the "choro state" and it produces a small dot in NC where that ZIP code is.   If yours is working and drawing the dots, it could be that you have ZIP Codes that are on the coast or on an island and the map isn't fine grained enough to show the exact coast line.  These will produce that message if it is slightly in the water.   You may want to make your dots bigger.  This macro will do that: /*-----------------------------------------------------------*/ /* Macro to create point data in an annotate data set  * annodata = point annotate data set created.   * inputdata = Input data set containing points to be drawn.  *      Note that this data must contain variables x and y  *      with the location of the points.  * color = Graph color.  eg: red  * size = dot size (optional).  Default is .7;  * tipvar = Variable name to be used for tool tip (optional).  * Note:  search for ????? for items that can be modified.  */    %macro make_dots(annodata, inputdata, color, size, tipvar); data &annodata;   length function color $ 8 style $20 position $ 1 text $ 60 html $1024;   retain xsys ysys '2' hsys '3' when 'a' size .7;   set &inputdata;   /*optional arguments*/   %if (&size ^= ) %then %do;     size=&size;   %end;   /* All annotate points are 360-degree pies.  */   function='pie';   rotate=360;   style='psolid';   color=&color;   /* optional tool tips */   %if (&tipvar ^= ) %then %do;     html= 'title=' || quote("&tipvar" ||'=' || trim(left(&tipvar)) );   %end;   output; run; %mend; ... View more

Sorry, I meant MAPSGFK.US_STATES as an alternative.   ... View more

MAPS.US is in Projected Radians.  You must project your Annotate data and your map data together so it will be in the same projection.  But maps.us does not have any unprojected data so you can do that.  You must start with something like MAPS.STATES which has unprojected radians.  Your annotate data must be in unprojected radians too.  (alternately, use MAPSGFK.COUNTIES which has LAT and LONG as Unprojected Degrees).   So, convert the annotated data to radians if it is in degrees (unless using MAPSGFK). Add an anno_flag=1 variable to the annotate data. Combine the map data and the annotate data into the same data set. Proc GPROJECT this data set. Split the data back into 2 data sets: Map and Annotate using the anno_flag variable. GMAP the map and annotate data.   ... View more

  Be careful of Google, Bing and other legal rules.   For example with Google, unless you have the paid Google plan, using the Google geocoder standalone (not with a Google map) may be illegal.  They require that you use Google Maps with most 'content'.  Content can be the result of the geocoder. https://developers.google.com/maps/terms   10.4.d. No use of Content without a Google map. Unless the Maps APIs Documentation expressly permits you to do so, you will not use the Content in a Maps API Implementation without a corresponding Google map. ... View more