Personal tools
@Pleiades in the Fediverse
20 November 2024

Export Updates 2024-11-20:
Pleiades gazetteer of ancient places

7 updated places.

1. Downloads: pleiades.stoa.org/downloads

2. pleiades.datasets: github.com/isawnyu/pleiades.da:

"main" branch:

89883b44 - updated legacy csv
e51e26ea - updated json
no change: rdf/ttl
6fa8888d - updated gis package
473cf3ab - updated data quality
364cbbc6 - updated bibliography
3ec8248d - updated indexes
935522f2 - updated sidebar

3. pleiades-geojson: github.com/ryanfb/pleiades-geo:

no change

20 November 2024

Updated Pleiades Sidebar data:

There are 28,331 Pleiades matches across all 6 datasets (cflago, edhgeo, itinere, manto, nomisma, wikidata). 5,582 of these are reciprocated by Pleiades. 19,219 unique Pleiades places are referenced.

New data from itinere, nomisma, and wikidata were incorporated.

github.com/isawnyu/pleiades.da

20 November 2024

Updated Pleiades < -- > Wikidata: 12141 Wikidata entities include a Pleiades ID and 4720 Pleiades entities include a Wikidata ID. Of these, 4716 are mutual (bidirectional). 6379 Pleiades resources to which Wikidata links can be added after they are checked. 4 Wikidata items to which Pleiades IDs can be added after they are checked. 90 Wikidata items that each link to more than one Pleiades ID. 903 Pleiades resources to each of which more than one Wikidata Item link.

github.com/isawnyu/pleiades_wi

19 November 2024

Pleiades Gazetteer Export Updates 2024-11-19:

21 updated places.

1. Downloads: pleiades.stoa.org/downloads

2. pleiades.datasets: github.com/isawnyu/pleiades.da:

"main" branch:

dfdcd13b - updated legacy csv
02f4206e - updated json
no change: rdf/ttl
a56f1f07 - updated gis package
517e7084 - updated data quality
9e70f4de - updated bibliography
81402be7 - updated indexes
e9409676 - updated sidebar

3. pleiades-geojson: github.com/ryanfb/pleiades-geo:

3f821392 - updated geojson and names index

19 November 2024

Updated Pleiades < -- > Wikidata: 12,130 Wikidata entities include a Pleiades ID property and 4,714 Pleiades entities include a Wikidata ID property. Of these, 4,704 are mutual (bidirectional).

github.com/isawnyu/pleiades_wi

There are 6,384 Pleiades resources to which Wikidata links can be added after they are checked, 10 Wikidata items to which Pleiades IDs can be added after they are checked, and 90 Wikidata items that each link to more than one Pleiades ID.

@Pleiades in the Fediverse - More…

Introducing Geocollider

Creators: Tom Elliott Copyright © The Contributors. Sharing and remixing permitted under terms of the Creative Commons Attribution 3.0 License (cc-by).
Last modified Jun 08, 2017 02:56 PM
tags:
A new tool to help you match lists of placenames or geographic locations against the Pleiades gazetteer.

The Pleiades community is pleased to announce the "public beta" of a new software tool for working with Pleiades data: Geocollider. The Pleiades Geocollider is a web application that takes input from a user in the form of a comma-separated or tab-separated data file. The input data file may contain a list of placenames, of geographic locations, or both. Geocollider attempts to align this dataset with the Pleiades gazetteer, returning to the user a comma-separated file containing information about possible matches. 

Geocollider is under active development by the Pleiades project. The software was conceived and created by Ryan Baumann of the Duke Collaboratory for Classics Computing. Funding for the development of Geocollider was provided by a grant from the National Endowment for the Humanities (grant number HK-230973-15) to New York University for a variety of improvements to Pleiades. The Geocollider work has been performed under a subaward from NYU to Duke. The code for Geocollider is written in Ruby, and has been released on GitHub under terms of an open-source MIT license. Code for the "front end" used to host Geocollider on the web is also available.

We invite you to give Geocollider a try, and to report back on your experience with the tool. An email to pleiades.admin@nyu.edu will suffice to reach us, but opening an issue report at GitHub about a problem or a requested feature will also work.