Event mapping is being developed in OpenHistoricalMap. This is a review of some of the known issues and proposed solutions. Details of event specific tagging and use of chronology relations are covered.
Size: 14.23 MB
Language: en
Added: Jun 08, 2024
Slides: 14 pages
Slide Content
Events Come to
OpenHistoricalMap
Richard Welty
SOTM US, 7 June 2024
Examples
•Event sites
•Woodstock 1969
•Routes of Explorers
•Troop Movements in Campaigns and Battles
Mapping Events
•Makes sense in OpenHistoricalMap
•Does not make sense in OpenStreetMap
•In OHM, should there be a separate, parallel
database for events or just all in one?
Requirements
•Must integrate with current OSM/OHM tagging
conventions
•Easy to identify and extract if we decide to
move to separate, parallel databases
•Leverage WikiData to correlate with non-geo
data
Not Everything Requires
New or Special Tagging
•Temporary Burials
•we have the Elliott Burial Maps from
Gettysburg and Antietam
•just tag a cemetery with a start & end date
Elliott Burial Map
Troop Movements
•Need specific tagging for this
•Unit locations are specified at certain times;
units move
•Use the chronology relation type to group
successive troop positions
•Don’t over do it - use external links for
additional non-geo data like OOB
Cope-Carman Map of
1908 - Daybreak
Tagging
•nodes and ways for geometry
•start_date and end_date in ISO DateTime
format - duplicate for a single point in time
•event:mil:deployment=line
•the unit is deployed in a line formation in
anticipation of combat
•right hand rule for direction faced
Tagging
•event:mil:deployment=column
•for a unit marching in a column - a road
march formation
•direction of way is direction unit is facing
Tagging
•event:mil:branch
•infantry, artillery, cavalry, etc.
•event:mil:unit
•regiment, brigade, division
Campaigns
•Not precisely the same as battles
•Larger units
•Usually follow roads
•Level of description changes when shifting
from campaign to battle and back
Campaigns
•Maryland Campaign of
1862
•This from Wikipedia
Campaigns
•tagging proposal still being developed
•perhaps add a route relation type
•e.g. events:mil:march
•include route relation in chronology relation
•start and end date for beginning, end of march