> What's the real id in this map, and are you using an 'id' statement on your Proc Mapimport? The proc will do the best it can without that, but by specifying the id variable you remove a lot of uncertainty & guesswork, which makes a better map. In the example you're setting country=1, but that's not always a valid thing to do, because then gmap might try to inter-connect pieces of the map in the wrong order (thinking they're all just segments of the same id). The real ID of my map was OBJECTID which I renamed _ID_ . OBJECTID has the same number of values as adding _ID_ created with CREATE_ID_, so I thought it was ok Here is my mapimport: proc mapimport datafile="\\sas9xbi\Data2\ID\DATA\Geo_Spatial\statisticalsectors_belgium\SCBEL01Z4.shp" out=imported /*CREATE_ID_*/ ; select X Y Area Area_ha CS102001 Nuts3 OBJECTID SUM_PERIME; rename OBJECTID=_ID_ CS102001=NIS9 SUM_PERIME=Perimeter; run;quit; adding "id OBJECTID;" does not change anything visible. > For example, here's what happens if you try to plot maps.uscounty similarly, with an invalid id (just making country=1 for all the ids, similar to what you've done in your map)... In my example I do a proc gremove before proc gmap. Like here : 25591 - Create an outline map of Africa using PROC GREMOVE data my_map; set maps.uscounty; country=1; run; proc gremove data=my_map out=my_map; by country; id county; run;quit; proc gmap data=my_map map=my_map; id country; choro country; run; > I narrowed one of the statistical sectors where the first bug appears in my map : Looks strange...
... View more
