Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GeoJSON: add a FOREIGN_MEMBERS=AUTO/ALL/NONE/STAC open option #11515

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

rouault
Copy link
Member

@rouault rouault commented Dec 18, 2024

-  .. oo:: FOREIGN_MEMBERS
      :choices: AUTO, ALL, NONE, STAC
      :default: AUTO
      :since: 3.11.0

      Whether and how foreign members at the feature level should be
      processed as OGR fields:

      - ``AUTO`` mode behaves like ``STAC`` mode if a ``stac_version`` member is found at
        the Feature level, otherwise it behaves as ``NONE`` mode.

      - In ``ALL`` mode, all foreign members at the feature level are added.
        Whether to recursively explore nested objects and produce flatten OGR attributes
        or not is decided by the ``FLATTEN_NESTED_ATTRIBUTES`` open option.

      - In ``NONE`` mode, no foreign members at the feature level are added.

      - ``STAC`` mode (Spatio-Temporal Asset Catalog) behaves the same as ``ALL``,
        except content under the ``assets`` member is by default flattened
        as ``assets.{asset_name}.{asset_property}`` fields.

@rouault rouault added enhancement funded through GSP Work funded through the GDAL Sponsorship Program labels Dec 18, 2024
@rouault rouault added this to the 3.11.0 milestone Dec 18, 2024
@rouault rouault force-pushed the geojson_FOREIGN_MEMBERS branch from 6b0c896 to 525141b Compare December 18, 2024 20:50
```
-  .. oo:: FOREIGN_MEMBERS
      :choices: AUTO, ALL, NONE, STAC
      :default: AUTO
      :since: 3.11.0

      Whether and how foreign members at the feature level should be
      processed as OGR fields:

      - ``AUTO`` mode behaves like ``STAC`` mode if a ``stac_version`` member is found at
        the Feature level, otherwise it behaves as ``NONE`` mode.

      - In ``ALL`` mode, all foreign members at the feature level are added.
        Whether to recursively explore nested objects and produce flatten OGR attributes
        or not is decided by the ``FLATTEN_NESTED_ATTRIBUTES`` open option.

      - In ``NONE`` mode, no foreign members at the feature level are added.

      - ``STAC`` mode (Spatio-Temporal Asset Catalog) behaves the same as ``ALL``,
        except content under the ``assets`` member is by default flattened
        as ``assets.{asset_name}.{asset_property}`` fields.
```
@rouault rouault force-pushed the geojson_FOREIGN_MEMBERS branch from 525141b to e4fe405 Compare December 18, 2024 21:03
@coveralls
Copy link
Collaborator

Coverage Status

coverage: 69.935% (+0.006%) from 69.929%
when pulling e4fe405 on rouault:geojson_FOREIGN_MEMBERS
into 42ca02c on OSGeo:master.

@rouault rouault merged commit e3d2342 into OSGeo:master Jan 6, 2025
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement funded through GSP Work funded through the GDAL Sponsorship Program
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants