GMAP Procedure
- Syntax
- Overview
- Concepts About Map Data SetsAbout GfK GeoMarketing Map Data SetsAbout Traditional Map Data SetsMap Data Sets Containing X, Y, LONG, and LATDifferences between GfK and Traditional Map Data Sets The METAMAPS Data SetSpecial GfK Data Sets for Annotating MapsSpecial Traditional Data Sets for Annotating MapsAbout Response Data SetsAbout Identification VariablesDisplaying Map Areas and Response DataSummary of UseAccessing SAS Maps OnlineImporting Maps from Esri Shapefiles
- Using
- Examples Using GfK GeoMarketing Map Data to Produce a Simple Block MapUsing Traditional Map Data to Produce a Simple Block MapUsing GfK GeoMarketing Map Data to Specify Response Levels in a Block MapUsing Traditional Map Data to Specify Response Levels in a Block MapUsing GfK GeoMarketing Map Data to Assign a Format to the Response VariableUsing Traditional Map Data to Assign a Format to the Response VariableUsing GfK GeoMarketing Map Data When Specifying the Statistic for the Response VariableUsing Traditional Map Data When Specifying the Statistic for the Response VariableUsing GfK GeoMarketing Map Data to Produce a Simple Choropleth MapUsing Traditional Map Data to Produce a Simple Choropleth MapUsing GfK GeoMarketing Map Data When Labelling Provinces on a MapUsing Traditional Map Data When Labelling Provinces on a MapUsing GfK GeoMarketing Map Data to Produce a Simple Prism MapUsing Traditional Map Data to Produce a Simple Prism MapUsing GfK GeoMarketing Map Data When Specifying Midpoints in a Prism MapUsing Traditional Map Data When Specifying Midpoints in a Prism MapUsing GfK GeoMarketing Map Data to Produce a Simple Surface MapUsing Traditional Map Data to Produce a Simple Surface MapUsing GfK GeoMarketing Map Data While Rotating and Tilting a Surface MapUsing Traditional Map Data While Rotating and Tilting a Surface MapMapping an Individual Country By Subsetting MAPS.WORLDUsing GfK GeoMarketing Map Data to Specify Country Subdivisions on a ContinentUsing GfK GeoMarketing Map Data to Produce a Choropleth Map Combining Three Map Data SetsUsing GfK GeoMarketing Map Data to Produce a Choropleth Map Annotating Cities
PROC GMAP Statement
Identifies the map data set and the response data
set that contain the variables associated with the map. The
statement also provides the option to display all map areas and to
specify annotation and an output catalog.
| Requirement: | Both a map data set and a response data set are required. |
Syntax
PROC GMAP MAP=map-data-set
DATA=response-data-set
<ALL>
<ANNOTATE=Annotate-data-set>
<DENSITY=0...6 | LOW | MEDIUM | HIGH>
<GOUT=<libref.>output-catalog>
<IMAGEMAP= output-data-set>
<STRETCH>
<UNIFORM>;
DATA=response-data-set
<ALL>
<ANNOTATE=Annotate-data-set>
<DENSITY=0...6 | LOW | MEDIUM | HIGH>
<GOUT=<libref.>output-catalog>
<IMAGEMAP= output-data-set>
<STRETCH>
<UNIFORM>;
Summary of Optional Arguments
specifies that the maps generated by the procedure
should include all of the map areas from the map data set, even if
the response data set does not include an observation for the map
area.
specifies a data set to annotate all of the maps
that are produced by the GMAP procedure.
for maps that have a DENSITY variable, specifies
the density of map observations that are used.
specifies the SAS catalog in which to save the graphics
output that is produced by the GMAP procedure for later replay.
creates a temporary SAS data set that is used to
generate an image map.
stretches map extents to cover all available space
in the device. This might cause the map to be distorted.
causes the same legend and coloring to be used
for all maps produced by the procedure instead of being calculated
within each BY group for each map.
Required Arguments
- DATA=response-data-set
-
identifies the SAS data set that contains the response values or the response values and the spatial information that are evaluated and represented on the map. If not specified, a response data set must have been created before issuing the PROC GMAP statement.Default:The GMAP procedure uses the most recently created SAS data set.Requirements:This statement is required if no response data set was created before issuing the PROC GMAP statement.
A response data set must contain the same identification variable or variables as the specified map data set, along with the values of the response variable.
See:SAS Data Sets
- MAP=map-data-set
- names a map data set supplied
by SAS that contains either the X and Y or LAT and LONG coordinates,
or all, for the boundary points of each map area. This includes map
data sets licensed by SAS from GfK GeoMarketing GmBH and converted
by SAS to a SAS data set format. Requirement:This statement is required.Interaction:The map data set must contain the same identification variable or variables as the response data set being used.
Optional Arguments
PROC GMAP statement options affect all of the graphs that are produced by the procedure.
- ALL
- specifies that the maps generated by the procedure should include all of the map areas from the map data set, even if the response data set does not include an observation for the map area. When you use the ALL option and a BY statement in a RUN group, the maps generated for each BY group include every map area from the map data set.
- ANNOTATE=Annotate-data-set
- specifies a data set to annotate all of the maps
that are produced by the GMAP procedure. To annotate individual
maps, use the ANNOTATE= option in the action statement.Alias:ANNO=
- DENSITY=0...6 | LOW | MEDIUM | HIGH
- for maps that have a DENSITY variable, specifies
the density of map observations that are used. The value that you
specify indicates the maximum value that the DENSITY variable can
have for the observation to be displayed. For example, if you specify
DENSITY=5, then only observations in the map data set whose DENSITY
value is less than or equal to 5 are displayed.Intuitively, the DENSITY variable specifies how close a map point is to other map points. If there are many map points in close proximity (high density), then it is possible to eliminate a number of them without seriously degrading the quality of the map. Many map data sets supplied by SAS contain a DENSITY variable. For map data sets that do not contain a DENSITY variable, you can add and populate the variable using the GREDUCE procedure.You can specify an integer from 0 to 6 for the DENSITY option, or you can specify one of the following: LOW = 1, MEDIUM = 3, HIGH = 6.If you do not specify the DENSITY option, then all the observations in a map data set are displayed. This is regardless of whether the data set contains a DENSITY variable or not. This is equivalent to specifying DENSITY=6.Alias:RESOLUTION=, RES=Restriction:If the map data set does not contain a column of DENSITY values, then a warning is issued and the option is ignored.See:GREDUCE Procedure for information about the DENSITY variable.
- GOUT=<libref.>output-catalog
- specifies the SAS catalog in which to save the graphics
output that is produced by the GMAP procedure for later replay. You can use the GREPLAY
procedure to view the graphs stored in the catalog. If you do not
use the GOUT= option, catalog entries are written to the default catalog
WORK.GSEG, which is erased at the end of your session.Restriction:Not supported by Java and ActiveX
- IMAGEMAP= output-data-set
- creates a temporary SAS data set that is used to generate an image map in an SVG file when you are sending output to the LISTING destination. (This option is not necessary when you are sending output to the HTML destination.) The drill-down URLs in the image map must be provided by variables in the input data set. These variables are identified to the procedure with the HTML= and HTML_LEGEND= options.
- STRETCH
- stretches map extents to cover all available space
in the device. This might cause the map to be distorted. When this option is
applied to the PROC GMAP statement, it applies to all statements.
If applied to a single statement, it applies only to that statement.Restriction:Not supported by Java and ActiveX.
- UNIFORM
- causes the same legend and coloring to be used
for all maps produced by the procedure instead of being calculated
within each BY group for each map. The UNIFORM option
pre-scans the data to generate a categorization across all the data,
regardless of BY grouping, and applies that categorization to all
maps in the BY group. This results in a static legend and color distribution
across all maps such that a single value always has the same color
in multiple maps. When specified on a PROC GMAP statement, UNIFORM applies to all BLOCK, CHORO, AREA, and PRISM statements included within the GMAP run-group.When omitted from the PROC GMAP statement, and specified on an individual BLOCK, AREA, CHORO, or PRISM statement, UNIFORM applies only to the maps produced by that statement.Restriction:Not supported by Java.