Difference between revisions of "Category:Historical Documents Working Group"

From Linked Earth Wiki
Jump to: navigation, search
( Pages with a poll, Working Group )
m (→‎Tambora's original structure)
m
 
(80 intermediate revisions by the same user not shown)
Line 4: Line 4:
  
 
== Overview ==
 
== Overview ==
−
In the Linked Earth context, a [[:Category:Working_Group|working group]] (WG) is a self-organized coalition of knowledgeable experts, whose activities are governed [[:Category:Working_Group|herewith]]. This page is dedicated to the discussion of data and metadata standards for [http://linked.earth/ontology/#document '''historical documents'''], and aims to formulate a set of recommendations for such a standard.
+
[[File:Floodswithtitle.png|thumb|right|alt=Pages Floods Working Group Logo|Credit: [http://www.pastglobalchanges.org/ini/wg/floods/intro Pages Floods Working Group]]]
 +
[[File:CRIAS.png|thumb|right|alt=Pages Floods Working Group Logo|Credit: [http://www.pastglobalchanges.org/173-initiatives/working-group/crias/1876-intro Pages CRIAS Working Group]]]
 +
 
 +
In the Linked Earth context, a [[:Category:Working_Group|working group]] (WG) is a self-organized coalition of knowledgeable experts, whose activities are governed [[:Category:Working_Group|herewith]]. This page is dedicated to the discussion of data and metadata standards for [http://linked.earth/ontology/#document '''historical documents'''], and aims to formulate a set of recommendations for such a standard. This working group is an initiative of the [http://www.pages-igbp.org/ini/wg/floods/intro Pages Floods Working Group] but also related to the [http://www.pages-igbp.org/ini/wg/crias/intro Pages CRIAS Working Group].
  
 

Members of 'Historical Documents Working Group'

    This working group contains only the following member.

    M

 
__MEMBERS__
−
 
  
 
== Sources ==
 
== Sources ==
 +
[[File:Sources Historical Documents.png|thumb|right|alt=Historical Documents|Sources / Historical Documents]]
  
 
Data is usually compiled from different historical sources.
 
Data is usually compiled from different historical sources.
 
The LiPD data structure supports several [[:Category:Publication_(L) | Publication]], that is normally used for referring to the publication
 
The LiPD data structure supports several [[:Category:Publication_(L) | Publication]], that is normally used for referring to the publication
 
describing the data. So this data cluster can be used for historical sources as well, in addition to the current publication describing
 
describing the data. So this data cluster can be used for historical sources as well, in addition to the current publication describing
−
the data.  
+
the data. It is related to known standards as Dublin Core or BibTEX
 +
 
 +
* Source-ID for later reference
 +
* Source Type (string), i.e. newspaper, book, ...
 +
* Source Author
 +
* Source Title
 +
* Publication Year
 +
* Publication Date
 +
* Journal Title
 +
* Publisher
 +
* Url to Source (i.e. to PDF)
 +
* DOI of Source (almost never exist for historical documents if not published as data compilation)
 +
 
 +
 
 +
* Source
 +
 
 +
<poll>
 +
Should the 'Source ID' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
The source type is a string i.e. book, newspaper, diary, ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options One#Source_Type|Enumerator Options]] 
 +
 
 +
<poll>
 +
Should the 'Source Type' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Author of Source' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Title of Source' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Publication Year' of the (original-) source be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Publication Date' of the (original-) source be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Journal' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Publisher' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'URL to Source' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
  
 +
<poll>
 +
Should the 'DOI of Source' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
  
 
== Scans, Pages ==
 
== Scans, Pages ==
Line 24: Line 124:
  
 
== Quotes ==
 
== Quotes ==
 +
[[File:Quote Historical Document.png|thumb|right|alt=Translated Quote|Original and translated quote from historical source]]
  
 
Out of each sources, several quotes could be extracted by transcribing them.
 
Out of each sources, several quotes could be extracted by transcribing them.
Line 37: Line 138:
 
* License: License of the quote (cc)
 
* License: License of the quote (cc)
 
* DOI: DOI, the quote is published
 
* DOI: DOI, the quote is published
 +
 +
 +
 +
*Quote
 +
 +
<poll>
 +
Should the 'Quote-ID' (unique for dataset) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
<poll>
 +
Should the 'Reference to Source' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
<poll>
 +
Should the Format of 'Reference to Source' be:
 +
A unique (in scope of dataset) id
 +
A shortform like Author(Year)
 +
</poll>
 +
 +
<poll>
 +
Should the 'Page of Quote' inside Source be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
<poll>
 +
Should the 'URL to Scan' of Page containing the Quote be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
The language (and protolanguage) is a string i.e. de, ar, fr, en,...
 +
 +
For details on possible options see [[Historical Documents Enumerator Options One#Language_Option|Enumerator Options]] 
 +
 +
<poll>
 +
Should the 'Language' of Quote or its Translation be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
<poll>
 +
Should the 'Protolanguage' of Quote be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
See i.e. [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes Wikipedia Language Code]
 +
 +
<poll>
 +
Should the 'Language Format' of Quote be in:
 +
ISO 639-1 (en, de, ar, zh, ...)
 +
ISO 639-2/T (eng, deu, ara, zho, ...)
 +
ISO 639-2/T (eng, ger, ara, chi, ...)
 +
ISO 639-3 (eng, ger, ara, zho, ...)
 +
Plain english (english, german, arabic, chinese, ...)
 +
Plain native (english, deutsch, العربية, 中文)
 +
Other (please add comment)
 +
</poll>
 +
 +
<poll>
 +
Should the 'Quote itself' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
The license type is a string i.e. cc-by, cc-by-nc, ...
 +
 +
For details on possible options see [[Historical Documents Enumerator Options One#License_Type|Enumerator Options]]
 +
 +
<poll>
 +
Should the 'License' of published Quote be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
<poll>
 +
Should the 'DOI' of published Quote be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
  
 
== Events ==
 
== Events ==
Line 47: Line 251:
 
* a time
 
* a time
  
−
and contains a climate related data. (to be defined)  
+
and contains a climate related data. (to be defined)
  
 +
=== Position ===
 +
[[File:Position Historical Documents.png|thumb|right|alt=Position used for Historical Documents|Position used for Historical Documents]]
  
 +
The position different than for the other archive types is not fixed. Usually a compilation of several sources refer to different scattered locations.
 +
The location usually can be named but might covers different scales (continent, country, area, city, street,...) and terrain types (city, river, sea, ...).
 +
It best corresponds to the '''Geospatial metadata''' of LiPD; see also http://schema.org/Place .
  
−
(source_id,quote_id,license_event,doi_event,position_description,name_position,location_type,latitude,longitude,geometry,elevation,geonames_id,calendar,begin_year,begin_month,begin_day,begin_hour,begin_timestamp,end_year,end_month,end_day,end_hour,end_timestamp,codeset_id,codeset_description,category,path,node_label,scale_label,scale_unit,value_label,value_index,average,variance,si_unit,si_average,si_variance
 
−
)
 
  
−
https://sweet.jpl.nasa.gov/
+
*Position
  
−
== Example ==
+
<poll>
 +
Should the 'Identifier of Location' (unique for dataset) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
  
−
=== Tambora's original structure ===
+
<poll>
 +
Should the 'Name of Location' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
  
−
* Sources
+
The location type is a string i.e. country, city, river, mountain, ...
  
−
{| class="wikitable"
+
For details on possible options see [[Historical Documents Enumerator Options One#Location_Type|Enumerator Options]]
−
|-
+
−
! source_id !! title !! comment_source !! author !! date !! publisher !! signature !! language_source !! note !! mediatype !! annote !! collection !! edition !! volume !! issue !! pages !! isbn !! issn !! address !! organization !! url !! date_format !! license_source !! doi_source !! sourcetype !! year !! institution !! month !! booktitle !! editor !! chapter !! journal !! series !! school !! chronic !! crossref !! key !! howpublished
+
−
|-
+
−
| 10664 || "Annales oder Jahrs-Geschichten der Baarfüseren oder Minderen Brüder S. Franc. ord. insgemein Conventualen genannt, zu Thann, Bd. 2" || <Transrisk-Source-ID>3701</> || "Tschamser, Malachias" || 1864-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || Colmar ||  ||  || yyyy-MM-dd || "not published" ||  || other || 1864 || ADHR ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10668 || "Quellentexte zur Witterungsgeschichte Europas von der Zeitwende bis zum Jahre 1850, Bd. 4" || <Transrisk-Source-ID>5687</> || "Weikinn, Curt" || 2002-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || yyyy-MM-dd || "not published" ||  || other || 2002 || UBFr ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 11407 || "Freiburger Zeitung" ||  || Journal ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || #http://az.ub.uni-freiburg.de/show/fz.cgi?cmd=showpic&ausgabe=01&day=16b3&year=1930&month=05&project=3&anzahl=4# ||  || "not published" ||  || other ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10727 || "L'Alsace au dix-huitième siècle au point de vue historique, judiciaire, administratif ... et religieux, Bd. 1" || <Transrisk-Source-ID>719</> || "Hoffmann, Charles" || 1907-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || Colmar ||  ||  || yyyy-MM-dd || "not published" ||  || other || 1907 || BNU ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10865 || "Die Hungerkrisen, ihre Ursachen und Folgen nach der Lichtenauer Pfarrchronik (1726-1830)" || <Transrisk-Source-ID>3614</> || "Uibel, Ludwig" || 1994-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || 401-419 ||  ||  ||  ||  ||  || yyyy-MM-dd || "not published" ||  || other || 1994 ||  ||  ||  ||  ||  || "Die Ortenau" ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10863 || "Staufener Chronik, Bd. 5" ||  || "Hugard, R." ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || "not published" ||  || other ||  ||  ||  ||  ||  ||  || "Staufener Wochenblatt vom 17. 3.1883" ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10674 || "Geschichte der Stadt Müllheim" || <Transrisk-Source-ID>1845</> || "Sievert, A. J." || 1886-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || Müllheim ||  ||  || yyyy-MM-dd || "not published" ||  || other || 1886 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 11552 || Acher-Rench-Zeitung ||  || Journal ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || "not published" ||  || other ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10763 || "Die Wiese ein Fluss und seine Geschichte" || <Transrisk-Source-ID>2796</> || "Golder, Eduard" || 1991-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || Basel ||  ||  || yyyy-MM-dd || "not published" ||  || other || 1991 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10671 || Kollnau || <Transrisk-Source-ID>1915</> || "Vetter, August" || 1990-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || Waldkirch ||  ||  || yyyy-MM-dd || "not published" ||  || other || 1990 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10862 || "Baierische National-Zeitung" ||  || Journal ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || #https://books.google.de/books?id=zBxEAAAAcAAJ&printsec=frontcover&dq=zeitung+1812&hl=de&sa=X&ved=0ahUKEwiW656aqcjNAhUoAcAKHaDyC7QQ6AEIHjAA#v=onepage&q=%C3%BCberschwemmt&f=false# ||  || "not published" ||  || other ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10685 || "Les moulins du Sundgau (Bd. 2): Le bassin de la Largue" || <Transrisk-Source-ID>3733</> || "Gutknecht, Pierre" || 1999-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || 191 ||  ||  || Riedisheim ||  ||  || yyyy-MM-dd || "not published" ||  || other || 1999 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|-
+
−
| 10794 || "Die Hauschronik der Wiesenbronner Familie Hüßner. Ihre Aufzeichnungen zu Wirtschaft, Geschichte, Klima und Geographie Mainfrankens von 1750-1894)" || <Transrisk-Source-ID>7636</> || "Glaser, R.; Schenk, W.; Schröder, A. (Hg.)" || 1991-01-01 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || Würzburg ||  ||  || yyyy-MM-dd || "not published" ||  || other || 1991 ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||
+
−
|}
+
  
−
* Quotes
+
<poll>
 +
Should the 'Type of Location' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Latitude of Location' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Longitude of Location' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Altitude/Elevation of Location' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the '(JSON)-Geometry of Location' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'Reference to Geonames' by ID be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the extracted corresponding quote piece = 'Phrase' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
=== Time ===
 +
The time derived for an event from historical documents is usually more precise than for other archive types.
 +
Often the uncertainty is just days or even hours. So it would be best to code the absolute date by gregorian
 +
calendar and a string of type ISO 8601. Optionally an absolute gregorian year (may be with floating point fraction
 +
instead of integer) can be calculated as well.
 +
 
 +
*Time
 +
 
 +
<poll>
 +
How should the event time primarily be defined:
 +
ISO 8601 mid-point time string and uncertainty in days (float)
 +
Start and end time as ISO 8601 string
 +
Gregorian year (float)
 +
</poll>
 +
 
 +
The original sources often contain the information in calendar notation different than gregorian.
 +
Julian calendar was used in Europe in historical time, but outside Europe other calendars existed
 +
or still exist, likeweise in chinese or arabic documents.
 +
 
 +
The calendar type is a string i.e. country, city, river, mountain, ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options One#Calendar_Options|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the time optionally be coded in 'Other Calendar Systems':
 +
yes
 +
no
 +
</poll>
 +
 
 +
If so, which parameters for start and end should be considered?
 +
 
 +
<poll>
 +
Cycle:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Year:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
<poll>
 +
Season / Solar Term:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Month:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Day:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Hour:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
It is also possible to extract the time related text from the quote and add it to a field 'phrase':
 +
 
 +
<poll>
 +
Phrase:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
 
 +
 
 +
=== Event itself ===
 +
 
 +
The event refers to the quote, maybe directly to the source, to the chronology/timing and the position/location.
 +
It also holds the coding of the phenomena, here it gets complicated - see next section.
 +
 
 +
<poll>
 +
Should the Event refer to 'Location' of described Phenomena:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the Event refer to 'Timing' of described Phenomena:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the Event refer to 'Quote' (by ID) where Phenomena is described:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the Event refer directly to the 'Source' where Quote describing Phenomena can be found:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the Event contain a 'DOI' when data-set is published somewhere:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
The license type is a string i.e. cc-by, cc-by-nc, ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options One#License_Type|Enumerator Options]] 
 +
 
 +
 
 +
<poll>
 +
Should the Event contain a 'License' when data-set is published somewhere:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
== Phenomena/Coding ==
 +
[[File:Indices.png|thumb|right|alt=Indices Historical Climatology|Indices used to code Phenomena in Historical Climatology / Documents]]
 +
 
 +
A lot of information can be found inside historical documents. Thereby the coding schema is complex. A lot of coding is done by using indices.
 +
Some examples and their coding to illustrate this:
 +
 
 +
* The weather was extremely warm -> temperature index + very hot (+3)
 +
* A lot of rain fell in December -> precipitation type + rain & precipitation amount + more than usual (+1)
 +
* The water level was 13 feet -> water level + value:13.0 + tolerance:1.0 + unit:feet
 +
* The drought lead to bad harvest of potatoes -> harvest + harvest amount: less than usual (-1) & potatoes / precipitation amount: less than usual (-1)
 +
* The wheat harvest was little but the wine quality was good -> harvest + harvest amount: less than usual (-1) & wheat / harvest + harvest quality: better than usual (+1) & wine
 +
 
 +
+: one dimensional combination
 +
 
 +
&: two (or more) dimensional combinations
 +
 
 +
/: two different events (i.e. cause vs effect)
 +
 
 +
(Coding tree as used in tambora.org can be found [https://www.tambora.org/index.php/coding/tree/list?translate=off here].)
 +
 
 +
To handle the innumerable amount of different parameters, it makes sense to group them into thematic clusters.
 +
 
 +
=== Cluster: Temperature ===
 +
 
 +
Inside this cluster are all temperature related parameters: Temperature measurements, descriptive temperature levels, freezing events, ...
 +
 
 +
 
 +
*temperature-cluster
 +
 
 +
Levels i.e. can be
 +
-3: very cold
 +
-2: cold
 +
-1: cool
 +
  0: normal temperature
 +
+1: warm
 +
+2: hot
 +
+3: very hot
 +
 
 +
<poll>
 +
Should the 'temperature level' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the temperature have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Trend i.e. can be
 +
-1: decreasing
 +
  0: constant
 +
+1: increasing
 +
 
 +
<poll>
 +
Should the 'temperature trend' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Temperature value is a measured, numerical value with units
 +
Standards of other archive types can be used here
 +
 
 +
<poll>
 +
Should the 'temperature value' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'temperature unit' (measurement) be:
 +
SI - Kelvin
 +
Degree Celcius
 +
Degree Fahrenheit
 +
Any
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'tolerance of the temperature' measurement be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll> 
 +
 
 +
The temperaure type is a string i.e. air, water, wind, ...
 +
It can be combined with the above quantitative parameters
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Two#Temperature_Type|Enumerator Options]] 
 +
 
 +
<poll>
 +
Should the 'temperature type' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
 
 +
The following two parameters are of type boolean - they happen or not.
 +
 
 +
<poll>
 +
Should the occurrence of 'freezing/frost/ice' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 +
<poll>
 +
Should the occurrence of 'thawing/melting' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
=== Cluster: Precipitation ===
 +
 
 +
[[File:Precipitation by type.png|thumb|right|alt=Precipitation Types|Precipitation Types https://commons.wikimedia.org/wiki/File:Precipitation_by_type.png]]
 +
 
 +
Inside this cluster are all precipitation related parameters: long- and short-term amounts, intensities, measurements, type of precipitation, ...
 +
 
 +
 
 +
*precipitation-cluster
 +
 
 +
Levels of long-term precipitation (weeks... month) i.e. can be
 +
-3: extremely dry
 +
-2: very dry
 +
-1: dry
 +
  0: normal precipitation
 +
+1: wet
 +
+2: very wet
 +
+3: extremely wet
 +
 
 +
<poll>
 +
Should the 'long-term precipitation level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the long-term precipitation level have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Levels of short-term precipitation (hours ... days) i.e. can be
 +
  0: no precipitation
 +
+1: some precipitation
 +
+2: much precipitation
 +
+3: very much precipitation
 +
+4: extremely much precipitation
 +
 
 +
<poll>
 +
Should the 'short-term precipitation level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the short-term precipitation level have:
 +
5
 +
4
 +
3
 +
other
 +
</poll>
 +
 
 +
The amount of precipitation is a measured value for a given  time frame (see timing)
 +
 
 +
<poll>
 +
Should the 'precipitation amount' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'precipitation amount unit' (measurement) be:
 +
meter [m] (SI)
 +
centimeter [cm]
 +
millimeter [mm]
 +
liter per square meter [l/m^2]
 +
other
 +
any
 +
</poll>
 +
 
 +
The intensity of precipitation is a measured value, often a peal value
 +
 
 +
<poll>
 +
Should the 'precipitation intensity' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'precipitation intensity unit' (measurement) be:
 +
meter per second [m/s] (SI)
 +
centimeter per hour [cm/h]
 +
millimeter per day [mm/d]
 +
millimeter per hour [mm/h]
 +
liter per square meter per hour [l/m^2*h]
 +
other
 +
any
 +
</poll>
 +
 
 +
The precipitation type is a string i.e. rain, snow, hail, dew, sleet, ...
 +
It can be combined with the above quantitative parameters, but can also stand alone
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Two#Precipitation_Type|Enumerator Options]] 
 +
 
 +
<poll>
 +
Should the 'precipitation type' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
 
 +
Levels of snow cover i.e. can be
 +
  0: no snow cover
 +
+1: thin snow cover
 +
+2: deep snow cover
 +
 
 +
<poll>
 +
Should the 'snow cover level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the snow cover level have:
 +
4
 +
3
 +
2
 +
1
 +
other
 +
</poll>
 +
 
 +
The snow depth is static (accumulated), whereas the snow fall is per time-frame
 +
 
 +
<poll>
 +
Should the 'snow depth' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'snow depth unit' (measurement) be:
 +
meter [m] (SI)
 +
centimeter [cm]
 +
millimeter [mm]
 +
other
 +
any
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'snow fall' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'snow fall unit' (measurement) be:
 +
meter [m] (SI)
 +
centimeter [cm]
 +
millimeter [mm]
 +
other
 +
any
 +
</poll>
 +
 
 +
=== Cluster: Hydrology ===
 +
 
 +
see also [http://wiki.linked.earth/Category:Floods_Working_Group Floods Working Group]
 +
 
 +
Inside this cluster are all hydrology related parameters: water levels, flood magnitudes,  ...
 +
 
 +
*hydrology-cluster
 +
 
 +
Flood levels (magnitude) i.e. can be
 +
  0: no flood
 +
+1: small flood
 +
+2: flood above average
 +
+3: flood of the century
 +
 
 +
<poll>
 +
Should the 'flood level' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Flood extend i.e. can be
 +
+1: regional
 +
+2: supra-regional
 +
 
 +
<poll>
 +
Should the 'flood extend' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'water level value' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'water level unit' (measurement) be:
 +
SI - meter
 +
Centimeter
 +
Feet
 +
Any
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'tolerance of the water level' measurement be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll> 
 +
 
 +
 
 +
<poll>
 +
Should the 'flood recurrence time' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'flood recurrence unit' be:
 +
SI - seconds
 +
days
 +
month
 +
years
 +
Any
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'tolerance of flood recurrence' measurement be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'discharge value' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'discharge unit' be:
 +
SI - cubic meter per second
 +
liter per second 
 +
Any
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'tolerance of discharge' measurement be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
 
 +
<poll>
 +
Should the 'flow velocity' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'flow velocity unit' be:
 +
SI - meter per second
 +
kilometer per hour
 +
miles per hour
 +
Any
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'tolerance of flow velocity' measurement be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
 
 +
low water levels i.e. can be
 +
  0: normal level
 +
-1: low water level (limited use)
 +
-2: very low water level (severely limited use)
 +
-3: extremely low water level (no water)
 +
 
 +
<poll>
 +
Should the 'low water level' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Trend i.e. can be
 +
-1: decreasing
 +
  0: constant
 +
+1: increasing
 +
 
 +
<poll>
 +
Should the 'water level trend' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Storm surge levels i.e. can be
 +
  0: no storm surge
 +
+1: average storm surge
 +
+2: strong storm surge
 +
+3: extreme storm surge
 +
 
 +
<poll>
 +
Should the 'storm surge level' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Following parameters are of type boolean
 +
 
 +
<poll>
 +
Should the 'occurrence  of erosion' (boolean) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'occurrence  of flash flood' (boolean) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'occurrence of sediment deposition' (boolean) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'occurrence of large plains flooded' (boolean) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'occurrence of long standing water' (boolean) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
=== Cluster: Clouds, Visibility ===
 +
 
 +
Inside this cluster are all cloud and visibility related parameters: cloud types, cloud cover, humidity, fog, ...
 +
 
 +
 
 +
*cloud-visibility-cluster
 +
 
 +
Levels i.e. can be
 +
  0:  0% sunny clear
 +
+1:  25% mostly sunny
 +
+2:  50% partly cloudy
 +
+3:  75% very cloudy
 +
+4: 100% fully cloudy
 +
 
 +
<poll>
 +
Should the 'cloud cover' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the cloud cover have:
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
The cloud type is a string i.e. cumulus, nimbostratus, cirrus, ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Two#Cloud_Type|Enumerator Options]] 
 +
 
 +
<poll>
 +
Should the 'cloud type' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
 
 +
Levels of humidity level i.e. can be
 +
-1: dry air
 +
  0: moderate humid air
 +
+1: humid air
 +
 
 +
 
 +
<poll>
 +
Should the 'humidity level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the humidity have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'relative humidity' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'relative humidity' be:
 +
0..1
 +
%
 +
Any
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'tolerance of relative humidity' measurement be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Levels of visibility i.e. can be
 +
-2: very poor visibility
 +
-1: poor visibility
 +
  0: average visibility
 +
+1: good visibility
 +
+2: very good visibility
 +
 
 +
<poll>
 +
Should the 'visibility level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the visibility have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Following parameters are of type boolean
 +
 
 +
<poll>
 +
Should the 'occurrence of fog' (boolean) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'occurrence of dust' (boolean) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
=== Cluster: Wind, Air Pressure ===
 +
 
 +
*wind-pressure-cluster
 +
 
 +
wind force levels (Beaufort) i.e. can be
 +
  0: calm
 +
  +1: light air
 +
  +2: light breeze
 +
  +3: gentle breeze
 +
  +4: moderate breeze
 +
  +5: fresh breeze
 +
  +6: strong wind
 +
  +7: high wind
 +
  +8: fresh gale
 +
  +9: strong gale
 +
+10: storm
 +
+11: violent storm
 +
+12: hurricane
 +
 
 +
<poll>
 +
Should the 'wind force level' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
wind directions i.e. can be
 +
  0: north
 +
  +1: north-east
 +
  +2: east
 +
  +3: south-east
 +
  +4: south
 +
  +5: south-west
 +
  +6: west
 +
  +7: north-west
 +
  +8: change of direction
 +
  +9: any direction
 +
 
 +
<poll>
 +
Should the 'wind direction' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'wind speed' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'wind speed unit' (measurement) be:
 +
SI - meter per second
 +
Kilometer per hour
 +
Miles per hour
 +
Any
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'tolerance of wind speed' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll> 
 +
 
 +
The type of wind is a string i.e. foehn, gust, khamsin, sandstorm, sirocco, snowstorm, tornado, ...
 +
It can be combined with the above quantitative parameters, but can also stand alone
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Two#Wind_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'type of wind' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
air pressure levels i.e. can be
 +
-1: low pressure
 +
  0: normal pressure
 +
+1: high pressure
 +
 
 +
<poll>
 +
Should the 'air pressure level' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
air pressure trend i.e. can be
 +
-1: falling pressure
 +
  0: steady pressure
 +
+1: raising pressure
 +
 
 +
<poll>
 +
Should the 'air pressure trend' (indices) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'air pressure value' (measurement) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'air pressure value' be:
 +
SI - Pascal
 +
Hectopascal
 +
Bar
 +
Torr
 +
millibar
 +
Any
 +
other
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'tolerance of air pressure' measurement be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
 
 +
=== Cluster: Phenomena, Natural Hazards ===
 +
 
 +
Inside this cluster are all parameters related to natural phenomena or hazards: earthquake, tsunami, aurora borealis, meteoroid, comet, solar eclipse, moon eclipse, halo, avalanche, rainbow, landslide, wildfire,  ...
 +
 
 +
*phenomena-hazard-cluster
 +
 
 +
The phenomena type is a string i.e. earthquake, tsunami, aurora borealis, meteoroid, comet, solar eclipse, moon eclipse, halo, avalanche, rainbow, landslide, wildfire,  ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Two#Phenomena_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'phenomena type' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Phenomena Intensity i.e. can be
 +
  0: none
 +
+1: weak
 +
+2: middle
 +
+3: strong
 +
 
 +
<poll>
 +
Should the 'phenomena intensity' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the phenomena intensity have:
 +
5
 +
4
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
=== Cluster: Society ===
 +
 
 +
Inside this cluster are all parameters related to society affections: damage, death, illness, social problems
 +
 
 +
 
 +
*society-cluster
 +
 
 +
The type of damage is a string i.e. animals, buildings, bridges, houses, dams, plants, forest, traffic routes, ships, harvest, hunger, thirst, ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Damage_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'type of damage' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the occurrence of 'mitigation' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Type of mitigation is a string i.e. charity, exemptions, indemnity, subsidies ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Mitigation_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'type of mitigation' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'number of injuries' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
Should the 'number of deaths' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Illness is a string i.e. bubonic plague, fever, measles, cholera, ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Illness_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'illness' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Social problems is a string i.e. migration, poverty, rioting, theft, unemployment ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Problem_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'social problem' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Levels of affected people i.e. can be
 +
  0: none
 +
+1: few
 +
+2: some
 +
+3: many
 +
 
 +
<poll>
 +
Should the 'affected people level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the affected people level have:
 +
5
 +
4
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
=== Cluster: Plant Phenology ===
 +
 
 +
[[File:Acer saccharinum phenology.jpg|thumb|right|alt=Plant Phenology|Plant Phenology https://commons.wikimedia.org/wiki/File:Acer_saccharinum_phenology.jpg]]
 +
 
 +
 
 +
Inside this cluster are all parameters related to plants: blossom, leave fall, harvest, ...
 +
 
 +
 
 +
*plant-phenology-cluster
 +
 
 +
Levels of harvest quantity i.e. can be
 +
-2: very low harvest volume
 +
-1: low harvest volume
 +
  0: average harvest volume
 +
+1: high harvest volume
 +
+2: very high harvest volume
 +
 
 +
 
 +
<poll>
 +
Should the 'harvest quantity level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the harvest quantity level have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Levels of harvest quality i.e. can be
 +
-2: very poor crop quality
 +
-1: poor crop quality
 +
  0: average crop quality
 +
+1: good crop quality
 +
+2: very good crop quality
 +
 
 +
 
 +
<poll>
 +
Should the 'harvest quality level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the harvest quality level have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
The plant type is a string i.e. apples, wheat, hay, wine, potato, cherries, ...
 +
It can be combined with the above quantitative parameters or the below observations, but can also stand alone
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Plant_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'plant type' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
The type of observation is a string i.e. blossom, harvest, leave emergence, leave fall, planting, sowing, ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Plant_Observation_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'type of plant observation' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Levels timing i.e. can be
 +
-1: earlier than usual
 +
  0: usual timing
 +
+1: later than usual
 +
 
 +
<poll>
 +
Should the 'timing level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
=== Cluster: Animal Phenology ===
 +
 
 +
 
 +
Inside this cluster are all parameters related to animals: health, arrival, departure, breeding,  ...
 +
 
 +
 
 +
*animal-phenology-cluster
 +
 
 +
Levels of absolute quantity i.e. can be
 +
  0: none
 +
+1: few
 +
+2: some
 +
+3: many
 +
 
 +
 
 +
<poll>
 +
Should the 'absolute quantity level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Levels of relative quantity i.e. can be
 +
-1: less than usual
 +
  0: average number
 +
+1: more than usual
 +
 
 +
<poll>
 +
Should the 'relative quantity level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
The animal type is a string i.e. birds, stork, sheep, swine, snail, locusts, ...
 +
It can be combined with the above quantitative parameters or the below observations, but can also stand alone
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Animal_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'animal type' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
The type of observation is a string i.e. arrival, departure, breeding, shearing, slaughtering, death, injuries,  ...
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Animal_Observation_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'type of animal observation' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
Levels timing i.e. can be
 +
-1: earlier than usual
 +
  0: usual timing
 +
+1: later than usual
 +
 
 +
<poll>
 +
Should the 'timing level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
=== Cluster: Economy ===
 +
 
 +
[[File:Hypermarkt Merkur Österreich - Wien Floridsdorf - 05.04.2017 - 6.jpg|thumb|right|alt=Super Market|Super Market  https://commons.wikimedia.org/wiki/File:Hypermarkt_Merkur_%C3%96sterreich_-_Wien_Floridsdorf_-_05.04.2017_-_6.jpg]]
 +
 
 +
 
 +
Inside this cluster are all parameters related to economy: price-, supply-, demand- / -level, -trend, goods
 +
 
 +
*economy-cluster
 +
 
 +
Price level i.e. can be
 +
-1: low price
 +
  0: normal price
 +
+1: high price
 +
 
 +
<poll>
 +
Should the 'price level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the price level have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Price trend i.e. can be
 +
-1: decreasing price
 +
  0: constant price
 +
+1: increasing price
 +
 
 +
<poll>
 +
Should the 'price trend' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the price trend have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Supply level i.e. can be
 +
-1: low supply
 +
  0: normal supply
 +
+1: high supply
 +
 
 +
<poll>
 +
Should the 'supply level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the supply level have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Supply trend i.e. can be
 +
-1: decreasing supply
 +
  0: constant supply
 +
+1: increasing supply
 +
 
 +
<poll>
 +
Should the 'supply trend' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the supply trend have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Demand level i.e. can be
 +
-1: low demand
 +
  0: normal demand
 +
+1: high demand
 +
 
 +
<poll>
 +
Should the 'demand level' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the demand level have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
Demand trend i.e. can be
 +
-1: decreasing demand
 +
  0: constant demand
 +
+1: increasing demand
 +
 
 +
<poll>
 +
Should the 'demand trend' be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
<poll>
 +
How many levels should the demand trend have:
 +
7
 +
5
 +
3
 +
2
 +
other
 +
</poll>
 +
 
 +
The market good is a string i.e. apples, wheat, meat, food, energy, fodder, hay, wood, ...
 +
It can be combined with the above quantitative parameters
 +
 
 +
For details on possible options see [[Historical Documents Enumerator Options Three#Market_Good_Type|Enumerator Options]]
 +
 
 +
<poll>
 +
Should the 'market good' (string, options, choice) be:
 +
Essential
 +
Recommended
 +
Desired
 +
Dropped (as not needed)
 +
</poll>
 +
 
 +
 
 +
== Example ==
 +
 
 +
Rename LiPD file extension from zip to lpd
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! source_id !! quote_id !! text !! page !! comment_quote !! license_quote !! doi_quote !! language_quote
+
! Description !! Tambora-Files !! LiPD-Files !! Remarks
−
|-
+
−
| 10664 || 140599 || "Telegramm von Neu-Breisach an Kreispräsidenten:↵Rhein fortwährend steigend, von 7 bis 10 Uhr 25 Centimeter. 6 Centimeter höher als 1852" ||  || <Transrisk-Source-ID>3363</>↵<Transrisk-Quote-ID>dc0e32f4bab79c60e056e6e8728a2bda</> || "not published" ||  ||
+
−
|-
+
−
| 10664 || 140593 || "Nachricht der berittenen Gendarmerie-Brigade aus Neu-Breisach:↵Der Rhein ist fast schon wieder in sein altes Bett zurück getreten." ||  || <Transrisk-Source-ID>3361</>↵<Transrisk-Quote-ID>8c68e85a03847407fc7429d0821af659</> || "not published" ||  ||
+
−
|-
+
−
| 10668 || 139058 || "Neckar-Überschwemmung infolge anhaltenden Regenwetters." || 75 || <Transrisk-Source-ID>5694</>↵<Transrisk-Quote-ID>317069c7bab02f08c67a601b3725f2e1</> || "not published" ||  ||
+
−
|-
+
−
| 11407 || 141736 || "Willstätt, 15. Mai. Die in den letzten Tagen niedergegangenen heftigen Regenmassen bedingten ein rasches Anschwellen der Kinzig, die nun Hochwasser führt, das nicht mehr weit von dem Stand des Jahres 1896 steht. Weite Wiesen und Ackergelände sind überflutet, und auch manchen Gärten hat das Hochwasser schon übel mitgespielt. Der Qualität des Grases ist dies über die Wiesen flutende trübe Hochwasser nicht besonders dienlich. Diese Wiesen sind darnach schwer zu mähen, da sich große Mengen Schlamm in dem Grase verfangen und ablagern. Immer noch ist die Kinzig im Steigen begriffen und wälzt pro Sekunde 150 Kubikmeter (das sind 1500 Hektoliter) Wasserdurch das Willstätter Wehr." ||  || <Transrisk-Source-ID>4546</>↵<Transrisk-Quote-ID>2f4b50424a87b91a6e75d7411b538735</> || "not published" ||  ||
+
−
|-
+
−
| 10727 || 139255 || "Brèche de 91 toises sur la digue principale entre Sundhoffen & Andolsheim" || 177 || <Transrisk-Source-ID>411</>↵<Transrisk-Quote-ID>b8fb462e0a75c68b1df18144be6cec47</> || "not published" ||  ||
+
 
|-
 
|-
−
| 10865 || 139666 || "Eine Gefährdung der Äcker und Wiesen, die in allen Jahreszeiten drohte, war das Hochwasser. Im Winter und im Frühjahr konnte dieses noch nicht allzuviel Schaden anrichten, nicht einmal im Sommer, wenn das Hochwasser die Fluren nur wenige Tage überflutete. So geschah es im Juli 1813, daß das Hochwasser des Rheins die ganzen Felder zwischen Lichtenau und Grauelsbaum überschwemmte (die Au!), so daß das Wasser an manchen Stellen vier Schuh hoch stand. Pfarrer Schoch nutzte diese Gelegenheit, um zusammen mit Revierförster Götz und Apotheker Wagner von der Schwarzbachbrücke aus im Kahn nach Grauelsbaum zu fahren. Nur an hoch gelegenen Stellen schauten noch die Ähren des Getreides über den Wasserspiegel. In Grauelsbaum standen nur noch vier Häuser auf dem Trockenen. Bei den meisten lief das Wasser zu den Fenstern hinein. Die Leute hatten in Lichtenau Zuflucht gefunden. Das Hochwasser verschwand aber sehr schnell wieder. Es war beträchtlicher Schaden entstanden, der aber nicht so groß war, wie man befürchtet hatte. Die Regierung spendete den Grauelsbaumern Getreide und Kartoffeln." || 412 || <Transrisk-Source-ID>3614</>↵<Transrisk-Quote-ID>6724b94f8e69225b899d8b1995f5f83d</> || "not published" ||  ||
+
| Flood Example || [[Media:flood_tambora_csv.zip]] || [[Media:Exp0000.tambora.2017.zip]] ||   
 
|-
 
|-
−
| 10863 || 139664 || "1813 (16. Juli) um Siepuliersonntag ist der Bach sehr stark angeloffen und das Wasser ist am folgenden Montag so stark angeloffen, dass es für größer erachtet wurde, als im Jahr 1758, nur ist in dieser Zwischenzeit der Bach in eine bessere Richtung gelenkt und von gar zu starken Umränk in bessere gründen gemacht worden. Es ist unweit das ganze Mattfeld oder- und unterhalb der Stadt zum großen Teil verrissen und mit Steinen und Sand bedeckt worden. Den unteren Ortschaften wurden wieder die Häuser und Matten mit Wasser versetzt, allwo auch mehrere Personen das Leben verloren haben.“" || 191 || "<Transrisk-Source-ID>1976</>↵<Transrisk-Quote-ID>5e8b6c6494589df3d75af66a5581fb66</>↵##DATUM##↵{#Tambora/Link/Quote /Id(139662) /Text(Ergänzung Datum) #}" || "not published" ||  ||  
+
| To-Do || To-Do || To-Do ||
 
|-
 
|-
−
| 10674 || 139662 || "10. bis 12. Juli, große Überschwemmung des Klemmbachs; Verwüstung des ganzen Tals, schwere Schäden in Müllheim." || 117 || <Transrisk-Source-ID>1850</>↵<Transrisk-Quote-ID>b52b18fa2d702678fd141b7007b3de67</> || "not published" ||  ||
+
| To-Do || To-Do || To-Do ||
−
|-
+
−
| 10664 || 139658 || "Etat de situation statistique et morale de la Commune de Strasbourg:↵L'Ill déborde le 28 Mars, et inonda tous les bas fonde riverains. L'inondation ne fut partier considérable, et ne causa pas de dommages remarquable." ||  || <Transrisk-Source-ID>3497</>↵<Transrisk-Quote-ID>ebce39617b25009ff43577a62c6e4fc7</> || "not published" ||  ||
+
−
|-
+
−
| 11552 || 142295 || "Hochwasser wie im Durchschnitt alle 50 Jahre einmal↵Rhein-Pegel fünf Meter über Normal-Stand↵Rheinvorland vollständig überflutet - Hohe Schäden an der Baustelle für das Kulturwehr↵Kehl (no). Am gestrigen Vormittag um 10 Uhr war die größte Gefahr vorbei: von da ab sank der Rheinwasserstand im Raum Kehl wieder, langsam zwar , aber stetig. Bis zu diesem Wendepunkt um 10 Uhr aber war der Rhein angeschwollen, bis die Wasseroberfläche um rund fünf Meter über der durchschnittlichen Höhe lag, die Durchflußmenge sich vervierfacht hatte. Im Bereich der Stadt Kehl entstanden keine bisher bekanntgewordenen Schäden, dafür aber an der Baustelle für das Kulturwehr bei Marien. 100 000 Mark, so Oberregierungsrat Wündisch, ist die untere Grenze für die Schäden, insgesamt werden sie sicherlich höher sein, genaue Angaben sind noch nicht möglich. Um zwei bis vier Wochen werden die Bauarbeiten verzögert. Das gesamte Rheinvorland war überflutet, die Schiffahrt war längere Zeit blockiert. Es handelte sich, so die Wasser- und Schiffahrtsverwaltung, um ein Hochwasser, das im langfristigen Durchschnitt nur alle 50 Jahre einmal vorkommt.↵Das Hochwasser am Oberrhein hatte sich schon in den Tagen zuvor angekündigt. Die Nebenflüsse des Rheins hatten ihm auf seiner ganzen Länge ungewöhnliche Wassermengen zugeführt, bedingt durch starke Regenfälle und gleichzeitige Schneeschmelze in den Bergen. Teilweise lagen die Nebenflüsse schon am frühen Dienstag mehrere Meter über dem normalen Wasserstand.↵In Kehl trat der Rhein in der Nacht von Dienstag auf Mittwoch über die Ufer. Er überflutete auf beiden Seiten das Rheinvorland; der Wasserstand erreichte jedoch in Kehl nicht die Höhe des Damm-Durchlasses bei der Großherzog-Friedrich-Straße. Die gesamte Rheinpromenade stand jedoch rund um die Uhr unter Wasser.↵Die Bauleitung beim Kulturwehr Marien war auf die Entwicklung vorbereitet. Regelmäßig kamen die Wasserstandsmeldungen vom Pegel in Rheinfelden am Hochrhein. Veränderungen, die sich dort zeigen, treten in gleicher Form zwölf bis 16 Stunden später in der Höhe von Kehl auf.↵Aus der erst kürzlich fertiggestellten Baugrube für den zweiten Bauabschnitt konnten somit bereits im Laufe des Dienstags die Geräte und Maschinen herausgeholt werden. Sehr viel waren allerdings noch nicht drin, da mit den Betonierarbeiten noch nicht begonnen worden war. Um 1 Uhr in der Nacht von Dienstag auf Mittwoch entschloß sich die Bauleitung dann, die Baugrube zu fluten. Die getroffenen Sicherheitsvorkehrungen reichten nicht mehr aus, um den Wassermengen Herr zu werden: sie waren ausgelegt für ein Hochwasser, das im Durchschnitt alle zehn Jahre einmal vorkommt.↵Das gestrige Hochwasser allerdings war ein sogenanntes 50jähriges Hochwasser. Während im Jahresdurchschnitt rund 1 000 Kubikmeter Wasser je Sekunde den Rhein hin unterfließen, waren es gestern rund 4 000 Kubikmeter - vier Millionen Liter! - je Sekunde.↵Obwohl die Baugrube beim Kulturwehr rechtzeitig geflutet wurde, brach dennoch ein Teil des Dammes, der als Baugrubenumschließung gebaut worden war. Eine Transformatorenstation fiel ins Wasser, zwei Notstromaggregate, eine Baracke mit Spanngliedern und Schalteilen wurde hinweggespült: über Kilometer hinweg wurden diese Schalteile vom Fluß verteilt.↵Auf einer Insel im Strom waren die dort stationierten Baukolonnen vom Festland abgeschnitten, die Verbindung war abgebrochen. Ein Bauarbeiter erlitt einen Kollaps, er mußte mit dem Rettungshubschrauber ins Krankenhaus gebracht werden. Erst am späten Mittwochvormittag gelang es mit Hilfe der Wasserschutzpolizei und der Bereitschaftspolizei Lahr, die ein großes Schlauchboot mit starkem Motor zur Verfügung hat, die eingeschlossenen Bauarbeiter-Kolonnen auszutauschen. Weitere Personenschäden waren nicht zu beklagen.↵Um rund zwei bis vier Wochen werden die Bauarbeiten am Kulturwehr verzögert, erklärte Oberregierungsbaurat Wündisch. Im vergangenen Herbst waren die Bauarbeiten ziemlich genau zur Hälfte abgewickelt gewesen. Allerdings auch nicht ungestört: ein ähnliches, wenn auch nicht ganz so hohes Hochwasser hatte im August 1978 die Bauleitung gezwungen, schon die erste Baugrube vorübergehend zu fluten.↵Von den Baukolonnen war die Straße am Damm, der am weitesten am Rhein liegt, bei Erkennen der Gefahr mit Eichenbalken, abgedichtet mit Plastikplanen, gesperrt worden. Diese Maßnahmen, so der bauleitende Oberregierungsrat Wündisch, habe sich als ausreichend erwiesen. Von ganz geringen Wassermengen abgesehen sei das Gelände jenseits der Balken-Sperre trocken geblieben.↵Durch ein Regulierungsbauwerk im Damm sei allerdings Wasser ins Hinterland gedrungen. Die Entscheidung, dieses Regulierungsbauwerk nicht zu schließen, sei allerdings dennoch richtig gewesen, weil sich sonst das aus dem Hinterland zum Rhein fließende Wasser ohnehin gestaut hätte und damit das gleiche Ergebnis erzielt worden wäre.↵Vom Pegel in Rheinfelden wurden seit Dienstagabend um 20 Uhr fallende Wasserstände gemeldet. Am Mittwochmorgen um 10 Uhr, also 14 Stunden später, wirkte sich dies in Kehl aus: mit 5,84 Meter beim Pegel Kronenhof wurde der höchste Wasserstand registriert, in den darauffolgenden fünf Stunden, also bis 15 Uhr, fiel der Pegelstand um zwölf Zentimeter auf 5,72 Meter. Im Laufe des Abends und der Nacht setzte sich dieser Rückgang kontinuierlich fort." ||  || <Transrisk-Source-ID>2659</>↵<Transrisk-Quote-ID>a5443c4fe6588c64cc604ec660d17a0b</> || "not published" ||  ||
+
−
|-
+
−
| 10763 || 139652 || "Zerstörung der Kleinhüningerbrücke (Steg) über die Wiese durch Hochwasser:↵24.4: wurde beim letzten grossen Wintergewässer die Hälfte des Steges bei Kleinhüningen nebst einem Joch weg und in den Rhein geschwemmt." || 86 || <Transrisk-Source-ID>2797</>↵<Transrisk-Quote-ID>9f24db0e6fc9e65644a02ae3c6eebfcd</> || "not published" ||  ||
+
−
|-
+
−
| 10671 || 139650 || "Das erste große Hochwasser nach der Eingliederung des Breisgaues in das Großherzogtum Baden suchte das Elztal vom 4. auf den 5. April 1812 heim. Es richtete am Hammerwerk beträchtlichen Schaden an. Rheinbaudirektor Fischer besichtigte die Schäden persönlich. Die Landesreste (Damm) war im Bereich des Rechens fortgerissen worden, der Kleine Rechen hatte großen Schaden genommen, der Rechenkanal war beschädigt, der große Rechen hatte jedoch mit geringen Schäden standgehalten. Aber unter der linken Holzwand des kleinen Rechens war die Gemeindeallmende eingebrochen. Diese Schadstelle wurde ursprünglich durch ein Faschinat von Reiswellen und Pfählen ausgebessert. Der Gesamtschaden belief sich auf rund 1300 fl. Einen kleinen weiteren Schaden ließen die Beständer André und Kunzer auf ihre Kosten ausbessern. Die hohen städtischen Stellen aber wollten vor der Kostenübernahme geklärt wissen, ob es sich tatsächlich um ein außerordentliches Hochwasser gehandelt habe und ob möglicherweise das Holzflößen die Hauptursache für den Schaden gewesen sei.↵Das führte zur folgenden Schilderung des Hochwasserverlaufs:↵Die Hammerwerkspachtungs Compagnie Andre und Kunzer“, hat nach Opern ihren Frühjahrs–Holzfloß durch den herrschaftlichen Floßmeister Andreas Furtwängler aus dem Oberen Simonswald anfangen lassen. Zur Zeit, wo man sich wegen einem vorhandenen mittelmäßig starken Wasser den besten Erfolg versprach: dieses Wetter, oder vielmehr das günstige Wasser hielt den 1 .ten, 2.ten und 3 .ten April abwechselnd an.↵Am 3 .ten Nachts wurde die Witterung kälter, es schneite über die Gebürge, und das Wasser fiel bis morgens merklich. Den 4 .ten Freitags trat Thauwetter ein, es fing bey warmem Winte zu regnen an, und der neu gelegte Schnee verschmolz; dieses Ereignis bringt in diesem engen Thale, in welches so viel Hohe Gebürge des Schwarzwaldes ihren Schoos ausleeren, jederzeit ein starkes wasser hervor. Der Floßmeister, welcher schon so lange Jahre in dieser Gegend das Flößen besorgt, und aus 40jähriger Erfahrung diese wilden Thalbäche kennt; ließ schon am Sonntag den 4 .ten Morgens mit dem Flößen, oder eigentlich Holzeinwerfen einhalten, weil er wegen dem großen Wasser eine Gefahr besorgte. Allein, weil das Wasser in den früheren Tägen vom 1.ten, 2.ten und 3.ten April schon stark angelaufen war, und sich der Schnee durch den Regen am 4.ten zu schnell ausgelöst hatte, konnte dies den Schaden nicht mehr verhindern, das Wasser wuchs zu einer außerordentlichen Höhe, trieb alles in einer Strecke von 4 bis 4 ½ Stunden in dem Simonswälder Bache und im Elzfluße gelegene holz, Rieß und Unrath auf einmal mit sich fort, und legte sich in ungeheuren Massen vor den großen Rechen. Die Stadt Waldkirch, welche gleich nach dem Hammerwerk ihren Holzbedarf für den Sommer, und Spätjahr, aus der Haslach im Simonswalde flößen wollte, und besorgte, das Floßwasser möchte zu bald aufhören, erbaute am Ausfluß des Haselbaches in den Simonswälderbach, einen Vorrechen, und zog bey selbem das vorgeflößte Holz wieder aus. Wegen gleicher Anschwellung des Haselbaches verlohr die Stadt in der Nacht vom 4.ten auf den 5.ten auch diesen Rechen, was zu Vermehrung des Unraths vor dem großen Rechen beygetragen haben mag.↵Die pacht Compagnie des Hammerwerks hatte die ganze Zeit viele Arbeiter, und Leute zum Einlassen des Holzes am Rechen, und Samstags Abends befand sich noch alles im besten Zustande, der Rechen war offen und das Wasser hatte seinen ordentlichen Durchlauf.↵Abends fing auch der Regen in der unteren Gegend sehr heftig an, es wurde ganz finster, löschte die angezündeten fackeln und Feuer aus, und wuchs von 7. 8. und 9. Uhr an , nicht nur sehr stark, sondern trieb die in dem Bache, und Flusse herumgelegenen Holzmassen in kurzer Zeit vor den Rechen, verstopfte denselben mit Reiß, und anderen unrath  und verursachte die außerordentliche Anschwellung des Wassers vor demselben. ↵Abends 10 Uhr gieng der Werkszimmermann Schneider mit einer Fackel über den Rechen, um zu sehen, wie es mit der Landveste stehe; er entdeckte dann als schon einer oberhalb auf der Landveste verursachten Einriß; holte den Zimmermeister Böhler herzu, und Baude befürchteten die Entstehung unausweichlichen Schadens.↵Das Wasser mußte durch die Schwellung immer mehr und mehr anwachsen, und stieg wenigstens 14 Schuhe Hoch über seine gewährliche Fläche; die Landveste, welche Linkerseits niederer war, als der Damm Rechter Seits muß schon lange vor letzterem überschwemmt worden seye.↵Die Arbeiter konnten es wegen dem zu hoch gestiegenen Wasser auf dem Damme rechter Seits nicht mehr aushalten, und mußten sich an den Berg zurückziehen, woselbst sie den anbrechenden Tag erwarteten, und mit demselben den Verlust der Landveste, nebst den übrigen Beschädigungen erblikten.↵Sontags den 5.ten legte sich der Regen; es trat heitere Witterung ein, und das Wasser fiel wieder.↵Wenn man unter auserordentliche Flußanschwellungen jene zu zählen pflegt, die eine außerordentliche Höhe erreichen, so wird es wohl keinem Zweifel unterliegen, daß man das vom 4.ten auf den 5.ten April angelaufene Wasser unter die Zahl der auserordentlichen rechnen müsse.↵Diese Behauptung unterstützt das Ermessen mehrer unbedenklicher Kunstverständigen.↵Der herrschaftliche Floßmeister Andreas Furtwängler aus dem Simonswald behauptet, daß in der Zeit von 40 Jahren kein einziges so ungewöhnlich starkes Wasser vorfanden gewesen seye, und zwar zur Zeit, als es der Kirnerischen Floßgesellschaft den Rechen durchgerißen habe. Der Herrschaftliche Werkszimmermann Mathias Schneider, welcher 10 Jahre auf dem Werk angestellt ist, und der Zimmermeister Böhler von hier, der 16 bis 18 Jahre auf demselben arbeitet, und bey jedem Floß als Arbeiter am Rechen und anderen Einsichtungen, gebraucht worden, behaupte, daß sie seit ihrer Anwesenheit auf dem Werke, ein so starkes, und so schnell angeschwollenes Hasser, wie jenes vom 4.ten auf den 5.ten April gewesen, noch nicht zu denken wüßten«.↵So berichtete am 16. Oktober 1812 der Amtsvorstand Krederer von Waldkirch. Er behauptete aber auch, daß das Flößen des Holzes die Hauptursache des Hochwassers gewesen sei, weil es sonst nirgends Schaden angerichtet habe. Dennoch habe es sich bei dem Hochwasser um ein außerordentliches gehandelt. Die einzige Möglichkeit, den Schaden zu vermeiden, wäre das Durchhauen des Rechens gewesen, aber das habe sich während der finsteren  Nacht nicht bewerkstelligen lassen. (GLA. 391/20061)." || 239 || <Transrisk-Source-ID>1921</>↵<Transrisk-Quote-ID>c5c2703940323b1eba97dad0328a49d3</> || "not published" ||  ||
+
−
|-
+
−
| 10862 || 139657 || "Berichte aus Frankfurt vom 6. April erzählen: Durch das schon seit einigen Wochen angehaltene Regenwetter trat der Main am 4. dergestalt aus seinen ufern, dass er in die Stadt drang, und die Mainzer- und Saalgasse überschwemmte. Viele Läden und Gewölbe standen ganz, andere halb unter Wasser. Die Buden längs dem Main waren sämtlich überschwemmt [...]. Am Samstag Abends stand der Main 14 Fuß 9 Zoll über seiner mittlern Wasserhöhe; Sonntags den 5. fiel er um anderthalb Fuß. Das Mainzer Marktschiff konnte nicht ankommen, weil der Leinpfad überschwemmt war." || 3 || <Transrisk-Source-ID>8613</>↵<Transrisk-Quote-ID>77ab9948345a1f1ce30d83c6ecc0cd6d</> || "not published" ||  ||
+
−
|-
+
−
| 10685 || 139304 || "Ignatius Guligag, 27 ans, se noya à Altenach. Il fut inhumé le 31 mars après autopsie judiciaire ( Alexsys, cahier 5, vol.1, Altenach, D 312)." || 12 || <Transrisk-Source-ID>3744</>↵<Transrisk-Quote-ID>e773cac9d7032605e326ed58ca0d338a</> || "not published" ||  ||
+
−
|-
+
−
| 10794 || 139335 || "* Am 9. Februar riß das Eis von der langen Brücke 2 Joche weg. * ↵(Glaser, R.; Schenk, W.; Schröder, A. (Hg.) (1991): Die Hauschronik der Wiesenbronner Familie Hüßner. Ihre Aufzeichnungen zu Wirtschaft, Geschichte, Klima und Geographie Mainfrankens von 1750-1894)" ||  || <Transrisk-Source-ID>7636</>↵<Transrisk-Quote-ID>5598deb7fe8898f64c5bff49a249dce5</> || "not published" ||  ||  
+
−
 
+
 
|}
 
|}
−
 
−
=== Same data in LiPD structure ===
 

Latest revision as of 09:41, 20 May 2019


Overview

Pages Floods Working Group Logo
Credit: Pages Floods Working Group
Pages Floods Working Group Logo
Credit: Pages CRIAS Working Group

In the Linked Earth context, a working group (WG) is a self-organized coalition of knowledgeable experts, whose activities are governed herewith. This page is dedicated to the discussion of data and metadata standards for historical documents, and aims to formulate a set of recommendations for such a standard. This working group is an initiative of the Pages Floods Working Group but also related to the Pages CRIAS Working Group.

__MEMBERS__

Sources

Historical Documents
Sources / Historical Documents

Data is usually compiled from different historical sources. The LiPD data structure supports several Publication, that is normally used for referring to the publication describing the data. So this data cluster can be used for historical sources as well, in addition to the current publication describing the data. It is related to known standards as Dublin Core or BibTEX

  • Source-ID for later reference
  • Source Type (string), i.e. newspaper, book, ...
  • Source Author
  • Source Title
  • Publication Year
  • Publication Date
  • Journal Title
  • Publisher
  • Url to Source (i.e. to PDF)
  • DOI of Source (almost never exist for historical documents if not published as data compilation)


  • Source
Should the 'Source ID' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id B79ACAACB8CF7E76F57C95CD94752C33

The source type is a string i.e. book, newspaper, diary, ...

For details on possible options see Enumerator Options

Should the 'Source Type' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 4B9828E446262CD2D25ECC5954AFC6B7

Should the 'Author of Source' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 1B1140A471D5BB004C42E2EAFF87FF82

Should the 'Title of Source' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 6DA9EFA61E43E3E9AC0548BFCEBE06B8

Should the 'Publication Year' of the (original-) source be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 0AE3099A39B686B6E2FA714D32A1A349

Should the 'Publication Date' of the (original-) source be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 00CFBB515E6BDF4EE42BF9828B76D2A9

Should the 'Journal' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 167D16FB083F91F3C90B643123FE4165

Should the 'Publisher' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 263B14776BDC462C240EB6B9903B72E5

Should the 'URL to Source' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 39F0D42A6060034B89801A81175A88E0

Should the 'DOI of Source' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id 07434CE6F44FD5F86CEC1CFF21C6A4E1

Scans, Pages

Each source can optionally have a bunch of images, that are the scans of the pages inside the source. Maybe this can be dropped for the LiPD format and only references to external images should be added to the quotes.

Quotes

Translated Quote
Original and translated quote from historical source

Out of each sources, several quotes could be extracted by transcribing them. Related data would most probably go into "measurementTables".

  • Quote-ID: For later reference
  • Reference to source: maybe short form like "Author()Year" is adequate
  • Page: String of the page(s) number where the quote is extracted from
  • Scan: Optional link(s) to externally stored image of this page(s)
  • Language: The language of the quote (or it's translation)
  • Protolanguage: The language the quote was written originally
  • Quote: The quote itself (UTF8)
  • License: License of the quote (cc)
  • DOI: DOI, the quote is published


  • Quote
Should the 'Quote-ID' (unique for dataset) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:58, 26 April 2019.
poll-id 6033CCA9D66D35A5EEFF9872F3A41308

Should the 'Reference to Source' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:58, 26 April 2019.
poll-id E06E94AB6F2809E712DA4FBE6E27F803

Should the Format of 'Reference to Source' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:23, 25 April 2019.
poll-id F1C4F26B5E53984D6C0994021A388A8B

Should the 'Page of Quote' inside Source be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:57, 26 April 2019.
poll-id D0013665A75E30D59E9E26E05AA1E345

Should the 'URL to Scan' of Page containing the Quote be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:58, 26 April 2019.
poll-id 9DBAD650333F97D3E145E7428F93D25A

The language (and protolanguage) is a string i.e. de, ar, fr, en,...

For details on possible options see Enumerator Options

Should the 'Language' of Quote or its Translation be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:58, 26 April 2019.
poll-id A1511268F490E690633AB5BCDF160B56

Should the 'Protolanguage' of Quote be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:58, 26 April 2019.
poll-id 747E4333DE595E07A8E2B050CC4136B3

See i.e. Wikipedia Language Code

Should the 'Language Format' of Quote be in:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:39, 2 May 2019.
poll-id 7719DDEE34608E157A81F436AB6BED82

Should the 'Quote itself' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:58, 26 April 2019.
poll-id 6C19394215C985AADC2879E46A03713C

The license type is a string i.e. cc-by, cc-by-nc, ...

For details on possible options see Enumerator Options

Should the 'License' of published Quote be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:58, 26 April 2019.
poll-id 2090D59A1031DE61B003019E590667EB

Should the 'DOI' of published Quote be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:58, 26 April 2019.
poll-id 1EA2DE3BF1F3CE01B45E55CF0BFACFE8

Events

Events, that are more like interpretations of the quote would go into "model part". Each events refers to

  • a quote
  • a position
  • a time

and contains a climate related data. (to be defined)

Position

Position used for Historical Documents
Position used for Historical Documents

The position different than for the other archive types is not fixed. Usually a compilation of several sources refer to different scattered locations. The location usually can be named but might covers different scales (continent, country, area, city, street,...) and terrain types (city, river, sea, ...). It best corresponds to the Geospatial metadata of LiPD; see also http://schema.org/Place .


  • Position
Should the 'Identifier of Location' (unique for dataset) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 11002E6509CF5415CC40F739878EEE66

Should the 'Name of Location' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 8800AF586B10F0B9D40F2238D39C4A8B

The location type is a string i.e. country, city, river, mountain, ...

For details on possible options see Enumerator Options

Should the 'Type of Location' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 86BF2A1725BB8AAACDCAFC164A71E8B7

Should the 'Latitude of Location' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id C0F983783CA34024B49FE6DDE1C8EC6A

Should the 'Longitude of Location' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 45F59BF6EB37C3E76C639AEAD8365C83

Should the 'Altitude/Elevation of Location' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 5767C9A8EFD597296845A436C4225EFE

Should the '(JSON)-Geometry of Location' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 6C47D798ABA029EF52C68A69D4A5EF45

Should the 'Reference to Geonames' by ID be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id B6D7616215DA302C678140D96A837647

Should the extracted corresponding quote piece = 'Phrase' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id A77FD3F023BA869C63F1178079DD95BF

Time

The time derived for an event from historical documents is usually more precise than for other archive types. Often the uncertainty is just days or even hours. So it would be best to code the absolute date by gregorian calendar and a string of type ISO 8601. Optionally an absolute gregorian year (may be with floating point fraction instead of integer) can be calculated as well.

  • Time
How should the event time primarily be defined:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:48, 25 April 2019.
poll-id F5072947F0CB8D3862347216F0EFEB01

The original sources often contain the information in calendar notation different than gregorian. Julian calendar was used in Europe in historical time, but outside Europe other calendars existed or still exist, likeweise in chinese or arabic documents.

The calendar type is a string i.e. country, city, river, mountain, ...

For details on possible options see Enumerator Options

Should the time optionally be coded in 'Other Calendar Systems':
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:37, 25 April 2019.
poll-id A808B3FBF7319B5B317A05F072FD6DA9

If so, which parameters for start and end should be considered?

Cycle:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id B869D0C865F52CEBEF107E2AED019D81

Year:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 3E1F87E9F3494940E97D8B1294BEF4E8

Season / Solar Term:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 47E0991A90408874086B60ED5FAF7FA9

Month:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 94F834249B96DD6DA43CDE4F865D341A

Day:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 0F0DE3F95B946E93863929FC85342699

Hour:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 6692B2DB39CD221EC982E21A77E1F39F

It is also possible to extract the time related text from the quote and add it to a field 'phrase':

Phrase:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 8EF417EF10EC62EB4F94AAB37B9E995B


Event itself

The event refers to the quote, maybe directly to the source, to the chronology/timing and the position/location. It also holds the coding of the phenomena, here it gets complicated - see next section.

Should the Event refer to 'Location' of described Phenomena:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id DC4AB195ED861533D664B11912F2723A

Should the Event refer to 'Timing' of described Phenomena:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 80D6C25C264FA5D9E16D98BF849034CB

Should the Event refer to 'Quote' (by ID) where Phenomena is described:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 21033A0DE082A0DDF73BB899F2C3ED53

Should the Event refer directly to the 'Source' where Quote describing Phenomena can be found:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 97326EFD19D249BD9F2E41C6418FEEBA

Should the Event contain a 'DOI' when data-set is published somewhere:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id 8D2AB12902A72243C71A5013CF6DE4AB

The license type is a string i.e. cc-by, cc-by-nc, ...

For details on possible options see Enumerator Options


Should the Event contain a 'License' when data-set is published somewhere:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:59, 26 April 2019.
poll-id BC42777F135E4EBF78619BAED4CAE82A

Phenomena/Coding

Indices Historical Climatology
Indices used to code Phenomena in Historical Climatology / Documents

A lot of information can be found inside historical documents. Thereby the coding schema is complex. A lot of coding is done by using indices. Some examples and their coding to illustrate this:

  • The weather was extremely warm -> temperature index + very hot (+3)
  • A lot of rain fell in December -> precipitation type + rain & precipitation amount + more than usual (+1)
  • The water level was 13 feet -> water level + value:13.0 + tolerance:1.0 + unit:feet
  • The drought lead to bad harvest of potatoes -> harvest + harvest amount: less than usual (-1) & potatoes / precipitation amount: less than usual (-1)
  • The wheat harvest was little but the wine quality was good -> harvest + harvest amount: less than usual (-1) & wheat / harvest + harvest quality: better than usual (+1) & wine

+: one dimensional combination

&: two (or more) dimensional combinations

/: two different events (i.e. cause vs effect)

(Coding tree as used in tambora.org can be found here.)

To handle the innumerable amount of different parameters, it makes sense to group them into thematic clusters.

Cluster: Temperature

Inside this cluster are all temperature related parameters: Temperature measurements, descriptive temperature levels, freezing events, ...


  • temperature-cluster

Levels i.e. can be 

-3: very cold
-2: cold
-1: cool
 0: normal temperature
+1: warm
+2: hot
+3: very hot
Should the 'temperature level' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:44, 26 April 2019.
poll-id 65502D023277498206B57688BD530F7D

How many levels should the temperature have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:45, 26 April 2019.
poll-id ADAB7A463A205E946F91EB439D72F97E

Trend i.e. can be 

-1: decreasing
 0: constant
+1: increasing
Should the 'temperature trend' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:47, 26 April 2019.
poll-id CA75A295662E1925453DBBDAAC9EDC84

Temperature value is a measured, numerical value with units Standards of other archive types can be used here

Should the 'temperature value' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:54, 26 April 2019.
poll-id 31651817B8C96932105AE8C5BE0618DF

Should the 'temperature unit' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:54, 26 April 2019.
poll-id 786A8617A75B1B702F30D4A255C9FDA5

Should the 'tolerance of the temperature' measurement be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:54, 26 April 2019.
poll-id 65E1F0E78137CF657366EBABACF025A9

The temperaure type is a string i.e. air, water, wind, ... It can be combined with the above quantitative parameters

For details on possible options see Enumerator Options

Should the 'temperature type' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:06, 2 May 2019.
poll-id 5CC715E9BDE5AF6692FFE90DECEF0A66


The following two parameters are of type boolean - they happen or not.

Should the occurrence of 'freezing/frost/ice' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:57, 26 April 2019.
poll-id B017D65C03AF92FC0C8108DA1CC16D83

Should the occurrence of 'thawing/melting' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 08:57, 26 April 2019.
poll-id EB4460E86661E290B32F5369328BBA3A

Cluster: Precipitation

Precipitation Types
Precipitation Types https://commons.wikimedia.org/wiki/File:Precipitation_by_type.png

Inside this cluster are all precipitation related parameters: long- and short-term amounts, intensities, measurements, type of precipitation, ...


  • precipitation-cluster

Levels of long-term precipitation (weeks... month) i.e. can be 

-3: extremely dry
-2: very dry
-1: dry
 0: normal precipitation
+1: wet
+2: very wet
+3: extremely wet
Should the 'long-term precipitation level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:12, 26 April 2019.
poll-id 0BC408B57C7E07876CC237732A6A4EBC

How many levels should the long-term precipitation level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:12, 26 April 2019.
poll-id F2B63053433745D49C1D193FD0173316

Levels of short-term precipitation (hours ... days) i.e. can be 

 0: no precipitation
+1: some precipitation
+2: much precipitation
+3: very much precipitation
+4: extremely much precipitation
Should the 'short-term precipitation level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:14, 26 April 2019.
poll-id 99E585C12A0AB90AA32F79D55534CE91

How many levels should the short-term precipitation level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:14, 26 April 2019.
poll-id FF918795D7594433F780F6B9AA3A8C4B

The amount of precipitation is a measured value for a given time frame (see timing)

Should the 'precipitation amount' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:19, 26 April 2019.
poll-id 394BF42D1C446F0CE5AE17E9DA822BE4

Should the 'precipitation amount unit' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:23, 26 April 2019.
poll-id D399079FDB133154DE16FE3268B9173D

The intensity of precipitation is a measured value, often a peal value

Should the 'precipitation intensity' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:21, 26 April 2019.
poll-id 1A4E114D41069E1DB5B6B24E6C373F4F

Should the 'precipitation intensity unit' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:25, 26 April 2019.
poll-id CC7687F582CE969364E219E8F639BEC2

The precipitation type is a string i.e. rain, snow, hail, dew, sleet, ... It can be combined with the above quantitative parameters, but can also stand alone

For details on possible options see Enumerator Options

Should the 'precipitation type' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:28, 26 April 2019.
poll-id BCDD1F5E126CEB741BDAEA9139F1E21B


Levels of snow cover i.e. can be 

 0: no snow cover
+1: thin snow cover
+2: deep snow cover
Should the 'snow cover level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:30, 26 April 2019.
poll-id 5FCBFA186D3FD3C8C5BA3B9088B89FBA

How many levels should the snow cover level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:31, 26 April 2019.
poll-id FF8C631F280539F7FA1F0E37C08A7118

The snow depth is static (accumulated), whereas the snow fall is per time-frame

Should the 'snow depth' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:31, 26 April 2019.
poll-id 145B73189382B854B476613A0287E1B4

Should the 'snow depth unit' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:32, 26 April 2019.
poll-id 41D0FD6993509D37D94932555ABD915D

Should the 'snow fall' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:33, 26 April 2019.
poll-id 89B0630F23AD5BD990C2E1EAF2683FCC

Should the 'snow fall unit' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:33, 26 April 2019.
poll-id 76DA2D73AF7B190F5534925EFD93938C

Cluster: Hydrology

see also Floods Working Group

Inside this cluster are all hydrology related parameters: water levels, flood magnitudes, ...

  • hydrology-cluster

Flood levels (magnitude) i.e. can be 

 0: no flood
+1: small flood
+2: flood above average
+3: flood of the century
Should the 'flood level' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:03, 26 April 2019.
poll-id D917816FE93EEF62F2706A6A3F7ACB45

Flood extend i.e. can be 

+1: regional
+2: supra-regional
Should the 'flood extend' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:05, 26 April 2019.
poll-id 154A712D8317BC95D7635D2D5FE6A32C

Should the 'water level value' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:13, 26 April 2019.
poll-id 84F8820DD6805A0F406F920F919BEB30

Should the 'water level unit' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:13, 26 April 2019.
poll-id DEBC2D0B2568E1AD99FC541FAE2625B1

Should the 'tolerance of the water level' measurement be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:14, 26 April 2019.
poll-id 8E503A573E69D8FFE79022A31F363856


Should the 'flood recurrence time' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:15, 26 April 2019.
poll-id BB393AEC7778E1AF64639E2CFF258A70

Should the 'flood recurrence unit' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:15, 26 April 2019.
poll-id 2768E72D1343E45930850B97DACF72FF

Should the 'tolerance of flood recurrence' measurement be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:17, 26 April 2019.
poll-id 0A9D750A3B35C09A231DC4B868306A16

Should the 'discharge value' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:17, 26 April 2019.
poll-id 944377AE31586516BA6F832B7FFF4D45

Should the 'discharge unit' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:18, 26 April 2019.
poll-id C3A57857629F79CC6410C9E5AB7CF854

Should the 'tolerance of discharge' measurement be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:18, 26 April 2019.
poll-id 71917093408BC4062038E3FC164B8563


Should the 'flow velocity' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:19, 26 April 2019.
poll-id 0D9C3628CAEF7F9911BD2933258B8C70

Should the 'flow velocity unit' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:19, 26 April 2019.
poll-id F460360D8604DFBC25634E3CC461507A

Should the 'tolerance of flow velocity' measurement be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:19, 26 April 2019.
poll-id 91580BA54F5D113CA33540F478FE03EC


low water levels i.e. can be 

 0: normal level
-1: low water level (limited use)
-2: very low water level (severely limited use)
-3: extremely low water level (no water)
Should the 'low water level' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:08, 26 April 2019.
poll-id 0DED93DA4042E968F4B5F8026A3E3761

Trend i.e. can be 

-1: decreasing
 0: constant
+1: increasing
Should the 'water level trend' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:08, 26 April 2019.
poll-id 22383E39B58A585DF51DDF9E5418499C

Storm surge levels i.e. can be 

 0: no storm surge
+1: average storm surge
+2: strong storm surge
+3: extreme storm surge
Should the 'storm surge level' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:11, 26 April 2019.
poll-id FA5CAC5F71DA7EC217FB13E585C886E2

Following parameters are of type boolean

Should the 'occurrence of erosion' (boolean) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:03, 26 April 2019.
poll-id D93CF5E6ABFDFB682507054CB79F595F

Should the 'occurrence of flash flood' (boolean) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:03, 26 April 2019.
poll-id 9C32719802310CEB864959ABB330D831

Should the 'occurrence of sediment deposition' (boolean) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:03, 26 April 2019.
poll-id 492532EED77DAC0398AD7A72A228C737

Should the 'occurrence of large plains flooded' (boolean) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:03, 26 April 2019.
poll-id 35EF7C83700931E8EC1E7F5F84ED6D5C

Should the 'occurrence of long standing water' (boolean) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:03, 26 April 2019.
poll-id 40B108D1A5AAFDFC5F1D29591C2522E7

Cluster: Clouds, Visibility

Inside this cluster are all cloud and visibility related parameters: cloud types, cloud cover, humidity, fog, ...


  • cloud-visibility-cluster

Levels i.e. can be 

 0:   0% sunny clear
+1:  25% mostly sunny
+2:  50% partly cloudy
+3:  75% very cloudy
+4: 100% fully cloudy
Should the 'cloud cover' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:39, 26 April 2019.
poll-id 3A806F3F31EDCA58FDFCA588B83085CD

How many levels should the cloud cover have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:40, 26 April 2019.
poll-id 2C67EA520BDADB24F9F99FAF9375574B

The cloud type is a string i.e. cumulus, nimbostratus, cirrus, ...

For details on possible options see Enumerator Options

Should the 'cloud type' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:42, 26 April 2019.
poll-id E60F95F6FB4D99952AC4BD4536EF2A4B


Levels of humidity level i.e. can be 

-1: dry air
 0: moderate humid air
+1: humid air


Should the 'humidity level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:55, 26 April 2019.
poll-id 63F04A4E15D23421DEE366E2864B2FFB

How many levels should the humidity have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:56, 26 April 2019.
poll-id 3050247892AD943372E976CA1B13B239

Should the 'relative humidity' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:57, 26 April 2019.
poll-id 16FCBB426D4C9D57E223746780A67F82

Should the 'relative humidity' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:57, 26 April 2019.
poll-id BCA0857BC409C43815605948735F564F

Should the 'tolerance of relative humidity' measurement be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:58, 26 April 2019.
poll-id 68723901C60567DD21046422F13D8B0A

Levels of visibility i.e. can be 

-2: very poor visibility
-1: poor visibility
 0: average visibility
+1: good visibility
+2: very good visibility
Should the 'visibility level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:02, 26 April 2019.
poll-id D4318F65856A95A4593F3D5B0DCBEFC9

How many levels should the visibility have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:02, 26 April 2019.
poll-id 345336607621104349E2A2C537F6B6A2

Following parameters are of type boolean

Should the 'occurrence of fog' (boolean) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 12:59, 26 April 2019.
poll-id 12031E20ADC706B42D99516FCDB2AA1B

Should the 'occurrence of dust' (boolean) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:00, 26 April 2019.
poll-id D2AC0CB7688436AC51D98288BCF3BA57

Cluster: Wind, Air Pressure

  • wind-pressure-cluster

wind force levels (Beaufort) i.e. can be 

  0: calm
 +1: light air
 +2: light breeze
 +3: gentle breeze
 +4: moderate breeze
 +5: fresh breeze
 +6: strong wind
 +7: high wind
 +8: fresh gale
 +9: strong gale
+10: storm
+11: violent storm
+12: hurricane
Should the 'wind force level' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:29, 26 April 2019.
poll-id E302EEAA443B75C9B11A0ABC42D2ED87

wind directions i.e. can be 

  0: north
 +1: north-east
 +2: east
 +3: south-east
 +4: south
 +5: south-west
 +6: west
 +7: north-west
 +8: change of direction
 +9: any direction
Should the 'wind direction' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:31, 26 April 2019.
poll-id 4B5DB3D922BF0F86EDFDBB0C58606F78

Should the 'wind speed' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:31, 26 April 2019.
poll-id A3A7D51232C1720A20486EBAA1EB1590

Should the 'wind speed unit' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:32, 26 April 2019.
poll-id 4C79C72884571D5EEF32F0283B50A1B7

Should the 'tolerance of wind speed' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:32, 26 April 2019.
poll-id 567EE6E9362E912611BCBCDAA701262F

The type of wind is a string i.e. foehn, gust, khamsin, sandstorm, sirocco, snowstorm, tornado, ... It can be combined with the above quantitative parameters, but can also stand alone

For details on possible options see Enumerator Options

Should the 'type of wind' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:34, 26 April 2019.
poll-id 92BFD051758677BC596615E84F1D1F19

air pressure levels i.e. can be 

-1: low pressure
 0: normal pressure
+1: high pressure
Should the 'air pressure level' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:37, 26 April 2019.
poll-id 68ED177D39B5FC8C159470406AFB9BB4

air pressure trend i.e. can be 

-1: falling pressure
 0: steady pressure
+1: raising pressure
Should the 'air pressure trend' (indices) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:37, 26 April 2019.
poll-id CCF27383F58F7F91ECF00F11328E5A2A

Should the 'air pressure value' (measurement) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:38, 26 April 2019.
poll-id AF786B293F72630CAE69DAF33B2E37FB

Should the 'air pressure value' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:39, 26 April 2019.
poll-id A58D8FCDC9223A219363FDA672BCA235

Should the 'tolerance of air pressure' measurement be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:39, 26 April 2019.
poll-id 49CF452CB706160B3DC68EA705EBB988


Cluster: Phenomena, Natural Hazards

Inside this cluster are all parameters related to natural phenomena or hazards: earthquake, tsunami, aurora borealis, meteoroid, comet, solar eclipse, moon eclipse, halo, avalanche, rainbow, landslide, wildfire, ...

  • phenomena-hazard-cluster

The phenomena type is a string i.e. earthquake, tsunami, aurora borealis, meteoroid, comet, solar eclipse, moon eclipse, halo, avalanche, rainbow, landslide, wildfire, ...

For details on possible options see Enumerator Options

Should the 'phenomena type' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:36, 29 April 2019.
poll-id BA13CDE9AC831FBE8E6E36CFBDAB5D9A

Phenomena Intensity i.e. can be 

 0: none 
+1: weak
+2: middle
+3: strong
Should the 'phenomena intensity' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:39, 16 May 2019.
poll-id 41B9237AB65B6BE6C733287658F122FD

How many levels should the phenomena intensity have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:39, 16 May 2019.
poll-id 04911F343681278D5D58E35F6EDF00D2

Cluster: Society

Inside this cluster are all parameters related to society affections: damage, death, illness, social problems


  • society-cluster

The type of damage is a string i.e. animals, buildings, bridges, houses, dams, plants, forest, traffic routes, ships, harvest, hunger, thirst, ...

For details on possible options see Enumerator Options

Should the 'type of damage' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:47, 26 April 2019.
poll-id 1C64923CC7224D291E0D133C19A2B9F1

Should the occurrence of 'mitigation' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:53, 26 April 2019.
poll-id A8961AAA2C12366DB6CE500557409ED8

Type of mitigation is a string i.e. charity, exemptions, indemnity, subsidies ...

For details on possible options see Enumerator Options

Should the 'type of mitigation' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:56, 8 May 2019.
poll-id 8893F25C9ECD8DD0128AE5DA2A9337C1

Should the 'number of injuries' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:55, 26 April 2019.
poll-id E7549C0AFF923350D685BE1F0B7E8507

Should the 'number of deaths' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:54, 26 April 2019.
poll-id 52B2B50E2037BB96CD080E7B94DE77F0

Illness is a string i.e. bubonic plague, fever, measles, cholera, ...

For details on possible options see Enumerator Options

Should the 'illness' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 13:59, 26 April 2019.
poll-id 4A2026D5F0CAD63CE70EE1D2B34211C0

Social problems is a string i.e. migration, poverty, rioting, theft, unemployment ...

For details on possible options see Enumerator Options

Should the 'social problem' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:39, 29 April 2019.
poll-id B6E52E338CCAE988407A2BAE4001A4CC

Levels of affected people i.e. can be 

 0: none
+1: few
+2: some
+3: many
Should the 'affected people level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:40, 29 April 2019.
poll-id 3D5A34DAC9DF3CC76A9F32401D28ADDD

How many levels should the affected people level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 07:40, 29 April 2019.
poll-id 91D6B91B52B58DE9784CCF08126E698D

Cluster: Plant Phenology

Plant Phenology
Plant Phenology https://commons.wikimedia.org/wiki/File:Acer_saccharinum_phenology.jpg


Inside this cluster are all parameters related to plants: blossom, leave fall, harvest, ...


  • plant-phenology-cluster

Levels of harvest quantity i.e. can be 

-2: very low harvest volume
-1: low harvest volume
 0: average harvest volume
+1: high harvest volume
+2: very high harvest volume


Should the 'harvest quantity level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:04, 26 April 2019.
poll-id BD988F82686E3ED3269F4F80A1C3815B

How many levels should the harvest quantity level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:04, 26 April 2019.
poll-id 48CC1E0B08ACAB16754C7DA9ACF68CC4

Levels of harvest quality i.e. can be 

-2: very poor crop quality
-1: poor crop quality
 0: average crop quality
+1: good crop quality
+2: very good crop quality


Should the 'harvest quality level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:06, 26 April 2019.
poll-id E8D16FD2DC8716599AEE66C1472321B7

How many levels should the harvest quality level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:06, 26 April 2019.
poll-id 5F36BD93F17530A8BEE98146E657F175

The plant type is a string i.e. apples, wheat, hay, wine, potato, cherries, ... It can be combined with the above quantitative parameters or the below observations, but can also stand alone

For details on possible options see Enumerator Options

Should the 'plant type' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:09, 26 April 2019.
poll-id DD430834105688293981E7D8569646F5

The type of observation is a string i.e. blossom, harvest, leave emergence, leave fall, planting, sowing, ...

For details on possible options see Enumerator Options

Should the 'type of plant observation' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:06, 8 May 2019.
poll-id CF471D7521819D6FF3E02A56EBEB11D1

Levels timing i.e. can be 

-1: earlier than usual
 0: usual timing
+1: later than usual
Should the 'timing level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:11, 26 April 2019.
poll-id E875FC470EC1CDE90A1E49A701EDD9EE

Cluster: Animal Phenology

Inside this cluster are all parameters related to animals: health, arrival, departure, breeding, ...


  • animal-phenology-cluster

Levels of absolute quantity i.e. can be 

 0: none
+1: few
+2: some
+3: many


Should the 'absolute quantity level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:20, 26 April 2019.
poll-id 948D4FAA7825CDDC567230B63EF2907B

Levels of relative quantity i.e. can be 

-1: less than usual
 0: average number
+1: more than usual
Should the 'relative quantity level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:22, 26 April 2019.
poll-id 45E16027D30548A09F0D7B5BE1925845

The animal type is a string i.e. birds, stork, sheep, swine, snail, locusts, ... It can be combined with the above quantitative parameters or the below observations, but can also stand alone

For details on possible options see Enumerator Options

Should the 'animal type' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:18, 26 April 2019.
poll-id 0FABB60D7250CD792EB05E9E64F1F4AF

The type of observation is a string i.e. arrival, departure, breeding, shearing, slaughtering, death, injuries, ...

For details on possible options see Enumerator Options

Should the 'type of animal observation' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 09:16, 16 May 2019.
poll-id 2FF5D1744AF7C8815016299F772C52CD

Levels timing i.e. can be 

-1: earlier than usual
 0: usual timing
+1: later than usual
Should the 'timing level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 14:11, 26 April 2019.
poll-id E875FC470EC1CDE90A1E49A701EDD9EE

Cluster: Economy

Super Market
Super Market https://commons.wikimedia.org/wiki/File:Hypermarkt_Merkur_%C3%96sterreich_-_Wien_Floridsdorf_-_05.04.2017_-_6.jpg


Inside this cluster are all parameters related to economy: price-, supply-, demand- / -level, -trend, goods

  • economy-cluster

Price level i.e. can be 

-1: low price
 0: normal price
+1: high price
Should the 'price level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:23, 29 April 2019.
poll-id C0419937178055EEA5765BED2D8D64E9

How many levels should the price level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:23, 29 April 2019.
poll-id 742D21DF8AE1F98F67B6F204C1473BF5

Price trend i.e. can be 

-1: decreasing price
 0: constant price
+1: increasing price
Should the 'price trend' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:24, 29 April 2019.
poll-id 072461E342CB51D2DCBAEF86BB167F71

How many levels should the price trend have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:24, 29 April 2019.
poll-id 49185C8C68F71F4855E0D109E7DF4A68

Supply level i.e. can be 

-1: low supply
 0: normal supply
+1: high supply
Should the 'supply level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:25, 29 April 2019.
poll-id 7465D9D42A5754517A31A75EC0EF9480

How many levels should the supply level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:25, 29 April 2019.
poll-id 8417DEB2862980A22D6D376FC69650AD

Supply trend i.e. can be 

-1: decreasing supply
 0: constant supply
+1: increasing supply
Should the 'supply trend' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:26, 29 April 2019.
poll-id 70E7134A4067F1ACA565810629DAD95F

How many levels should the supply trend have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:26, 29 April 2019.
poll-id BD118E3F2561530809E164C9834BD163

Demand level i.e. can be 

-1: low demand
 0: normal demand
+1: high demand
Should the 'demand level' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:26, 29 April 2019.
poll-id 830873BA275F3345551DAA2CCF673161

How many levels should the demand level have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:26, 29 April 2019.
poll-id 2CA48A9DE9DD93969BF109389DF181C3

Demand trend i.e. can be 

-1: decreasing demand
 0: constant demand
+1: increasing demand
Should the 'demand trend' be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:27, 29 April 2019.
poll-id C0BAE8DB76D9A9AE06C47AFE1C31FD23

How many levels should the demand trend have:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:27, 29 April 2019.
poll-id 1CE1B3A3B32BFC811EF815DAE6B86694

The market good is a string i.e. apples, wheat, meat, food, energy, fodder, hay, wood, ... It can be combined with the above quantitative parameters

For details on possible options see Enumerator Options

Should the 'market good' (string, options, choice) be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 06:29, 29 April 2019.
poll-id 70978262347F8BAF0D90AEECA27B4173


Example

Rename LiPD file extension from zip to lpd

Description Tambora-Files LiPD-Files Remarks
Flood Example Media:flood_tambora_csv.zip Media:Exp0000.tambora.2017.zip
To-Do To-Do To-Do
To-Do To-Do To-Do

Media in category "Historical Documents Working Group"

The following 6 files are in this category, out of 6 total.

Retrieved from "https://wiki.linked.earth/wiki/index.php?title=Category:Historical_Documents_Working_Group&oldid=81199"