OpenHistoricalMap/Imports/Pleiades

From OpenStreetMap Wiki
Jump to navigation Jump to search

Pleiades background

https://pleiades.stoa.org/

https://pleiades.stoa.org/places

Data covers what bbox? Large

What time frame?

Import goals

Get the data set into OHM with OHM-appropriate tagging and data structures

Don't create a mess

Import Method

download full places json at a specific data - http://atlantides.org/downloads/pleiades/dumps/

update all wikipedia and wikidata tags, osm links, and whg ids, as appropriate

translate to user-editable data tables using scripts

manually [!] massage data to buff out rough edges

create osm point/way/relation data for each location row

create ohm relations (for stable ids) for each place, with associated locations as members


Import Scoping

Historic data modeling is complex. OHM's goal is to help provide a skeleton framework for others to build against. So, the scope of this isn't a perfect subset of Pleiades. Hopefully, it is a 'good enough' subset.

To that degree, this import leans on many of Pleiades simplifications (e.g. coalescing names, representative data points).

Import caveats:

Ideally, this data would be kept fresh & in sync with Pleaides. Why didn't you take this route?

https://pleiades.stoa.org/help/how-to-track-changes-in-pleiades


Why store Pleiades attribute info in OHM? Why not dynamically update it or pull directly from there?


Hey! Pleiades took used a bunch of OSM data for sourcing - are you really importing OSM data into OHM?

No. This is why we're using Pleiades "representative" data points for the import. Yes, this is a derivative in some ways of OSM.


How many lookups to include?

OHM is not the master list of concordance lookup, but a few important items are included for reference.


Concerns and Cautions:

https://rmhorne.org/2018/11/11/what-do-you-do-with-36409-places-and-6506-connections-some-cartographic-representations-of-pleiades-data/

Data Structure

Places: connect names with locations

Names have time periods associated with them

Places can have many features

Features can have many locations

Can locations have more than 1 way?

Data Mapping

Pleiades_place::OHM[relation]

relation start_ and end_ dates come from: place or name?

Pleiades_location::OHM[point|way]

way,node::polygon/point
attributes from locations


Import-specific Tagging

import_id = pel_imp_jm_2110xx

license = CC-BY-SA 3.0

import_src =


Import Stats

In - Pleiades

xxxxx points

xxxxx polygons

xxxxx line strings

Out - OHM

Labeled POIs

Ways

Relations

Import Processing Scripts

link to github

Proposed Import File

link to github