Was able to get this put together eventually, using: proc gmap data=ohiodata map=map all anno=anno_state;   id county;   choro ptbpct / discrete legend=legend1 anno=anno_centroids(where=(county in (&county))) xsize=4.75in;   format ptbpct pctlabels.;   label ptbpct='Map Measure Ranges'; run; quit;   The map file did need the state outline boundary added to it to suppress errors in the log similar to: DATA SYSTEM REQUESTED, BUT VALUE IS NOT ON GRAPH 'Y' And the resulting map had the bottom portion of the state outline truncated.    Normally the 'B' value for the when variable would indeed result in the lines being covered; in this case though they were outside the polygons being drawn in most cases, and where the county boundaries and state boundary were identical, the user wanted to see the solid county boundary.    Thanks for the guidance on this one!  At times simple things just aren't as obvious as it would appear.   --Ben ... View more

Hi Robert,   Thanks for the ideas; this application has a varying # of zip codes shown in the same size area on a report, so I won't be able to generalize and insert an annotate entry.   If I come across anything I will post it here.   --Ben ... View more

Well that's slick.  I like it!   I will keep that in mind when I am asked again how to get stuff to appear on the right side.  That is a lot less work than what my coworker ended up doing.   Thanks!!   --Ben ... View more

The coworker who was working with this one used the Round() function on the start value to bring it within the fuzz value and that worked. I believe he used the 1e-12 argument for the rounding. So apparently there was some floating point issues with these values on the server we are on. Thanks much for the assistance! ... View more