← Back to Tools — full list of third-party integrations of the EM Framework.

Ecosystem

Tools that consume s3dgraphy.

Beyond the first-party components of the Extended Matrix Framework, a growing number of third-party tools have chosen to ground their archaeological data on the EM data model. This page lists those external integrations — projects whose code and release cycle live outside the EM organisation but whose users benefit from a graph that travels across the framework.

The list serves two audiences: researchers evaluating which of their existing tools already speaks EM, and developers considering a similar integration in their own codebase. For the first-party components, see Tools.

Inclusion criteria

  • Public, active repository under an OSI-approved licence, with maintenance signal in the last twelve months.
  • Non-trivial s3dgraphy usage — a projector, a roundtrip story, or a sustained consumer of the API rather than a one-off import script.
  • Declared maintenance with a named maintainer or organisation and a documented integration entry point.

Listed integrations

  • PyArchInit

    QGIS plugin

    A single environment for stratigraphic, alphanumeric, multimedia and topographical archaeological data inside QGIS — used by research groups and field operators since 2005.

    PyArchInit consumes s3dgraphy to bridge QGIS-side stratigraphic recording with the Extended Matrix data model: stratigraphic units, relationships and selected paradata authored in PyArchInit can be projected onto a s3dgraphy graph and exchanged with the rest of the Extended Matrix Framework.

    Maintained by
    Luca Mandolesi · Enzo Cocca (s3dgraphy integration)
    s3dgraphy support
    0.1.41 · vendored under ext_libs/s3dgraphy
    Licence
    GPL-2.0

How to be listed

Maintainers of consumer tools that want to be added to this page are invited to open an issue on the s3dgraphy issue tracker with a short integration story covering: tool name, repository URL and licence; a one-line description; the version of s3dgraphy currently consumed and the vendoring or dependency strategy; a pointer to integration documentation; and the maintainer name and contact.

The s3dgraphy maintainers will review the request, confirm the soft inclusion criteria, and add the entry on this page and on the corresponding manual page in a subsequent release.