|Status:||Draft (under way)|
|Definition:||For the natural evaporation of water to allow harvesting of
|Drafted on:||5 August 2009 (UTC)|
(note: #Formatting_notes explains the unconventional order of the following sections.)
Related features/examples thereof
- reservoir_type=cooling: For cooling industrial waste water, e.g. nuclear power plant coolant
- reservoir_type=sewage: For the treatment of domestic water-born waste
- reservoir_type=tailings: Ore and waste materials discarded in ore-treatment and mining processes, in water
- reservoir_type=water_storage: The "traditional" use of the word.
While NaCl salt evaporators are of ancient origin and by far the most prevalent, many use-cases would benefit from a heirarchy of different types of the common ancestor class "reservoir". Designing this heirarchy early-on will make the renderers more scalable/maintainable.
Tactically, closer alignment with the US National Hydrography Dataset (NHD) schema will make the imported data more precise and useful; the USGS/NHD heirarchy is also eminently sensible for mapping (and scientific) purposes.
Mineral evaporators and chemical settling ponds are key features of many EPA Superfund cleanup site projects.
TODO: images from PD sources (USGS map standards).
- Standards for National Hydrography Dataset - High Resolution -- describes the feature heirarchy used in the NHD, definitions of these features, and the criteria the USGS uses to determine which features/characteristics to capture and map.
- Part 5: Publication Symbols, Standards for 1:24,000- and 1:25,000-Scale Quadrangle Maps, and Part 6: Publication Symbols.... -- how USGS map features are rendered and printed.
As US Gov't publications, all three of the above are available for image snarfing to help create renderings.
I have formatted this proposal somewhat differently than the norm, in something of an "upside-down" order. I've put what I think are the most important technical facts first, to more objectively describe the facts of the poroposal.