|
DESCRIPTIONA number of types of scaling units may be used when plotting data. They are described here.EXAMPLESA number of examples illustrating the various scale types may be veiwed from the Gallery Scaling and Axes page
ABSOLUTE UNITSAbsolute units are not used for plotting data but rather for defining plot areas and for purposes such as placing annotation, etc. Absolute space is measured in inches (or centimeters if set in the config file, proc settings, or using the -cm command line option). The origin (0,0) is always at the lower-left corner.DATA SCALING UNITSA number of scaling units are available. Scaling is set in proc areadef or in proc defineunits.
The following are the available types of scaling.
For each type a description is given. Each type also
has one or more display format specifications,
which determine how incremental stubs will be presented.
LINEARStandard linear numeric scale. Numeric values may be any mixture of integer or floating point (exponential/scientific notation e.g. 4.336e11 is supported). Linear scaling is used for plotting continuous numeric data; it may also be used with series, such as bars when no location value is present in the data, or lineplots when no X value is present in the data.
Display format:
Display of numerics
is controlled using a
printf-spec
LOGLogarithmic numeric scale. Numeric values may be any mixture of integer or floating point (exponential/scientific notation is supported). The log of 0.0 or of negative numbers is nonexistant; therefore log plots should have a minima > 0 (very small numbers such as 0.01 are OK). Also available is log+1 scaling, which is similar to log but uses log( value+1 ). This is useful for log-characteristic data that can include values at or near 0.0. If using log scaling along with autorange, and if values of 0.0 are found, log+1 scaling will automatically be used. Display format - same as linear, above.
The proc axis stubcull attribute may be useful in eliminating "stub pile-up"
when rendering log axes.
CATEGORIESPositioning by category. This scaling method differs from the others in that it does not use a continuous scale. It is useful in positioning bars, rangebars, 1-D scatterplots or symbols based on a value or category. Values are considered labels and may be anything-- they may even contain embedded spaces and \n. No proc areadef range is specified; instead, the categories are specified in an areadef xcategories or ycategories attribute. Data are categorized by comparing with all category labels until a match is found. The details of how this comparison is actually done can be controlled using areadef attribute catcompmethod.
Display format - the defined category names.
DATEAllows date information to be plotted directly. A number of date notations (including year/month and quarter year notations) are supported for plotting and date arithmetic. It is possible to omit weekends if desired - see proc settings. Display format: Dates may be displayed in any of the supported date arithmetic formats, or in a number of additional display formats
The basic date unit is always a day, regardless
of which notation is in use. Stub and tic increments
may be expressed in months or years, if desired.
TIMEAllows date information to be plotted directly. Several time notations are supported for plotting and time arithmetic. Display format: Times may be displayed in any of the supported time arithmetic formats.
The basic time unit is a minute.
DATETIMEAllows time information to be plotted across multiple days. A datetime data field should have the format date.time (i.e. the date and time are connected using a dot). If your data has the date and time in two separate fields, the proc getdata filter attribute may be used to connect them with a dot. The date and time formats may be any of those supported for plotting and arithmetic. For example, if your datetime fields are like this: 22Aug1999.16:44 you would specify the datetime format as ddMmmyyyy.hh:mm. Display format: Same as above, except that the date component or the time component may be omitted if desired. The basic datetime unit is a day.
An example of datetime scaling is in
hitcount
DATETIME WITH TIME WINDOWINGSometimes it is desirable to show only portions of each day, when showing the entire 24 hour day would be too much. Examples of this include a work day or a trading day. datetime scaling allows you to do this- you can indicate the time range for each day at the end of the datetime keyword. For example:
Rules: Only whole hours may be used in the time window definition. Time values that are outside the defined time window will be displayed at the time window boundary and a warning will be issued. The areadef range must contain time components that are within the time window range. Incremental axis labels in day units may be used, but hour units may not be used.
An example of datetime scaling with time window is in
hitcount3
|
 data display engine Copyright Steve Grubb 
|
Markup created by unroff 1.0, December 10, 2002.