User:Fradeve11/prove2

From OpenStreetMap Wiki
Jump to navigation Jump to search

Tagging scheme to describe historic structures/areas/elements.

Why we need new historical tagging?

The historical workgroup is an initiative of the Italian OSM community to bring in the project features for the most diffused types of cultural heritage in Europe and in the world. At now (half 2009), OSM lacks of more or less 10 types of cultural evidences, more or less diffused in all the continents. This consideration has been raised after the first ArchaeoMapping Party of the OSM history: Pompei 2008 (08-12-08). In pills: OSM is used for almost all applications of cartography, and now we want to enable OSM to be used also for historic heritage knowing - conservation - turism management.

The 2 logos are from Wikimedia Commons, and are used for "Finnish road sign no. 772 a. Museum or historic building"; it's in public domain because it is a part of a decision or a statement by an authority or a public body of Finland.

Pompeji vesuv.jpg


historic historic=yes Museo tai historiallinen rakennus 772a tunnusosa.svg

Museo tai historiallinen rakennus 772a.svg

Name

This applies both to historic areas and historic elements (highways, columns, etc.).

name local language spelling
name:it Italian language spelling in national lettering.
Examples: "Area archeologica di Pompei"
name:en English spelling in national lettering.
Examples: "Archaeological Area of Pompeii"
name:la Latin spelling in national lettering.
Examples: "Pompeii"

Example

Feature Documentation Tagging example
historic names
Example for Pompeii: Latin names
name=Taverna di Febo
name:la=Taberna Phoebi

Historic areas

type
Mf area.png
de historischer Ort
en Historic area
us Historic area
fr Zone historique
it Area storica

The historic site (land area), mostly fenced or outlined by hedge, barrier or access restriction is tagged on land with:

Feature
Tag
Status
Present in Tagwatch
Archaeologic area historic=archaeological_site
Gtk-ok.svg Approved
yes [2766]
Palaeontological area geological=palaeontological_site
Gtk-ok.svg Voting
no
Historic station area/building railway:historic=station_site
Symbol divide vote.svg Voting
yes [199]

Historic aqueducts

type
Mf way.png
de antikes Aquädukt
en Historic aqueduct
us Historic aqueduct
fr Aqueduc historique
it Acquedotto storico

Roman ones in en.wiki

Feature
Tag
Status
Present in Tagwatch
aqueducts
historic=aqueduct
bridge_type=aqueduct
also have a look at Proposed_features/aqueductSymbol move vote.svg To be proposed
Useful combination
historic:civilization=*


Historic public baths (thermae)

type
Mf node.png Mf area.png
de
en Historic thermal baths
us Historic thermal baths
fr thermes historiquees
it Terme antiche

Thermae, Roman ad Greek, Roman ones on en.wiki

Feature
Tag
Status
Present in Tagwatch
ancient public baths
building=yes
historic=thermae
Symbol move vote.svg To be proposed
Useful combination
culture=*


Ancient amphitheatres

type
Mf node.png Mf area.png
de
en Historic amphitheatre
us Historic amphitheatre
fr Amphithéâtre historique
it Anfiteatro storico

Roman ones on en.wiki

Feature
Tag
Status
Present in Tagwatch
ancient amphitheatres
building=yes
historic=amphitheatre
Symbol move vote.svg To be proposed
Useful combination
culture=*


Obelisks

type
Mf node.png Mf area.png
de Obelisk
en Obelisk
us Obelisk
fr Obélisque
it Obelisco

en.wiki

Feature
Tag
Status
Present in Tagwatch
obelisks

building=yes
historic=obelisk
Symbol move vote.svg also have a look at man_made=obelisk To be proposed
Useful combination
culture=*
height=*


Stones

type
Mf node.png Mf area.png
de
en Historic stones
us Historic stones
fr
it Pietre storiche
Feature
Tag
Status
Present in Tagwatch
Notes
boundary_stone
historic=boundary_stone
Symbol move vote.svg To be proposed
yes [450]
generic tag for megaliths
historic=megalith
Symbol move vote.svg To be proposed
no
menhir
historic=megalith +
megalith_type=menhir
Symbol move vote.svg To be proposed
yes [16]
In this key:value pair will be merged also all:
historic=menhir [13]
menhir=yes [2] etc.
stone_circle
historic=megalith +
megalith_type=stone_circle
Symbol move vote.svg To be proposed
yes [1]
In this key:value pair will be merged also all:
historic=stone_circle [13] etc.
dolmen
historic=megalith +
megalith_type=dolmen
Symbol move vote.svg To be proposed
yes [2]
In this key:value pair will be merged also all:
historic=dolmen [6]
dolmen=yes [2] etc.
milestone
historic=milestone
Symbol move vote.svg To be proposed
yes [50]


Historic roads

type
Mf way.png Relation.png
de
en Historic roads
us Historic roads
fr Rues historiquees
it Strade storiche

We need a smart way to tag historic highways: both in good conditions and in bad conditions. Roman viaducts are here on en.wiki

Feature
Tag
Status
Present in Tagwatch
Notes
historic roads
* roman roads
* pilgrimage roads
* ancient commercial roads
historic=road
Symbol move vote.svg To be proposed
In this key:value pair will be merged also all:
historic=roman_road [50] etc.
viaducts
historic=bridge
bridge_type=highway
Symbol move vote.svg To be proposed

Useful combinations

For both the elements (roads and viaducts) we recommend the following combinations of tags:

Feature
Tag
Status
Present in Tagwatch
Useful combination
a specific Relation:route:
route=historic
Symbol move vote.svg To be proposed
no
Useful combination
culture=*
Symbol move vote.svg To be proposed
no
Useful combination
smoothness=*
cutting=yes
tunnel=yes
width=*
Gtk-ok.svg Approved
yes

Examples

Feature Documentation Tagging example
Appian Way
Appian Way on en.wiki
historic=road
name=Appian Way
name:la=Via Appia
type=route
route=historic
culture=roman
Camino de Santiago
Camino de Santiago on en.wiki
historic=road
name=St. James' Way
name:es=El Camino de Santiago
type=route
route=pilgrimage
Silk Road
Silk Road on en.wiki
historic=road
name=Silk Road
name:it=Via della Seta
type=route
route=historic


Castles

type
Mf node.png Mf area.png
de Burg
en Castle
us Castle
fr Château fort
it Castello

See historic=castle for further informations.

Feature
Tag
Status
Present in Tagwatch
Notes
castle
historic=castle
Gtk-ok.svg Approved
yes
Useful combinations
name=*
Gtk-ok.svg Approved
yes
Useful combinations
wikipedia=article_name
Gtk-ok.svg Approved
yes
Use different tags for linking
the same article in different languages, e.g.
wikipedia:en=Pillnitz
wikipedia:de=Schloss Pillnitz
Useful combinations
castle_type=*
Symbol divide vote.svg Discussion
yes
castle_type=* could be:
castle_type=burg
castle_type=schloss
castle_type=burg;schloss
castle_type=festung
castle_type=kremlin
castle_type=shiro
castle_type=defensive
castle_type=stately
castle_type=fortress
castle_type=roman
Useful combinations
ruins=yes
Gtk-ok.svg Approved
yes
Use it when the castle is a ruin,
that means if only remains of buildings without roof
or at least some walls exist
(don't use historic=ruins anymore!).


Tumulus

type
Mf node.png Mf area.png
de
en Cairn
us Tumulus
fr
it Tumulo
Feature
Tag
Status
Present in Tagwatch
Notes
cairn
historic=archaeologic_site +
site_type=cairn
Symbol divide vote.svg Discussion
yes [32]

This tag is heavily under discussion; historic=archaeologic_site+site_type=cairn could be substituted by site_type=tumulus or man_made=cairn. Also see historic=tomb and tomb=*

Memorial

type
Mf node.png Mf area.png
de
en Memorial
us Memorial
fr
it Memoriale
Feature
Tag
Status
Present in Tagwatch
Notes
memorial
historic=memorial
name=*
Gtk-ok.svg Approved
yes
This is used only for memorials.
For monuments use historic=monument.


Battlefield

type
Mf node.png Mf area.png
de Schlachtfeld
en Battlefield
us Battlefield
fr Champ de bataille
it Campo di battaglia

The site of a battle or military skirmish in the past. this could be on land or at sea.

Feature
Tag
Status
Present in Tagwatch
Notes
battlefield
historic=battlefield
Gtk-ok.svg Approved
yes [60]
In this key:value pair will be merged also all:
historic=battelfield [1]
historic=battle [2]
historic=battle_field [3]
historic=battle_ground [1]
historic=battle_site [1]
Useful combinations
name=*
date=*
Gtk-ok.svg Approved
yes
Name stands for the name of the battle;
Date for the date of that as YYYY-MM-DD.


Wreck

Monument

Heritage designation

Feature
Tag
Status
Present in Tagwatch
Notes
heritage designation
historic=heritage +
designation=*
Symbol divide vote.svg Discussion
yes [~50]

Example

Feature Documentation Tagging example
UNESCO_world_heritage
Example for Wikipedia:World_Heritage_Site
historic=heritage +
designation=UNESCO_world_heritage


Others useful tags

Museums

de Museum
en Museum
us Museum
fr Musée
it Museo
Feature
Tag
Status
Present in Tagwatch
museum

building=yes
tourism=museum
Gtk-ok.svg Approved
Useful combination
operator=*
building=yes
opening_hours=*


Topology

The most popular question after this kind of tagging proposal is

Why have you proposed some features as "new", when we have already them? For example, for roman bridges, you have proposed

historic = bridge
bridge_type = viaduct
culture = roman

when we could have for example

brige = yes
highway = path
historic = yes

that could be use, avoiding to introduce "historic = bridge" into database.

Answer: We need to strongly distinguish actual and suitable features from past ad historic ones. Probably, if I query the OSM database for all "bridge = yes", mostly I don't want the historical bridges (unsuitable for cars); in the same time, if I query database for "historic = bridge", i get them without adding any other query (while in the other case I must query for "bridge = yes" + "historic = yes"). Moreover, in the proposed model, the tag bridge_type contains the ancient use destination of the bridge. For example, a bridge that was built to carry a road and now is suitable today only for pedestrian, could be tagged as "historic = bridge" + "bridge_type = viaduct" + "highway = pedestrian" + "culture = roman". For the same reason, the use of historic = yes should be reduced, because searching for a "main" tag should not give a results including historic features.

So, the main problem is that the historic=* tag is more complex that other tags, because it represents features of the past, and mostly not usable today for they original ancient purpose. For this reason, all the historic features must be excluded from simply queries, which must give only actual features.

Problem: conventions to express the historical period

So, they're really a lot of features. What can we do? A problem remains open: how to distinguish building time.

Datation with period

historic = megalith
period = neolithic

Datation with date

historic = megalith
start_date = 3100 BC

or, for a Pompeii fountain

historic = yes
amenity = drinking_water
date = 78-08-24

TODO