Resource Library: Graphics/graphics-16000.iso/msdos/mapping/ozgis80/ozgis.doc

Text File | 1992-01-18 | 489KB | 6,540 lines

                                OzGIS

                                V8.0

                            (January 1992)


















                         Geismar Holdings Pty Ltd.

                         QMDD Box 6108
                         Queanbeyan 2620,
                         Australia.


                                                                       2
                         PREFACE

OzGIS is a software system for displaying geographically referenced data as
coloured choropleth maps on graphics display devices. The maps portray the data
values associated with geographic zones by uniform colours, site data by
different sized symbols, and line data by different line types.

OzGIS is designed to provide the following interactive graphics facilities:

      -  to facilitate the interpretation of spatial distributions of data
      -  to prepare colour maps to be output on hard copy devices for
         publication and presentation,
      -  to facilitate the interpretation of spatial distributions of data
      -  to assist the analysis and modelling of spatial relationships in
         data.

The system can therefore be used to analyze socio-economic and demographic
data produced by censuses and surveys and to support management decisions
associated with for example marketing, sales, site and personnel location,
and advertising.


The software was originally developed as part of a research project at the
Division of computing Research of the Commonwealth Scientific and Research
Organisation (CSIRO) in Canberra for a mapping product called COLOURMAP.

Software development started in 1979 with the purchase of hardware that had
been developed for the DIDS mapping system in the White House in Washington DC.
This hardware consisted of a PDP11 mini-computer and a DeAnza display system.
The display featured a 12bit frame buffer, 4096 value primary look-up table and
cascaded 256 value colour table. This enabled maps of up to 4000 zones (e.g.
USA Zip codes) to be displayed and manipulated very rapidly, and is the best
hardware so far produced.

The environment changed over several years, with moves to larger PDP11 systems
and to VAX and CDC machines. Several display systems were used, Tektronix,
Jupiter and RAMTEK, and maps were generated on plotters and film recorders. The
system was also available on CSIRONET, an Australia-wide computer network with
Control Data and FACOM host computers. The 1981 ABS Census data could be
accessed via the SIR/CENSYS system on the Cyber 845. A system was developed to
handle the Census district boundaries digitised by the Division of National
Mapping, to enable windowing, line simplification and aggregation for production
of geographic map data files. The SAS system was available on the FACOM 180 for
statistical analysis and display of map data.

 The Division of computing research was split into the CSIRONET computing bureau
and the new Division of Information Technology in 1985. Later, CSIRONET was
given to private industry. The mapping project was abandoned.

The software was resurrected in late 1990 and ported to the IBM PC to produce
the current system.

The first year of development was supported by Techway, and APASCO supported
the development of techniques for retail applications. APASCO used the system
and hardware for several years as part of their consulting activities to churn
out thousands of maps.


                                                                       3
 The purpose of the Guide is to introduce the facilities of OzGIS. The Guide is
intended to complement the messages and assistance given during the operation of
OzGIS.

 The user should understand the techniques of statistical data analysis and
computer mapping, and also have an elementary understanding of colour
representations.

This manual describes the  IBM PC version. Some of the facilities that were
available on the PDP11 and VAX systems have not yet been ported.




Geismar Holdings is a Canberra based software company offering consulting and
contract programming services in the areas of:

. C and FORTRAN programming
. Spatial applications
. Scientific applications
. Graphics
. UNIX workstation, minicomputer and PC environments


                                                                       4
                    1. OzGIS INTRODUCTION
                       ==================


  1. 1 Introduction
       ------------


Easy to use systems are necessarily trivial systems, and the enormous number of
options within OzGIS means that it takes some time to understand everything.

However, maps can be produced quite simply by using only a small number of
options and by using the system defaults.

Start by using the OzCensus; its a simpler version of OzGIS suitable for
Census-type mapping.

This manual tries to lead readers through the main options first and for the
most common applications first. Working through the manual and generating the
maps as explained will soon provide the knowledge to enable the rest of the
system to be used.

The system consists of several modules:

OzEnter  - for entry of data files into the system.
OzData   - preparation of data for mapping
OzZone   - formation of zones / polygons structure from line segments
OzGIS    - interactive display and analysis
OzCensus - Display and analysis of Census type data (subset of OzGIS)
OzGISco  - maths coprocessor version of OzGIS
OzMap    - output of saved displays on plotters and printers and to files
OzTerr   - definition of territories from zones
OzProj   - map projections

Future releases may include:

OzCatch - allocation of zones to site catchments

  1. 2 Concepts
       --------

 OzGIS can be considered as one system of a facility for analysis and display
of Census type data. The various components are:

 - Database systems for manipulation and retrieval of attribute data
 - Systems for generation of map boundary data
 - Statistical analysis systems with graphic display and reporting facilities
 - Mapping systems with analysis and hardcopy facilities.

 Visual inspection of choropleth maps is the intuitive way to interpret the
spatial features of data. An analyst needs to be able to rapidly display and
manipulate maps to aid his understanding. OzGIS was designed to enable maps to
be changed within seconds so the analyst does not lose his train of thought.

 OzGIS enables the analyst not just to display a map, but to generate the map
that best shows the features of the attribute data. A hardcopy map can be
generated as the final operation as a record or for dissemination.

                                                                       5

The original design of OzGIS employed image processing technology to obtain
speed of display. The essential hardware components were a dedicated super mini
computer and an advanced raster display system. These display systems enable
maps to be displayed (in image form) in full colour, where the colours are
selected from a large palette. The main feature is that the colours are assigned
by hardware tables, and can be rapidly changed by rewriting the tables. Hence,
once a map has been displayed, attribute data can be rapidly processed and
displayed, as the major difference between successive maps is that the map zones
change colour. The hardware components can be packaged together to form a
compact unit; a mapping workstation.

 It is expected that an analyst would have access to a workstation close to his
office. The workstation would usually be connected via a computer network to
provide access to large host machines. The host machines would contain the
database systems from which map data could be extracted, and other systems for
analysis and hard-copy generation.

 OzGIS aims to accept basic data files and to provide most of the facilities
required for the analysis and display of attribute data as choropleth maps. The
analyst has to be able to rapidly use the facilities, so OzGIS provides an
interactive user interface. The user interacts via menus and is aided by on-line
assistance.

  1. 3 Environment
       -----------

 OzGIS requires advanced raster display systems for rapid display of maps.
Unfortunately PC display systems are extremely limited in capability. In
particular only a maximum of 256 colours are available (on 512K super VGA
boards). OzGIS is able to generate maps on most graphic devices by using polygon
fill to colour map zones. This faciity also allows for hardcopy generation of
maps previewed on raster displays.  PC display systems do not have hardware
polygon fill, so map display is slow.

 OzGIS is based on the GKS graphics standard. The standard provides device
independence, and the basic graphic capabilities of lines, text and fill. OzGIS
does contain its own set of GKS-type routines which can be used to interface to
display devices with hardware fill capabilities or to other device independent
packages. The INTERACTOR graphics package is used for the interactive version,
and the SCIPLOT package for hardcopy map production.

 OzGIS is a large FORTRAN program. It will run on computer systems with a
FORTRAN 77 compiler and about a mega-byte of memory. The system is well
structured, so by using overlays and reducing capabilities (array sizes) the
software can be implemented in smaller memory machines. Hence OzGIS is
reasonably portable.  The PC version is heavily overlayed to fit it into the
artificial 640K limit imposed by the DOS operating system.

Generally the speed of the system is dependent on hardware:

Processor 286 -> 386 -> 486
Disk speed
Floating point processor
Extra memory for RAM disk

INTERACTOR is a graphics package produced by:


                                                                       6
Interactive Software Services,
25 St Michael's Close,
Penkridge,
Stafford. ST19 5AD.
U.K.

We have found INTERACTOR very good, and the support is excellent.

SCIPLOT is a plotting package produced by:

MicroGlyph Systems,
PO Box 474,
Lexington, MA 02173,
U S A

                                                                       7
                    2. SUMMARY
                       =======


OzGIS was designed to:

. facilitate the interpretation of the spatial distributions of data
. prepare maps to be output on printers and plotters
. assist the analysis and modelling of spatial relationships in data

The system can therefore be used to analyse socio-economic data produced
by censuses and surveys and to support management decisions associated with
for example Government planning, marketing, sales, site and personnel
location, advertising and natural resources.

Products:

. Zone maps displaying polygons that are filled (with colours, patterns or
  hatching) to show the distribution of attribute data
. Line maps displaying lines in different line patterns to show the attribute
  data distribution
. Site maps displaying symbols at locations where the symbol sizes show the
  attribute data distribution
. Bivariate maps showing filled zones for two attribute files
. Zone and line maps showing lines overlayed on zones for two attribute files
  Zone and site maps showing site symbols overlayed on zones for two attribute
  files
. Geographic maps displaying polygons, line segments, symbols or site names
  according to feature types but without reference to attribute files
. Histograms showing the number of items (zones, lines or sites) assigned
  to each class, or the number of items within value intervals (distribution)
  or the attribute values sorted in ascending order
. Scatter diagram for two attributes
. Map statistics
. Map reports

Files:

. Data files are raw Ascii data files in a variety of external formats. Standard
  GIS formats and formats from Census Bureaus and Mapping Agencies are
  supported
. Geographic files describe geographic data in terms of the graphic elements
  zones, polygons,line networks, line segments, and points
. Attribute files contain the values of attributes (variates, statistics,
  variables) referenced to zones, line or site names.
. Names files contain a list of zones, lines or sites that defines a region
  of interest
. Combine files define new items in terms of zones for aggregation
. Marker files define simple shapes as polygons for display as symbols
. Saved display files contain the information to regenerate a complete map
. Device files define the graphics devices and their capabilities; colours,
  fonts, line types, hatching, markers etc

User Interface:

. Menu / windows interface
. Help facility

                                                                       8
. Trace information
. File interrogation, audits, deletion
. Tutorials

Data processing

. Subsetting of geographic files
. Line segment simplification
. Joining short line segments for polygons
. Amalgamation of geographic and attribute data
. New attributes by arithmetic and logical expression
. Building zones structure from line segments
. Generation of names files
. Generation of template attribute data files
. Map projections

Quantisation

. Classification methods: equal value, quantiles, specified intervals,
  specified number, refined, sequential colour, mean and standard deviations,
  nested means, natural breaks, percentiles, fixed
. Quantisation over value ranges
. Quantisation for lists of items
. Independent quantisation for one or two files

Map regions

. Display of several geographic files at the same time, joined together or
  as multiple regions
. Windowing and viewporting for layout
. Coordinate grids
. Overlays of line segments, names and symbols

Attribute selection

. Sequentially off attribute file
. By position in file
. By description

Map enhancement

. Specification of legend contents
. Addition of text
. Addition of histograms showing distributions, sorted values or quantisation
  results
. Addition of scatter diagrams to bivariate maps
. Overlay of mean and standard deviation, median and regression curves on
  diagrams

Hardcopy Map Production

. HP compatible plotters
. Many dot matrix printers
. Postscript laser printers
. HPGL, CGM and word processor files

Applications


                                                                       9
. Territory assignment
. Site catchments

Environment

. Requires minimum of IBM PC compatible with hard disk, 640K RAM and EGA.
. Preferred hardware is AT compatible with 512K super VGA card giving 256
  colours at at least 640 x 480 resolution. 1Mbyte boards with Trident or
  Tseng Labs 4000 chipsets are recommended.
. MS DOS operating system

                                                                      10
                    3. SYSTEM CONFIGURION
                       ==================


  3. 1 Introduction
       ------------

Various parameter files have to be set up correctly before the system can be
used as OzGIS supports a range of video boards. This should be quite straight
forward for standard EGA and VGA boards, but as there are no standards for
super VGA boards the procedure gets involved.

The configuration is worth spending the time on as it is very important to
display maps as fast as possible and to use the highest display resolution
possible. If you plan to do a lot of mapping it is worth purchasing the
hardware (its optional).

Resolution is provided by using Super VGA boards.

Speed is provided by:

    . Super VGA boards with 256 colours (512K or 1 Mbyte RAM on the board)
    . Using an extra 1MByte of RAM as a RAM disk.
    . Math coprocessor
    . fast processors (386 / 486)

The other hardware worth having is a mouse. While the arrows on the keyboard
can be used, they are slow.


FOLLOW THE INSTRUCTIONS CAREFULLY!


  3. 2  DOS system files
       -----------------

The start-up command file AUTOEXEC.BAT will have to be modified so the programs
can be accessed by changing the path statement to reference /ozgis. e.g.

PATH C:\DOS;C:\PROGS;C:\OZGIS


The system file CONFIG.SYS has to have:

FILES=20
BUFFERS=20

These changes to the DOS system files will not take effect until the system is
re-booted.

  3. 3  Standard EGA and VGA boards
       ----------------------------

If you have a super VGA board skip this section.

You need to be aware of the resolution of your video card. This is one of:


                                                                      11
350 lines of 640 pixels for EGA
480 lines of 640 pixels for VGA

Both boards have 16 colours.

You now need to check two configuration files:

All the following take place in the \ozgis directory.


The file \OZGIS\OZGIS.INI is the initialisation file for the system.
This file has to be modified using your word-processor.

The file should be well commented, and modifications should be fairly obvious.
Ensure that you dont alter the columns used i.e. the file is not free format!

The first three lines should be either:

for the EGA board

       640         Number of pixels across EGA screen
       350         Number of lines on screen
        16         Number of colours


or for the VGA board

       640         Number of pixels across VGA screen       (640 - 1024)
       480         Number of lines on screen                (350 - 768)
        16         Number of colours                        (16 or 256)



The file \OZGIS\INTERACT.INI is the initialisation file for the interactor
graphics package. This file has to be modified using your word-processor.

The file should be well commented, and modifications should be fairly obvious.

If a standard VGA card is being used, nothing may have to be changed.

If an EGA card is being used the display type may have to be set via
the DISPLAY= parameter.



  3. 4  Super VGA boards
       -----------------

The recommended display is a super VGA board with the ability to display 256
colours at a resolution of at least 640 X 480, as this enables maps of up to
240 zones to be manipulated rapidly by changing the colours via the colour
look-up table. Other displays require the map polygons to be redrawn every time
the colours change (e.g. by displaying another attribute).

Hence you should use the highest resolution available with your board and
monitor that gives 256 colours. (this may not be true if you are mapping e.g.
environmental data without attribute data or have maps of more than 240 zones
when resolution may be more important).

                                                                      12

First determine the resolution and number of colours you want to use. This will
depend on the amount of memory on your board and the chipset. If in doubt read
your video board manual or ask your computer shoppe.

In order of preference the resolutions are:

Pixels Lines Colours

1024   768   256         (1MByte boards)
 800   600   256         (512K boards)
 640   480   256         (512K boards with standard monitor)
 800   600    16         (256K board)

If your board has only 256K of memory you should consider adding more memory,
but in the meantime use the highest resolution possible for 16 colours

The boards supported by the graphics package are:

    Chipset     Chipset   640x350   640x400   640x480   800x600  1024x768
                Number
    Tseng 3000    0          y                   y         y
    Tseng 4000    1          y         y         y         y         y
    Paradise      2                    y         y
    Video 7       3                    y         y         y
    Everex        4          y         y         y         y
    ATI           5                    y         y         y
    Trident       6                    y         y         y         y
    Chips & Tech  7                    y         y         y
    Ahead B       8                    y         y         y
    Oak           9                              y         y

The precise combination of modes available on any given board varies
according to the manufacturer and the amount of video RAM available.
The 640x480 and 800x600 modes require 512k and the 1024x768 mode requires
1 megabyte.


You now need to modify two configuration files:

All the following take place in the \ozgis directory.


The file \OZGIS\OZGIS.INI is the initialisation file for the system.
This file has to be modified using your word-processor.

The file should be well commented, and modifications should be fairly obvious.

The first three lines have to be the resolution and number of colours e.g.

       800         Number of pixels across VGA screen       (640 - 1024)
       600         Number of lines on screen                (350 - 768)
       256         Number of colours                        (16 or 256)

Ensure that you dont alter the columns used i.e. the file is not free format!


The file \OZGIS\INTERACT.INI is the initialisation file for the interactor graph

                                                                      13
package. This file has to be modified using your word-processor.

The file should be well commented, and modifications should be fairly obvious.


The display type may have to be set via the DISPLAY= parameter.

Super VGA boards require registers to be initialised. Look through the list and
find yours. If its not there you may have to use the system as a standard VGA
as described in the previous section, but first look in your video board manual
to see if there is information about the registers to be used to set modes. If
there is you may be able to set up an appropriate mode command as described
in the following paragraphs (try it to see if it works).

The following section gets quite complicated, but all you have to do is to
enable a command that corresponds to your video card.


e.g. if you have a TSENG Labs ET4000 card you will find the following entry:

REM mode13  = 56 0 0 0 1 1024 768 (1024x768 256-colour graphics)  C

All you have to do is remove the "REM " from the front (dont forget the blank
i.e. left align it).

You would normally also remove the comment too, so you end up with:

mode13  = 56 0 0 0 1 1024 768  C

(the "C" on the end is require with a mouse to tell the system to generate a
cursor as mouse drivers normally do no do that with super VGAs).



Try and find the corresponding entry for your board. If you are still confused
try reading the following:


INTERACTER supports 5 non-standard screen modes numbered 9 to 13 which
can be activated by inserting suitable 'MODEnn' keywords in the INTERACTER
initialisation file. The INTERACT.INI file contains some examples which
contain suitable initialisation file MODEnn entries for various combinations
of video board and display monitor.


The supported non-standard screen modes are as follows

   INTERACTER      Mode Type
   Mode Number
   -----------     ---------
       9            640x400 'Olivetti' monochrome graphics
      10            132x25   16 colour text
      11            800x600  16 colour 'Super VGA' graphics
      12            256 colour 'Super VGA' graphics
      13            256 colour 'Super VGA' graphics

Notes :
(1) The dimensions of mode numbers 12 and 13 are definable as part of

                                                                      14
    the MODEnn keyword. By default they are 640x480 and 800x600 modes.
(2) 800x600 and 1024x768 modes will require a multisync or Super-VGA type
    monitor. On certain boards, 132 column mode also requires such a monitor.
    Be sure to use a suitable monitor/adapter combination.
(3) The precise mode numbers used by particular video board manufacturers
    can vary. Users should check the documentation supplied with their
    video board before including the supplied example MODEnn entries
    in their INTERACTER initialisation file.

Initialisation entries can be found for following:

  Ahead B chipset
  ATI VGA Wonder chipset
  Chips & Technology chipset
  Everex chipset
  Oak Technology chipset
  Olivetti M24/M28/M300, AT&T 6300, Compaq Portable
  Paradise chipset (inc. Compaq, Dell, HP D1180A, AST VGA's))
  Toshiba 3100 + Gas plasma screen
  Trident chipset
  TsengLabs ET3000 chipset
  TsengLabs ET4000 chipset
  VAXmate II
  Video 7 chipset

  By default, mode numbers 12 & 13 are 640x480 and 800x600 256 colour Super
  VGA modes using the TsengLabs ET3000 chipset.
  However the precise dimensions of these modes can now be specified using the
  MODE12 and MODE13 initialisation keywords which now take up to 7 parameters :

      MODE12 = ax bx cx dx chipset width height
      MODE13 = ax bx cx dx chipset width height

      ax bx cx dx = Interrupt 10h mode selection register values, as before

      chipset     = VGA chipset number :
                    0 = Tseng Labs ET3000 (default)  5 = ATI
                    1 = Tseng Labs ET4000            6 = Trident
                    2 = Paradise                     7 = Chips & Technology
                    3 = Video 7                      8 = Ahead B
                    4 = Everex                       9 = Oak Technology

      width       = screen mode width in pixels
                    (default = 640 in mode 12 or 800 in mode 13)

      height      = screen mode height in pixels
                    (default = 480 in mode 12 or 600 in mode 13)

  Any trailing values which are omitted take the default values indicated.
  Available modes on the supported chipsets include :

    Chipset     Chipset   640x350   640x400   640x480   800x600  1024x768
                Number
    Tseng 3000    0          y                   y         y
    Tseng 4000    1          y         y         y         y         y
    Paradise      2                    y         y
    Video 7       3                    y         y         y
    Everex        4          y         y         y         y

                                                                      15
    ATI           5                    y         y         y
    Trident       6                    y         y         y         y
    Chips & Tech  7                    y         y         y
    Ahead B       8                    y         y         y
    Oak           9                              y         y

  The precise combination of modes available on any given board varies
  according to the manufacturer and the amount of video RAM available.
  The 640x480 and 800x600 modes require 512k and the 1024x768 mode requires
  1 megabyte. Here are some examples of suitable initialisation file keywords

  VGA board based on the Tseng Labs ET3000 chipset :
    MODE12 = 46
    MODE13 = 48

  VGA board based on the Paradise chipset :
    MODE12 = 94 0 0 0 2 640 400
    MODE13 = 95 0 0 0 2 640 480

  VGA board based on the Video 7 chipset :
    MODE12 = 28421 103 0 0 3
    MODE13 = 28421 105 0 0 3

  VGA board based on the Everex chipset :
    MODE12 = 112 19 0 0 4 640 350
    MODE13 = 112 20 0 0 4 640 400

  The number of text columns and rows available in modes 12 and 13 varies
  according to the pixel dimensions :

    Columns = mode_width/8
    Rows    = mode_height/14 (if mode_height < 480)
           or mode_height/16 (if mode_height >=480)

  This gives the following text dimensions :

     640x350 mode :  80 columns x 25 rows
     640x400 mode :  80 columns x 28 rows
     640x480 mode :  80 columns x 30 rows
     800x600 mode : 100 columns x 37 rows
    1024x768 mode : 128 columns x 48 rows

- Since most Microsoft compatible mouse drivers do not support a mouse
  cursor in non-standard PC graphics modes, an option has been added to
  the MODEnn initialisation file keyword which tells INTERACTER to display
  it's own cross-hair cursor in such modes. Simply place a single letter
  'C' (upper or lower case) at the very end of the record containing the
  MODEnn keyword to cause INTERACTER to provide a mouse cursor in that mode.

      MODE9  = 64 C
      MODE11 = 88 C
      MODE12 = 94 0 0 0 2 640 400 c
      MODE13 = 95 0 0 0 2 640 480 c


EXAMPLE................



                                                                      16
Here is the configuration file for a 1Mbyte Trident board (1024 x 768 x 256)
using a mouse and saving screens on disk.


DISPLAY    = 10
CHARSET    = c:\ozgis\standard.chr
COLUMNS    = 80
TEMPMENU   = \ozgis\menu.tmp
TEMPWINDOW = \ozgis\window.tmp
mode13  = 98 0 0 0 6 1024 768 C


The system is now configured for OzGIS with super VGA board.
If you are going to produce maps on printers and plotters you will have
to configure for OzMAP as described in the following section.

  3. 5 Maths Coprocessor
       -----------------

If you have a maths coprocessor you can use a different version of the main
OZGIS program.

You need to modify the batch files \ozgis\ozgis.bat and \ozgis\ozcensus.bat to
use the program ozgisco instead of ozgisprg.

  3. 6 Extra RAM
       ---------

If you have more than 1 Mbyte of RAM you can speed up display of menus and
other windows enormously by using a RAM disk.

You put a command in your config.sys file like:

DEVICE=C:\DOS\RAMDRIVE.SYS 1024 /E

This then gives you a pseudo disk drive in RAM, so its very fast. The drive
identifier is one more than you are using e.g. if you have one disk drive
called C: then the RAM disk drive will be D:

After you have put in the command, reboot you PC and type "DIR D:" to check
that you got it right (see your DOS manual).

Now modify the \ozgis\interact.ini file to define the two save files to be on
the RAM drive. The entries should look something like:

TEMPMENU   = D:\menu.tmp
TEMPWINDOW = D:\window.tmp


  3. 7 Hardcopy configuration
       ----------------------

You may wish to leave this section until you want to output maps to printers or
plotters.

The configuration file \ozgis\sciplot.ini has to be set up if OzMap is going to
be used to produce hardcopy maps. The file looks like:


                                                                      17
VGA                                  VGA or EGA
40.0      0                          HP Plotter metafile
18.0      1                          Dot-matrix printer metafile
18.0      1                          Postscript Ascii metafile
18.0      1                          Encapsulated Postscript file
18.0      0                          HPGL file
18.0      1                          CGM file
18.0      0                          WordPerfect graphics file
18.0      1 COM1                     On-line Apple Laser Writer
40.0      0 LPT1                     On-line HP plotter
00C3                                 device mode & serial modes HEXIDECIMAL

The first column is the width of the drawing surface in cm. Values will need to
be set for your plotter or printer.

The second column is the drawing line width for Postscript, Encapsulated
Postscript, Apple LaserWriter, Computer Graphics Metafile, dot matrix, and HP
LaserJet printers.
0  = Ignore parameter
1  = 1 device space units (1-10 Valid)

The third column is the port used for printers and plotters:
'COM' - Primary Serial Port
'COM2'- Secondary Serial Port
'LPT1'- Primary Parallel Port
'LPT2'- Secondary Parallel Port

The value at the bottom is a hexidecimal set of flags for setting the port for
on-line printers or plotters.

The packed coded device mode word with the device mode byte in the most
significant part of the integer, and the serial modest byte in the least
significant part of the integer.

Format of the integer = [device mode | serial modeset].

Device mode byte description:  [bits]
76543210
_______0  = XON/XOFF flow control
_______1  = Hardware flow control on DSR line
______0_  = Bell with FRAME or PLTEND
______1_  = No bell with FRAME or PLTEND
_____0__  = Cr with FRAME or PLTEND
_____1__  = No cr with FRAME or PLTEND
____0___  = Check for break in PLOT
____1___  = No check for break in PLOT
___0____  = HP pen plotter handshake init
___1____  = No HP pen plotter handshake init

Serial modeset byte description:  [bits]
7      6   5  4    3        2        1    0
--Baud Rate-- -Parity-  -Stop Bits- -Char Length-
000 -   110  00 - None  0  - 1   10  - 7 Bits
001 -   300  01 - Odd   1  - 2   11  - 8 Bits
010 -   600  11 - Even
011 -  1200
100 -  2400
101 -  4800

                                                                      18
110 -  9600
111 - 19200

For example, 9600 baud, no parity, 1 stop bit, 8 bits is

110 00 0 11 = C3 hex = 195 decimal


  3. 8 Plotter setup
       -------------


Plotter pens should agree with those defined in device files. The standard
order is:
BLACK        PEN 1
BLUE         PEN 2
GREEN        PEN 3
RED          PEN 4
YELLOW       PEN 5  The last four dont matter that much!
MAGENTA      PEN 6
CYAN         PEN 7
GREY         PEN 8

If this order conflicts with other packages in use the device files can be
modified. The order of the first four pens is particularly important for colour
simulation, although as long as all pens have different colours the final maps
will probably be acceptable.


Plotters will usually use software handshaking.

HP pen plotters require a serial interface between the  Personal Computer and
the HP pen plotter. On the PC side, a cable with a D9 or D25 connector should be
connected to a  serial port or asynchronous adapter port. On the HP pen plotter,
a cable with a D25 connector should be connected to the computer/modem port. A
detailed specification of the way the  cable should be wired follows:

Serial cable wiring for HP pen plotters: 7440A, 7470A, 7475A, 7550A

 ----------------------------             -----------------------
| Personal Computer          |           | HP Pen Plotter        |
| [Serial I/O Port or        |           | [Computer/modem port] |
| Asynchronous Adapter Port] |           |                       |
 ----------------------------              ----------------------

      Transmit Data     *-------------------*   Receive Data
       [D9/Pin-3, or                             [D25/Pin-3]
        D25/Pin-2]

      Receive Data      *-------------------*   Transmit Data
       [D9/Pin-2, or                             [D25/Pin-2]
        D25/Pin-3]

      Signal Ground     *-------------------*   Signal Ground
       [D9/Pin-5, or                             [D25/Pin-7]
        D25/Pin-7]

      Data Set Ready    *-----*-------------*   Data Terminal Ready

                                                                      19
       [D9/Pin-6, or          |                  [D25/Pin-20]
        D25/Pin-6]            |
                              |
      Clear-To-Send     *-----*
       [D9/Pin-8, or
        D25/Pin-5]

      Data Terminal Rdy *--------------*-----*  Data Set Ready
       [D9/Pin-4, or                   |         [D25/Pin-6]
        D25/Pin-20]                    |
                                       |
                                       *-----*  Clear-To-Send
                                                 [D25/Pin-5]

Please note that the previous wiring diagram is necessary if full hardware
handshake is desired. If the user intends to  use only software handshake
(XON/XOFF), then only three wires  are required. For software handshake the only
connections  required are: signal ground, receive data, and transmit data.

     There are certain restrictions when an HP pen plotter is used as the plot
device. Not all HP pen plotters possess equal capability! SciPlot only supports
the 7470A, the 7475A, and the 7550A HP Pen Plotter. There are enough control
mechanisms in SciPlot to allow the use of others though.  Please note the
following:

 The "INIT=ON" command in the VECTOR.CFG file will send initialization commands
in the I/O stream to the  plotter when VECTOR is executed. Older HP plotters
will  produce errors on receipt of these handshake mode commands.  If this
happens, set "INIT=OFF" in the VECTOR.CFG file, and the offending commands will
be deleted from the stream.

  3. 9 Mouse
       -----

If you have a mouse it must be installed in the standard way.

The driver must be call MOUSE.COM (for the system to detect it).

Mouse drivers usually only work with standard VGA and EGA. If you are operating
in super VGA modes you would have to set the mode command in
\ozgis\interact.ini with a "C" on the END (as already described) for the cursor
to appear.

                                                                      20
                    4. BASIC CHOROPLETH MAPPING EXAMPLE
                       ================================


  4. 1 OzCensus
       --------

The main display and analysis program is OzGIS.

A much simpler version of OzGIS is provided called OzCensus.

This version is suitable for simple mapping of Census type data and is
recommended for use while learning to use the system.

OzCensus has two or three menus and about twenty menu options while the full
OzGIS version has about fifty menus and a few hundred menu options.

When you want to do more advanced mapping use OzGIS!

  4. 2 Example map
       -----------

The most common application is the display of data such as Census data as
coloured polygons. Here the processes necessary to display such data are
described.

You should print out the template for the function keys \ozgis\fnkeys.doc

You will probably have a file of attribute data (such as population Census
data) and a file of digitised boundary data for mapping:
We will look at data for Far East Asia. There are two data files:

FEA-G.DAT are the digitised boundary data, and
FEA-A.DAT are the attribute data

First of all we have to enter the data so it is checked and written into
internal files:

type

cd \ozdemo
ozenter

1. select the option to enter standard format geographic files
give the input data file as fea-g
give the output geographic file as fea

2. select the option to enter an attribute file
give the input data file as fea-a
give the output attribute file as fea

3. type F10 to exit

Now the files can be displayed

type


                                                                      21
ozcensus


choose the option to "DISPLAY A NEW MAP".

give the attribute file name as FEA (from above)

When asked for the geographic file name input "L". A list of the available files
will appear (type Enter or Esc to exit). Give the geographic file name as FEA

The data are now processed, the map is displayed, and the next menu appears.

You now have a default map with legend and distribution diagram. The legend
has the numbers of zones in each class on the left and the class value ranges
to the right of the coloured boxes.

Now investigate some of the options:

Choose the option to display the next sequential attribute

If you only have 16 colours the system does not display the map until you
request regeneration. This enables several options to be changed before the
slow polygon drawing takes place.

If the map does not change type F3 to regenerate the map.


Select the option to select by number. Type 0 to get a list.
Type Esc to return to the question. Type in a number to select an attribute.
(type F3 to regenerate if necessary)


Now investigate some of the function keys:

You can print the file FNKEYS.DOC for a template.

Type F1 to get a help message. Esc is usually used to return.

F2 hides the menu; type Esc to redisplay it.

F3 regenerates the map when required (followed by Enter to display a menu).

F4 enables files to be audited and maintained. Type F4 and select the option to
interrogate files. Select geographic files and use the file name FEA (the one
displayed). Type Esc three times to return to main menu (Esc is used to return
to the previous menu).

F6 enables the user interaction to be controlled; try turning on partial trace
(level 1) which causes a series of messages to appear at the bottom of the
screen telling you what the system is doing, but not as many as level 2.

F8 causes a jump back to the previous main menu. This enables skipping back
several levels. You will find that at main menus this is the only way to exit.
(Irrelevant with the tiny number of menus in OzCensus).

F10 is used to exit from the program. Dont use it yet!

Select the option to change the number of classes.

                                                                      22

change the number of classes to 10.
(type F3 to regenerate if necessary)

Select the option to change the quantisation method. Another menu will appear.
These options are very important as they enable the map to show the data in a
way relevant to the purpose of the analysis.

Choose QUANTILES and set the number of classes to 10 (deciles).

Type Esc to go back to the previous menu.

Choose the option to display statistics. Type return (or Esc) to remove the
window.

Choose the option to interrogate the map. This will enable the current values
for the displayed zones to be listed. A cursor will appear on the screen which
indicates the bottom left position. Place it using either the arrows (type
Enter to select the position) or the mouse (left button to select). A box
cursor then appears to select the other corner. All zones are listed where the
minimum bounding rectangle (MBR) intersects the selected window.


etc

Continue investigating options

Type F10 to exit.

                                                                      23
                    5. INTERACTIVE USER INTERFACE TO OzGIS
                       ===================================

      The user controls OzGIS by responding to menus, questions and
commands presented on the alphanumeric terminal.

      This section describes these forms of user communication.

  5. 1 Menus
       -----


  5. 1. 1 Menu format
          -----------

      Menus are presented in the format below.  The MENU HEADER
contains the previous menu item selected, or in the case of a main menu
the system title.

               [MENU HEADER]
                1:  [menu item 1]
                2:  [menu item 2]
                         :
                         :
                         :
                n:  [menu item n]

Menu items are numbered sequentially from one.  A selection is made by typing in
the character next to the item. Alternatively the arrows can be used to move up
or down and Enter typed to select.


  5. 1. 2 Function keys
          -------------

      User assistance is provided at every menu by typing function keys:

      (print out fnkeys.doc for a template)


      F1    presents "help" or informative messages about the menu items
            and describes the effect of selection of the items

      F2    enables the menu to be removed so it does not obscure the display.
            Esc will display it again.

      F3    regenerates the map after parameters have changed. Enter must be
            typed to display the next menu.

      F4    permits interrogation and maintenance of OzGIS files.
            A menu is presented with the following options:

               -  delete a file
               -  interrogate the header of a file
               -  generate a list of files.

      F6    permits the extent of user communication to be controlled.

                                                                      24
            A menu with the following options is presented:

               -  turn user assistance messages on/off
               -  turn trace messages from tasks on/off
               -  turn the bell to signal cursor operation on/off
               -  turn on debug (useful for reporting errors)

            The default of the option for user assistance messages is "on"
            (i.e., that the messages are displayed).
            The default of the option for trace messages depends on the module.
            (it is useful for data entry and preparation)
            The debug option is for system testing, but may be useful to trace
            faulty data problems. Output goes to the print file OZGIS.OUT

      F8    exits from the current menu to the last major menu, which
            depends on the stage of processing.

      F10   quit the OzGIS session.

Pressing the "Esc" key before entering any other character has one of
two effects:

      -  return to the previous menu
or    -  repeat of the current menu ("F8" should be typed to return to the
previous main menu)
The option taken depends upon the stage of processing.

  5. 1. 3 Stacking selections
          -------------------

Menus take quite a time to display as the underlying graphics has to be stored
first. A series of selections can be made when the sequence of menu options is
known, and the menus will not appear.

  5. 2 Questions
       ---------

      Questions are asked by OzGIS when data are required for an
operation.  The user must supply the data by entering appropriate responses
on the keyboard.

      The format of questions consists of the question, a possible range of
values in brackets (if appropriate), a default value in parentheses (if
appropriate) and terminated by a question mark.  The range of values and
default values indicate the form of the expected answer.  An example is:

      -  request to replace an existing file:
         DO YOU WANT TO REPLACE THE FILE [Y,N]?


         The user must respond by typing either "Y" (for "YES") or "N"
         (for "NO").

      The following single character responses provide assistance when
answering questions:

      "H":  presents a "help" or informative message about the required
            response.

                                                                      25

      "E":  returns to the previous menu without further action.


      Errors in responses are trapped and result in help messages being
printed.  The user is asked the question again.

  5. 3 Commands
       --------

      Commands are issued by OzGIS when an operation has to be
performed by the user.  When the operation is completed, control returns to
the appropriate menu.

      The format for commands consists of a directive, a possible range of
values in brackets (if appropriate), a default value in the input field (if
appropriate), terminated by a colon.  Examples are:

      -  to provide the number of classes:
         TYPE NUMBER OF CLASSES [1-6] (4):

         The number of classes must be in the range 1 to 6, and if
         the user simply presses the "Enter" key a default value of 4 will
         be selected.

      -  request for the name of a file:
         TYPE FILENAME (TEST):

         The filename must be entered as a character string, or the
         "Enter" key pressed to accept the default filename "TEST".

      The following single character responses provide assistance when
responding to commands:

      "L":  provides a list of data items that can be selected.

            e.g. for FILENAME, a list of available files will be printed.
            e.g. for ATTRIBUTE DESCRIPTION, the names of attributes on the file
            will be listed.

      "H":  presents a help or informative message about the desired
            operation.


      "E":  returns to the previous menu without further action.

Errors in responses are trapped and cause a help message to be printed and
the command to be repeated.

  5. 4 Graphic interaction
       -------------------

      Graphic interaction in OzGIS involves the use of the mouse and/or
arrow keys to control the cursors on the monitor.
Use the left mouse button or type Enter to select the position.

      The user is directed to operate the mouse etc by the appearance of the
cursor on the monitor and by an appropriate command on the screen.  The

                                                                      26
extent of the command depends on the current level of user communication
(see F6  option)

There are two types of cursors:

1. a pointer to select a position of object
2. a box to select a region. The bottom left corner is selected and then the
   other.

  5. 5 Pop-up
       ------

The menus and windows operate in "pop-up" mode. This requires that the screen
under the menu etc has to be saved to file before the menu appears so it can be
restored. This is slow. Display speed can be increased by specifying the save
files to be on RAM disk (if you have extended memory) by modifying the file
name in the \ozgis\interact.ini file.

  5. 6  Print file
       -----------

Every program generates printout on a file OZGIS.OUT.

This includes:

Reports
Error messages
Debug output

                                                                      27
                    6. OzGIS FILES
                       ===========

      This Chapter describes the various files which are processed by
OzGIS.  Some of the files can be entered into OzGIS as data, and
the external formats for these files are given later.  All of the
files have internal formats, which are generated as part of the user
interaction.

Data files usually come from Census bureaux, map data suppliers or your
corporate database.

The file types will become obvious with use of the system.

      External data files must be entered into OzGIS explicitly.  This
operation permits OzGIS to generate internal representations of the
data for efficient processing and to check the data.

      The following kinds of files must be entered into OzGIS:

      -  marker files
      -  device files
      -  presentation files

      Certain files must be prepared explicitly within OzGIS under user
direction.  These files are:

      -  saved display files
      -  catchment files (OzCatch)
      -  time lapse files  (no longer available)
      -  palette files (no longer available)
      -  hardcopy files  (no longer available)

      Some files can be prepared externally or internally.  These are:

      -  geographic files
      -  name files
      -  combine files
      -  colour names file  (no longer available)

      OzGIS distinguishes the various types of files, so that users can
interrogate the current set of files of a specified type.

(a)  Geographic Map files describe geographic (map) data in terms of
     graphic elements - zones, polygons, line networks, line segments and
     points.  The data can be drawn in geographic regions, or overlayed on
     displayed maps.

     The files are generated by digitising base maps.  This is a
     time-consuming soul-destroying task.  Fortunately digitised map data
     are available for many commonly used maps e.g. states, postcodes,
     Census districts.  Where special zones are required, they can often be
     defined in terms of Census districts and the map boundaries obtained
     by amalgamating the digitised Census boundary data (dropping internal
     lines).  This has the additional advantage that Census data can also
     be extracted for the amalgamated zones and used for comparisons with
     the user's own attribute data.

                                                                      28

(b)  Attribute files contain the values of attributes (variates,
     statistics, variables) referenced to zone, line or site names.  Each
     file may contain a number of attributes for a fixed set of names.

     Attribute files are processed to assign a class number to zones
     (colour) or lines (line type) or sites (symbol sizes) in a displayed
     map.

     Attribute data files are usually generated via a standard database or
     modelling system or by a user's own programs.

(c)  Names files contain a list of zones, lines or sites that defines a
     geographic region of interest.  The files may be used to subset
     geographic data.  It may also be used to restrict the set of
     attributes to be quantised for a map, or alternatively the set of
     zones lines or sites to be displayed on a map.

(d)  Combine files - define new items in terms of zones.  A file may define
     new zones in terms of amalgamated base map zones or the influence of
     surrounding zones on a site.

     The file contains a list of names of the new zones or sites defined.

     For each new item there is a list of the base map zones it is defined
     by and a list of weights.
     New zones are defined by complete base map zones so the weights have
     value 1.0 e.g. Sales Territories. Site Catchments are used to retrieve
     data from underlying map zones so the weights give the proportions of
     the zones (range 0-1).

(e)  Marker files - define simple shapes as single polygons for display as
     markers.

     The data are simply the (X,Y) points that are used to draw the
     polygons.  The points are in the range -0.5 to +0.5 so the polygon can
     be easily scaled and displayed centred at a location.

(f)  Saved Display files contain the data to regenerate a complete display.
     These files should be stored by the user upon completion of a display
     for later recall.  Subsequent manipulation of the display is possible
     after recall.
     There are two modes. The screen is usually saved so the map can be rapidly
     displayed, but this is not relevant for later regeneration on plotters
     etc.

     Saved display files are the common level of storage and retrieval of
     maps.  A user may build up a set of commonly displayed maps with all
     the desired features that can be displayed and modified rapidly.
     Saved display files are also used for presentations.

(g)  Presentation files contain references to a number of Saved Display
     files.  The files are used to present a set of displays quickly,
     usually for demonstration purposes.

(h)  Time Lapse files contain a set of attributes for display as a time
     lapse sequence.  All attributes are quantized in the same way by
     OzGIS and must exist on the same file. e.g. data that has been

                                                                      29
     collected regularly, say weekly, can be displayed as a 'movie' to see
     if there are any time-based spatial features.
     The format of the files is internal to OzGIS.  These facilities
     are only available for 256 colour display systems.
      (no longer available)

(i)  Device files - define the graphic devices and their capabilities.
     Each device is a GKS workstation.  Several files may exist for each
     device giving different values for the graphic primitive attributes
     (line type, text, colours, patterns etc.).  In particular, each file
     contains sets of fill colours or patterns for single and bivariate
     maps.


(j)  Palette files contain a set of colours which can be selected for
     display.  The set of colours is displayed as a palette during the
     colour selection process.  Colour palette files can be modified and
     generated by user interaction, but their format is internal to
     OzGIS.
     (no longer available)

(k)  Colour Names files contain a set of colour names and associated blue,
     green and red (B,G,R) values for the display system.  The files enable
     users to specify colours by typing a name (e.g. LIGHT RED) on the
     keyboard.  Colour names files can be entered as external data files or
     can be prepared by entering names and indicating the corresponding
     colours.
     (no longer available)

(l)  Hardcopy files - contain information to enable maps to be reproduced
     off-line on other devices (with the vector program)
     (no longer available)

(m)  Catchment files - contain definitions of sites, boundaries of
     catchments around sites, and catchment weights.  Catchment files are
     interactively generated with reference to a base map.
     (not implemented yet)

                                                                      30
                    7. DEVICE FILES
                       ============

Device files control the appearance of maps:

     . polygon colours and type of fill
     . text colours, sizes and fonts
     . line colours and styles
     . sequences of class colours or hatch patterns
     . menu and message colours

Experience showed that it is better to have fixed sets of definitions rather
than allow the user to specify the display parameters.

Remember that the basic display definition (number of pixels, lines and colours)
was specified when configuring the system.

The best way to understand device files is to look at the contents:

First of all type:

cd \ozgis
ozgis

Select the option to CHANGE DEVICE FILE

Give the file as *C16SV1

Select the option to DISPLAY DEVICE CHARACTERISTICS

You will now get a display that shows the text types (sizes and colours),
line (types and colours) and the various polygon fills as rectangles.

Of particular interest are the class colours. The bottom set is a sequence of
121 colours which is designed to give the appearance of increasing attribute
values. In this device file for a 16 colour board the colours are in blocks,
but for 256 colour boards all the colours will be different (and can be used
for "continuous colour" maps). The set of colours above are a 7 x 7 set for
bivariate maps. They actually map onto the same set as for single variate maps,
so if bivariate maps are to be produced different device files should be used.

Now choose a bivarite device file *C16BV1 and display that. The bivariate
sequence will show a progression of colour in each dimension.

There is a set of files for 16 colour displays, *C16SV1 to *C16SV9 for single
variate maps, and *C16BV1 to *C16BV3 for bivariate maps.


There is also a set of files *C256SV1 to *C256SV9 and *C256BV1 to *C256BV3 for
256 colour boards. If you have a suitable board display one of these. The
colour sequence will now be complete.


Other device files are also available, primarily for display on printers and
plotters, but these can also be used on the display; try them!

*HATCHSV1 is for display of hatched single variate maps and *HATCHBV1 for

                                                                      31
bivariate maps.

You should now display a few of the single variate decvice files (*C16sv? or
*C256SV?) and decide on one that you will use as the default file.

When you have decided on the default file type F10 to exit from OzGIS and:

cd \ozgis
copy C256SV6.DEV DEFAULT.DEV  (using the file you have chosen)

                                                                      32
                    8. OzGIS MAP TYPES
                       ===============

Several types of maps and diagrams can be displayed.


  8. 1 Attribute maps
       --------------

     There are one or two streams of attribute processing for the types of
maps available for zone, line and site attribute data:

     -  zones map
     -  lines map
     -  sites map
     -  two zone streams i.e. bivariate maps
     -  zones and lines
     -  zones and sites

     The type of map is selected before display and cannot be changed.

Basic choropleth maps have already been demonstrated. Here are some more
examples... Remember you can type "L" to get a list of files when asked for a
file name.

  8. 1. 1 Bivariate zones map Example
          ---------------------------

Select the bivariate zones option.

Use attribute files LOWE1 and LOWE2 and geographic file LOWE.

Remember that you may have to type F3 to display the map.

 Note the form of the legend; the primary attribute (first file, top
description) is the vertical part of the legend.

Type F8 to return to the main menu.

  8. 1. 2 Zones & sites Example
          ---------------------

Now select zones & sites option.

Use the LOWE1 and LOWE2 attribute files again, and the LOWE zones geographic
file.

Give the sites geographic file as LOWE-S1.

Next choose the option to change quantised data and then the option to display
more quantised sites. Give the next sites geographic files as LOWE-S2. Use
symbol number 2 (number one is already used).

You will have a coloured zones map with different sized symbols. This type of
map is for applications such as deciding where to put shopping centres, where
different symbols can be used for e.g. existing centres, centres owned by
different retail chains and proposed new centres.

                                                                      33

  8. 1. 3 Geographic (GIS) maps Example
          -----------------------------

Maps can be displayed that show geographic data without attribute data i.e.
polygons, lines, names at points and symbols at points.

Where the data are preclassified feature codes can be used to subset the files
for display.

For example, display some of the Hawaii DLG files. These files came from the
USGS, and after some cleaning up, were entered as DLG-3 data and the polygons
formed using OzZone.

Select the option to display geographic maps.

Select the option to display polygons and use file HAWDLGWB, which is the
outlines of the islands. Use any polygon number, give some text for the legend
(e.g. "Islands") and use the no boundaries default.

Type F3 to regenerate if necessary.

Select the option to display polygons for feature codes.
Use file HAWDLGAB  which is administrative boundaries. The file has feature
codes in the range 900103 to 900108. Give the range as 900103 to 900103 and use
polygon number say 4.  Repeat for another feature code range and polygon
number.

The administrative boundaries go outside the island coastlines so you may want
to redraw the island outlines by overlaying line segments for file HAWDLGWB.

Select the option to overlay line segments for feature codes.
Use file HAWDLGRD which is roads.  The file has feature codes in the range
2905001 to 2905041.  Select a subset e.g. 2905000 to 2905020.
Give the legend text as "roads".

Select the option to overlay line segments.
Use file HAWDLGST which is streams. Give the legend text as streams.

Select the option to display names at sites. Give the file HAWDLGWB.  The
polygon names will be displayed (the area numbers from the DLG file). Usually a
points file would be used that has the actual names.

If necessary, type F3 to regenerate the map.

Select the option to add text, type in a title e.g. "HAWAII", and position it at
the top of the map.

Note that if you regenerate the map the polygons are drawn first, and then line
segments, symbols and finally names.  Within each type they are displayed in
the order specified.  If a mistake is made overlays can be removed.


If polygons overlap, "polygon overlay" operations can be simulated by
displaying using hatching. e.g. select the hatch device file *HATCHSV1 from
the main menu and then display polygons from the two files HAWDLGWB (the
islands) and HAWDLGAB (administrative boundaries).

                                                                      34

Type F8 to return to the top level menu

Be aware that you can type several menu selections without waiting for the
menus to appear.

  8. 1. 4 Diagrams Example
          ----------------

Distributions, sorted values and quantisation results can be displayed as full
screen diagrams for one or two attribute files. Scatter diagrams can be
displayed for two files.

Choose the display attribute file option and then the distribution for two
attribute files. Use LOWE1 and LOWE2 files. Next choose "change display
features", followed by "add statistics" and "display mean & std. deviation".

You can change attributes and quantisation in the usual ways (and type F3 to
show the results).

  8. 2 Device files
       ------------

Device files are a critical part of the system as they define how maps are to
appear. Experience showed that it is better to have standard sets of colours,
line types, fonts, text sizes etc than to try and interactively select them.

Select the option to display device characteristics. This option is used when
defining your own device files. A major feature is the colour sequences. The
full colour sequences, available in the CSVGAS.. files have 121 colours
available, while other files have a subset of 10 colours. The full sequence is
designed to give a progression of colours to show the range of attribute
values. The full set is used for continuous colour maps. 121 are used as it can
be exactly sampled for most numbers of classes (120 is divided by 2,3,4,5,6,8
and 10). similarly there is a bivariate sequence for bivariate maps. This is 49
colours (7x7), (as 6 is divided by 2 and 3). You should not change hardware
text sizes as they are fixed by the VGA/ EGA capabilities, but any size can be
used for software fonts. Any colours can be changed. You can also set up your
own markers.

To design your own device files you usually modify a standard one.

Note that bivariate device files should be used for bivariate maps.

Now choose the option to change the device file and display several others. You
can choose the one you like best and go back to the entry phase and make it the
default device file (or copy the .DEV file).

Device files are usually held as system files (in \ozgis) so the file names
must be given with a '*' at the front.

  8. 3 Presentations
       -------------

This option enables a set of saved display files to be defined for
demonstrations.

An Ascii file is set up that gives the names of the saved display files and

                                                                      35
menu lines that are associated with them.

  8. 4 Time Lapse Display (not available)
       ----------------------------------

Special options are available for the display of time lapse files.  The
following parameters can be altered:

      -  The time interval between successive attributes (given in units of
         approximately seconds)

      -  The time interval between the end and beginning attributes of a
         sequence (given in units of seconds); i.e. the pause between a
         repeated sequence.

      -  The beginning and end attribute of the sequence being displayed.

The zone legend format is not updated during a time lapse sequence, and by
default the class description of the legend is set to the "HIGH" and "LOW"
format.  Histograms and scatter plots cannot be displayed during a time lapse
presentation.
tribute values.

                                                                      36
                    9. ATTRIBUTE SELECTION
                       ===================

     Various attribute files can be nominated to generate a map display.
It is the user's responsibility to ensure that the names referenced by the
attributes match the names of the displayed zone lines and sites in the
map.  Obviously colours can be assigned only to the zone with names common
to the attribute and zone files etc.

Only some of the names have to agree; it is quite common to process attribute
data for a larger area than is displayed.

     Attribute may be selected for quantisation and display from attribute
files in various ways:

To try these options, display a zones map using attribute file LOWE1 and
geographic file LOWE as before and then select the option to change attributes.

  9. 1 Sequentially
       ------------

This option will simply select the next attribute off the file. As usual F3 may
have to be used to display the map.

  9. 2 By number (position in file)
       ----------------------------

A prticular attribute may be selected by the position within the file. Type
zero to generate a list of the attributes on the current file.

  9. 3 By attribute description
       ------------------------

The attribute can also be selected by typing part of the description e.g.
"FORC" to retrieve "ARMED FORCES". Typing L lists the attributes.

  9. 4 By arithmetic operation
       -----------------------

This option is not available due to the limited PC memory. See the data
preparation option.

                                                                      37
                   10. QUANTISATION
                       ============

     Attributes are usually presented to OzGIS as values which have to
be quantized into a number of classes for display.

     A maximum of 10 classes can appear in single variate zone displays and
9 classes (a maximum of 3 per variate) in a bivariate display.  A maximum
of 4 classes is available for lines and 4 classes for sites.

     The quantisation process is the most important aid for the analyst in
understanding the features of the attribute data.  The quantisation method
and parameters should be chosen logically according to the purpose of
analysing the data.

     The aim is to display the map that best shows the spatial features and
distribution of the data.

Note that the best maps usually have a small number of classes; manipulate the
map to show the data according to requirements. This contrasts with the
production of atlases, where large numbers of colours are used as the purpose
to which the map will be put is not known.

To try these options, display a zones map using attribute file LOWE1 and
geographic file LOWE as before, and select the option to change the
quantisation. Try changing the number of classes first and then work through
the various methods.

There are other options to change the list of zones to which quantisation is
applied and to change the range of values over which the method operates.

 10. 0. 1 Quantisation Methods
          --------------------

     The following methods for quantization are available for determining
the class intervals:

   (a)  Equivalence Classes:  numbers are assigned to the attribute values
        (possibly with integer round-off).  The attribute values should lie
        in the range of the maximum number of classes permitted but they
        will be scaled for the selected number of classes.

        This method enables the quantisation to be carried out on another
        system and the resulting class numbers entered instead of attribute
        values.  A common use is for mapping discrete data e.g. political
        parties on election maps.

   (b)  Quantiles:  intervals are computed by assigning the same number of
        zones to each class.

        This method has often been used to generate choropleth maps, e.g.
        deciles.  The effect of equal numbers of zones is maps that have
        approximate equal areas of each class colour.  Such maps are
        pretty.  Unfortunately quantiles tend to obscure the distribution
        of the attribute data.

   (c)  Equal Value Intervals:  intervals are computed from equal

                                                                      38
        increments over the range of attribute values.

        The default quantisation method selected when a map is first
        generated is equal value intervals.  The advantage of this method

        is that the number of zones assigned to each class indicate the
        distribution of the data.  It is recommended for general purpose
        maps and for initial investigations of attribute data.

   (d)  Refined Equal Value Intervals:  intervals are computed from equal
        increments over the attribute value range, modified by a
        "round-off" procedure (e.g. an increment of 10.12 would become
        10.00).

        Maps for publications usually have 'nice' values in the legend.

   (e)  121 Equal Value Intervals:  121 intervals are computed from equal
        increments over the range of attribute values.  Only 8 classes are
        displayed in the legend, but the colours are assigned over the 121
        quantized values to give a "continuous colour" appearance.
        This option is only available with standard zone maps.

   (f)  Interactive Selection of Class Intervals:  intervals are selected
        by the user by placing crosshairs on a displayed histogram.
        (256 colours interactive mode only!)

   (g)  Mean and Standard Deviation:  intervals are determined by dividing
        the range of attribute values at the mean value and at specified
        offsets from the mean that are multiples of the standard deviation
        of the data.  The number of classes must be even.

        This method has particular application for attribute data from
        random populations where the data are expected to have a normal
        distribution and hence statistical theorems govern percentages of
        population within the classes.

   (h)  Nested Means:  intervals are determined by iterative division of
        the range of attribute values at the mean value of the subdivision.
        The number of classes must be 2, 4 or 8.

   (i)  Natural Breaks:  intervals are determined by iterative division at
        the largest difference between attribute values.  The number of
        attribute values between differences is user-specified.  Hence
        class intervals occur at "jumps" in the data.

   (j)  Specification of Class Intervals:  interval values (for a specified
        number of classes) are typed in by the user.

        Hence data within certain value ranges can be isolated.   Suitable
        class intervals for hard-copy maps can be selected.

   (k)  Specification of Numbers Per Class:  intervals are determined by
        user-specification of the number of zones or sites in each class.
        The numbers need only be given for some of the classes; the
        remaining zones or sites will be distributed over the remaining
        classes during each quantization.

        An analyst can isolate data at the extremes of the attribute

                                                                      39
        distribution by using this method.

   (l)  Class Number Percentiles:  intervals are determined from
        user-specified values giving the percentages of the number of zones
        within each class.

   (m)  Class Range Percentiles:  intervals are determined from
        user-specified values giving the percentage of the total range of
        attribute values in each class.

   (n)  Current Class Intervals:  the intervals (and number of classes) are
        used to quantize subsequent attributes.

        Hence a series of maps can be produced with the same legend which
        enables attributes to be compared.

   (o)  Current Numbers:  the number of zones or sites per class (and
        number of classes) are used to determine the intervals for
        subsequent attributes.

 10. 0. 2 Quantisation Ranges
          -------------------

      The range of values over which the quantization is applied can be
restricted in all methods.  The following options are available for
limiting the range:

      -  the extremes of all values (default)
      -  user-specified limits (the user enters the low and high values)
      -  refined values (i.e., automatically rounded to "nice" values)
      -  limits fixed at current values for subsequent quantisations

Zones with values outside these limits are assigned the "excluded zone"
value and colour, lines and sites are not displayed.

For example a standard legend for percentage data with value ranges
0,25,50,75 and 100 could be generated by choosing extremes to be 0 and 100
and fixing them, and by using 4 equal value classes.

 10. 0. 3 Quantisation Lists
          ------------------

      Each of the attribute processing streams has an associated list
that holds the names of the items being quantised i.e. zones or lines or
sites.  There is one list for a single stream, one zones list for bivariate
maps, and for two streams there is a list of zones and a list of lines or
sites.

      Each list selects the items that are to be quantised from the
corresponding attribute file.  When a map is generated the lists are set to
all the names if the attribute files (common names in the case of bivariate
maps).

      Zone lists can be reset to:

      -  all zones in current attribute file (single variate)
      -  all zones common to two attribute files (bivariate)
      -  the displayed zones

                                                                      40
      -  zones in a names file

      Zone lists can also be modified by adding or deleting zone names by
typing in a name or selecting the zone with the cursor (256 colour mode)

      Site lists and line lists can be modified by giving the names.

      Hence the quantisation can take place for a set of items that is
independent of the displayed, zone lines and sites (although it is
illogical for none to be the same).  It is common for the quantisation to
be carried out over a larger geographic area than that being displayed.
Sometimes zones are removed because the attribute data are doubtful e.g.
Census districts with a low population.

      Changing attribute files does not change the items whose values are
quantized.

                                                                      41
                   11.  DISPLAY CONTROL & MAP DESIGN
                       =============================


 11. 0. 1  Map Quantisation Legends
          -------------------------


      A legend is always displayed on the monitor when an attribute is
quantised for map display.  Similar legends are displayed for zones, lines
and sites.

The elements of a legend are:

      -  TITLE, a title for the legend (maximum of 3 lines and 16
         characters per line).

      -  UNITS, description of the units of a legend (maximum of 10
         characters).

      -  HEADER, a header for the class annotation (maximum of 8
         characters).  The default is "RANGE".


      -  CLASS ANNOTATION, either

            -  the class intervals as numbers aligned between boxes
               (maximum of 8 characters), or

            -  class description aligned with the centre of boxes (maximum
               of 2 lines, 8 characters per line), or

            -  "HIGH" and "LOW" at the top and bottom of the boxes
               respectively.

      -  EXCLUDED ZONES, annotation for the "excluded zones" class

      -  MISSING DATA ZONES, annotation for the "missing data" class

      -  NUMBERS, the numbers of items in each class.

      Zone legends have fixed size boxes that give the colours used for the
classes.

      Site legends have variable sized symbols in a special colour that give
the markers and their sizes used for the classes.

      Line legends replace the boxes by sample lines in a special colour
that give the line types used for the classes.

      All text in a legend is written with small fixed size characters.

      Display of the legend elements can be controlled by the user.  The
boxes corresponding to attribute classes are always displayed but the
elements (including "excluded zones" and "missing data " boxes) can be
removed.


                                                                      42
      Some of the legend text can be replaced by characters entered by the
user on the keyboard, viz.,

         -  title
         -  units
         -  header
and      -  class description

      The default map layout sets the map image viewport as the left three
quarters (approximately) of the monitor, and the legend viewpoints on the
right side of the screen.  The zone legend is on the bottom, line or site
legend above.

      New legend viewpoints can be selected with the box cursor.  A single
variate legend may need more than one column to fit.

 11. 0. 2 Overlays (GIS) legends
          ----------------------

When line overlays, markers, text at points or polygon underlays are displayed
a legend appears that describes the overlays. The text must be specified by the
user.

 11. 0. 3 Other Legends
          -------------

      When several line files are being displayed using different lines, or
several site files are displayed using different markers, a legend can be
added.

      The line and marker legends have similar format:

      -  a header line of text
      -  legend entries
      -  marker or box in quantisation legend colour
      -  description

 11. 0. 4 Text
          ----

      Lines of text can be typed in and displayed on the screen in one of
the four available text types.  The text is positioned with the cursor.  Up
to 20 lines of text can be displayed.

      Lines of text can be deleted and moved around the screen.

      Text is usually added to a map to supply extra information e.g. the
name of the geographic region and type of zones, organisation names,
disclaimers.

 11. 0. 5 Attribute Diagrams
          ------------------

      (a)  Histograms can be displayed in the map area.  The
           histograms show one of the following:

            -  the number of items (zones or sites) within equal intervals
               of a single attribute

                                                                      43
            -  the number of items within class intervals of a single
               attribute
            -  the attribute values corresponding to zones sorted in
               ascending order of attribute value.

               The bars of a histogram are coloured according to the class
               colours in the legend.  For two variate displays, two
               histograms can be displayed one underneath the other.  The
               histograms provide an overview of the statistical
               distribution of the attribute values.

      (b)      Scatter plots can be displayed in the map area for
               bivariate zone displays.  The plots show the distribution of
               zones within the ranges of each attribute.  The elements of
               the plot are coloured according to the class colours in the
               legend.  The scatter plots provide an overview of the
               statistical distribution of the attribute values.

      (c)   Statistics can be added to the diagrams:

      -  mean and standard deviation lines
      -  median

      A regression polynomial of order 1,2 or 3 can be added to a scatter
diagram.

      The diagram viewport is selected with the cursor.

      Addition of a distribution histogram or scatter diagram (bivariate)
add considerably to the information content of a map.  It is recommended
that they be displayed.

 11. 0. 6 Displayed Colours (removed)
          ---------------------------

      All colours within a map display can be changed by the user when a
256 colour VGA display system is being used.  Individual colours can be
selected in three ways:

      (a)  by reference to a colour palette.  The colour is selected with
           the crosshairs (256 colour mode).

      (b)  by a blue, green and red (B,G,R) triple.  Values for each of the

           elements in the triple range from 0 to 1.0;  a red colour would
           therefore be 0.0,0.0,1.0.

      (c)  by a name from a colour names file.  The name is a character
           string typed on the keyboard.

Any of these ways can be selected by the user.

      The set of colours is assigned to map classes and associated map
elements by reference to the current device file.

This enables colours for all of  the classes to be assigned quickly, although
individual colours in the set can be modified subsequently.


                                                                      44
      Displayed elements must be identified in order to change their
colour.

      Certain elements are explictly referenced in the menus associated
with colour change, and can be identified by selecting the appropriate menu
option.  These elements are:

     -  text
     -  markers
     -  lines
     -  zone boundary
     -  map background
     -  excluded zones
     -  zones with missing data
     -  zone attribute classes
     -  background of attribute diagrams
     -  site legend markers
     -  line legend

Specific attribute classes, text, markers and lines are identified by
number.

                                                                      45
                   12. MAP REGIONS
                       ===========


 12. 0. 1 Regions
          -------

      Maps usually consist of a data from a geographic file displayed on a
default part of the monitor.

      Map regions enable complex map layouts to be generated.  Maps often
have only one region, typically zones from one geographic file displayed on
the default viewpoint on the monitor.  Multiple regions, each with defined
window and viewport provide many possibilities e.g. subsets of a main map
can be added as new regions at high magnification e.g. extreme parts of a
map can be chopped off and added on as new regions in a corner e.g. several
files for different parts of a country could be displayed as separate map
regions.

      Geographic files can be displayed in user-defined parts of the
monitor.

      A map region is established when a geographic file is displayed.  The
region is defined by the geographic window (or subset) and its displayed
area (or viewport) on the monitor.  A maximum of 10 map regions can be
defined in a map.

      A geographic window is the total area of the geographic file.  Files
are subset as a data preparation process.

      A viewport is selected by positioning the cursor on the monitor with
the mouse or arrows (i.e. it is a rectangular part of the screen).

      It is possible to overlay data from geographic files onto a map
region.  More than one set of zones from a geographic file can be displayed
in a region but the zones being displayed will overwrite any underlying
zones.

      Geographic files are automatically windowed, scaled and clipped for
display on map regions.

      When multiple files are displayed on a region, the precedure order is
quantised zones, lines, sites, line overlays, markers and finally text at
points.

      Multiple regions can be defined anywhere on the map display area of
the monitor.  However, if regions overlap the display procedure is
established by the order of display.  Therefore the user should consider
the order of display carefully in multiple region presentations.

      Geographic files can be displayed  in any order, and
regions can be defined and changed as desired.  Many  of these operations
destroy the data in the display system memory (the map display is
corrupted) so F3 must be typed to completely regenerate the map display.

                                                                      46

 12. 0. 2 Map List
          --------

      A list of displayed items (zones, lines and sites) is maintained by
the system.

      The list is sorted into alphabetical order, and the items are
displayed using pixels corresponding to the position in the table (fast
interactive system).  This enables items to be selected with the cursor and
identified.

      A list of flags corresponding to the map list is also held.  The

flags enable some of the displayed items to be dropped interactively.

      The flags are usually set to items in the attribute files:

      The options are:

      -  names in attribute file (single variate)
      -  common to two attribute files (bivariate)
      -  names in two attribute files (zones and lines or sites)
      -  names for ranges of classes
      -  names in quantisation lists

      Items can be added or deleted by selecting them with the cursor or
typing the name.

      The PC version of OzGIS can display up to 500 items.  When
the number of display items (plus standard features) is less than the
length of the hardware LUT (number of simultaneous colours) the system can
display the results of quantising zone attribute data extremely rapidly by
changing the colours.  When the number of items is too large the system has
to revert to displaying each zone by polygon fill.

 12. 0. 3 Quantised Zones
          ---------------

      Up to 10 sets of zones files can be displayed on defined regions.
Adjacent files will automatically join.  GKS clips the polygons to the
edges of the region viewports.  Where regions overlap, the zones of the
last one to be displayed will overwrite the displayed data underneath.

      Zones that are not in the map list are not displayed.

      When the system operates in fast interactive mode the zones are
displayed once and the colours changed for the quantisation results.  In
polygon fill mode the zones are displayed every time attribute data are
quantised using fill (colour, pattern or hatch) for the appropriate
classes.

      Note that OzGIS expects overwriting to occur.  Hence display of
polygons on top of others is not successful using hatching on plotters,
so OzGIS handles polygons in a special way for this case.

                                                                      47

 12. 0. 4 Quantised lines
          ---------------

      Up to 10 sets of lines can be displayed on regions.  GKS clips lines
to region viewports.

      Lines that are not in the map list are not displayed.

      Each file is assigned to a different line, and is displayed in that
line colour.  Four different lines are available.  The results of the
quantisation are displayed by using different line types.

      The attribute data can be quantised into up to four classes, so four
line types are used.  The line files are assigned to the four available
lines according to overall classification when they are defined (e.g.
roads, railway tracks and rivers).

 12. 0. 5 Quantised sites
          ---------------

      Up to 10 files can be displayed on regions.

      Sites that are not in the map list or are outside the region window
are not displayed.

      Each file is assigned to a different marker and is displayed in that
marker's colour and background colour.  Four different markers are
available.  The results of the quantisation are displayed as different
sized markers.  When operating in fast interactive mode, the markers are
displayed in bit planes so they can be rapidly cleared.

      The attribute data can be quantised into up to four classes so four
different marker sizes are used.  The files are assigned to the four
available markers according to overall classification (e.g. owners of banks
at the sites).

 12. 0. 6 Line Overlays
          -------------

      The segments from up to 10 geographic files can be displayed as
overlays on map regions.  Each file is assigned to a region and one of four
available lines and is displayed as a solid line in that line's colour.
GKS clips the lines to the region's viewport.

 12. 0. 7 Polygon underlays
          -----------------

      The polygons from up to 10 geographic files can be displayed as
underlays on map regions.  Each file is assigned to a region and one of eight
available polygon colours.

 12. 0. 8 Marker Overlays
          ---------------

      The points from up to 10 geographic files can be used to display
markers at points in regions.  Each file is assigned to a region and to one

                                                                      48
of four available markers.  Markers are not displayed for points outside
the region's window.

 12. 0. 9 Name Overlays
          -------------

      The  points from up to 10 geographic files can be used to display
names at points in regions.  Each site file is assigned to a region and to
one of four available types of text.  Names are not displayed for points
outside the region's window.

 12. 0.10 Map Modification
          ----------------

      The window and viewport of a map region can be modified by selecting
a new one with the cursors.

      Files displayed for quantisation can be deleted from regions, unless
the only one of that type.

                                                                      49
                   13.  MAP ANALYSIS
                       =============


 13. 0. 1 Map Reports
          -----------


      An option is available to write a full map report (giving details of
the displayed items, their attribute values and class numbers) on the line
printer file OZGIS.OUT


 13. 0. 2 Attribute Data Statistics
          -------------------------


      The statistics of displayed attributes can be computed and printed
under user control.

      The following stastics are computed for a simple attribute:

      -  minimum value
      -  maximum value
      -  mean value
      -  median value
      -  standard deviation
      -  skewness
      -  kurtosis

      For pairs of attributes (bi-variate displays) the above statistics
are computed for each attribute, as well as

      -  correlation coefficient
and   -  regression polynomial coefficients (to order 3).

      These values can be printed on the user's terminal or the line
printer file OZGIS.OUT


 13. 0. 3 Map Interrogation
          -----------------


      When a map has been displayed, it is possible to interrogate the map
data interactively.

      The details generated by interrogation are the names of the zones,
lines or sites, the values of the displayed attributes (one value for
single variate displays, and two for bivariate) and their assigned class
number.  The options for interrogation are:


   (a)  class number range

        -  items (zones, lines or sites)
 within a specified range of class numbers.

                                                                      50

   (b)  single item identification

        -  zone line or site selected by entering its name at the keyboard.

   (c)  set identification

        -  items selected by a names file, items in map, or items in
           quantisation lists.

   (d)  Lists

        -  The names of all the displayed items are held in one list.
           Each attribute stream has an associated list of items that are
           being quantised.

   (e)  Interactive selection

        -  The "box cursor" can be used to describe a rectangular region to
           select items.  The selection of zones and lines is either by
           all minimum bounding rectangles (MBR) of the items that fall
           completely within the cursor window or MBRs that intersect
           the window.  Sites (and zone centroids) are selected by points
           that lie inside the window.


                                                                      51
                   14. OzEnter DATA ENTRY
                       ==================


 14. 1 Introduction
       ------------


Most data are entered into OzGIS as external data files. Examples are Census
data and Census digitised boundaries. These files come from Census Bureaux,
Mapping agencies, data supply companies or your own data-base systems.
Some data can be prepared or modified with word processors or spreadsheets.

This chapter describes the formats of external data files required by
OzGIS and shows how to enter the example file provided with the system.

The files are entered into the system via the OzEnter program which checks the
data and writes them to internal files.

All data files must have names that finish with the extension DAT.
e.g. LONDON.DAT, SALES.DAT

Often data files will need further processing by the OzData program before used
for mapping e.g. attribute data may need manipulating by arithmetic expressions
geographic line segments may need thinning and forming into polygons.

Future versions of the OzGIS system may have incompatible internal file formats
so always keep important data files.

The system comes with many of the system files already entered e.g. device
files. The data files are also provided.

 14. 2 Demonstration Files
       -------------------

The OzGIS system is supplied with a complete set of sample external
data files so that the user can become familiar with the system.  These
files can be inspected to clarify the file formats.

The files are usually in the directory \OZDEMO

 14. 3 Example geographic and attribute data
       -------------------------------------

Generally there will be two data files for each map; a file that describes the
map boundaries and another for attribute data. The example files are:

1. Far East Asia

Attribute file - FEA-A
Geographic file- FEA-G

These files have already been input in the demonstration chapter.

2. Lowe electorate (Sydney)

Attribute files- LOWE-A1 and LOWE-A2

                                                                      52
Geographic files- LOWE-G (zones), LOWE-S1, LOWE-S2 (sites)

3. Australia

Attribute file - OZ-A
Geographic file- OZ-G

These files are already entered (supplied with the system).

 14. 4 Example device files
       --------------------

The characteristics of devices and the appearance of maps are given by display
files. Data files are provided for all the device files supplied with the
system. There are two sets for 16 and 256 colour video boards, and also sets
for hatching and colour simulation on plotters etc.

Files are already entered on the system and have already been used.

 14. 5 Marker data files
       -----------------

These have already been entered, and are supplied with the system. They are
circle, diamond, hbar, nabla, plus, square, triangle, vbar. (You can of cource
have your own markers).


 14. 6 Colour names data (no longer used)
       ----------------------------------

A colour names file X11-BGR.DAT is supplied and has probably already been
entered as the default.

The colour names file can be entered as:

Type ozenter to run the data entry program
select the option to enter a colour names file
give the name of the data file as X11-BGR
give the output file name as DEFAULT
type F10 to exit

                                                                      53
                   15. OzData DATA PREPARATION
                       =======================

The raw data are input to the system using the OzEnter program. However, the
data often need further processing. Also, some data needed within the system
cannot be specified as data files and need to be prepared.

These facilities are provided by the OzData program.

 15. 1 Attribute Files
       ---------------

   A new attribute file can be generated from an attribute file and a
   combine file.  The combine file defines new zones (or site catchments)
   in terms of the names referenced by the attribute file.

   Attributes can also be derived from existing attributes by applying
   arithmetic operations to the attribute values.

   Attributes are identified by the character # followed by a number,
   indicating the sequential position of the attribute on the input file
   (e.g. #10 represents the tenth attribute).  An example of an expression
   to form a composite attribute is:

                 (#1+#2)/2 > 0 < 1000

   This creates a new attribute whose values are half the sum of the values
   from the first and second attributes on the input file.  Any valid
   arithmetic expression is acceptable.  The output values are limited to
   the given range.

   Functions available are:-

      LOG10  :  common logarithm
      SQRT   :  square root
      ABS    :  absolute value
      EXP    :  exponential
      SIN    :  sine
      COS    :  cosine

   Functions removed from the PC version are:

      LOG    :  natural logarithm
      AINT   :  truncation
      TAN    :  tangent
      ATAN   :  arc tangent
      SINH   :  hyperbolic sine
      COSH   :  hyperbolic cosine

   Pi is referred to as PI.

   Operators are:

   +  addition
   -  subtraction
   *  multiplication
   /  division

                                                                      54
   >  greater than or equal to
   <  less than or equal to

   Expressions are evaluated left to right and have a limit of 70
   characters.  Parentheses should be used to ensure there are no
   ambiguities.

   The user must give a 30 character attribute description and 10 character
   units description for each new attribute that is generated.


 15. 2 Geographic Files
       ----------------

Geographic files can be subset (windowed) on the basis of a
list of required display items (zones, sites, lines).
      - items in a names file
      - items in an attribute file
      - items within a window selected with the cursor from a displayed file

The line segments can be simplified to reduce the number of points that
have to be processed.  This is used to speed up display where the
resolution of the digitised data are higher that that needed for display
terminals.

Line segments that form polygons can be joined together into long segments.
Where many short segments are used this process, in conjunction with
simplification, can sustantially reduce the disk storage required and speed
processing.

The zones in a geographic file can be amalgamated according to a combine
file to generate a new geographic file.  The new file contains the new
zones.  The same combine file can be used to generate attribute data for
the same new zones.

 15. 3 Palette Files (Removed from system)
       -----------------------------------

Palettes are generated by selecting colours for the elements of a
palette shown on the screen.  The colours can be selected in the
following ways:

      -  by entering blue, green and red values.

      -  by reference to another palette

      -  by reference to a colour names file

      -  by reference to a colour cross-section displayed in the map area
         of the screen.

After colour selection, the palette can be saved as a file.

   An existing palette file can be modified to produce a new file, by
   displaying it and adding or deleting elements.

                                                                      55

 15. 4 Colour Names Files  (Removed from system)
       -----------------------------------------

   Colour names files are generated by typing in a name and then selecting
   the corresponding colour in the ways described above for selecting
   colours for palettes.  An existing colour names file can be modified.

 15. 5  Names Files
       ------------

Names files give lists of items (zones, sites,lines) that are to be processed.
These lists can be generated from other types of files. These options are
particularly useful when the names files are to be modified.

 15. 6  Output to Data Files
       ---------------------

Options are provided to output internal files as data files so they can be
modified with word-processors for further processing.

Names files can be editted to change the lists of items used for processing.

Attribute files can be output in simple database format.

Combine files can be modified as part of the definition of territories and
sites.

Attribute templates can be generated for preparation of attribute files with
a word-processor.

                                                                      56
                   16. OzZone BUILDING ZONES FROM SEGMENTS
                       ===================================


 16. 1 Use
       ---

Zone boundary data can be supplied either as the complete set of points for the
outsides of each polygon or as the line segments that make up the boundaries.
Most segments will be common to two polygons so only about half the number of
points are required. The segment form also allows zones to amalgamated into
larger zones (by dropping internal segments) and to be thinned (by dropping
excess points).

The segments form is preferred to polygon formats.

The program takes line segments and joins the ends together to form polygons.
The names of the zones on each side of the segments are used to derive the zone
names.

Complex polygons are handled. Zones can be made up of many polygons, both
disjoint polygons and polygons within polygons. The display order of the
polygons are calculated so e.g islands within lakes within zones all appear.

The OzZone program has been implemented as a separate program to provide
maximum capacity on the PC.

It is usual to line simplify (thin) the segments before building as many
digitised boundary files (e.g. census) are at a much higher resolution than
require for the display. Joining of line segments and further thinning may
follow.

The algorithm assumes that the segments have been produced on a proper
digitising system and are correct e.g. it is assumed that end-points meet and
the segments do not cross. Problems such as repeated segments, missing segments
etc may cause problems. Ensure you use the program with trace turned on. If
necessary turn on debug and look at the OZGIS.OUT file.

Use the file interrogation option to find the statistics on the geographic file
e.g. the number of zones.

OzData can be used to generate a prototype attribute file (simple format) from
the zones in the geographics file and hence get some test data that can be
entered via OzEnter to form an attribute file. Displaying both files with
OzCensus will allow the file to be checked.


 16. 2 Example
       -------

The procedure can be demonstrated with any of the geographic data files:

Use OzEnter to input the standard geographic file LOWE-G and give it name
TEMP1.

Start OzData, select geographic files and then line simplification. Input file
TEMP1 and output the new one as TEMP2. Simplify according to the size of the

                                                                      57
final map on the screen e.g. give a value of 100 to throw away a lot of the
data points.

Now use OzZone to input TEMP2 and output it as TEMP3.

Finally use OzGIS to display the result (using attribute file LOWE1).

                                                                      58
                   17. MAP PROJECTIONS (under development)
                       ===================================


 17. 1 Introduction
       ------------

OzGIS is a program is that will process a geographic file to form a new
geographic file converting either from (Longitude,Latitude) to a projection
or in the reverse direction.

You will have to have a basic knowledge of the projection you want to use
e.g. that AMG is UTM with the Australian Spheroid and a false origin
(500000,10000000).

OzProj is based on public domain software from USGS.


 17. 2 Precision
       ---------

Vertices are stored in single precision in OzGIS (there is not
enough memory on the PC to do anything else). This means an accuracy of
seven digits, so some values may not be accurate e.g. UTM may be a few metres
out.  If more precise values are required, you may have to define your own false

 17. 3 Latitude / longitude
       --------------------

Latitude / longitude data must be given with units degrees.

Latitudes are negative in the Southern hemisphere.

Usual value ranges are:
Longitude -180 to +180
Latitude  -90  to +90

Note that the X value in data files is the longitude.

examples: (-100.0,50.0) i.e. longitude -100, latitude 50
          (145.0, -42.0) a point in Tasmania

 17. 4 Projections
       -----------

Twenty projections are supported:

Albers Conical Egual Area
Azimuthal equidistant
Equidistant Conic
Equirectangular
General Vertical Near-side Perspective
Gnomic
Lambert Conformal Conic
Lambert Azimuthal Equal Area
Mercator
Miller Cylindrical

                                                                      59
Oblique Mercator (Hotine)
Orthographic
Polar Stereographic
Polyconic
Stereographic
Transverse Mercator
Sinusoidal
State Plane (USA)
Universal Transverse Mercator
Van der Grinten

 17. 5 Ellipsoids
       ----------

Several spheroids are available. The default is Clarke 1866.

MERIT 1983
GRS 1980(IUGG, 1980)
IAU 1976
Airy 1830
Australian Natl, S. Amer., IAU 64
GRS 67(IUGG 1967)
Bessel 1841
Clarke 1866
Clarke 1880 mod.
Everest 1830
Hough
International 1909 (Hayford)
Krassovsky, 1942
Mercury 1960
Modified Airy
Modified Everest
Modified Merc 1968
New International 1967
Southeast Asia
Walbeck
WGS 66
WGS 72
Sphere of 6370997 m

                                                                      60
                   18. HARDCOPY MAP PRODUCTION
                       =======================


 18. 1 Overview
       --------

Maps are designed with the interactive OzGIS program and saved as Saved display
files. These files are then read into the OzMap program and output on the
desired device or file. Attributes and quantisation can be changed in the usual
way to produce a series of maps.

Often maps will be previewed on the screen and then output to a plotter,
printer or file.

Hardcopy map production is limited by the capabilities of the SCIPLOT package.

SciPlot produces many graphic file types:

The Postscript file is an ASCII file that may be edited or sent directly to any
Postscript printer.

The Encapsulated Postscript file (EPS) and the Computer Graphics Metafile (CGM),
an ANSI standard format file, are files that should not be edited for they
contain binary information.  EPS and CGM files can be imported directly into
wordprocessors or other graphical products.

The HP pen plotter file (HPGL) is an ASCII file that can be edited or imported
into wordprocessors or other graphical products.

The WordPerfect file (WPG) is a binary file in WordPerfect's internal graphics
format.  WPG files are directly importable into the WordPerfect wordprocessor.

The SciPlot Graphics file is a file in SciPlot's own internal format and is
used solely as input to the VECTOR program.  This file is a binary file in very
compact format.  It contains the stream of vectors which represent the figures,
characters, etc. generated during the execution of the application program.
VECTOR processes this graphic file and arranges raw vectors in a direction of
paper motion order before display on dot matrix printers and laserjet printers.

For Apple LaserWriters, HP pen plotters, and other graphics devices that
support avector drawing commands directly, ordering is not required and VECTOR
immediately displays the vectors.

VECTOR's function is to provide a utility to register SciPlot's output on
plotting devices (dot matrix and laserjet printers) which cannot be supported
directly without requiring significant system resources.  VECTOR also provides
interactive preview of graphics files on the screen or bath processing at some
other time.


 18. 2 Device files
       ------------

Several device files are provided to control the appearence of maps on output
devices. These device files can also be used with OzGIS (they will need minor
modification for use with EGAs).

                                                                      61

You have to use device files that use hatching for polygon fill. The
configuration section explains the files available. Generally you need to use
hatching device files that have the same resolution as that used in OzGIS or
aspects and character sizes may not be suitable.

HATCHSV1   - provides polygon display using hatching.
HATCHBV1   - hatching for bivariate maps.
CSIMSV* and CSIMBV* - a series of device files that use the red, green and blue
plotter pens (or screen colours) to simulate the colour sequences; look at then
on the screen first to decide which ones to try.

The hatching device files can of course be modified to define other hatching
patterns.


 18. 3 VECTOR Program
       --------------


This program enables metafiles produced in the OzMap program to be output to a
variety of devices and files with such options as rotation and scaling.


VECTOR has two modes of operation, an interactive mode and a batch mode.
The batch mode processes command strings from a disk file.  The user can
include the command filename with the VECTOR command (eg. VECTOR
command.fil).  Alternatively, the user can wait until VECTOR issues a
prompt for the type of interaction desired.  The format of the command
file and a description of the VECTOR.CFG file follows:

VECTOR[d:][path][filename[.ext]] [/U]

[d:][path][filename[.ext]] [/U] - Process file which contains
filenames of graphics files to be processed in batch mode.  These
files will be processed one at a time and plotted on the designated
printer, plotter, or graphics crt device.  As a default, the
VECTOR.CFG file will be searched for a process filename.  When a
filename is specified on the VECTOR command line, the process
filename given in VECTOR.CFG file is totally ignored and replaced by
this new filename.

/U - This update option is used to override all parameters specified
in the VECTOR.CFG file. The option initiates an interactive dialog
with the user to obtain a new set of parameters for VECTOR. The user
is given the opportunity at the end of the dialog to update the
current VECTOR.CFG file with these new parameters.

VECTOR.CFG Configuration File.

The VECTOR.CFG configuration file contains a list of commands that
define VECTOR processing parameters. Each time VECTOR executes, it
reads and interprets this file. If the VECTOR.CFG file cannot be
located, VECTOR will interact with the user from the terminal to set
up these parameters.

Format of Configuration File Commands:


                                                                      62
Cmd    Option        Description

FILE   =CONS         -Get graphics filenames from console.
       =[d:][path][filename[.ext]]- Use this file as a process file
containing graphics filenames.

DEVICE =DOT          -Dot Matrix Printer
       =PEN          -HP Pen Plotter
       =JET          -HP LaserJet Printer
       =WRITER       -Apple LaserWriter Printer
       =CGA          -CGA Color Screen
       =EGA          -EGA Color Screen
       =VGA          -VGA Color Screen
       =HGA          -Hercules Monochrome Screen

PORT   =COM1         -Printer/Plotter on Primary Serial Port
       =COM2         -Printer/Plotter on Secondary Serial Port
       =LPT1         -Printer/Plotter on Primary Parallel Port
       =LPT2         -Printer/Plotter on Secondary Parallel Port

ANGL   =XXX.XX       -Rotation Angle (degrees)
XSCL   =XXX.XX       -X-Axis Scale Factor
YSCL   =XXX.XX       -Y-Axis Scale Factor
XOFS   =XXX.XX       -X-Axis Offset (inches)
YOFS   =XXX.XX       -Y-Axis Offset (inches)

WAIT   =ON           -Wait between Plot Frames
       =OFF          -Do not wait between Plot Frames

[When serial port is used for printer/plotter device, following
commands are valid]:

HAND   =SOFT         -Software Handshake (XON/XOFF)
       =HARD         -Hardware flow control on DSR line

MODE   =195          -Serial Port Mode Set Code, specified in
decimal format. 195 = (9600 baud, no parity,
1 stop bit, 8 bit characters)

- Mode Set Code Description -    [bits]

7     6    5  4     3       2          1       0
--Baud Rate-- -Parity-   -Stop Bits-  -Char Length-
000 -  110   00 - None 0  -    1      10  - 7 Bits
001 -  300   01 - Odd  1  -    2      11  - 8 Bits
010 -  600   11 - Even
011 - 1200
100 - 2400
101 - 4800
110 - 9600
111 -19200

[When dot matrix printer is used, following commands are valid]:

PINS   =9           -EPSON (MX-80,FX-80,FX-85,FX-850...)
       =24          -RPDON (LQ-800)

HRES   =HIGH        -High Horizontal Resolution

                                                                      63
       =LOW         -Low Horizontal

VRES   =HIGH         -High Vertical Resolution
       =LOW          -Low Vertical Resolution

- Printer Resolution Table -

Printer  Resolution   Vertical  Horizontal
9-Pin     LOW           72         120
9-Pin     HIGH          216         240*
24-Pin     LOW          180         180
24-Pin    HIGH          180         360
* 240 dot per inch resolution is not available on MX-80.

[When HP Pen plotter is used, following plotter initialization
command is valid]:

INIT   =ON           -Send handshake init sequence before plotting
       =OFF          -No handshake init sequence required

When a process file is specified, VECTOR will process multiple graphics
files in a batch mode. For the individual graphics file, VECTOR processes
one plot frame at a time, for each file may contain more than one plot
frame.  For dot matrix and HP LaserJet printers, VECTOR first sorts all
the vector records in a minimum Y order for one plot frame.  This sorting
is accomplished by creating an in-memory linked list directory of the
disk records for the frame.  VECTOR accesses the graphics file randomly,
bringing in only those records that contain vectors in the current
process window. These print devices restrict the processing to a paper
movement order. For HP Pen Plotters, Apple LaserWriters, and crt
displays, VECTOR can process the vectors directly without any sorting for
these devices support vector drawing commands.

An inherent difficulty in this sort of processing approach is the limit
imposed by the processor's memory size. There is an upper bound on the
size of the graphics plot that can be handled because the linked list
directory as well as a limited set of the vectors must be memory
resident.  The exact size limit is difficult to predict because it is a
function of the number of records in the file, the density of vectors per
processing window, and the amount of lengthy vectors that must be
remembered over many processing windows.  The VECTOR.OBJ file on the
distribution diskette supports 64KB of directory sort space.  If this is
not enough, a VECTOR.LRG file is included which supports 256KB of
directory sort space.  Please note that the use of the VECTOR.LRG object
file will significantly increase the size of the VECTOR.EXE file.

Features

The features incorporated in VECTOR are numerous.  Multiple plot frame
processing is automatic.  A graphics vector file may be accessed from any
disk.  Normal FORTRAN I/O is used to read the 128 byte binary records by
the direct access method.  The VECTOR program will respond to a
control-C/Break at any time during execution.  This will terminate the
current processing task, reset the printer to the top of form, and
request another task.  Statistics for each plot frame, as well as total
run statistics are displayed during the execution of VECTOR. For the dot
matrix type graphics printer, four basic resolutions are provided by
VECTOR depending on the type of printer attached.  A low resolution mode

                                                                      64
is supported to quickly review the plot with very limited definition.
This mode is useful for quick turn-around. The high resolution mode takes
much more time because of hardware constraints, but gives very
satisfactory results.  VECTOR also has an on-screen preview capability
which allows quick identification of graphics files.

Error Conditions:

During the execution of VECTOR, several error messages might be displayed
on the terminal.  The only message that is not serious has to do with a
premature termination of the programs that produced the graphics output
file. The message reads "Premature End-of-File at Record XXXX". It just
means that the graphics file was not terminated properly, but all the
graphics data is valid.

The second class of messages is serious and should not be ignored. The
messages are listed along with reasons.

"Error reading graphics file" - means that FORTRAN I/O was unable to read
the graphics file. The file should be recreated on another disk to
correct the error condition.

"File not in graphics format" - means that the speacified file is not in
SciPlot graphics format. Check to see if the filename is correct or was
produced by a current version of SciPlot.

"Graphics file too large for memory" - means that the graphics file
specified cannot be processed by VEACTOR due to inadequate memory sort
space.

"Too many vectors for memory" - means that number of vectors per
processing window is too dense. Try using the VECTOR.LRG object deck to
generate the VECTOR.EXE command file.


The VECTOR program supports IBM Graphics, IBM ProPrinters, EPSON MX-80,
FX-80 with GRAFTRAXPLUS, FX-85, FX-850, LQ-800 dot matrix printers
connected on an 8-bit parallel I/O interface.  All 8 bits are necessary
to register the full resolution of the graphics printers.  The resolution
obtained is a plot frame of (960,1920,2880) pixels over 8 inches in the
horizontal direction by (1800,2160) pixels over 10 inches in the vertical
direction. The feature of positioning (1/216th, 1/180th) of an inch is
used, giving a basic resolution of (120,240,360) by (180,216) pixels per
inch over a unit square of one inch on a side.  The IBM
Graphics/ProPrinter, and the EPSON FX-80,85,850 printers have twice the
resolution as that of the EPSON MX-80.  The hardware requires double
passes to absolutely register two dots in adjacent columns for this high
resolution mode.  This is the reason for the lengthy processing time in
this mode.

There is no paper positioning done by VECTOR. Therefore, the user must
position the paper before executing the VECTOR program.  This is done
purposefully to allow plots to be manually positioned.  It is possible to
imbed plots in full text with a careful alignment of the paper.

The HP Pen Plotter, the HP LaserJet, and the Apple LaserWriter are all
supported by VEACTOR to register the graphics files produced by SciPlot.


                                                                      65

 18. 4 Example
       -------

You start by displaying a map with OzGIS and adding any text etc. When it is
ready you save the map. There are two options for saved displays; either can be
used but when saved for hardcopy output the screen is not saved so takes less
disk space.

The OzMap program is then started.

The name of the saved map file is given and a HARDCOPY! device file chosen.
Use the default one.

Type F3 to display the map on the screen.

Now select a device - choose the printer metafile.

Type F3 to output the map to the file; give the file name e.g. phred.

Type F10 to exit OzMap.

Type VECTOR to execute the program.

Accept all default values (dot matrix printers) and give the Graphics file as
phred.hrd (note the file extension).

The map will be printed.

                                                                      66
                   19. OzTerr
                       ======

Usually territories are to be developed from base zones according to some
criterion;  e.g. Sales territories should all have similar sales potential;
e.g. School districts should have similar numbers of children.

The operations are as follows.

     A base map is displayed:  Usually this will be a standard geographic
     file (e.g. Melbourne postcodes).  Basic OzGIS facilities are used
     to subset files if non-standard regions are required.

     Specification of territories:  Each territory has a unique 10
     character name.  Zones are assigned off the screen with the cursor.
     Zones can be moved between territories and deleted.  Territories can
     be defined or deleted at any time.

     Specification of a base-map attribute file:  Territory attributes are
     continually calculated by adding the values for the base zones in each
     territory.  The derived values are quantised (usually sequential
     colour 121 class method), the territories coloured, and a legend and
     histogram of sorted values displayed.

     Zones can be shuffled according to the displayed territories attribute
     values to meet the assignment criteria  while watching the legend
     and histogram.

     When territory assignment is complete, the definition is output as a
     combine file.

OzData provides a facility for amalgamating attribute data
for a combine file.

     The combine file can be used to amalgamate the base map geographic
     file zones to produce a new geographic file, where the new zones are
     the territories.

     The new geographic file and attribute data can be mapped
     by OzGIS in the standard way.

     Territory assignment can be iterated by displaying the base map as
     before, but using the combine file to set the initial territory
     definition.  Similarly, if a basic territory assignment is know, it
     can be  input as a combine data file and used to start the process.

                                                                      67
                   20. OzCatch (NOT AVAILABLE YET)
                       ===========================


 20. 1 Introduction
       ------------

Modules have been developed for site selection
on a VAX using RAMTEK display systems.

This software has to be completely rewritten for the limited PC displays.

 20. 2  SITE CATCHMENTS
       ----------------

The system aims to provide facilities for analysis of sites for the
 definition of site locations and catchments, the
retrieval of data, development of models and display of results.

The base of the process is the catchment file.
A catchment file holds the definition of several sites.  The sites have
some common grouping (e.g. all part of the same retail chain) and all fit
on the same base map.

A typical analysis would involve several catchment files, e.g. several sets
of sites each for a different organisations( e.g. several sets, each
defined on different base maps to increase resolution. )

    Site definition is carried out for a current set of sites.  These
     sites can be modified and new sites defined.  A base map is always
     displayed and all the current sites must fit on the displayed map.

    Also defined for assistance
 are any other catchment files relevant to the analysis.
     Site symbols, names and catchments are displayed if they fit on the
     map.  These sites can not be modified.

A catchment file contains the following information for each site.

-    site name (10 characters)
-    site location
-    site symbol display location
-    site name display location
-    catchment contours (up to 5)
-    base zones and weights within catchment
-    type of zones.

A site analysis could be carried out as follows.

Phase 1 - Definition

Each catchment file has to be defined.

-    A base-map geographic file of suitable size is displayed.

-    An old catchment file may be read in for modification.


                                                                      68
-    Sites are defined by giving a name and location (cursor or typing lat
     long).  Initial catchment contours are given as circles.

-    The results are stored as a catchment file.

The zones list in the catchment file can now be output as anames file.

The names file is passed to OzData, attribute data are retrieved for the site
catchments, and some basic statistics calculated.  On the basis of
correlation coefficient and error levels for particular sites, the
modifications for site catchments are decided.

e.g.   there may be 2 or 3 base maps for Melbourne and
others for the country areas, each with different sites on them.

Phase II - Modification of Catchments

The site catchments (or positions) now have to be modified to obtain better
agreement with known results.

-    The base map is displayed again.  Other site catchment files and
     geographic overlays (e.g. roads) may also be displayed.  Note that the
     base map could be changed.

-    the sites are modified.  More contours may be added.  Contours may be
     replaced with circles of different radii or a replacement digitised.

-    Zones lists are re-calculated.

-    The new sites are processed by OzData again, and the process repeated
     if necessary.

For example,  the base maps could change, say to go from
postcodes to collection districts.  Contours would change to get a better
fit to the client's data.

Phase III - Zones

A base map is displayed and the contours overlayed.
The pixels within each contour polygon are counted and from the
total zone pixel counts and contour weights
a list of zones and weights for each site is generated
and stored in the catchment file.

The user has to make sure that the base map extends past the
catchment.
Note that any type of zones can be used as the contours are
stored as lat-long points.

Phase IV - Display Preparation

A base map is displayed that is to be used for the final maps, and current
catchment file displayed.  All the catchment files are displayed -
contours, symbols and site names.

Symbols and names in the current catchment file are repositioned with the
cursor if they conflict with those from other files.
Lines are displayed between the symbol and true positions.

                                                                      69

A new catchment file is generated.

An combine file is generated for retrieval of attribute data for all site
names.

A base map is displayed and the catchment files displayed that are to have
the same symbol on the maps.

A geographic file is generated for site symbol display.

A geographic file to display the lines between the offset
symbol locations and site locations is generated.
This file also contains points for site name display.

For example,  a base map for the part of Victoria required
would be subset from a Victorian postcode map.  All the catchment files are
displayed and names and symbols moved for the locations where there are two
close sites.

Phase V - Map Production

A names file is generated from the combine file for
all sites that are to be displayed.

-    Data are retrieved from OzData for the names file.

-    A map is displayed for either just sites, or sites on quantised map
     zones.

     If there are several sets of sites each file
 is added and possibly assigned
     to a different symbol.
Note that symbol 1 is the top bit plane, symbol 2 the
next down etc.

Standard geographic overlays can be added from the geographic
files that were generated; sites names, symbols, lines
between symbol and true locations.

-    Other geographic overlays, diagrams etc are added.

For example,  a map could be displayed by using the Victorian
postcode map as a base with postcode attributes, and displaying symbols at
sites using attributes calculated by OzData.  If potential sites are being
evaluated, they would be in different geographic files and different
symbols would be used.


                                                                      70
                     A. DATA SOURCES
                       ============


  A. 1 Australia
      ---------


  A. 1. 1 AUSLIG data
          -----------

The Australian Land Information Group in Canberra can supply
the boundaries of the Collection Districts for the 1986 Census.

Data are available for each state for:-
      - collection districts
      - postcodes
      - Local Government Areas
      - Statistical divisions
      - etc

Ozenter can process the AUSLIG segments data to produce the OzGIS segments,
which can then be formed into polygons with OzZone (to reflect
the structure of the data e.g. which polygons are inside others).

The data are extremely detailed, so large files are involved. Hence subsetting,
segment joining and line simplification are usually used.

All data are projection code 1 = latitude-longitude, units degrees.

Make sure you get census boundaries in SEGMENTS format on floppy disk.

Other map data are available, but need reformatting for use with OzGIS e.g.
names file.

Unfortunately, government policy of cost recovery means that AUSLIG data are
expensive.

Several publications are available.

Contact:

AUSLIG SALES (Digital Data), PO Box 2, Belconnen ACT 2616.
Phone [phone]  Fax [phone]

  A. 1. 2 Australian Bureau of Statistics
          -------------------------------

The ABS collects and disseminates enormous volumes of statistics, some of which
is available on floppy disk and CD ROM for mapping.

The major data source is the Census of Population and Housing - by far the most
extensive source of demographic data available in Australia.

The ABS will supply data on floppy disk. Data output from the GeoStats product
in LAMM format is supported.


                                                                      71
The ABS will supply boundary data for the 1991 Census.

Many publications describing the data are available.

Contact:

Information Services,
Australian Bureau of Statistics,
PO Box 10, Belconnen, ACT 2616.
Phone [phone], or 252 6007.

or any ABS state office.

  A. 2 New Zealand
      -----------

The Department of Statistics have a product SAM (Socio-economic Area Mapping)
and will supply data suitable for mapping.

Contact their Information Consultancy Group first.

Offices are in Auckland, Wellington, Christcurch and Dunedin.

The boundary data are digitised and maintained on a GeoVision system so it is
suggested that they be obtained in Gina format.  The data are prepared by the
Department of Survey and Land Information - you could contact them directly.

Population Census data and other attribute data are available in comma
delimited formats.

  A. 3 United Kingdom
      --------------

The various agencies are in the process of generating digitised boundary data,
and there are some private efforts.

Contact:
The Office of Population Censuses and Surveys (OPCS),
St Catherines House,
10 Kingsway London
Phone [phone]

or:

Customer Services,
General Register Office,
Ladywell House,
Edinburgh.
Phone [phone]

  A. 4 Canada
      ------

Statistics Canada has not answered our letters or FAX.

                                                                      72

  A. 5 USA
      ---

The Advanced Technology Group (ATG) market PC systems to extract Census and
Tiger boundary data from CDrom.

Contact: ATG Inc.,
205 Regency Executive Park,
Suite 306,
Charlotte,
NC 28217.    Phone [phone]


The US Census Bureau produce a large amount of boundary and attribute data.
They have a product called TIGER/boundaries for PC mapping.

We obtained some information early in 1991, but a subsequent letter and a FAX
offering to buy test data have not been answered.

  A. 6 Others
      ------

Attemps to obtain other data from other suppliers has so far failed. The best
we get is a heap of glossies. Questions we ask in our letters are ignored.
Requests for test data are either greeted with paranoia or are ignored.

Hence we request users with data to send us samples, with documentation so we
can support the data in the system.

                                                                      73
                     B. MAP DATA FORMATS
                       ================


  B. 1 Introduction
      ------------

The OzGIS system was designed to accept data from external sources.

These data may be supplied in standard GIS formats that are supported by the
system or may have to be reformatted into one of the system formats before use.

  B. 2 Data Format
      -----------

The data files have been designed with a simple format which can be easily
generated on computer systems.

Most data are held as character files so that they can be generated by
programs with, for example, database system export procedures, formatted
FORTRAN write statements, or by a text editor.  The record lengths are up to
80 bytes long.

Each file starts with a comment record of up to 80 characters, which should
be used to hold a meaningful description of the file.  The OzGIS system
will display this comment when data files are interrogated, so it is in the
users' interest to make the comments meaningful.  This record must contain
at least one non-blank character.

Data values are entered in record fields that are multiples of 10 bytes.
The following computer restrictions apply:

     -  Character data (e.g. zone names) are usually left justified and
        blank filled.  Sorted character strings must conform to the ASCII
        collating sequence.

     -  All real values (i.e. with decimal points) can be placed anywhere
        in the 10 byte fields, but the decimal points must be included.

     -  All integer values must be right justified in the 10 byte fields.
        Their values must be within the range the computer is capable of
        handling.

The maximum numbers of some data items that can be handled
are system parameters. Refer to theaAppendix.

  B. 2. 1 Description of File Formats
          ---------------------------

The formats for describing the data files in the following sections are
similar.

The number of bytes in the field is given at the start of the line.  If
there are several values in a format, this condition is indicated
differently (e.g. 8 x 10 implies eight fields of 10 bytes).

The information on the next line is the type of data in a field:

                                                                      74

     byte     = character
     real     = number containing a decimal point
     integer  = number without a decimal point


  B. 3 Format of attribute files
      -------------------------


  B. 3. 1 General
          -------

Attribute data are often obtained from Census Bureaux. These data are seldom
what is required, so will need processing by OzData before use.

Data often need normalising to allow for the differences in zone sizes. This is
done by arithmetic operations where new attributes are derived by dividing by
total population, area etc.

Also, data often need amalgamation e.g. census age groups to get the required
group.

  B. 3. 2 Standard format
          ---------------

Attribute files contain the attribute value of each zone or line or site
for a number of attributes.  The names must correspond to those defined in
a geographic file.

The attribute description is used by OzGIS as a heading in a map
displaying the attribute.  The units description is used by OzGIS as a
heading to the class values in the map legend.

For efficient use of the system and to facilitate disc file management,
files should contain as many attributes as possible (to avoid having
separate files for each attribute).

Attribute files will usually be prepared by special programs which extract
data from a data-base and convert attribute values into the OzGIS
format.

     Comment Record:
     80       byte      comment describing the data

     Header Record:
     10       integer   number of attributes
     10       integer   number of names
     10       real      value used to indicate missing data

     Name Records:
     8 x 10   byte      names, sorted into ascending order

Sets of records follow to define the attributes:-

     Definition Record:
     30       byte      attribute description
     10       byte      units description

                                                                      75

     Values Records:
     8 x 10   real      attribute values for zones, lines or sites in name
                        order


  B. 3. 3 Sample attribute file DEMOATTR.DAT
          ----------------------------------

DEMOATTR.DAT   - ATTRIBUTES FOR SIMPLE 3 ZONE TEST MAP
         5         6     -9.9
ABCDEFGHIJZONE 1    ZONE 2    ZONE 3    ZONE 4    ZONE Z
FIRST STATISTIC               FIRST UNITS
       1.0       2.0       3.0       4.0       5.0       6.0
SECOND STAT                   SECOND UNITS
     100.0     200.0      -9.9     400.0     500.0     600.0
THIRD STAT                    3RD UNITS
       0.1       0.9       0.3       0.7       0.1       0.8
FOURTH STATS                  4TH UNIT
       1.0       2.0       3.0       3.0       2.5       1.5
FIFTH STAT                    5TH UNIT
       9.0       6.0       3.0       2.0       6.0       8.0

  B. 3. 4 Simple Attribute format (database format)
          -----------------------------------------


Many data retrieval systems (e.g. ORACLE,SAS) produce attribute data in a form
where for each attribute the names and their values are given.

This table format is supported in OzGIS although there are some restrictions
on its use.  The list of names is obtained from the first attribute; hence
no new names can occur in following attributes (although names may be
missing).  A set of data records for an attribute is assumed to finish (and
the next set start) when the attribute description changes.

     Comment record:
     80      byte       Comment describing the data

     Data records:
     10      byte       name
     10      real       value
     30      byte       attribute description
     10      byte       attribute units


  B. 3. 5 Sample simple attribute file DEMOSASA.DAT
          -----------------------------------------

SIMPLE FORMAT ATTRIBUTE FILE - DEMOSASA.DAT
TOP            1.0   DESCRIPTION A                 UNITS A
SQUARE         2.0   DESCRIPTION A                 UNITS A
DIAMOND        3.0   DESCRIPTION A                 UNITS A
TRIANGLE       4.0   DESCRIPTION A                 UNITS A
TOP            1.0   DESCRIPTION B                 UNITS B
DIAMOND        3.0   DESCRIPTION B                 UNITS B
SQUARE         2.0   DESCRIPTION B                 UNITS B
TRIANGLE       4.0   DESCRIPTION B                 UNITS B

                                                                      76
TOP            1.0   DESCRIPTION C                 UNITS C
SQUARE         2.0   DESCRIPTION C                 UNITS C
DIAMOND        3.0   DESCRIPTION C                 UNITS C
TRIANGLE       4.0   DESCRIPTION C                 UNITS C
TOP            1.0   DESCRIPTION D                 UNITS D
TRIANGLE       4.0   DESCRIPTION D                 UNITS D
DIAMOND        3.0   DESCRIPTION D                 UNITS D
DIAMOND        3.0   DESCRIPTION E                 UNITS E
TRIANGLE       4.0   DESCRIPTION E                 UNITS E


  B. 3. 6 Spreadsheet data formats
          ------------------------


Data from spreadsheets can be input in Lotus 1-2-3 format.

The spreadsheet must be set up in a fixed format:

The data values are in a matrix with the values for the zones (or sites or
lines) in columns and the different attributes across in the rows.
Values can be missing and can be integer or floating point.

The first column must contain labels which are the 10 character zone (site etc)
names, beginning at row 3. These must be SORTED in ascending order.

The top row contains labels that are the (up to) 30 character attribute
descriptions starting at column 2.

The second row is the 10 character attribute descriptions.

e.g. the file DEMO123.dat can be read into the spreadsheet. It should look
like:

            POPULATION GROWTH   SALES
            NUMBER              $
ABBOTSFORD                 7418      237
BURWOOD E                  9925      955
CONCORD                    8984      202
CROYDON N                  9369      298
CROYDON W                   735
FIVE DOCK                  9903      716
HABERFIELD                           727
HOMEBUSH                   6631      704
HUDSONPARK                 4668       71
MORTLAKE                   1725      198
STRATHFIELD                6285      663
YARALLA                    9875      516

  B. 3. 7 LAMM format
          -----------

The LAMM package was developed at the CSIRO Division of Building Research. The
format is supported as it is the only suitable format for mapping available in
the Australian Bureau of Statistics GEOSTATS system.

An example file is DEMOLAMM:


                                                                      77
12,8
MALES 35 - 44 (81)
MALES 35 - 44 (86)
MALES - UNEMPLOYED (76)
MALES - UNEMPLOYED (81)
MALES - UNEMPLOYED (86)
INCOME MALES $18001-$26000 (76)
INCOME MALES $18001-$26000 (81)
INCOME MALES $18001-$26000 (86)
'ABBOTSFORD'   69 0 14 27 48 0 51 55
'BURWOOD E'    223 0 48 134 89 0 218 397
'CONCORD'      102 0 5 12 29 0 109 197
'CROYDON N'    161 0 27 50 53 0 156 284
'CROYDON W'    180 0 24 36 76 0 307 241
'FIVE DOCK'    50 0 20 2 0 0 19 11
'HABERFIELD'   126 0 28 20 20 0 208 185
'HOMEBUSH'     114 0 26 51 37 0 165 212
'HUDSONPARK'   243 0 65 99 65 0 231 385
'MORTLAKE'     0 0 0 0 2 0 0 113
'STRATHFIELD'  100 0 4 7 10 0 74 70
'YARALLA'      7 0 16 2 0 0 4 3


  B. 3. 8 Comma delimited format
          ----------------------

The comma delimited format consists of a set of records:

Each record has a series of values separated by commas.

The first value is the item (zone,line or site) name and there follows one
number for each attribute.


The comma delimitted form is seriously deficient in that it contains no
attribute descriptions.

Processing this format would require asking the user to type in the description
for each attribute which is time consuming and there is always the danger that
an attribute could be incorrectly labelled.

Either:

read the data into a spreadsheet

Or:

convert into LAMM format with a word processor.

The file DEMOCOMD.DAT looks like:

2727400,115,114,105,6
2727800,77,75,63,29
PHRED,85,81,66,36
NEW YORK,5,6,3,3
2728200,27,27,21,12
2728300,74,72,63,34
.

                                                                      78
.
.
.
2739100,13,12,12,5
2739200,2,0,3,1


  B. 3. 9 Other attribute data formats
          ----------------------------

Other formats will be supported as required.

We will support any formats for major data suppliers, but you must send sample
data and documentation.

We will also attempt to support file formats from other packages.

  B. 4 Standard format of geographic files
      -----------------------------------


  B. 4. 1 General Information
          -------------------

The standard data format reflects the internal topological file structure.

In practice, a complete data file is seldom available. It is more common to
bring in just points (as a map and points partition) or lines (as a map and
segments partition). Zones are usually formed from the segements with the
OzZone program.

Coordinates are usually given either in degrees (for lat,long) or in metres /
feet for UTM.

  B. 4. 2 Structure of data
          -----------------

Geographic files contain several partitions.  The first must be the map
partition, and can be followed by at most one of each of zones, polygons,
lines, segments and points partitions.

Each partition is preceded by a type record, which is one of MAP, ZONES,
POLYGONS, LINES or POINTS; for example, a zones file must  have the
following structure:

     Comment record
     MAP
     map records
     POLYGONS
     polygon records
     ZONES
     zone records
     SEGMENTS
     segment records

Different partitions are present (the MAP partition is always first)
 according to the type of data:-


                                                                      79
Files which describe zones have a ZONES partition to define
the zones, a POLYGONS partion to give the polygons that
bound each zone (including lakes and islands), and a SEGMENTS partition
to define the coordinate points that draw the segments along the
polygon boundaries.

Sites files have a POINTS partition to give the site names
and locations.

Lines files have a LINES partition to define the line names
and a SEGMENTS partion to define the coordinate points in the
segments that make up the lines.

Line overlays are defined by SEGMENTS partitions.

Marker and name overlays are defined by POINTS partitions.

Coordinate data should be entered in standard units.  Coordinate pairs are
always in the order (X,Y) (e.g. (Longitude, Latitude)).  Note that latitude
must be entered as a negative number in the Southern Hemisphere.

Data entered in latitude-longitude projection with units of degrees can be
converted to other projections.
Feature codes may be included to give a classification of geographic items.
e.g. segments may be classified as different types of roads.

All geographic regions (windows) are given in actual coordinate values in
the order:  X-minimum, X-maximum, Y-minimum, Y-maximum.

  B. 4. 3 Internal Data
          -------------

The geographic data are held internally as a word-addressable
random access disk file.
The file structure reflects the data structure with the necessary
indexing etc for processing.
Additional data are also generated for efficient processing:-

Polygons are held in display order so the map zones can be
rapidly displayed.

 A POINTS partition is generated internally by OzGIS
for the centroids of the zone polygons.
This enables markers or zone names to be overlayed over
a zones map, and for the points to be displayed as sites
where the site names are the zone names.

Lists of names are also generated for zones, lines or sites
for rapid retrieval.

  B. 4. 4 Comment Record
          --------------


     80      byte       comment describing the data


                                                                      80

  B. 4. 5 Map Partition
          -------------


This partition contains general information about the file (map) and must
be the first partition.

     Type Record:
     3        byte      partition header = MAP

     Window Record:
     4 x 10  real       the region covered by the file

     Projection Record:
     10 integer         Map projection code
                        0=none, 1=lat-long degrees
     10       integer   type of zones (optional)


  B. 4. 6 Zones Partition
          ---------------


This partition defines the zones in the geographic region.

Each zone is defined by one or more polygons.  A zone may consist of a
polygon, several separated polygons, polygons with interior polygons of
other zones, etc.

If a zones partition is present, a polygons partition with the referenced
must be given.

The partition may be used as a polygon underlay and feature codes may be used
to give a classification e.g. the polygons may be different soil types.

     Type Record:
     5        byte      partition header = ZONES

     Definition Record:
     10       integer   number of zones
     10       integer   number of feature codes

     Feature code Records (if required):
     8 x 10  integer    feature codes

     Zone Records:
     10       byte      zone name, usually left justified, blank filled
     10       integer   number of polygons in the zone

     Polygon Records:
     8 x 10  integer    identifying numbers of the polygons

                                                                      81

  B. 4. 7 Line Partition
          --------------


The partition defines networks of lines (e.g. roads, rivers).  Each network
has a name and is specified in terms of line segments.The name can be used
to apply quantised attribute data.

Type record:
     5       byte       partition Leader = LINES

Header record:
     10      integer    number of lines


Line record:
     10      byte       line name, usually left justified, blank
                        filled
     10      integer    number of segments forming the line


Region Record:
     4x10    real       line limits (window)
                        X minimum, X-maximum, Y-minimum, Y-maximum)

Segments Records:
     8x10    integer    the identifying numbers of the line segments.

  B. 4. 8 Polygons Partition
          ------------------


A polygon defines an enclosed geographic area.  Each polygon is specified
in terms of the line segments which constitute its boundary.  If a zones
partition is given, every polygon referenced by the zones must be defined.

The centroid or internal point of a polygon is be used by OzGIS to
locate text (zone names) or graphic symbols;
a points partition is generated.

Type Record:
     8        byte      partition header = POLYGONS

     Header Record:
     10       integer   number of polygons

A set of records follow for each polygon:-

     Definition Record:
     10       integer   polygon identification number
     10       byte      name of zone enclosed by polygon
     10       integer   number of lines forming the polygon boundary
     10       integer   level of polygon for display using
                        polygon fill 0=standard, 1=lakes, 2=islands in
                        lakes etc. (range 0-5)


                                                                      82
     Region Record:
     4 x 10   real      polygon limits (window)
                        (X-minimum, X-maximum, Y-minimum, Y-maximum)

     2 x 10   real      centroid or labelling point (X,Y) in the polygon
                        (set to centre of window if not given)
     10       real      area of polygon
                        (calculated if not given)

     Segments Records:
     8 x 10   integer   the identifying numbers of the segments + ve if
                        segment is clockwise, -ve if anticlockwise.

  B. 4. 9 Segments Partition
          ------------------

Line segments are defined by a set of points connected by straight lines.

Segments may define the boundaries of zones, define line
networks, or line overlays.

When a segment is a boundary segment of a polygon, it can be the boundary
of at most two polygons.
  In other words, the polygons must be a unique tessellation of the geographic r

When the segments define polygon boundaries, the partition should contain
only the segments of the polygons, and the records must contain the names
of the zones on each side.  Left and right zones are defined by the
direction implied by the sequence of points in the line.  The zone names
must correspond to those defined in the zones partition.  The special zone
name OUTSIDE (left aligned)
should be used when the line is at the edge of the map, or on
the boundary of void areas.

Line segments (of polygons)
 must be closed (i.e., the last point in a segment must be the
first point of another segment), and segments must not cross or have loops.
Further, segment must not be repeated.

Segments that are to be used as geographic overlays may have feature codes to
give a classification e.g. different types of rivers.

     Type Record:
     8        byte      partition header = SEGMENTS

     Header Record:
     10       integer   number of segments

A set of records follows for each segment.

     Definition Record:
     10       integer   identifying number
     10       byte      name of left zone (if line is part of a zone
                        boundary)
     10       byte      name of right zone (if line is part of a zone
                        boundary)
     10       integer   number of points in segment
     10       integer   number of feature codes

                                                                      83

     Feature code Records (if required):
     8 x 10  integer    feature codes

     Point Records:
     8 x 10   real      (X,Y) coordinate pairs (4 per record)

  B. 4.10 Points Partitions
          -----------------


The partition contains a set of points or sites at which symbols can be
overlayed on the map.  The site name can be used to apply quantised
attribute data or used to annotate the points.

Feature codes can define a classification for display as sites.

Type Record:
     6        byte      partition header = POINTS

     Header Record:
     10       integer   number of points

     Point Records:
     10       real      X-coordinate value
     10       real      Y-coordinate value
     40       byte      site name or annotation
     10       integer   number of feature codes

     Feature code Records (if required):
     8 x 10  integer    feature codes

Note that only the first 10 characters are used for the site name.

  B. 4.11 Sample boundaries geographic file DEMOZSEG.DAT
          ----------------------------------------------

Geographic data for zones (e.g. Census districts) are usually brought in as the
line segments that form the boundaries of the zones.

The boundary segments contain the (X,Y) vertices that make up the line and the
names of the zones on each side of the line.

These data are usually entered using OzEnter, then excessive vertices discarded
(thinned) using OzData, and then the full zone / polygon/ line segment /
centroids structure built using OzZone to prepare for display.

For example, to extract ZIP code boundaries from USA TIGER files, the left and
right ZIP codes are extracted from the records and formed into left aligned
zone names, and the latitude / longitude vertices are also extracted. If the
left and right zone names are the same the segments are internal to the zone
and can be ignored.

The following illustrates the standard format used to enter such data. Note
that the MAP partition is required but that the extent need not be given.

EXAMPLE ZONE BOUNDARY SEGMENTS THAT CAN BE BUILT INTO ZONES - DEMOZSEG.DAT
MAP

                                                                      84
  0.0       0.0       0.0       0.0
         0
SEGMENTS
        10
       107ZONE 1    OUTSIDE            2
102.00    503.00    114.00    503.00
       125ZONE 2    ZONE 1             2
102.00    503.00    110.00    513.00
       143ZONE 1    ZONE 3             2
114.00    503.00    110.00    513.00
       161ZONE 3    OUTSIDE            6
114.00    503.00    115.00    505.00    116.00    507.00    117.00    509.00
118.00    511.00    119.00    513.00
       187ZONE 2    ZONE 3             2
110.00    513.00    119.00    513.00
       205ZONE 2    OUTSIDE            4
119.00    513.00    114.00    518.00    109.00    517.00    104.00    516.00
       227ZONE 2    OUTSIDE            2
104.00    516.00    110.00    513.00
       245SURPLUS   SURPLUS            2
119.00    513.00    122.00    506.00
       263OUTSIDE   ZONE 2             2
103.00    509.00    110.00    513.00
       281OUTSIDE   ZONE 2             2
102.00    503.00    103.00    509.00

  B. 4.12 Sample geographic file DEMOZONES.DAT
          ------------------------------------

The full topological geographic structure can be entered (although in practise
this is seldom available).

COMMENT LINE FOR TEST DATA     - DEMOZONE.DAT
MAP
102.00    122.00    502.00    518.00
         0
ZONES
         3
ZONE 1             1
       352
ZONE 2             2
       377       402
ZONE 3             1
       327
POLYGONS
         4
       327ZONE 3             3         0
110.00    119.00    503.00    513.00    114.00    510.00
       187      -161       143
       352ZONE 1             3         0
102.00    114.00    503.00    513.00    108.00    506.00
      -125       107       143
       377ZONE 2             3         0
102.00    110.00    503.00    513.00    104.00    508.00
      -263      -281       125
       402ZONE 2             3         0
104.00    119.00    513.00    518.00    110.00    515.00
       205       227       187

                                                                      85
SEGMENTS
        10
       107ZONE 1    OUTSIDE            2
102.00    503.00    114.00    503.00
       125ZONE 2    ZONE 1             2
102.00    503.00    110.00    513.00
       143ZONE 1    ZONE 3             2
114.00    503.00    110.00    513.00
       161ZONE 3    OUTSIDE            6
114.00    503.00    115.00    505.00    116.00    507.00    117.00    509.00
118.00    511.00    119.00    513.00
       187ZONE 2    ZONE 3             2
110.00    513.00    119.00    513.00
       205ZONE 2    OUTSIDE            4
119.00    513.00    114.00    518.00    109.00    517.00    104.00    516.00
       227ZONE 2    OUTSIDE            2
104.00    516.00    110.00    513.00
       245SURPLUS   SURPLUS            2
119.00    513.00    122.00    506.00
       263OUTSIDE   ZONE 2             2
103.00    509.00    110.00    513.00
       281OUTSIDE   ZONE 2             2
102.00    503.00    103.00    509.00


  B. 4.13 Sample lines geographic file DEMOLINES.DAT
          ------------------------------------------

A lines structure is used for line data that is to be displayed for attribute
data:

COMMENT LINE FOR TEST DATA       DEMOLINES.DAT
MAP
103.50    121.50    503.50    517.50
         0
LINES
         4
ROAD 3             3
110.50    119.50    503.50    513.50
       187       161       143
ROAD 1             3
103.50    114.50    503.50    513.50
       125       107       143
ROAD 2             3
103.50    110.50    503.50    513.50
       263       281       125
ROAD 4             3
104.50    119.50    513.50    517.50
       205       227       187
SEGMENTS
        10
       107ROAD 1    OUTSIDE            2
103.50    503.50    114.50    503.50
       125ROAD 2    ROAD 1             2
103.50    503.50    110.50    513.50
       143ROAD 1    ROAD 3             2
114.50    503.50    110.50    513.50
       161ROAD 3    OUTSIDE            6

                                                                      86
114.50    503.50    115.50    505.50    116.50    507.50    117.50    509.50
118.50    511.50    119.50    513.50
       187ROAD 2    ROAD 3             2
110.50    513.50    119.50    513.50
       205ROAD 2    OUTSIDE            4
119.50    513.50    114.50    517.50    109.50    517.50    104.50    516.50
       227ROAD 2    OUTSIDE            2
104.50    516.50    110.50    513.50
       245SURPLUS   SURPLUS            2
119.50    513.50    121.50    506.50
       263OUTSIDE   ROAD 2             2
103.50    509.50    110.50    513.50
       281OUTSIDE   ROAD 2             2
103.50    503.50    103.50    509.50

  B. 4.14 Sample points geographic file DEMOPOINT.DAT
          -------------------------------------------

Points files just give the (X,Y) locations and a site name / label.

These files can be used with an attribute file for mapping site data or can be
used to place sysmols or labels at locations (overlays).

COMMENT LINE FOR TEST DATA     - DEMOPOINT.DAT
MAP
102.00    122.00    502.00    518.00
         0
POINTS
         3
114.0     503.0     PNT1
104.0     516.0     PNT2
114.0     518.0     PNT3


  B. 5 Format of polygon geographic files
      ----------------------------------


  B. 5. 1 Standard (not implemented)
          --------------------------


Geographic data are often available in polygon format, and this data
definition enables it to be used used with OzGIS.

The common line segments on the boundaries of adjacement polygons are
effectively defined twice in polygon data; OzGIS assumes that they are
exactly the same.  The polygon boundary must not cross itself.

Each polygon has a name, which is the name of the zone to which it belongs.

Polygons may occur inside other polygons.  Where the polygon is not part of
a zone (e.g. a lake) it may be given the name OUTSIDE.  The level field
defines lakes, islands within lakes etc.  When maps are generated on
devices using polygon fill the level gives the order of display so the
polygons will overwrite correctly.



                                                                      87
Comment record:

     80      byte       comment describing the data

Definition Record:
     10      integer    map projection code
     10      integer    zone type (optional)

Each polygon is defined by a set of records:

Polygon header:
     10      byte       zone name, usually left justified, blank filled
                        or OUTSIDE if an internal polygon.
     10      integer    number of points in the line
     10      real       level of polygon for hardcopy generation using
                        polygon fill 0=standard, 1=lakes, etc.

Centroid record:
     2x10    real       centroid or labelling point (X,Y) in polygon

Point records:
     8x10    real       (X,Y) coordinate pairs (4 per record) The last
                        point must be the same as the first.


  B. 5. 2 Simple Format (SAS) Zone Files
          ------------------------------


Simple format files are in common use by the SAS system and other packages
providing SAS interfaces.  Polygon for lakes etc. should follow standard
polygons to provide the correct display order for overwriting.

   Header   Record

     80      byte       Comment

Each data record has the form
     10      byte       zone name
     10      real       X coordinate
     10      real       Y coordinate
     10      integer    Polygon number within zone

  B. 5. 3 Sample simple zones data file DEMOSASG.DAT
          ------------------------------------------

SAS FORMAT GEOGRAPHIC DATA - DEMOSAS.DAT
SQUARE        3.0       5.0
SQUARE        7.0       5.0
SQUARE        7.0       10.0
SQUARE        3.0       10.0
DIAMOND       8.0       8.0
DIAMOND       10.0      5.0
DIAMOND       12.0      8.0
DIAMOND       10.0      11.0
TRIANGLE      13.0      5.0
TRIANGLE      16.0      10.0
TRIANGLE      19.0      5.0

                                                                      88
TRIANGLE      13.0      2.0            2
TRIANGLE      15.0      2.0            2
TRIANGLE      14.0      4.0            2
SQUARE        4.0       0.0            2
SQUARE        8.0       0.0            2
SQUARE        8.0       4.0            2
SQUARE        4.0       4.0            2
SQUARE        0.0       0.0            2
SQUARE        5.0       1.0            2
SQUARE        5.0       3.0            2
SQUARE        7.0       3.0            2
SQUARE        7.0       1.0            2
OUTSIDE       15.0      6.0            2
OUTSIDE       15.0      7.0            2
OUTSIDE       17.0      7.0            2
OUTSIDE       17.0      6.0            2
TOP           4.0       8.0
TOP           19.0      8.0
TOP           19.0      9.0
TOP           4.0       9.0

  B. 6 GIS / standard geographic file formats
      --------------------------------------


  B. 6. 1 DIME format
          -----------

This format is supported, but has not had much use. The data are primarily 2
point segments, so is inefficient on storage.

Note that only 499 2 point segments can be handled.

The data are usually passed through OzZone to build polygons and then through
OzData to join up the segments into ones of decent length.

The data are long Ascii records, and look something like:

XX91609160012583                       1
  MANUEL              ST                       8    8      201   299   200
   29891600000011 14502 1450219711197119160       38  440195019510003016     234
  10003016     213   1818                        396750 757476396740
7574760610215040685606098370406849
  MANUEL              ST                       8    8      301   359   300
  35891600000029 14502 1450219711197119160       44  480195019510003016     233
  10003016     212   1818                        396740 757476396730
7574760609837040684906095020406848
  MANUEL              ST                       8    8      361   399   360
  39891600000037 14502 1450219711197119160       48  540195019510003016     233
  10003016     233   1818                        396730 757476396718
7574760609502040684806090470406846
  SCHOOL              ST                       9    9      900   998   901
   99991600000045 162   162  19720197209160       37  220200020010003031     107
  10003031     108   1818                        396611 755737396619
7557430605026045580006053140455632
  SCHOOL              ST                       9    9     1000  1098  1001
  109991600000052 162   162  19720197209160       22  140200020010003031     115
  10003031     115   1818                        396619 755743396624

                                                                      89
7557460605314045563206054910455542

  B. 6. 2 DLG optional 3 format
          ---------------------

The DLG-3 format is the major interchange format in use, and data can be obtaine
from many mapping agencies e.g. from USGS.

The data differs in concept from the usual data displayed by OzGIS in that it
is preclassified by the assignment of numeric "feature codes".

All identifiers are numbers. These are converted to names by adding prefixes.
Point names are POINT + 5 digit number, zone names are AREA + 6 digit zero
filled number e.g.

AREA000001
AREA000630
POINT00004
POINT00234

The data entry process processed the lines only. Any line with one vertice or
two vertices and the same node numbers is taken as a point.

Other lines are output with the left and right names set to the area names.
Left and right area numbers of zero or one are taken to be outside the map.

Feature codes are stored as numbers (combined input pairs) for lines, points
and zones e.g. '291  22' becomes 2910022.

The first area is ignored as it should be the boundary of the map.

Polygons are generated by passing the geographic file through the OzZone
program.  This carries the area feature codes through to the polygons, retains
the line segments, and forms a points segment that contains the centroids of
the polygons.

Note that file must have 80 character fixed length records.

Some test files are supplied for Hawaii.  These were read off the USGS GeoDATA
CD ROM on a SUN system, and 'newline' characters inserted to form 80 character
records.  The files had to be editted as an arbitrary polygon was given as
outside the map as the left and right areas on the line (this could also be
handled during display by specifying feature codes).

The test files are:

HAWDLGWB - water boundaries i.e. the islands
HAWDLGWB - administrative boundaries
HAWDLGRD - roads
HAWDLGST - streams

The data format is described in the US Geological Survey Circular 895-c
"USGS Digital Cartographic Data Standards, Digital Line Graphs"

The files look like:

USGS-NMD  DLG DATA - CHARACTER FORMAT - 09-29-82 VERSION s21_wb.dlg
HAWAIIAN ISLANDS POLY 10 DROPPED        1967, 1980  2000000.

                                                                      90

     3     3  9999     2 0.50800000000D+02     4     0     4     1
   0.637820640000000D+07   0.676865799729109D-02   0.800000000000000D+07
   0.180000000000000D+08  -0.157000000000000D+09   0.300000000000000D+07
   0.0                     0.0                     0.0
   0.0                     0.0                     0.0
   0.0                     0.0                     0.0
 0.10000000000D+01 0.0               0.0               0.0
SW       19.000000 -160.000000        -316386.41  1771715.66
NW       22.000000 -160.000000        -312489.03  2102112.53
NE       22.000000 -155.000000         208312.61  2101093.98
SE       19.000000 -155.000000         210917.63  1770684.40
WATER BODIES           0    74    74 010    12    12 010    70    70   1
N    1  -316386.41  1771715.66           0           0     0
N    2  -312489.03  2102112.53           0           0     0
N    3   208312.61  2101093.98           0           0     0
N    4   210917.63  1770684.40           0           0     0
.
.
.
.
N   74  -320966.08  2105481.92           2           0     0
   -69    70
A    1   -68438.87  1949336.24           3     0     1     0     0
     8     9     7
     0     0
A    2  -327997.34  2094827.63           3     0     1     0     0
   -10    -2    -1
    40   150
.
.
.
.
A   13   -91708.84  2025480.45           3     0     1     0     0
   -66   -65   -67
    40   150
L    1     7     6     2     0                24     1     0
  -332906.23  2078428.77  -332805.62  2077920.57  -331991.53  2078579.38
  -332446.45  2079748.67  -331479.96  2080407.19  -331224.96  2080914.69
  -331578.38  2082032.98  -331221.19  2082845.09  -330100.11  2084620.90
  -329235.22  2085279.61  -328573.03  2086192.72  -328571.24  2087107.12
  -327247.56  2088577.74  -325977.26  2088727.66  -325164.16  2088878.47
  -324909.37  2089284.37  -324503.57  2088978.78  -323182.17  2089280.99
  -322319.07  2089025.30  -321707.68  2089938.51  -321250.68  2089836.02
  -320995.88  2090241.92  -319775.79  2090696.74  -318961.20  2091609.55
   290  4000
.
.
.
.
L   70    74    66    11     0                 2     1     0
  -320966.08  2105481.92  -321422.78  2105736.82
   290  4002

                                                                      91

  B. 6. 3 Gina format
          -----------

The standard interchange format for GeoVision GIS is Gina.

OzEnter processes some of the file. Feature codes must be numeric. Zone names
generated are of the form ZONE12345 and site names are of the form POINT12345.

Only boundary lines and points are output - OzZone has to be used to generate
the zones / polygons.

The sample file DEMOGINA.DAT is as follows:

udb-start b v 8192

udb-header 0.5 fred-db "Fred's test database"
descr      29oct85 14:32:10 example GINA files
coord-sys  rect  feet
extent -12000, -8000,  12000, 8000
layer 1 base        "base information layer"
layer 2 roads       "roads and streets layer"
layer 3 hydro       "hydrographic layer (rivers, streams etc)"
layer 4 telephone   "telephone plant layer"
layer 5 lots        "property lots layer"

network 1 emergency l 2 "emergency routes"
network 2 property  p 5 "property polygon network"

udb-primary
table road free
field name        char 40   i n   "road name"
field r_type      char 12   i n   "type of road, arterial, highway etc"
field lanes       num  2,0        "maximum number of lanes"
field surface     char 10   n     "type of surface"
fc   1000, 1099
table house free
field h_type      char 10   n     "house type: bungalow;""test quotes""  etc"
field lot_no      num 10    i     "lot number"
fc   1130,  1139
table lots free
field lot_no      num  10   i u n "lot number"
field address_no  num  6,0  i n
field street      char 40   n     "street name"
fc   1100


udb-feature
feat 1  1002 2 0 l xy 0 0 0 1 0
coor 1805 1120 1805 1143
coor 2018 1143 2018 1204 2508 1204
text "Elm Street"
attr Elm suburban 2 "asphalt"
feat 2  1004 2 0 l xy 0 0 0 1 0
coor 2508 1204 2508 820
text "Oak Street"
attr Oak arterial 4 "concrete"

                                                                      92
feat 3  1400 5 2 l xy
coor 2508 903 2508 933
feat 4  1400 5 2 l xy
coor 2508 933 2568 933
feat 5  1400 5 2 l xy
coor 2568 933 2568 903
feat 6  1400 5 2 l xy
coor 2508 903 2568 903
feat 7  1400 5 2 l xy
coor 2508 873 2508 903
feat 8  1400 5 2 l xy
coor 2568 903 2568 873
feat 9  1400 5 2 l xy
coor 2508 873 2568 873
feat 20  1100 5 2 p xy
coor 2520 920
attr  10875,  104 Oak
feat 21  1133 5 0 l xy
coor 2530  920
attr 2-story  10875
feat 22  1100 5 2 p xy
coor 2520  890
attr 10874,  106 Oak
feat 23  1133 5 0 l xy
coor  2530 890
attr bungalow 10874

udb-polygon
poly 3 20 r e
poly 4 20 r e
poly 6 20 l e
poly 5 20 r e
poly 6 22 r e
poly 8 22 r e
poly 9 22 l e
poly 7 22 r e

udb-indirect
table road_types free
field r_type    char 12 i u n  "road type"
field maint     char 2         "maintenance class"
field resp_code char 3  n      "responsibility code"
attr highway    m3  A-4
attr aterial    m6  B-3
attr secondary  n2  B-1
attr suburban   s4  B-8


udb-indirect
table house_types  free
field h_type    char 10  i u n "house  types"
field tax_code  char 4   n     "taxation code"
attr bungalow  10-5
attr 2-story   12-2
attr split     11-5

udb-end

                                                                      93

  B. 6. 4 ANSII standard
          --------------

The new standard format for interchange will be supported when test data become
available.

  B. 6. 5 SIF format (not available)
          --------------------------

SIF format will be supported if there is a demand.
Data files appear to be 80 character ascii files.

The files contain a series of commands that define how the coordinates are to be
displayed.

Most of the commands are ignored.

The commands of value seem to be:

DID/ is the first record in the file, and gives some basic information. The
parameter MO=2 or MO=3 gives the number of dimensions (compulsory?). Any Z value
is ignored.

OVR/   defines the active level. This is stored in the relations as a number
column 'ovr' as it seems to  be  effectively a layer.

ASC/ggnum defines the graphic group number, and is used to  form the entid of
form SIFggnum.

If ggnum is 0 the item is ignored (not appended).

If ggnum is <0 a number is assigned to it (sequentially starting at 10001).

LST/xx, defines a line. There are 2-101 vertices in a record. If a record has
101 values and the next record starts with the same point as the end point it is
taken to be a continuation. (actually found some records with more than 101)

LST/ and LST/OP are line strings.

LST/HO and LST/SO are polygons (solid & holes)

Vertices are (x,y) or (x,y,z) according to the DID/ header.

New records that are not continuations are taken to be new components.



  B. 6. 6 DXF format (not available)
          --------------------------

DXF format will be supported if there is a demand.


                                                                      94

  B. 7 Format of names files
      ---------------------


Names files give lists of zones, lines or sites which are to be used to
restrict certain kinds of processing in OzGIS.

The file would usually be prepared with a text editor, possibly operating
on a file output from OzGIS.

     Comment Record:
     80       byte      comment describing the data

     Name Records (one per zone or line or site)
     10       byte      name


  B. 7. 1 Sample names file DEMOATTR.DAT
          ------------------------------

DEMONAMES.DAT - NAMES FILE
ZONE 1
ZONE 2
ZONE 4


  B. 8 Format of colour names files (Removed from system)
      --------------------------------------------------


Colour names files are usually generated within OzGIS, but they may be
entered as data files. The file X11-BGR is supplied.

Comment record:
     80      byte       comment describing the file

Colour records:
     40      byte       colour name (in ascending order)
     10      real       blue value, range 0.0 to 1.0
     10      real       green value, range 0.0. to 1.0
     10      real       red value, range 0.0 to 1.0

The demonstration file DEMOCOLNM.DAT looks like:

DEMO COLOUR NAMES FILE
aquamarine                                   .8314    1.0000     .4980
blue                                        1.0000     .0000     .0000
brown                                        .1647     .1647     .6471
darkseagreen                                 .5608     .7373     .5608
hotpink                                      .7059     .4118    1.0000
lemonchiffon                                 .8039     .9804    1.0000
lightskyblue                                 .9804     .8078     .5294
mintcream                                    .9804    1.0000     .9608
pink                                         .7961     .7529    1.0000
purple                                       .9412     .1255     .6275
royalblue                                    .8824     .4118     .2549

                                                                      95
salmon                                       .4471     .5020     .9804
steelblue                                    .7059     .5098     .2745
turquoise                                    .8157     .8784     .2510
yellowgreen                                  .1961     .8039     .6039


  B. 9 Format of combine files
      -----------------------


Combine files define new map zones in terms of zones in a base map, or site
catchments in terms of percentages of base zones.

Comment record:
     80      byte       comment describing the file

Header record:
     10      integer    number of items defined


Sets of records follow for the items:

Item definition record:
     10      byte       name (ascending order)
     10      integer    number of zones

Zone records:
     10      byte       zone name (ascending order)
     10      real       proportion of zone in area (0 to 1.0)



  B. 9. 1 Sample combine file DEMOCOMB.DAT
          --------------------------------

This file defines three territories AREA1, AREA2, AREA3 in terms of base zones
A, B, ......

3 AREAS
         3TEST AREAS
AREA1              1
H             1.0
AREA2              3
N             1.0
O             1.0
R             1.0
AREA3              5
A             1.0
B             1.0
C             1.0
D             1.0
E             1.0

  B.10 Format of presentation files
      ----------------------------


Presentation files give a set of saved map files that are to be referenced

                                                                      96
by menu items so the maps can be easily displayed when giving demonstrations.

     First record:

     60      byte       menu header

A pair of records is given for each saved display file
     60      byte       menu item text
     50      byte       saved map file in full form


  B.10. 1 Sample presentation file
          ------------------------

AURISA Exhibition
Far East Asia zone map
DEMOFEA.SAV
Lowe Electorate bivariate zone map
BIVLOWE.SAV
Diagram map
DIAG1.SAV
Zones & Sites map
ZONESITE.SAV
Australia Statistical Division zones map
DEMOOZ.SAV
Canberra LGAs zone map with overlays
ACT.SAV

  B.11 Format of marker files
      ----------------------


Markers are displayed in OzGIS as single polygons using polygon fill.

OzGIS has standard files available (star, triangle etc.) but a user can
define additional ones.

A marker is a single closed polygon.  OzGIS requires that the points that
define the polygon lie within a circle of unit diameter.

The data points are usually prepared by drawing the marker on graph paper,
centred on the origin, and lying within a circle of radius 0.5.

     Comment record:

     80      byte       marker name, comments

     Header record:

     10      integer    number of points (3-100)

     Boundary record:

     8x10    real       Polygon points (X,Y) 4 per record
                        Values are in the range (-0.5 to +0.5)  The last
                        point must be the same as the first


                                                                      97

  B.11. 1 Sample marker file SQUARE.DAT
          -----------------------------

SQUARE.DAT - MARKER
         5
-0.35     -0.35     -0.35     0.35      0.35      0.35      0.35      -0.35
-0.35     -0.35

  B.12 Format of device files
      ----------------------


Device files describe the characteristics of graphics display devices and set
colours etc.

Standard files are usually held on the system for all devices available. Users
would not usually define their own.

 OzGIS was designed to operate as a highly interactive colour mapping system
where speed of display was obtained by the use of an  advanced raster display
system.

 The software can operate on most graphics devices, but there could be loss of
speed and capabilities depending on the characteristics of the devices being
used.

 OzGIS is based on graphics packages with the functionality of the GKS graphic
standard. These graphic packages provide graphic primitives such as lines,
text, and filled polygons. An important feature of GKS is that it is device
independent so the package allows OzGIS to produce maps on a large range of
devices.

 Every device available for use with OzGIS has at least one file associated with
it.

All devices within OzGIS have the same characteristics so e.g. a map previewed
on a display device can be output directly to a hard-copy device. The files
ensure that a device with limited capabilities can  simulate the required
capabilities in the best way.

 The device files also set GKS primitive attributes such as colours and zone
fill types. A colour display system has several files available that provide
standard sets of colours for maps. Files with similar colours are usually
available for different devices for hard-copy generation.

The easiest way to generate device data files is to edit standard ones.

The device files require colours to be specified in blue,green,red. One way to
decide on these values is to look at the definitions in the colour names data
file \ozgis\x11-bgr.dat.

Hardcopy device files are based on the SCIPLOT package which has a fixed set of
colours. Of course plotter colours depend on the pens. SCIPLOT colours are:
     Black
     Blue
     Green

                                                                      98
     Cyan
     Red
     Magenta
     Brown
     Light Gray
     Dark Gray
     Light Blue
     Light Green
     Light Cyan
     Light Red
     Light Magenta
     Yellow
     White



     Comment record:

     80      byte       Device description


     Size record:

     10      real       Extent of device surface
     Note: defines units used for all sizes in data i.e. divide by this
     10      real       width of device in device units (now set fromOZGIS.IN)
     10      real       max address height of device    (now set fromOZGIS.IN)

     Type record:

     10      integer    GKS workstation number
     10      integer    Display type, 1 = raster display, pixel addressed
                                      2 = continuous coordinates
     10      integer    Fill type, 1 = solid colour
                                   2 = pattern
                                   3 = hatch
     10      integer    Locator device number, 0 = none, 1 = default
                                               2 = crosshairs

     Advanced Raster Record  (now set fromOZGIS.IN)

     10      integer    number of bit planes (1-24)
     10      integer    length of LUT (1-4096)
     10      integer    number of pixels across screen (256-4096)
     10      integer    number of lines on screen (256-4096)
     10      integer    run-length encoding/decoding, 0 = not available

     Colour definition record:

     10      integer    number of colours defined

     Colour table records:

     10      real       blue value (0.0 - 1.0) for colour table
     10      real       green
     10      real       red

     Hatch definition record:

                                                                      99

     10      integer    number of hatch patterns (0 - 256)

     Hatch records (if required):

     10      integer    line number (1 - 8)
                        (from overlay and quant. lines)
     10      real       line angles (0.0 - 180.0)
     10      real       line separation  (<0.1)
     10      integer    line number (0 - 4) , 0 = not used
     10      real       second line angle (if reqd)
     10      real       second line separation (if reqd)

The rest of the data records set internal tables for GKS primitive
attributes.  Most records reference the colour table; the index has range 1
to length of table.


A style table is used with the colour table for polygon fill according to
the fill type.

-  SOLID - the colour is used, style not relevant
-  HATCH - the pen colour is obtained from the colour table, the hatch
           pattern number from the style table
-  PATTERN - the colour table is not used, the style table gives the device
             dependent pattern number

Area Fill records:

10   integer            colour index
10   integer            fill or style index

Several fill records are required, in following order:

-  background. NOTE also the menu / messages/ everything colour
-  zone missing data
-  excluded zones
-  diagram background
-  line or site quantisation legend and diagram
-  8 polygon underlay records

Text records:

10   integer            colour index
10   integer            font number  (1-9)
10   integer            text precision 0=STRING, 1=CHAR, 2=STROKE
10   real               height of character space (pixels)
10   real               width of character space  (pixels)

Note:  on display devices hardware text of known size will be used.
Fonts are available for use on the screen, but are more usually used for output
on plotters.

The following fonts are available:

1 VGA/EGA hardware font or default hardcopy font
2 Simplex Roman, the most basic
3 Duplex Roman, more detailed than the simplex with about twice as many strokes

                                                                     100
4 Complex Roman, similar but with more tapered segments
5 Triplex Roman, heavier version
6 Simplex script, based on handwriting
7 Complex script
8 Complex italic italic version of complex roman
9 Triplex italic

The text records are:

4 records to define the text available for name overlays at sites or typed
in text.
The text is usually defined in increasing size order.

Legend text record:  This is fixed size text used for generation of all the
legends.  The size is very important as it governs the overall size of the
legend e.g. the zone legend boxes are 3 times the text height in height, 2
times the text width in width.

Attribute description text record:  This is normally large text.  The
interactive system has to be able to clear it off for each attribute so it
should be fixed size hardware text in that case.  When two variates are
displayed the two descriptions are separated by
 a 'VS' or 'AND' generated using the
legend text.


Line records:

10   integer            colour index
10   integer            GKS type (1-4)
                        1 = solid, 2 = dashed, 3 = dotted, 4 = dash dot

The actual records are as follows:

4 records for lines to be used for line overlays.

4 records for lines to be used for quantised lines (line-type has no
meaning here as types are assigned according to quantisation).

Note that these first 8 records also define the hatching
plotter 'pens' if applicable.

A record to define zone boundaries line.

A record to define the line used to draw axes on diagrams (should be
solid).

A record to define the line used to draw statistical values on diagrams.

Marker records:

10     integer     colour index
10     integer     fill style index
10     real        marker height (and width)
40     byte        marker file name, left aligned, system format

The records are as follows:


                                                                     101
4 records for markers to be used as overlays at sites.

4 records for markers used for sites with quantised attribute data (marker
size has no meaning, is set for class).

1 record for site marker background  (currently not used)

1 record for scatter diagram (GKS marker no 1)

Colour Sequence records (170 records):

10     integer  colour index
10     integer  style index

These records give sequences of colours (or patterns) or hatching for
colouring zones after quantisation.

There are two types of sequence:

-  a 121 value array for single variate zones followed by
-  a 7x7 array for bivariate


The class fill is found by sampling out of the sequence for the number of
classes, e.g. for bivariate

2 classes         1        7
3 classes         1   4    7
4 classes         1  3  5  7

Similarly, the single variate 121 value array allows exact sampling for
number of classes 2-7; a best choice is made for 8,9 or 10 classes.  In the
special case of pseudo-continuous colour maps the whole 121 values are
used.

Menu colour records

10 integer background text number (0-7)
10 integer foreground text number (0-7)

The menu colours are:

1 main menus
2 lists
3 help messages
4 input of values
5 error messages

The 5 menu records use internal text numbers

Note:  Files for advanced raster display systems with long LUT's should be
set up as follows:

-  Display type = 1
-  Fill type = 1
-  LUT length 256 or greater
-  One LUT colour for each record in the data file i.e. all colour index
   values unique

                                                                     102

The system by passes the colour index and style index when operating in
fast interactive code and accesses the LUT directly.

                                                                     103
                     C. GLOSSARY OF TERMS
                       =================

The purpose of this Appendix is to provide definitions for a number of
terms used within this Guide.  Most of these terms are commonly used words
or phrases which have taken on a more precise technical meaning in one of
the areas spanned by the OzGIS system.  Technical terms have been
borrowed from the jargon of statistics, data processing, computer software
and hardware, cartography, and graphic arts.  Because of the diversity of
these disciplines, it is unlikely that a potential OzGIS user will have
developed a level of expertise in each.  This glossary should provide most
of the information necessary for communicating the basic concepts of
OzGIS.

The glossary is available on-line, and is accessed by typing 'G' to a menu
selection request.

Area - 1) A measurement of the size of a geographical region whose shape is
   displayed on the OzGIS monitor.  2) An arbitrary portion of the face
   of the monitor.

Attribute - A general term for the variable associated with a set of
   geographic zones, lines or sites to be processed by OzGIS.
   Attributes may be variates, statistics or simply data collected for each
   item.  Note that the modes of display for an attribute are usually
   referred to as "single variate" or "bi-variate".  See also Variate and
   Statistic.

Background - The informationless area displayed on the monitor around a map
   and its associated components.  Usually given a user selected, neutral
   colour such as black or white.

Bit - A unit of information representing the value (either 1 or 0) of a
   single binary digit.

Bivariate - A display of the relative distribution of two different sets
   of statistics on the same map.  It must be noted that no relationship
   between the two statistics is implied by the display.  For example, if
   the distribution of little old ladies is displayed simultaneously with
   the distribution of cricket players, the result is not a display of the
   distribution of little old ladies who play cricket.  See also Variate.

Boundary - A set of lines displayed on the monitor to represent the edges
   of polygons defined to the system.  Often the same as zone edges.

Byte - A group of eight bits.  See also Bit.

Catchment - The region of influence around a site e.g. suburbs around a
   shopping centre where most of the customers live.


Character - A single symbolic pattern which may be displayed on either the
   monitor or terminal.  It may be alphabetic, numeric, or punctuational,
   as the normal symbols encountered on a typical typewriter keyboard, or a
   special symbol generated for display as an entity, such as a square root
   symbol.


                                                                     104
Choropleth Map - A map portraying the values of an attribute averaged over
   data collection units (or zones) and represented by a symbol covering
   the entire unit.  A map displayed by OzGIS represents the zones by a
   uniform colour.

Class - A convenient subdivision of the total range of values of a
   particular statistical variate.  Classes are usually chosen to make
   computations or analyses less labourious, or to make the results of such
   analyses more obvious or meaningful.  For example, the range of a set of
   values might be divided into ten equal classes in order to highlight
   items in the top ten percent.  See also Variate, Class Boundary, Class
   Interval and Class Number.

Class Boundary - The special values of variates which determine the upper
   and lower limits of the range of a class.  See also Class.

Class Interval - The range of variate values between the upper and lower
   limits of the class.  See also Class.

Class Number - A cardinal number assigned to each class into which a
   particular statistical range has been divided.  Conventionally, the
   class whose members have the lowest magnitude is assigned number 1, with
   class numbers increasing uniformly as the magnitude of class values
   increases.  See also Class.

Colour - One of the combinations of blue, green, and red which may be
   specified for display on the monitor.  The total number of colours
   available depends on the display system.

Colour Space - The range of colours which may be specified for display on
   the colour monitor.  Since the colours are specified as values of blue,
   green, and red, it is convenient to think of the colour space as a cube
   located on a standard three dimensional coordinate system.  Black is
   placed at the origin, with each of the x, y and z axes representing
   blue, green, and red, respectively.  The range of possible values is 0.0
   to 1.0 on each axis of the cube.

Continuous Colour - A method of representating statistical values
   associated with map zones by graduating zone colours to correspond with
   changes in statistical value.  From a user defined, or default, sequence
   of colours, OzGIS generates the intermediate colours to provide a
   12 colour graduated path through the colour space.  The statistic to be
   represented is quantized into 12 equal value classes, and the classes
   are assigned colours from the generated colour sequence.  This allows
   small changes in statistical value to be represented by subtle changes
   in colour, while large changes in value may be visually observed as
   significant colour differences.


Controller - A general term applied to a piece of intermediate equipment in
   the data path between the electrical signals of a processor and their
   physical realization in a peripheral device.  Within OzGIS, the term
   will most often be used for the Color Display Controller.
   It will be used to a lesser extent to describe interface controllers for
   the various disc and tape drives.

Coordinate - One of a pair of numbers which designates the location of a
   geographic point with respect to another known point.  Geographic files

                                                                     105
   for entry into the system under OzGIS must have their points
   specified in appropriately scaled and formatted coordinates.  The
   coordinates specified by the user are converted by OzGIS for display
   on the monitor.  On the monitor screen, the origin is in the lower left
   hand corner of the viewing area.  The coordinates of a point on the
   monitor screen are specified by their distance right and up from the
   origin

Crosshair Cursor - A pair of lines at right angles to each other which is
   displayed on the monitor to designate the location of a certain point of
   interest.  Under most circumstances, the location of the crosshair
   cursor may be controlled by movements of the mouse.  See also Box
   Cursor, and Joystick.

Data - Numerical values associated with certain physical phenomena, such as
   128 cm long, 14 years old, or 43 kangaroos.  As a generality,
   OzGIS was not designed to handle data, but rather the statistics
   derived from data, such as average length, medium age, or number of
   kangaroos per hectare.  See also Statistics.

Decile - One of the nine data values which divide the range of a variate
   into ten equal sized classes.  See also Quantile and Percentile.

Default - A set of parameters automatically selected by OzGIS in the
   absence of any stated preference by the user.  The actual default
   parameters may be defined by the user in the users default file.  For
   example, OzGIS may initially display a map by arbitrarily selecting
   zone colours from a palette of possible shades which the user selected
   previously.  After this default colouring, the user may wish to change
   some particular zone colour to improve the appearance of the display.

Disc - An electronic device for storing digital data on a rotating plate
   coated with magnetic material.  See also Controller.

Display - As a verb, the act of presenting information on the monitor or
   terminal for the purpose of visually communicating that information to
   the user.  This includes all the procedures necessary to correctly
   present the information in a format suitable for both the equipment and
   the viewer.  Example:  "A map is displayed on the monitor, while a menu
   is displayed on the terminal".


   As a noun, the presentation which is visually perceived when a user
   looks at the screen of the monitor or terminal;  the total information
   content on the screen.  Examples:  "The terminal display indicates the
   options possible now";  "This map display is too red".  See also Monitor
   and Terminal.

Display Elements - The components or items of a display on the OzGIS
   monitor;  for example, legend, title, image map, boundaries, image
   symbols, histograms.

Distribution - The manner in which a number of samples of data are spread
   across the range of possible values.  May be a subjective statement,
   such as:  "These data appear to have an even distribution".  More often,
   some quantifiable measure will be given such as:  "These data have a
   normal distribution with a mean of 40 and standard deviation of 3".
   Sometimes, distribution information will be presented in graphical form,

                                                                     106
   such as a histogram or scatter diagram.

Equal Value Quantization - A method of dividing the range of values of a
   statistical variate into a number of classes where the magnitude of the
   range of each class is the same.  See also Class.

Excluded Zone - A zone displayed on the map and coloured with a special
   shade indicating that it has not been used for quantization or has been
   omitted from the area of interest.

File - A number of data items grouped together and considered as a unit for
   convenience of storage and retrieval by a computer.  Within OzGIS,
   such files are stored as distinct entities on disk.  Files are
   identified by media designation, name, and type.  The OzGIS user
   normally supplies only the file name, but the storage media may also be
   specified.  The file type is supplied by the system.  The same name may
   be used for files of different types, but within a particular type, no
   two files may have the same name.

Frequency - A statistical term referring to the number of members of a
   population falling into a specified class.  See also Class.

Geographic Data - Digitized map data which are referenced to a geographic
   (or spatial) coordinate system, usually a map projection.

Graphics - Data which can be displayed on the monitor in terms of lines
   points and text, as opposed to colouring and filling regions of the
   screen.  Used to refer to geographic and symbol data.

Histogram - A type of bar graph in which vertical rectangles are erected on
   the horizontal axis with the height of each bar representing the
   frequency, and the width representing the corresponding class interval,
   for each of the classes of a particular variate.  OzGIS can display
   such statistical information on the monitor.  See also Scatter Diagram,
   and Class.


Information - The subjective knowledge which may be associated with an
   objective set of data.  The ages and locations of children are data;
   the distribution of school age children is statistic;  where the schools
   should be built is information.  See also Data and Statistics.

Interval - The numerical distance between the upper and lower limits of a
   class.

Joystick - An electro-mechanical device which converts the positions of a
   small lever into electrical voltages.  The voltages are further
   converted into digital signals which are used by the PDP11 to
   position various cursor patterns on the monitor screen.  See also Box
   Cursor, and Crosshair Cursor.

Legend - A display on the monitor which indicates the correspondence
   between the statistical values and their associated colours or symbols
   as defined for a particular map.  The legend usually occupies
   approximately the rightmost one fifth of the viewing area of the monitor
   and has two general forms, single variate and bivariate.  One type of
   single variate legend consists of a column of coloured rectangles beside
   which are numbers indicating the corresponding class boundaries for

                                                                     107
   those colours.  The other is a rectangular column with colours gradually
   changing from top to bottom, and an upper and lower number indicating
   the range across which the "Continous Colour" varies.  The bivariate
   legend consists of a 45 degree parallelogram divided left to right and
   up and down into coloured smaller parallelograms.  A set of numbers
   along the left side indicates the class boundaries of the primary
   variate, while similar numbers across the upper side indicate the
   secondary variate class boundaries.

Line - This term has three special meanings within OzGIS in addition to
   its normal English usage.  (1) Any set of contiguous segments comprising
   the section of a zone boundary which has one zone on its right and a
   second zone on its left as part of a map.  (2) Any contiguous set of
   segments as part of a graphics display.  (3) A set of alpha-numeric
   characters meant to be displayed as one row on either the monitor or the
   terminal.

Location - The position of a datum point, or pixel, on the monitor screen.
   This is given by its x and y coordinates, with the origin in the lower
   left hand corner.  The range of values depends on the display system.

Lookup Table (LUT) - A table in the display system which can modify the
   value in memory for display purposes.

Map - Geographic data which can be displayed on the monitor by colouring
   and filling regions of the screen or as lines or symbols.

Map Projection - Refers to the coordinate system used for processing the
   display of a map.


Markers - Special characters or symbols which may be displayed on the
   monitor to identify locations of points.  For example, aircraft
   symbols to indicate the location of airports.  Different sized markers
   are used to show the classification of site attribute data.

Mean - The arithmetic average of a set of data values.

Memory - A portion of the OzGIS hardware used for the storage of data
   by the altering of the electrical state of the appropriate circuitry.

Menu - An itemized list of alternative actions which might be selected
   within OzGIS.  Menus are displayed on the terminal.  The terminal
   keyboard is used to enter selections from the options listed on the
   menu.  The sequence of menu items which is selected controls the "flow"
   of the OzGIS program through its various tasks.

Monitor - The electronic equipment, resembling a colour television
   receiver, on which maps and graphics are displayed.

Nested Means - A quantization method in which classes are generated by
   dividing each variate range into two classes about the mean for that
   range.  For example, the central class limit is set at the overall mean,
   then the upper and lower classes are each divided at the means of the
   two parts, giving four classes.  This process may be repeated, giving
   eight classes.

Operating System - Computer software provided to facilitate usage of the

                                                                     108
   various computer resources available within the OzGIS system.

Overlay - As a noun, overlay refers to graphic data written on top of the
   existing display.  This is displayed on the monitor as though placed
   between the previous display and the viewer.  Overlays generally are
   entered in the refresh memory in single bit planes.
   As a verb, overlay refers to the act of adding graphics data to a
   display by putting it "on top of" the previous display.

Palette - An array of coloured rectangles which is displayed on the monitor
   at certain stages of OzGIS.  The palette shows a range of colours
   which are available for selection by the user.  Palettes are held as
   files within OzGIS.  Several palette files are provided as part of
   the software package.

Parameter - A general term referring to a physical characteristic which may
   be measured or quantified in some way, even though the precise value of
   that measurement may be unknown in specific instances.  For example, age
   is a parameter of human beings.

Percentile - One of the set of 99 values which divide the range of a
   statistic into 100 equal sized classes.

Peripherals - Items of auxillary equipment added to a computer to enhance
   its performance.  These include such items as disc drives, tape drives,
   and printers.


Pixel - The smallest, individually controllable, element (or cell)
   displayed as dots of colour on the monitor's screen.  The monitor area
   is made up of lines of pixels.  For each pixel, there is a corresponding
   location in the refresh memory for storing the data value associated
   with that pixel.  This location is the smallest datum area which can be
   individually controlled by the software.  See also Image and Location.

Point - A geographic feature which, for display purposes, may be described
   by only indicating its location as an x and y coordinate.

Polygon - A geographic area described by the line segments forming its
   boundary and the zone name which forms its surface.  One or more
   polygons may be combined to form a zone.

Presentation Maps - A set of maps prepared for rapid display on the
   monitor.

Primary Variate - The set of statistical values characterized by a common
   name which is displayed on any given single variate map.  Two such sets
   of values are displayed on a bivariate map.  The primary variate is
   named at the top of the title, and its colour values are indicated in
   the rows of the legend.  See also Variate.

Processor - The hardware which executes the procedural and computational
   tasks specified by OzGIS.  The standard OzGIS processor is a
   Digital Equipment Corporation minicomputer, the VAX.

 Projection - The representation of a physical shape on the screen of the
   monitor according to a fixed mathematical coordinate system.  Normally,
   a projection in OzGIS terms will refer to a method for presenting

                                                                     109
   maps of geographic areas.  See also Map Projection.

Quantile - Any of the specific values which divide the range of a statistic
   into equal sized classes.  Some values have other special terms, i.e.,
   if the range is divided into four classes, the boundary values are
   called quartiles.  See also Percentile.

Quantify - To assign a number or quantity to an otherwise unnumbered
   entity.  In particular, to assign a class number to a statistical value
   or zone name.

Quantization - The process of assigning class numbers to zones according to
   the value of the statistic for that zone.  Viewed the other way,
   quantization is the process of putting zones into classes.

Quartile - One of the three data values which divide the range of a variate
   into four equal sized classes.  See also Quantile and Percentile.

Raster - a term applied to image data.  In particular data handled on a
   line basis.


Refresh Memory - The portion of the hardware (within the display
   controller) which holds the digital data necessary to continuously
   regenerate the colour monitor display.  The cathode ray tube (CRT) of
   the monitor produces its display by electrically stimulating various
   phosphorus based compounds deposited on its face.  The colours thus
   produced fade rapidly with time and must be continually "refreshed".
   The data necessary to perform this refresh correctly is stored in the
   refresh memory.

Region - A designated portion of a map displayed on the monitor.  A region
   consists of one or more zones or parts of zones defined in some way
   (e.g. a circular region centered at a point on the map).  The concept of
   a region is important when the displayed map consists of several
   geographic areas.  In this context, a region consists of a window
   (geographic area) and its displayed viewport on the screen (screen
   area).  See also Area.

Save - To store on disc (or magnetic tape) all the pertinent data regarding
   a map displayed on the monitor.  The maps which are "saved" can later be
   fully regenerated with all details preserved.

Scatter Diagram - A two dimensional plot of points whose x and y
   coordinates are the values of the individual variates associated with
   those points.  Scatter diagrams are displayed on the monitor in
   conjunction with bivariate maps.  In this instance, each map zone is
   assigned a point on the diagram.  The y-coordinate of the point
   corresponds to the value of the primary variate for that zone as
   displayed on the map.  The x-coordinate of the point has a similar
   relationship to the secondary variate.  In addition, the point will be
   coloured the same as its associated map zone.  Scatter diagrams provide
   a visual method of assessing the correlation between the two variates
   displayed on the map.

Secondary Variate - The second set of statistical values which are
   displayed (along with a primary variate) on the map.  The
   secondary variate is named at the bottom of the title.  See also Primary

                                                                     110
   Variate.

Segment - A set of connected straight lines defined to OzGIS by
   specifying the coordinates of their starting, intermediate, and end
   points, along with the names of the two zones on either side of the
   lines.  Consequently, segments must represent a portion, or all, of the
   boundary between two zones.  See also Line and Boundary.

Site - A geographic location that has associated attribute data.  A site is
   defined by a name and fixed location e.g. a site could be a city or a
   retail store.

Standard Deviation - A statistical measure of the dispersion amongst a set
   of measured values.  The standard deviation is mathematically equivalent
   to the positive square root of the variance of the sample on which the
   statistic is based.


Statistics - A general term referring to:  1) The branch of mathematics
   involved with performing certain analytical calculations regarding
   various relationships among sets of numerical data, and 2) The numerical
   results of such calculations.  The height of an individual is data;  the
   average height of a group is a statistic.

Status - The present condition of the software and hardware system,
   especially as to its progress toward the completion of the tasks at
   hand.  The status messages are displayed as a response to
   typing interpretation of various abbreviated messages displayed on the
   terminal.  The status messages are displayed as a response to typing an
   "S" command.

Terminal - An item of hardware comprising a keyboard for entering commands
   to the processor, and some means for the processor to return
   alpha-numeric messages to the user.  The standard OzGIS terminal is
   the Digital Equipment Corporation VT100.  This contains the necessary
   keyboard, and a cathode ray tube for displaying processor generated
   messages.  Some OzGIS installations may also have a printer terminal
   for providing a permanent copy of the messages on paper.

Territory - a zone which has been formed by amalgamating bas zones e.g. sales
   territories formed from postcodes.

Text - Combinations of characters which may be specified by typing at the
   terminal.  Lines of text may be displayed on either the terminal or the
   monitor in various fonts.  See also Character, and Line.

Time Lapse Maps - A formatted set of maps concerning a geographic area and
   certain statistics associated with it as they have been collected over
   time.  Time lapse files are used to display the time related changes in
   the statistical data by rapid and periodic changes in map colours
   corresponding to the statistics.  For example, variations in population
   density, as recorded by the 1971, 1976, and 1981 census data, could be
   shown by changing the colours of the displayed map at one second
   intervals corresponding to the 3 sets of data.

User - The person who is interactively controlling the OzGIS system at
   the terminal.


                                                                     111
Value - The number associated with a particular statistical item, as
   opposed to the colour associated with that item.  For example, the zone
   might be coloured red to indicate four to ten beer drinkers per pub in
   that zone.  The actual value of the statistic might be 9.4 beer drinkers
   per pub.

Variate - A measurable quantity which may take on any of the values within
   a given range, and which has associated with it a specified probability
   function describing the manner in which the permissible values are
   likely to occur.  See also Bivariate, Primary Variate, and Secondary
   Variate.

Viewport - The rectangular area of the colour monitor face selected for
   displaying a specified item.

Window - The rectangular portion of a geographic map which is selected for
   display on the colour monitor.


Zone - A geographic area which is to be considered as a spatial unit.  A
   zone is defined in terms of one or more polygons which form it.
   Statistically, a zone is defined in terms of a single value for each
   variate in question.  This relationship of one variate value per defined
   geographic zone allows zones to be completely and uniformly coloured in
   a map display.  See also Polygon and Variate.

Zone Name - An alphanumeric designation attached to the various
   computerized data associated with a zone.  The zone name facilitates for
   the processor the task of relating various data items to the proper
   zones.

                                                                     112
                     D. SYSTEM LIMITS
                       =============

The OzGIS system has a standard set of limits to various maximum counts. These
correspond to array sizes.

The limited memory on the PC makes these limits quite small.


The standard limits are:-

500   max no displayed zones+sites+lines
500   max no values in attribute file (zones,sites,lines)
10    max no map regions
10    max no quantised zone geog files
10    max no quantised site geog files
10    max no quantised line geog files
10    max no line overlays
10    max no polygon underlays
10    max no marker overlays
10    max no name overlays
20    max no test strings displayed
50    max no polygons in a zone
499   max no segments in a polygon
100   max no segments in a line
256   max no vertices in a segment
500   max no points in a fast display polygon
1000  max no zones per item in a combine file
256   max length of display system LUT
2000  max no vertices in foreign segments data file
5000  max no zones that can be built from line segments

                                                                     113
                     E. TROUBLE-SHOOTING
                       ================

Many of the Oz programs use most of available memory in the 640K. If you have
other programs loaded they man not run. This will often show up as errors when
opening files.

If you have trouble displaying maps then you probably have not configured the
system properly. If you are using a super VGA get the system working in standard
VGA mode first. Generally check the \ozgis\interact.ini file for the DISPLAY
parameter for the monitor type (usually 10). Super VGA modes need the correct
startup register values to be set. Edit the interact.ini file and throw away
irrelevant parts.

If you have trouble with the mouse in super VGA mode you may need the C
parameter on the end of the mode command in the interact.ini file. Ensure that
there are no comments following the C parameter. There have also been problems
with incompatible mouse drivers; microsoft and Genius drivers are known to work.
The mouse driver must be called MOUSE.COM.

If you have trouble with menus reload the \ozgis\ozgis.men file. This file
defines all the menus and actions and is constantly rewritten. A hardware error
could corrupt the file.

Check the osgis.out file after problems to see if there are any error messages.

GIS data (digitised data) are often incorrect. This can cause problems with
polygon display e.g. if zone boundaries cross themselves, and during zone
building. Your data supplier probably wont be of much help. Try windowing into
the part of the map with problems to isolate it and use the debug option to
print values. You will have to patch the data files with a word processor.

Rebooting the system while the OzGIS programs are running can cause "loss" of
disk space. This can be recovered using CHKDSK.

                                                                     114
                     F. OzGIS REFERENCES
                       ================


O'CALLAGHAN, J.F., SIMONS, L. and PALMER, J.A.B. (1980).  A prototype
system for interactive colour mapping.  Proc. URPIS-8 (k. Davies (ed.)),
Surfers Paradise, pp. 9.1-9.5.

SIMONS, L., O'CALLAGHAN, J.F. and PAINE, T. (1982).  COLOURMAP - an
interactive colour mapping workstation.  Proc. DECUS (Digital Equipment
Computer Users Society), Melbourne, Vol. 10, pp.1501-1504.

O'CALLAGHAN J.F., and SIMONS, L.W.J. (1983) COLOURMAP: An Interactive
Colour Mapping System. Proc. First Australasian Conference on Computer
Graphics, Sydney.

O'CALLAGHAN J.F., and SIMONS, L.W.J. (1984).   Map Display Techniques for
Interactive Colour Mapping.

Henzell, O'Callaghan. A Sequential Line Simplification Algorithm based on
Equivalent Height. CSIRONET Technical Report, May 1980

Robertson, O'Callaghan. The Generation of Colour Sequences for Univariate and
Bivariate Mapping. IEEE Computer Graphics and Applications, February 1986.

Gerald Evenden. Cartographic Projection Procedures for the UNIX Environment - A
User's Manual. USGS open-file report 90-284.

General Mapping References

J Sibert, 'Continuous-colour Choropleth Maps', Geo-Processing, (1980)
207-216.

'The Harvard Library of Computer Graphics Mapping Collection', Harvard
University.

E Giamottic and P Puliafits, 'An Interactive Spatial Information System: A
Tool for Regional Planning'; Proc IFIP 79.

J Dalton et al, 'Interactive Colour Map Displays of Domestic Information',
Proc SIGGRAPH 79, Computer Graphics, Vol 13 No 2 ACM/SiGGRAPH.

A Robinson et al, 'Elements of Cartography', Wiley 1978.


D Des Jardins, 'Multi-Level Statistical Maps in Graphic Communication',
Proc NCGA, Anaheim 1982.

                                                                     115
                     G. OTHER SPATIAL SOFTWARE
                       ======================


  G. 1 Background
      ----------

 Geismar Holdings has been involved with the development of several other
systems with the Commonwealth Scientific and Industrial Research Organisation,
Division of Information Technology. CSIRO is the major Australian government
research organisation.

These systems are based on the latest hardware and software technolgy, and
typically run on Unix workstation (e.g. SUN SPARC), are written in C or C++ and
use commercial relational database systems (e.g. Oracle, INGRES).

Several systems developed at CSIRO Division of Information Technology are now
being maintained and marketed by Australian Companies. Geismar provides
contract programming services to CSIRO and to a company selling the systems,
CLOUGH Engineering (Systems Division).

We do not market these systems, but can arrange for information to be sent.


  G. 2 SIRO-DBMS Spatial Information in a Relational DBMS
      --------------------------------------------------


SIRO-DBMS is a spatial database tool-kit for databases in the fields of
Geographic Information Systems, Land Information Systems and Facilities
Information Systems.  It offers high performance for queries involving
selection by location, full integration of spatial and other corporate
information, support for distributed database and a simple data model for
spatial databases built on the relational data model.

The system is of particular interest to Spatial Information System software
developers.

SIRO-DBMS is built as a shell around off-the-shelf relational database
management systems (rdbms) and uses the rdbms solely for both graphic and
attribute information.  No changes to the rdbms are required and the full rdbms
facilities remain available for use on tables interpreted by SIRO-DBMS as
describing spatial entities.  This provides for full integration of the spatial
database with other corporate databases.

The data model allows the geometric definitions of objects to be described as a
point, a rectangle, a line, a chain, a ring, a polygon (simple or complex) etc
in agreement with the ANSII standard on data interchange.  Linkages enable
hierarchies of components (e.g. points into chains into polygons). Other
attributes for entities can be described using the full set of data types
provided by the host rdbms.  Several options are available for the internal
representation of the geometry of objects, to allow database to be designed to
best satisfy the particular requirements of the task in hand.

The core operations are append, retrieve, delete and update.

Spatial operations available are minimum-bounding-rectangle, intersection,

                                                                     116
enclosure, crossing, connection, within-buffer and adjacency.

Good performance is provided by spatial indexing, a specialist form of indexing
for retrieval of objects by their location, implemented using the standard
rdbms indexing facilities.  Tests on a 1 Mip system show response times of 0.5
seconds (elapsed) to retrieve an average of 7 points from a set of 230000
points by windowing and response times of under 2 seconds (elapsed) to retrieve
5 polygons from a set of 300000 polygons.

Distribution of a SIRO-DBMS Spatial Database is achieved using the distributed
database tools in the host rdbms.  Further support is provided by the SIRO-DBMS
'class' facility, which allows a spatial data set to be distributed on regional
computers with SIRO-DBMS accessing only relevant partitions of the data set.

SIRO-DBMS has been implemented in the C programming language.  It has been
ported to several UNIX workstations, including SUN, HP and PC systems. Versions
are available that use ORACLE, INGRES and INFORMIX as the kernel rdbms, although
any other rdbms with SQL and with host language interfaces are potentially
suitable.  SIRO-DBMS is being used within the Centre for Spatial Information
Systems for development of Geographic Information Systems.


  G. 3 DISIMP Image Processing
      -----------------------


Processing and analysis of spatial data has become increasingly important in
areas such as land resource management, mapping, mineral exploration,
agriculture and oceanography. Previously, comprehensive, flexible and
functional high performance image processing and analysis systems have not been
available. This gap has been bridged by an extensive suite of image processing
software, DISIMP, developed by The Centre for Spatial Information Systems of
the CSIRO's Division of Information Technology.

Featuring a sophisticated, icon-based user interface, DISIMP is an ideal tool
for any application involving restoration, analysis, enhancement and display of
digital images. DISIMP is now available on a growing range of computer systems,
which can be networked together to provide a flexible and expandable
distributed image processing workstation environment .

DISIMP has comprehensive facilities for processing digital images from many
different sources. The full integration of graphics with support for geographic
projections, provides GIS functionality. Imaging facilities include image
restoration and enhancement, geometric and intensity transformations,
statistical analysis and interactive colour image display.  Special facilities
are provided in DISIMP for analyzing multi-spectral images from the Landsat,
SPOT and NOAA satellites and for integrating these images with related data
involving topographic, geophysical and cultural properties.  The main
applications for DISIMP have therefore been in the analysis of remotely sensed
data and in image-based geographic data processing.

The modular and flexible design of DISIMP allows system builders to extend its
capabilities and to develop additional utilities as required for specific
applications.  The design provides an excellent base for the development of
production-oriented systems for specific applications, and allows DISIMP to be
configured as part of turnkey systems for image processing.

DISIMP has recently been released for the workstation/Unix environment and is

                                                                     117
available for SUN/SPARC and HP systems with various image displays.  The
software supports multi-host configurations of distributed workstations linked
into a host environment with tape and large scale storage facilities.  DISIMP
also supports a wide range of peripherals, including digitizers, interactive
image display systems and hardcopy devices.

DISIMP is being installed in a growing number of user sites, including Federal
and State government departments, universities, mineral exploration companies
in Australia. It is also in use in research, government and commercial groups
overseas.

 Software Functions and Organisation
 Version 4.1 of the software was released in 1988 and contains more than 125
utilities.  Version 4.1 supports the Apollo DN3000 and DN4000 workstations with
a Truevision VISTA display.  Version 5.0 runs on the SUN / SPARC under Xwindows
in 8-bit mode on the standard screen or in 24-bit mode with a RasterOps card.
The software is written in standard FORTRAN 77, but some low level routines for
bit manipulation and file access are provided in assembler (or C on UNIX
systems) to improve operational performance.

A menu-driven interface to the utilities has been implemented to assist users
unfamiliar with the capabilities of the packages and their utilities.  A modern
icon-based interface to control the interactive image has been developed for
bit-map graphics workstations.


Special Features of DISIMP

DISIMP is in demand as a general package for image processing applications
and as a base for further development.

Generalised image representation
 . device independence:  handles images on various devices (disc,
        magnetic, tape, display system, etc.) in a uniform way
 . detailed image information in a standard header and in ancillary
        data records
 . multi-image and multi-channel files
 . no limit to image dimensions or number of channels
 . binary, packed, integer, floating point and complex intensity
        data formats
 . geocoding for geographically-referenced data
 . special encoding for physically-based data

Flexible image transfer
 . user-defined image windowing and viewporting
 . variable expansion and sampling of images
 . intensity scaling and clipping
 . pixel aspect ratio correction
 . null value handling
 . error checking and reporting


Advanced image processing
 . generalised image correction, registration and rectification
 . integration of graphic and tabular data
 . generalised image/graphic handling
 . support for a range of geographic map projections
 . fast three-dimensional transformations

                                                                     118
       (relief shading, perspective, shadowing and stereo views)
 . colour space transformations based on human perception theory
 . colour display calibration and modelling for colour consistency
 . realistic scene synthesis:  coloured surfaces and transparencies

User-accessible subroutine libraries for
 . image and file handling
 . programming interactive applications
 . general image processing

Extensive user support
 . on-line help messages
 . menu-driven interface to utilities
 . comprehensive documentation and training
 . comprehensive support and maintenance

Details of the packages are documented in various publications:

       DISIMP Users' Guide
       DISIMP Utilities Reference Manual
       DISIMP Programmers' Guide
       -Part 1 Image Processing Base
       -Part 2 Common Display Interface
       -Part 3 File Formats and File Access
       DISIMP System Reference Manual
       Software Application Notes (series)
       Utility Users' Guide (series)
       DISIMP Release Notes

 A two-day course has been developed for training users at DISIMP sites, and is
offered as part of the installation procedure.  Users and collaborators are
welcome to spend time working with the Project Team in Canberra.

A User's Meeting is hosted regularly by the Project Team to discuss the
priorities for support activities and to exchange experiences at user sites.


  G. 4 ITA Interactive Location and Territory Planning
      -----------------------------------------------


ITA is a decision-support system designed to facilitate the solution of
location and territory planning problems.  Applications include location
planning for warehouses, schools, fire stations, and retail stores; electoral
reapportionment; and definition of administrative districts and sales
territories.  Areas under consideration for further development include
transportation network analysis and demand modelling for marketing
applications.

The emphasis on solving problems distinguishes ITA both from the
general-purpose geographic information systems and from specialized predictive
modelling packages.  ITA is designed to run on a graphics workstation, which
provides the basis for an easy, intuitively direct style of dialogue between
the system and its users.  No special knowledge of computing is needed for
effective use of the system:  most operations are invoked simply by using a
mouse to select items from menus.

Both automated and manual plan-making techniques are provided.  The manual

                                                                     119
techniques allow users of the system to make or modify plans directly, using a
mouse to select and assign objects on the workstation's graphical display
monitor.  The automated techniques are heuristic optimization procedures,
capable of addressing requirements such as efficiency in terms of
transportation costs, compactness in the shape of territories, restrictions on
territory size, connectivity constraints, and scope restrictions.

To enhance a planner's understanding of a problem or situation in its
geographical context, the plan-making procedures are closely integrated with a
number of powerful display techniques, based primarily on the use of maps.
These include functions such as zooming and panning, chloropleth display of
spatially referenced attribute data, geographical    attribute data,
geographical inquiry, and attribute data summaries.  ITA also provides
facilities for producing hard-copy output, in the form of printed reports and
plotted maps.

All the data used by the system is stored and managed in a relational database.
The database for collaborative projects in Australia is set up in terms of the
Census Collector Districts and other geographical entities defined by the
Australian Bureau of Statistics (ABS).  The ABS has provided most of the
spatially referenced data used in these projects, and the cartographic
components of the database have been obtained from the Australian Survey and
Land Information Group.  A database administrator's utility program called
ITA-ADMIN simplifies management of the database and allows ITA users to
introduce data from sources other than those mentioned above.

The primary version of ITA is currently based on the DECstation colour graphics
workstations, with the Ultrix (Unix System V) operating system and X11
graphics. The software is also available on SUN, HP Apollo and Intergraph
workstations.



  G. 5 CSIRO Division of Information Technology
      ----------------------------------------


The Division of Information Technology was established in 1985 as the result of
increasing demand for strategic research and development to assist the
Australian information industries.

The research activities of the Division concentrate on software-related aspects
of information technology, covering software engineering, information systems
and computer communications.  The Division has about 70 staff located in
laboratories in Sydney (headquarters), Melbourne and Canberra.

The Division collaborates with other research groups in CSIRO, academic
institutions and industry.  Consultants from these external groups assist the
Division in research planning and management.  Joint appointments are also
being made to focus the research efforts with other institutions, and visitor
exchange programs are being developed with overseas organisations.

As an example of its research associations, the Division is affiliated with the
Centre for Information Sciences Research at the Australian National University,
and the Canberra Laboratory of the Division is located on the ANU Campus.

The Division has a number of commercial agreements with industrial partners in
order to make its research results available to industry and to develop

                                                                     120
products for local and international markets.  These agreements cover software
licences, collaborative and contract research, product design and development
and consultancy.

The activities of the Divisional research programs are outlined below.

CENTRE FOR SPATIAL INFORMATION SYSTEMS

The Centre conducts research leading to the design, implementation and
application of computer based systems for processing geographic and spatially
referenced data.  The main research topics of the Centre involve key software
technologies:  expert systems, spatial data bases, image processing, computer
graphics, spatial analysis, computer mapping and distributed computing.
Software developed by this research is now being exploited by collaborative
programs with industry.

The research is being focussed on the requirements of systems for applications
including resource and environmental management, atmospheric and oceanographic
research, mineral exploration, public utilities and sales planning and
marketing.

As an example, a prototype information system is being developed with the CSIRO
Division of Wildlife and Ecology for monitoring seasonal weather conditions to
assist the management of pastoral properties in the Australian rangelands.

The Centre has established several joint research agreements with Australian
companies for product design and development, with the aim of developing
Australian products for the international market.  These agreemens are
supporting research on image processing and graphic techniques in collaboration
with several other research groups for applications in remote sensing, oil and
mineral exploration and biological analysis.  An interactive terrain modelling
package  is currently the subject of commercial negotiation.

The Centre is developing spatial inferencing techniques for use in "emergency"
planning systems, such as required in military command and control and in civil
emergencies.  The techniques involve "expert system" concepts to detect and
analyze conflicts for proposed tactical plans, given the constraints of
personnel, equipment, environmental conditions and threats.  This is a
collaborative project with the ANU Department of Computer Science, and the
Applied Research and Development Division of Computer Power.

SOFTWARE ENGINEERING

The program has a broad charter covering many aspects of software technology.
There are four main projects.

A collaborative project with the Royal Melbourne Institute of Technology is
investigating the use of multiple processors ('parallelism') to achieve
extremely fast computer systems.  The research is concentrating on algorithms,
programming methodologies and languages to exploit a particular model of
parallel architecture called "dataflow".  The main applications of this work
are currently in scientific computing and artificial intelligence.

Another project is concerned with the development of associative memory
techniques for high speed table searching and their implementation in hardware.
 A prototype implementation has been produced in collaboration with the
University of New South Wales and is now the subject of commercialization.
Associative memory techniques are key components in information systems and

                                                                     121
knowledge-based systems.

The program has considerable expertise in the software engineering of
knowledge-based (expert) systems, and has used its experience to tackle several
practical problems such as the re-engineering of the cotton pest management
system SIRATAC (with CSIRO Division of Plant Industry) and the analysis of the
results of thyroid assay blood tests (with Garvin Institute of Medical
Research).  Expert systems are becoming increasingly important for automating
industrial processes.

A new project on human-computer interfaces aims to develop techniques to
provide more effective means of communication between user and computer
systems.  These techniques will rely heavily on graphical representations and
will be compatible with the computer technology anticipated in the 1990s.

COMPUTER COMMUNICATIONS

Programs in computer communications undertake research on computer networking
and the development of digital communications services on these networks.  The
research aims to improve the current computer communications infrastructure in
the Australian academic and research environment and to assist manufacturers to
exploit the opportunities presented by the emerging international standards for
interconnection of different computer systems.

One program is concerned with the development of prototype systems for
communication services based on the Open System Interconnection (OSI) Reference
Model, which has been adopted by the International Standards Organization.
Members of the program participate in the development of standards for
communications services such as  file transfer, access and management (FTAM),
electronic directory services and distributed computing, in order to reduce the
product development time.  Products based on the emerging standards have
enormous sales potential in the international markets.

The program has established an extensive computer environment, with gateways to
Australian and international networks, for testing products and prototype
implementations of OSI standards.

Another program is concerned with the specification, validation and
implementation of protocols which underlie computer communication services.
This area called "protocol engineering" employs formal software engineering
techniques and aims to produce more efficient and more reliable implementations
of complex communications systems.

for further information contact:

The Information Officer,
CSIRO Div. Information Technology,
GPO Box 664,
Canberra 2601,
Australia.
Fax [phone]

                    CONTENTS

  1. OzGIS INTRODUCTION                                              4
  1. 1 Introduction                                                  4
  1. 2 Concepts                                                      4
  1. 3 Environment                                                   5
  2. SUMMARY                                                         7
  3. SYSTEM CONFIGURION                                             10
  3. 1 Introduction                                                 10
  3. 2  DOS system files                                            10
  3. 3  Standard EGA and VGA boards                                 10
  3. 4  Super VGA boards                                            11
  3. 5 Maths Coprocessor                                            16
  3. 6 Extra RAM                                                    16
  3. 7 Hardcopy configuration                                       16
  3. 8 Plotter setup                                                18
  3. 9 Mouse                                                        19
  4. BASIC CHOROPLETH MAPPING EXAMPLE                               20
  4. 1 OzCensus                                                     20
  4. 2 Example map                                                  20
  5. INTERACTIVE USER INTERFACE TO OzGIS                            23
  5. 1 Menus                                                        23
  5. 1. 1 Menu format                                               23
  5. 1. 2 Function keys                                             23
  5. 1. 3 Stacking selections                                       24
  5. 2 Questions                                                    24
  5. 3 Commands                                                     25
  5. 4 Graphic interaction                                          25
  5. 5 Pop-up                                                       26
  5. 6  Print file                                                  26
  6. OzGIS FILES                                                    27
  7. DEVICE FILES                                                   30
  8. OzGIS MAP TYPES                                                32
  8. 1 Attribute maps                                               32
  8. 1. 1 Bivariate zones map Example                               32
  8. 1. 2 Zones & sites Example                                     32
  8. 1. 3 Geographic (GIS) maps Example                             33
  8. 1. 4 Diagrams Example                                          34
  8. 2 Device files                                                 34
  8. 3 Presentations                                                34
  8. 4 Time Lapse Display (not available)                           35
  9. ATTRIBUTE SELECTION                                            36
  9. 1 Sequentially                                                 36
  9. 2 By number (position in file)                                 36
  9. 3 By attribute description                                     36
  9. 4 By arithmetic operation                                      36
 10. QUANTISATION                                                   37
 10. 0. 1 Quantisation Methods                                      37
 10. 0. 2 Quantisation Ranges                                       39
 10. 0. 3 Quantisation Lists                                        39
 11.  DISPLAY CONTROL & MAP DESIGN                                  41
 11. 0. 1  Map Quantisation Legends                                 41
 11. 0. 2 Overlays (GIS) legends                                    42
 11. 0. 3 Other Legends                                             42
 11. 0. 4 Text                                                      42
 11. 0. 5 Attribute Diagrams                                        42
 11. 0. 6 Displayed Colours (removed)                               43
 12. MAP REGIONS                                                    45

 12. 0. 1 Regions                                                   45
 12. 0. 2 Map List                                                  46
 12. 0. 3 Quantised Zones                                           46
 12. 0. 4 Quantised lines                                           47
 12. 0. 5 Quantised sites                                           47
 12. 0. 6 Line Overlays                                             47
 12. 0. 7 Polygon underlays                                         47
 12. 0. 8 Marker Overlays                                           47
 12. 0. 9 Name Overlays                                             48
 12. 0.10 Map Modification                                          48
 13.  MAP ANALYSIS                                                  49
 13. 0. 1 Map Reports                                               49
 13. 0. 2 Attribute Data Statistics                                 49
 13. 0. 3 Map Interrogation                                         49
 14. OzEnter DATA ENTRY                                             51
 14. 1 Introduction                                                 51
 14. 2 Demonstration Files                                          51
 14. 3 Example geographic and attribute data                        51
 14. 4 Example device files                                         52
 14. 5 Marker data files                                            52
 14. 6 Colour names data (no longer used)                           52
 15. OzData DATA PREPARATION                                        53
 15. 1 Attribute Files                                              53
 15. 2 Geographic Files                                             54
 15. 3 Palette Files (Removed from system)                          54
 15. 4 Colour Names Files  (Removed from system)                    55
 15. 5  Names Files                                                 55
 15. 6  Output to Data Files                                        55
 16. OzZone BUILDING ZONES FROM SEGMENTS                            56
 16. 1 Use                                                          56
 16. 2 Example                                                      56
 17. MAP PROJECTIONS (under development)                            58
 17. 1 Introduction                                                 58
 17. 2 Precision                                                    58
 17. 3 Latitude / longitude                                         58
 17. 4 Projections                                                  58
 17. 5 Ellipsoids                                                   59
 18. HARDCOPY MAP PRODUCTION                                        60
 18. 1 Overview                                                     60
 18. 2 Device files                                                 60
 18. 3 VECTOR Program                                               61
 18. 4 Example                                                      65
 19. OzTerr                                                         66
 20. OzCatch (NOT AVAILABLE YET)                                    67
 20. 1 Introduction                                                 67
 20. 2  SITE CATCHMENTS                                             67
  A. DATA SOURCES                                                   70
  A. 1 Australia                                                    70
  A. 1. 1 AUSLIG data                                               70
  A. 1. 2 Australian Bureau of Statistics                           70
  A. 2 New Zealand                                                  71
  A. 3 United Kingdom                                               71
  A. 4 Canada                                                       71
  A. 5 USA                                                          72
  A. 6 Others                                                       72
  B. MAP DATA FORMATS                                               73
  B. 1 Introduction                                                 73
  B. 2 Data Format                                                  73

  B. 2. 1 Description of File Formats                               73
  B. 3 Format of attribute files                                    74
  B. 3. 1 General                                                   74
  B. 3. 2 Standard format                                           74
  B. 3. 3 Sample attribute file DEMOATTR.DAT                        75
  B. 3. 4 Simple Attribute format (database format)                 75
  B. 3. 5 Sample simple attribute file DEMOSASA.DAT                 75
  B. 3. 6 Spreadsheet data formats                                  76
  B. 3. 7 LAMM format                                               76
  B. 3. 8 Comma delimited format                                    77
  B. 3. 9 Other attribute data formats                              78
  B. 4 Standard format of geographic files                          78
  B. 4. 1 General Information                                       78
  B. 4. 2 Structure of data                                         78
  B. 4. 3 Internal Data                                             79
  B. 4. 4 Comment Record                                            79
  B. 4. 5 Map Partition                                             80
  B. 4. 6 Zones Partition                                           80
  B. 4. 7 Line Partition                                            81
  B. 4. 8 Polygons Partition                                        81
  B. 4. 9 Segments Partition                                        82
  B. 4.10 Points Partitions                                         83
  B. 4.11 Sample boundaries geographic file DEMOZSEG.DAT            83
  B. 4.12 Sample geographic file DEMOZONES.DAT                      84
  B. 4.13 Sample lines geographic file DEMOLINES.DAT                85
  B. 4.14 Sample points geographic file DEMOPOINT.DAT               86
  B. 5 Format of polygon geographic files                           86
  B. 5. 1 Standard (not implemented)                                86
  B. 5. 2 Simple Format (SAS) Zone Files                            87
  B. 5. 3 Sample simple zones data file DEMOSASG.DAT                87
  B. 6 GIS / standard geographic file formats                       88
  B. 6. 1 DIME format                                               88
  B. 6. 2 DLG optional 3 format                                     89
  B. 6. 3 Gina format                                               91
  B. 6. 4 ANSII standard                                            93
  B. 6. 5 SIF format (not available)                                93
  B. 6. 6 DXF format (not available)                                93
  B. 7 Format of names files                                        94
  B. 7. 1 Sample names file DEMOATTR.DAT                            94
  B. 8 Format of colour names files (Removed from system)           94
  B. 9 Format of combine files                                      95
  B. 9. 1 Sample combine file DEMOCOMB.DAT                          95
  B.10 Format of presentation files                                 95
  B.10. 1 Sample presentation file                                  96
  B.11 Format of marker files                                       96
  B.11. 1 Sample marker file SQUARE.DAT                             97
  B.12 Format of device files                                       97
  C. GLOSSARY OF TERMS                                             103
  D. SYSTEM LIMITS                                                 112
  E. TROUBLE-SHOOTING                                              113
  F. OzGIS REFERENCES                                              114
  G. OTHER SPATIAL SOFTWARE                                        115
  G. 1 Background                                                  115
  G. 2 SIRO-DBMS Spatial Information in a Relational DBMS          115
  G. 3 DISIMP Image Processing                                     116
  G. 4 ITA Interactive Location and Territory Planning             118
  G. 5 CSIRO Division of Information Technology                    119