Comments (3)
Yeah, this is a problem that I'd noticed in a couple of places in the original document Eric generated from the Pleiades dataset. I'm going to pull him and Tom in on this, because my bet is it's coming from a centroid related to a bunch of un-located places that are associated only with the bounds of a Barrington Atlas map page.
from periodo-data.
Something to discuss with @paregorios:
Arguably the spatial coverage of Pleiades time periods is not expressed in the most useful way at the moment. E.g. Classical (Greco-Roman; 550 BC-330 BC). It has no textual spatial coverage description (i.e. no general description from the Pleiades curators of the spatial region that the period covers), and it links to all of the following Wikidata places:
wikidata:Afghanistan, wikidata:Albania, wikidata:Algeria, wikidata:Armenia, wikidata:Austria, wikidata:Azerbaijan, wikidata:Bosnia and Herzegovina, wikidata:Bulgaria, wikidata:Croatia, wikidata:Cyprus, wikidata:Czech Republic, wikidata:Egypt, wikidata:France, wikidata:Georgia, wikidata:Germany, wikidata:Gibraltar, wikidata:Greece, wikidata:Hungary, wikidata:India, wikidata:Iran, wikidata:Iraq, wikidata:Israel, wikidata:Italy, wikidata:Jordan, wikidata:Kenya, wikidata:Kosovo, wikidata:Kuwait, wikidata:Kyrgyzstan, wikidata:Lebanon, wikidata:Libya, wikidata:Macedonia, wikidata:Malta, wikidata:Moldova, wikidata:Monaco, wikidata:Montenegro, wikidata:Morocco, wikidata:Oman, wikidata:Pakistan, wikidata:Palestine, wikidata:Portugal, wikidata:Romania, wikidata:Russia, wikidata:Saudi Arabia, wikidata:Serbia, wikidata:Slovenia, wikidata:Somalia, wikidata:Spain, wikidata:Sudan, wikidata:Switzerland, wikidata:Syria, wikidata:Tajikistan, wikidata:Tunisia, wikidata:Turkey, wikidata:Turkmenistan, wikidata:Ukraine, wikidata:United Kingdom, wikidata:Uzbekistan, wikidata:Yemen
Presumably, that long list of countries could be replaced with some broader modern regions, or with historical regions. I'm not sure what makes most sense for people using Pleiades + PeriodO data, but the status quo seems sub-optimal.
from periodo-data.
The way we derived the spatial coverage in Pleiades was unique, and I think still useful: rather than trying to take a statement of spatial coverage from the label or asking @paregorios to make a list, we took the entire dataset and inferred spatial coverage from the sum of the locations of all of the places tagged with a given period label. The spatial coverage takes the form of modern nations because we were still using DBpedia at that point.
There's some noise in there, either from the very broad application of those period labels in the Barrington Atlas or from mistakes in Pleiades, but this seems to me a valuable proof of concept for the inferential establishment of spatial coverage for a period from place locations in an existing gazetteer (as opposed to the top-down designation, which presents its own challenges). I'm not averse to consolidating, but can we do that while maintaining the bottom-up calculation from site locations in this case?
from periodo-data.
Related Issues (20)
- Fix broken British Museum URLs
- Dan Hick's massive thread of period names
- Marine isotope stages (MIS) HOT 1
- Fix mis-encoded character and capitalization of authority title HOT 3
- Period missing an English label HOT 2
- Character problem with Latin rendering of Russian diacritics from LCHS HOT 17
- Duplicate LCSH periods HOT 1
- Inconsistency in storing a source's publication date
- Authorities missing source publication dates HOT 1
- Submitting an authority that is a new edition of an old source HOT 5
- Buddhist Studies Time Authority Database HOT 1
- Taiwanese periods from Academica Sinica
- Seshat Databank HOT 1
- eHRAF Archaeology database HOT 1
- chronOntology data HOT 1
- Dyson, Stephen L. — Late Iron Age stop date and alt. labels
- Mapping graphs for Chronontology and Wikidata HOT 1
- Getty ATT periods as interpreted by DAINST in Chronontology HOT 5
- Revisit the way temporal extents are modeled
- Replace OCLC URIs with Wikidata ones HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from periodo-data.