c0mm0.com — the continuously verified register of European data

Register record·API·FR·REGION·Updated MonthlyVERIFIED · checked 2d ago
O

Objects discovered during archaeological excavations by the City of Chartres and Chartres métropoleObjets découverts lors des opérations archéologiques de la Ville de Chartres et de Chartres métropole

Objets découverts lors des opérations archéologiques de la Ville de Chartres et de Chartres métropoleObjects discovered during archaeological excavations by the City of Chartres and Chartres métropole

APIExecutable4/7Query nowOpen workbenchSubscribe🇫🇷France

This spatial dataset lists objects (ceramics, cut flints, etc.) recorded during archaeological excavations carried out by the Archaeology Department of the City of Chartres and Chartres métropole. Each object is identified and dated, with start and end dates indicating its estimated period. Location precision has reportedly been reduced to prevent looting of archaeological sites. The dataset is published via the regional open-data platform of Centre-Val de Loire and maintained by the Région Centre-Val de Loire, providing access to archaeological findings for research, heritage documentation, and public information purposes.”Vous trouverez, dans ce jeu de données spatiales, les objets (céramique, silex taillés, etc.) relevés lors des opérations archéologiques de la Direction de l’archéologie (Ville de Chartres et Chartres métropole). Chaque objet est identifié et daté (dates de début et de fin). Pour éviter les pilla...

geospatialgovernment
57
fair

Weighted across five axes. Tap a ring for what it measures.

Data schema (9 fields)

Filterable via the API (7)
idopenumunobstypunobsinterpretdatedebutdatefinperiode

Click a field to see example values.

FieldTypeDescription
idopeFilterable via the APIIdentifiant de l'opérationtextInternal identifier of the archaeological operation (country code, INSEE code, order number).Identifiant interne de l'opération archéologique. Il comprend le numéro du pays, le code INSEE et un numéro d'ordre. Il permet de faire le lien avec l'opération associée. (Clé étrangère)
numunobsFilterable via the APINuméro de l'unité d'observationtextField registration number of the observation unit.Numéro d'enregistrement de terrain de l'unité d'observation.
typunobsFilterable via the APIType d'unité d'observationtextType of observation unit, e.g. 'isolat' for a mapped object.Typologie de l'unité d'observation. La valeur "isolat" correspond à un objet topographié sur le terrain (ex. céramique, os, silex...).
interpretFilterable via the APIInterprétationtextInterpretation or nature of the isolated object (e.g. ceramic, flint).Interprétation de l'isolat.
datedebutFilterable via the APIDate de débuttextStart date of the object's production.Date de début de production de l'objet.
datefinFilterable via the APIDate de fintextEnd date when the object's production or use ceased.Date de fin correspondant à l'arrêt de la production ou de l'utilisation de l'objet.
periodeFilterable via the APIPériodetextHistorical period(s) corresponding to the start and end dates.Période(s) correspondante(s) à la date de début et la date de fin.
geomGéométrie de l'unité d'observationgeo_shapeGeographic shape of the observation unit.Géométrie de l'unité d'observation.
geo_point_2dCoordinatesgeo_point_2dGeographic coordinates (latitude and longitude) of the object.Geographic coordinates (latitude and longitude) of the object.

Schema captured from opendatasoft 2 days ago.

Query the data

Pick columns and a sort, then fetch a live preview straight from the source. Choose an API-filterable column (marked ▾) under “Where” to pick from its list of values.

=

Sample data (5 records)

These rows are ODbL-1.0: share-alike. Reusing them obliges you to license any derived database on the same terms.

Record 1geom: {"type":"Feature","geometry":{"type":"Mu · idope: 03328253010002
{
  "geom": {
    "type": "Feature",
    "geometry": {
      "type": "MultiPoint",
      "coordinates": [
        [
          1.4289278,
          48.3609458
        ]
      ]
    },
    "properties": {}
  },
  "idope": "03328253010002",
  "datefin": "-3500",
  "periode": "neolithique",
  "numunobs": "15196.4002",
  "typunobs": "isolat",
  "datedebut": "-4500",
  "interpret": "silex",
  "geo_point_2d": {
    "lat": 48.3609458,
    "lon": 1.4289278
  }
}
Record 2geom: {"type":"Feature","geometry":{"type":"Mu · idope: 03328006004003
{
  "geom": {
    "type": "Feature",
    "geometry": {
      "type": "MultiPoint",
      "coordinates": [
        [
          1.4257084,
          48.445218
        ]
      ]
    },
    "properties": {}
  },
  "idope": "03328006004003",
  "datefin": null,
  "periode": "indetermine",
  "numunobs": "2014.2",
  "typunobs": "isolat",
  "datedebut": null,
  "interpret": "clou",
  "geo_point_2d": {
    "lat": 48.445218,
    "lon": 1.4257084
  }
}
Record 3geom: {"type":"Feature","geometry":{"type":"Po · idope: 03328085034022
{
  "geom": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        1.5190359,
        48.4558737
      ]
    },
    "properties": {}
  },
  "idope": "03328085034022",
  "datefin": "-4000",
  "periode": "neolithique",
  "numunobs": "2100.302",
  "typunobs": "isolat",
  "datedebut": "-4300",
  "interpret": "céramique",
  "geo_point_2d": {
    "lat": 48.4558737,
    "lon": 1.5190359
  }
}
Record 4geom: {"type":"Feature","geometry":{"type":"Mu · idope: 03328253010002
{
  "geom": {
    "type": "Feature",
    "geometry": {
      "type": "MultiPoint",
      "coordinates": [
        [
          1.4289233,
          48.3609522
        ]
      ]
    },
    "properties": {}
  },
  "idope": "03328253010002",
  "datefin": "-3500",
  "periode": "neolithique",
  "numunobs": "15317.4094",
  "typunobs": "isolat",
  "datedebut": "-4500",
  "interpret": "silex",
  "geo_point_2d": {
    "lat": 48.3609522,
    "lon": 1.4289233
  }
}
Record 5geom: {"type":"Feature","geometry":{"type":"Mu · idope: 03328253010002
{
  "geom": {
    "type": "Feature",
    "geometry": {
      "type": "MultiPoint",
      "coordinates": [
        [
          1.4289147,
          48.3609501
        ]
      ]
    },
    "properties": {}
  },
  "idope": "03328253010002",
  "datefin": "-3500",
  "periode": "neolithique",
  "numunobs": "15317.3634",
  "typunobs": "isolat",
  "datedebut": "-4500",
  "interpret": "céramique",
  "geo_point_2d": {
    "lat": 48.3609501,
    "lon": 1.4289147
  }
}

Live sample captured at profiling time — values may have changed upstream.

Verification Status

Using the API

Configuration

Base URL
https://data.centrevaldeloire.fr/api/explore/v2.1/catalog/datasets/objets-decouverts-lors-des-operations-archeologiques-de-la-ville-de-chartres-et-

License

  • ✓ Redistributable
  • ✓ Attribution required

Query examples

curl -s 'https://data.centrevaldeloire.fr/api/explore/v2.1/catalog/datasets/objets-decouverts-lors-des-operations-archeologiques-de-la-ville-de-chartres-et-/records?limit=20' -H 'Accept: application/json'

First 20 records of the dataset as JSON.

Uses the Opendatasoft Explore v2.1 syntax — supports select, where, group_by and order_by.

Full API documentation ↗

Rate limits

15 000 req/day
per ipmeasured
observed 2 days ago

Dataset

Volume & freshness

Records
6.2k
6214
Update cadence
Monthly
declared upstream
Last upstream update
3 years ago
2024-04-10
Temporal coverage
2000 → ongoing

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: opendatasoft

Machine-readable & source

Objets découverts lors des opérations archéologiques de la Ville de Chartres et de Chartres métropole — live verification badge

Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.