OpenHistoricalMap/Tags/Events

See also: OHM Forum Discussion: Event Tagging - Battlefields, Campaigns, Explorer routes

Description and Discussion of possible Event Tagging schemes. Current work has been focused on tagging battles, and these schemes will need to generalize to cover other usages such as movements of Explorers and Expeditions.

Currently some experimental work is being done on the site of the Antietam Battlefield (part of the Maryland Campaign of 1862)

Some older thoughts on tagging battlefield movements may be found on the American Civil War Project page. This page will be updated with current tagging from Antietam and the tagging discussion will migrate from the American Civil War page to here.

Current Tagging

Namespaces

• event:
  • namespace for ephemeral data
• event::mil:
  • namespace for ephemeral data of military application
• event:expedition
  • namespace for explorers/expedition tracking
• event:journey
  • namespace for a trip of significance
• event:venue
  • namespace for (transient) event venuses (e.g., Woodstock 1969)

Point in Time

start_date=* and end_date=* with the same time for a single point in time.

Temporary Burials & Relocated Cemeteries

• landuse=cemetery
• start_date=*
• end_date=*
• name=*
  • At Antietam, Union Temporary Burial, Confederate Temporary Burial, Horses Temporary Burial
• description=*
  • additional information if available (e.g., which unit was buried there)

Troop Positions

Prefix with event:mil

On ways and nodes

• time
• event:mil:deployment=*
  • line, column, bivouac, vedette
  • direction of way matters for line and column. for column, direction march. for line, apply right hand rule to get direction of march
  • areas or points good for bivouac and vedettes

On relations

Unit information is attached to chronology relations, one level up from the geometry. Nested relations to reflect OoB information are discouraged; instead use external links to reflect higher level, more complex military organizations.

• ephem:mil:unit=*
  • company, regiment, brigade etc.
• name=*
  • name of unit, e.g. 12th Massachusetts
• ephem:mil:branch=*
  • e.g. infantry, cavalry, artillery
• ephem:mil:commander=*
  • name of commander if known and there is only one

TODO: using route relation with subtypes in certain cases. This seems well suited for modeling of marches during campaigns which will generally follow established roads of the time.