IUENNA

Web Mapping with IUENNA

Public map interfaces for exploring selected spatial metadata and project geodata from the Jauntal/Podjuna research area.

Explore IUENNA in ARCHE Home
Workflow Interfaces Leaflet Example AI-assisted Development

Overview

IUENNA uses browser-based maps as discovery interfaces for spatially referenced archaeological records. The maps complement, rather than replace, the archived datasets and metadata in ARCHE.

The project combines established GIS workflows in QGIS with lightweight web technologies such as Leaflet and, for one export, the qgis2web plugin. A separate experimental interface was iteratively developed with generative-AI coding assistance; its archaeological source data remain project data, not AI-generated content.

For citation, licensing, reuse, and provenance, users should follow the persistent identifiers and record-level information supplied by ARCHE.

Typical publishing workflow

  1. Prepare and validate spatial data in QGIS, including coordinate reference systems and attribute fields.
  2. Choose a web-suitable representation, for example GeoJSON for selected vector data or a qgis2web export for a configured QGIS project.
  3. Review which attributes may be published and retain persistent links to the authoritative repository records.
  4. Publish the static web assets through GitHub Pages and test map behaviour, accessibility, and browser performance.
  5. Where code-generation tools are used, review their output manually and keep archaeological assertions separate from generated interface code.

IUENNA map interfaces

The two interfaces below serve different purposes. The qgis2web map is a direct GIS-to-web export for selected Globasnitz data. The AI-assisted map is an experimental custom interface developed with generative-AI coding support and additional filtering/export functions.

AI-assisted WMA

Custom Leaflet interface with filters, list/map synchronization, selection tools, and data export. Generative AI assisted the software-development process; published archaeological data remain source-controlled project data.

Open AI-assisted WMA

qgis2web WMA

Static Leaflet export produced from QGIS/qgis2web for selected Globasnitz geodata, with the source dataset linked through its ARCHE persistent identifier.

Open qgis2web WMA

Minimal Leaflet example

This deliberately small example shows the technical pattern only. It does not represent an archaeological interpretation.

<div id="map" style="width:100%;height:500px"></div>
<script>
const map = L.map('map').setView([46.55694, 14.70278], 12);
L.tileLayer('https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png', {
  attribution: '&copy; OpenStreetMap contributors'
}).addTo(map);
</script>

Location example from ARCHE place metadata

The three markers use coordinates published in the IUENNA ARCHE-derived place index for Globasnitz, Jaunstein, and Hemmaberg. They are shown as location references only; no archaeological zones or significance are inferred from the marker geometry.

AI-assisted development

Generative-AI tools were used as coding and editing aids in parts of the web-mapping workflow, for example when drafting interface logic, refactoring JavaScript, or reviewing text. Generated suggestions were subject to human review.

The project-specific IUENNA Refiner was tested for metadata-cleaning and formatting support. Its output is not authoritative unless checked against the project data and source records.

Technical strengths and limitations

Strengths: static hosting keeps the deployment simple; QGIS, Leaflet, and qgis2web are open-source tools; persistent repository links preserve a clear route back to source metadata.

Limitations: large client-side vector layers can affect browser performance; qgis2web exports may need manual adjustment; and interactive discovery maps are not substitutes for the archived datasets or their documentation.