This proposed agreement is new. Its terms are subject to revision by the Lawrence Berkeley National Laboratory (LBNL) legal department. If you wish to accept this offer, you will need to sign a statement releasing LBNL from any liability resulting from inaccuracies in the density-equalized maps, or resulting from our delays in producing them. The wording of that statement has not yet been finalized.
LBNL's uncompensated efforts fall in the same category as proposal development, and may not take precedence over currently funded projects. The benefit to LBNL is our enhanced potential for soliciting new funding, through increased public awareness of the DEMP technique,
We do not guarantee that your map can be successfully density equalized, especially if the population density is highly non- uniform. Minor topological errors are to be expected, for polygons having zero or very small population.
If you plan to use the maps to analyze cases of disease or other discrete events, we do NOT require your individual case records. It is your responsibility to obtain the case data and to develop the statistical techniques for analyzing the density-equalized maps. Please read carefully "Appropriate Use of Density Equalized Maps."
In return for providing this service we require:
The following four files should returned by e-mail to firstname.lastname@example.org, either as quoted text within a single ASCII message, or as quoted ASCII (not binary) enclosures.
format: geo1 geo2 geo3 geo4 pts pop1 pop2 pop3 pop4 example: 6 1 1251 0 4 1247 1.52 15 1.06E+02 6 1 1252 0 7 612 0. 9 2.12E+03 6 2 1412 0 5 0 4.21 12 0.00E+00 etcFile 2 contains npoly lines, one for each polygon. Each line contains four integer geocodes (geo1,geo2,geo3,geo4); the number of points (pts) in the polygon; and up to four non-negative population fields (pop1,pop2,pop3,pop4). The order of polygons in file 2 must be the same as in files 3 and 4.
Each line in file 2 (including internal lakes if any are present) must have a unique set of geocodes (geo1,geo2,geo3,geo4). If you use fewer than four geocodes, fill the unused fields with zero.
The number of points in the polygon (greater than or equal to 3). Do not include repeated endpoints. The sum of the "pts" column in file 2 must be equal to npts, which is the number of lines in file 4.
May not be negative. If you use fewer than four population fields, fill the unused fields with zero.
format: geo1 geo2 geo3 geo4 desc example: 6 1 1251 0 "Bloomington county" 6 1 1252 0 "Tracyville tract 1252" 6 2 1412 0 "New Paltz township" etcFile 3 contains npoly lines, one for each polygon. Each line contains four integer geocodes (geo1,geo2,geo3,geo4), and a character field "desc". The order of polygons in file 3 must be the same as in files 2 and 4.
as in file 2.
The name of the geographic area, surrounded by double quotes. Brief comments may be included (within the same quotes).
format: x y example: -35.1534 52.3058 -35.5476 52.3022 -35.5432 52.7190 -35.1481 52.7155 -35.7043 48.1565 -35.0104 48.1449 etcFile 4 contains npts lines, one for each point in each polygon. In each polygon, points should be listed in counter-clockwise order. Do NOT repeat the starting point of each polygon. The choice of x and y coordinates is arbitrary, but for geographic data the preferred choice is degrees of longitude and latitude, respectively. Values of west longitude and south latitude should be negative. The order of polygons in file 4 must be the same as in files 2 and 3.
File 4 must be topologically correct, which implies: (a) points shared by adjacent polygons have exactly the same x and y coordinates (b) no two points in any polygon have the same coordinates (c) no polygon has zero area (d) no segments in the map intersect each other (e) the area enclosed by the external boundary is exactly equal to the sum of all the polygon areas.