Update specification to use Vecorel

Author: m-mohr

.github/workflows/test.yaml

@@ -8,7 +8,7 @@ jobs:
     steps:
       - uses: actions/setup-python@v5
         with:
-          python-version: '>=3.9'
+          python-version: '>=3.10'
       - uses: actions/checkout@v4
       - name: Install pipenv
         run: |
@@ -20,7 +20,7 @@ jobs:
     steps:
       - uses: actions/setup-python@v5
         with:
-          python-version: '>=3.9'
+          python-version: '>=3.10'
       - uses: actions/checkout@v4
       - name: Install pipenv
         run: |
@@ -33,12 +33,10 @@ jobs:
     steps:
       - uses: actions/setup-python@v5
         with:
-          python-version: '>=3.9'
+          python-version: '>=3.10'
       - uses: actions/checkout@v4
       - name: Install pipenv
         run: |
           pip install pipenv
           pipenv install
-      - run: pipenv run test-geojson-features
-      - run: pipenv run test-geojson-collection
-      - run: pipenv run test-geoparquet
+      - run: pipenv run test-examples

CHANGELOG.md

@@ -10,35 +10,23 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 ### Added
 
 - Property `category`
-- Property `determination_details`
-- Information about the encoding of datatypes at the collection-level
+- Property `determination:details`
 
 ### Changed
 
-- Switched from v0.1.0 to v0.2.0 of the schema language
-- Renamed `fiboa_extensions` to `schemas`
-- Schemas must be valid HTTP(S) URLs
-- GeoParquet: Renamed Parquet metadata key from `fiboa` to `collection`
-- GeoJSON: Switched `contentEncoding` for data type `binary` from `binary` to `base64`
-- GeoJSON data types: `null` is not allowed any longer, instead omit the property
-- GeoJSON FeatureCollection: Collection-level data is provided at the top-level, not in a `fiboa` property
+- fiboa is an extension to the Vecorel specification now
+- Renamed `determination_method` to `determination:method`
+- Renamed `determination_datetime` to `determination:datetime`
 
 ### Removed
 
-- Value `administrative` was removed from `determination_method` in favor of the new property `category`
+- Value `administrative` was removed from `determination:method` in favor of the new property `category`
 - `fiboa_version` in favor of adding the schema URL of the specification to `schemas`.
-- GeoJSON Feature: `links` property
 
 ### Fixed
 
 - Various minor clarifications and editorial enhancements
-- Added descriptions to the allowed values for `determination_method`
-- Clarified handling of missing values
-- GeoJSON: Clarify the encoding of the top-level properties (including `links` and `fiboa`)
-- GeoJSON: Clarify the use of RFC 7946
-- GeoParquet: Properties that are optional can be omitted if all values are null values
-- GeoParquet: Added encoding for bounding boxes and objects
-- GeoParquet: Clarified the use of Map and Struct data types
+- Added descriptions to the allowed values for `determination:method`
 
 ## [v0.2.0] - 2024-04-10
 

CITATION.cff

@@ -9,8 +9,8 @@ preferred-citation:
   title: "Field Boundaries for Agriculture (fiboa) specification"
   abstract: "Making field boundaries openly available in a unified way."
   version: 0.3.0
-  year: 2024
-  date-released: 2024-04-10
+  year: 2025
+  date-released: 2025-08-26
   license: Apache-2.0
   url: https://github.com/fiboa
   repository: https://github.com/fiboa/specification

CODE_OF_CONDUCT.md

@@ -34,7 +34,7 @@ Releases are cut from main, see the [process](process.md) document for more deta
 
 ## Check files
 
-You'll need to install Python >= 3.9 and pip to setup the test environment.
+You'll need to install Python >= 3.10 and pip to setup the test environment.
 We use pipenv to execute the tests.
 
 Start with the following command in the folder where this README is located:
@@ -47,7 +47,5 @@ Finally, you can run the tests as follows:
 
 - To check the markdown run: `pipenv run test-docs`
 - To check the fiboa schema run: `pipenv run test-schema`
-- To check the examples run:
-  - `pipenv run test-geojson-collection` and `pipenv run test-geojson-features` for GeoJSON
-  - `pipenv run test-geoparquet` for GeoParquet
+- To check the examples run: `pipenv run test-examples`
 - To create a GeoParquet from the GeoJSON examples: `pipenv run create-geoparquet`

CONTRIBUTING.md

@@ -4,13 +4,11 @@ verify_ssl = true
 name = "pypi"
 
 [packages]
-fiboa-cli = ">=0.4"
+fiboa-cli = ">=0.20"
 pymarkdownlnt = ">=0.9"
 
 [scripts]
 test-docs = "pymarkdown -d md024,md013 scan ."
 test-schema = "fiboa validate-schema core/schema/schema.yaml"
-test-geojson-collection = "fiboa validate geojson/examples/featurecollection -s core/schema/schema.yaml --data"
-test-geojson-features = "fiboa validate geojson/examples/individual-features -s core/schema/schema.yaml --data"
-test-geoparquet = "fiboa validate geoparquet/examples -s core/schema/schema.yaml --data"
-create-geoparquet = "fiboa create-geoparquet geojson/examples/featurecollection/features.json -o geoparquet/examples/example.parquet -s core/schema/schema.yaml"
+test-examples = "fiboa validate examples -s https://fiboa.org/specification/v0.3.0/schema.yaml,core/schema/schema.yaml -n -1"
+create-geoparquet = "fiboa create-geoparquet examples/example.json -s https://fiboa.org/specification/v0.3.0/schema.yaml,core/schema/schema.yaml -o examples/example.parquet"

Pipfile

@@ -22,17 +22,18 @@ The core data schema of fiboa is quite simple: it’s a set of definitions for a
 The number of attributes in the core is quite small by design.
 The idea is that most of the ‘interesting’ data about the field will be located in extensions.
 
-The specification in this repository consists of three parts:
+The specification in this repository consists of just one fudamental part:
 
 - [Core Specification](core/README.md)
   (file format agnostic definition for data and metadata)
-- [GeoJSON Encoding](geojson/README.md)
-- [GeoParquet Encoding](geoparquet/README.md)
 
-To complement the specification, there are also best practices and extensions available:
+It can be enriched by extensions and there's a
+[list of extensions](https://vecorel.org/extensions/).
 
-- [Best Practices](best-practices/README.md)
-- [Extensions](https://github.com/fiboa/extensions/)
+> [!NOTE]  
+> Internally, the fiboa specification is an extension to the Vecorel ecosystem and 
+> is fully compatible with it. In fact, Vecorel and fiboa share significant portions of
+> the extensions and tooling.
 
 ## Relation to other standards and working groups
 
@@ -43,6 +44,7 @@ e.g. the determination-related fields in the core specification.
 
 Related standards and working groups are:
 
+- [Vecorel](https://vecorel.org)
 - [Adapt standard](https://adaptstandard.org), including their [WG17](https://github.com/ADAPT/Standard/issues/97)
 - [Varda FieldID](https://www.varda.ag/global-field-id)
 - [Deere Boundaries](https://developer.deere.com/dev-docs/boundaries)
@@ -57,6 +59,6 @@ Please get in touch by [opening an issue](https://github.com/fiboa/specification
 The fiboa community strives to provide a welcoming and transparent environment for all of the project’s participants.
 You can find additional information about our community best practices and collaborative development processes below:
 
-- [Code of Conduct](CODE_OF_CONDUCT.md)
+- [Code of Conduct](https://vecorel.org/code-of-conduct/)
 - [Contribution Guideline](CONTRIBUTING.md)
-- [Development and Release Process](process.md)
+- [Development and Release Process](https://github.com/vecorel/specification/blob/main/process.md)