Personal tools
@Pleiades on Mastodon
26 July 2024

Export Updates 2024-07-26:
Pleiades gazetteer of ancient places

6 new and 138 updated places.

1. Downloads: pleiades.stoa.org/downloads

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

"main" branch:

1ebffb68 - updated legacy csv
be6fa14f - updated json
5c10e900 - updated rdf/ttl
52ae6ad7 - updated gis package
d60270a9 - updated data quality
d8b12172 - updated bibliography
adffa334 - updated indexes

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

3a8d7c66 - updated geojson and names index

19 July 2024

New in the Pleiades Time Periods vocabulary:

The Iron Age IIc Period in the Levant as defined by the Levantine Ceramics Project.

pleiades.stoa.org/vocabularies

19 July 2024

149 database objects (place, name, location, and connection resources) were created or modified.

19 July 2024

Export Updates 2024-07-19:
Pleiades gazetteer of ancient places

5 new and 77 updated places.

1. Downloads: pleiades.stoa.org/downloads

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

"main" branch:

fdfb2d5b - updated legacy csv
5b26b0a1 - updated json
no change: rdf/ttl
ac074b2e - updated gis package
d860647d - updated data quality
0f266f33 - updated bibliography
5518eae3 - updated indexes

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

32038c72 - updated geojson and names index

18 July 2024

Export Updates 2024-07-18:
Pleiades gazetteer of ancient places

3 new and 17 updated places.

1. Downloads: pleiades.stoa.org/downloads

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

"main" branch:

4a3c9d63 - updated legacy csv
1e741d7d - updated json
no change: rdf/ttl
ca5ee051 - updated gis package
ba3aa40d - updated data quality
075cab45 - updated bibliography
d6174954 - updated indexes

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

0caa3d9d - updated geojson and names index

@Pleiades on Mastodon - More…
You are here: Home Project news and content updates Pleiades Project Blog New Website Features: Positional Accuracy

Skip to content. | Skip to navigation

New Website Features: Positional Accuracy

Creators: Tom Elliott Copyright © The Contributors. Sharing and remixing permitted under terms of the Creative Commons Attribution 3.0 License (cc-by).
Last modified Mar 06, 2024 11:49 AM
tags:
A software development iteration in February 2024 with our long-time contractor, Jazkarta, Inc. has introduced some new features for users of the Pleiades website. This post introduces enhancements that provide visitors with increased visibility and functionality of positional accuracy information. A future post will address improvements in bibliographic data management for contributing users.

Positional accuracy

Pleiades has always kept track of the spatial accuracy of the coordinates stored in our Location resources. Whereas modern map series and GIS datasets produced in and since the 20th century generally manage and report this information as part of a spatial metadata package at the map, series, or dataset level, Pleiades was designed to aggregate spatial data from multiple sources and to provide for continuous enhancement. Accordingly, we devised the Positional Accuracy Assessment (PAA) as a document type in which information about the source and method of collection for one or more spatial geometries could be captured, as well as a "horizontal accuracy" value (encompassing formal accuracy and precision) in meters +/-. Users of Pleiades have always been able to "drill down" from an individual Location page to the corresponding PAA, and the accuracy data has long been included in our JSON and "GIS Package" exports.

As of last week, users will see the "horizontal accuracy" data drawn from our PAAs used in two new ways on the website.

A screen capture of a Pleiades place page that includes a "Locations" subheading, and under that subheading another subheading that reads "Representative Locations" and under that subheading a single bullet item that reads "OSM location of so-called "Tempio di Apollo" (750 BC - AD 300) accuracy: +/- 20 meters."Positional accuracy: on Location listings on Place pages

On each Place page, the "Locations" subheading introduces a summary list of all Location resources associated with that Place. These summaries now include the "horizontal accuracy" values in meters drawn from the corresponding PAA. Consider, for example, the Place page for the Temple of Apollo (VII,7,32) in Pompeii.

For those interested in the structure and details of Pleiades PAAs, here are some examples of widely used or exemplary ones:

Satellite photo map showing excavated area of central Pompeii. The remains of the temple are outlined by a yellow rectangle with rounded corners and, within that, a more precise blue rectangle with an orange dot in the center.Positional accuracy: on Maps on Place pages

Maps on Pleiades Place pages now have a new feature permitting users to switch on or off location accuracy buffers around each Location geometry. When locations are shown in the Place page, a check box appears below the map labeled "display location accuracy buffers". By selecting (activating) this check box, the user will cause the map to add a yellow buffer around each Location, showing the relative extent of the footprint implied by the "horizontal accuracy" value in each corresponding PAA. Consider here the map for the same Place page discussed above.

This feature can be particularly useful when confronted with a Pleiades Place resource for which the available Locations still rely on coordinates digitized from small-to-medium-scale maps or when multiple Locations from different sources are presented. For example:

  • Sevasto: a settlement site in Greece digitized from a Barrington Atlas map at 1:500,000 scale.
  • Buddahs of Bamyan: coordinates sourced from a third-party service with presumed 2,000 meter accuracy.
  • Nakoleia: a settlement site near modern Seyitgazi in Turkey for which three Locations are currently offerred: one digitized from a Barrington Atlas map, one digitized from a Tabula Imperii Byzantini map, and one digitized from high-resolution modern GIS data but only for the nearby, associated modern location rather than the archaeological site.