

Geometry Parameters
Normally there is just one geometry, you use "geo", otherwise you would need "geo1", "geo2", etc.
Parameters in red are required, arameters in italics indicate deprecated parameters.
- URL or relative path of the polygons in "psc" format (with extension ".psc"). This kind of outline data set may be compressed and end in "psc.gz".
- or
URL or relative path of the circles in "cir" format (with extension ".cir"). The circle format is usually the result of a Dorling cartogram.
or
URL or relative path of the circles in "cxy" format (with extension ".cxy"). The circle format is usually the result of a Dorling cartogram.
ARC/INFO shapefile format: use shp2psc to convert such a file to the psc format.
- geoname *
- Name of the geometry which apears in the pop-up-menu (only when there is more than one geometry).
- nam / una / nau
- URL or relative path of the areal unit names (with extension ".nam")
una, nau : File of the same structure but saved as Unicode text. - lab / ula / lau
- URL or relative path of the areal unit labels (only for circles; default is the nam-file)
ula, lau : File of the same structure but saved as Unicode text. - filter
- Filter data set. Format of the filter dataset; description aside.
- filterW
- Weight data set (usually with extension ".wgt"); description aside. Normally, the absolute population number form the weights.
- hinumgeo
- Maximum number of geometry files ( 5 )
- geoorder
- Order of the geometry datasets how they appear on the menu (1, 2, 3, 4, ....).
- geo exclude
- Geometry datasets may be excluded from the menu. Example: (1, 2) = do not include geo1 and geo2).
geo*
Layers
In order to add elements like rivers, lakes, geometric forms, other boundaries etc. there is a layer concept. The layer parameter consists of a sequence number and a layer type and other description parameters.
- layer*
- The number (layer1, layer2, etc.) has no meaning but they have to be distinct.
- Sequence number. The layers were painted in the order of this number. By default the thematic map is on level 0, the legend on level 1 (just above the map). Layers below the thematic map get a negative number, layers above a number > 1. You can change also the postion of the map and the legend.
- Layer type. At the moment the following types are supported:
- 1: Legend (default: sequence=1)
- 2: "normal" geometries, as .psc or .cir
- 5: rectangle in world coordinates
- -5: rectangle in screen coordinates
- Fillcolor (not for legends)
- Bordercolor (not for legends)
- Line thickness (in test stage, at the moment just for polygon geometries), values: 0, 2, ... 9; The numbers define one pixel shifts, e.g. 25, 2457, 12345678 (25: the geometry is drawn three times: in original position, one pixel above and one pixel to the right).
1 2 3 4 • 5 6 7 8
Examples:
- <param name="layer1" value="-12,2,geometry/ch_lakes.psc, #111111, #222233,25">
<param name="layer5" value="13,-5,2, 2, 50, 60, #ff8800, #005500">
<param name="layer3" value="56,5,674244.3,228901.31,711900.8,278332.47, #0000dd, #ffff00">
<param name="layer4" value="88,1">
<param name="layer2" value="93,2,geometrie/zh_182.cir,none, #000000">
Previous page: Data Parameters || Next page: shp2psc: Shapefile to MAPresso geometry format
.psc format
This is a compact format for polygon boundaries. It can easily be derived from ArcGIS shapefiles (using the Java application shp2psc). It is recommended to use .psc instead of .shp.
.cir format
It has the following structure:
Row 1: number of observations;
Rows 2 to (nobs+1): ID / x / y / radius (tab delimitted).
Example:
171
1•667327.4•223303.5•1191.0
2•668476.4•227875.7•3048.0
3•661933.4•228675.1•1882.7
...
261•679561•242579•18159.9
.cxy format
Row 1: number of observations;
Rows 2 to (nobs+1): ID / x / y (tab delimitted).
These coordinates are used for graduated circle symbol maps.
Example:
182
1•679692•237256
2•676443•238036
3•677557•240977
...
272•685795 250878
.nam / .lab format
Unicode variants: .nau, .una / .lau, .ula
Names of the areal units, one (or two) per row in the same sequence as the polygons or circles. If there is a second name (after a tab), only the second column names appear as polygon labels.
Example:
Aeugst
Affoltern•Aff.
Bonstetten
...
Stadt Z$urich•Z$urich
.fil format
For each boundary:
number of areal unit on one side;
number of areal unit on the other side;
length of common boundary (tab delimitted). Please note: we use a serial number of the areal units and not the IDs. Borders to lakes or to polygons outside the covered region may have the same number for the to adjacent polygons.
Example:
1 2 3773.99738
1 9 2648.35318
1 12 115.0252
2 2 1345.30548
2 9 2999.51607
...
171 167 1613.47709
-999
There are different ways to generate a .fil filter. Here you find a R program and a provisional documentation for a 2 step process (ArcGIS + Excel).
.wgt format
It has the following structure: 1st row: number of observations; 2nd to (nobs+1)th row: ID / weight of unit ID (tab delimitted).
Example:
171
1•1542
2•10258
3•4165
...
261 340402