README 2.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869
  1. From: Glynn Clements <glynn*gclements.plus.com>
  2. Date: Mon, 18 Dec 2006 17:28:43 +0000
  3. List-Archive: <http://grass.itc.it/pipermail/grass-dev>
  4. The relevant files (all installed into $GISBASE/etc) are:
  5. 1. parms.table
  6. One line for each known projection. A sample entry:
  7. AEA:Albers Equal Area:LAT0=ask,23.0;LAT1=ask,29.5;LAT2=ask,45.5;LON0=ask,-96.0;X0=ask,0.0;Y0=ask,0.0
  8. The first field is the projection name, as used by the old geo.h file.
  9. AFAICT, the corresponding +proj= parameter is identical except in
  10. lower case.
  11. The remainder of the line (after the colon) is a semicolon-separated
  12. list of parameter definitions of the form parm=spec. The LHS is the
  13. parameter name as used by geo.h; these don't necessarily match the
  14. corresponding the proj parameter, but you can translate them using the
  15. desc.table file (see below).
  16. The RHS has two parts, separated by a comma. The first part is either
  17. "ask" or "noask", corresponding to whether or not g.setproj should
  18. prompt the user for a value. The second part is either "nodfl" or a
  19. default value. Note that the combination "noask,nodfl" never occurs;
  20. if an option is marked as "noask", there will always be a default
  21. value.
  22. 2. desc.table
  23. One line for each known parameter (other than +proj=). A sample entry:
  24. LON0:lon:lon_0:Central Meridian
  25. The first field is the parameter name as used by the old geo.h file,
  26. and as used in parms.table.
  27. The second field is the type, and can be one of:
  28. bool int float lat lon zone
  29. This determines the set of valid options for the parameter (the "zone"
  30. type corresponds to the UTM zone).
  31. The third field is the name of the corresponding proj parameter
  32. (without the leading "+"), and is the key stored in the PROJ_INFO
  33. file.
  34. The fourth field is a textual description of the parameter.
  35. 3. units.table
  36. One line for each known distance unit. A sample entry:
  37. feet:foot:0.3048
  38. The three fields are (in case it isn't obvious) the plural form of the
  39. name, the singular form, and the size of the unit in metres.
  40. However, note that g.setproj still has a fair number of special-case
  41. hacks. Some of those are useful-but-not-essential (e.g. automatically
  42. selecting the correct ellipsoid for certain projections), while others
  43. are necessary (e.g. the zone= and south parameters for UTM need to go
  44. into the WIND/DEFAULT_WIND files as well as the PROJ_INFO file).