Spain Castilla y León field boundaries in the fiboa schema, 1 edition (2025). Every claim below is quoted from the source, the converter, or measured from the published files; each query was run before it was written down, and its output follows it as comments.
https://data.source.coop/ftw/harmonized-field-data/es_cl/latest/es_cl.parquethttps://data.source.coop/ftw/harmonized-field-data/es_cl/year=<year>/<file>.parquet, e.g. https://data.source.coop/ftw/harmonized-field-data/es_cl/year=2025/es_cl.parquets3://ftw/harmonized-field-data/es_cl/year=*/*.parquet — the S3 form of the same prefix through the Source Cooperative proxy, because * needs a listing that plain https does not provide. In DuckDB: CREATE SECRET sc (TYPE s3, PROVIDER config, ENDPOINT 'data.source.coop', URL_STYLE 'path', REGION 'us-west-2'); then read_parquet(glob, hive_partitioning = true) adds the year column. No credentials are needed.https://data.source.coop/ftw/harmonized-field-data/es_cl/year=2025/es_cl.pmtiles, layer es_cl; MapLibre styles in styles/.ST_Area/ST_Distance return units of that CRS; transform with ST_Transform if you need lon/lat, or use metrics:area.year is the edition, not the observation date. It is the year of the source publication (the converter variant). determination:datetime, where present, is the source's own date for a field.id is only guaranteed unique within one edition (fiboa requires uniqueness per file; it is the source column DN_OID). Whether an id persists across editions is not verified here; do not join editions on it without checking.collection key-value metadata: admin:country_code = ES, crop:code_list = https://fiboa.org/code/es/sigpac/land_use.csv, admin:subdivision_code = CL, determination:datetime = 2025-01-01T00:00:00Z (2025 edition). Read them with parquet_kv_metadata() in DuckDB or pyarrow.parquet.ParquetFile(f).schema_arrow.metadata[b'collection']; they differ per edition where the source does.Fields and hectares per edition, through the partition glob:
Fields around a point, transforming the point into the data's CRS instead of the data into WGS84:
Every collection in this catalog shares the fiboa core columns, so the same queries work across countries; s3://ftw/harmonized-field-data/*/latest/*.parquet with union_by_name = true reads the newest edition of all of them (see the catalog AGENTS.md).
Assets and structural links resolve relative to the object that carries them; there is no self link. Source: this collection is generated by tools/catalogize.py in the catalog repository — fix documentation there.