Add early support for JSON-FG#2136
Conversation
e88d476 to
2359c2e
Compare
|
How does this provider differ from a (generic) GDAL based formatter capable of formatting to any OGR data type? |
|
It is very close potentially, what are you imaging? |
| with gdal.OpenEx(json.dumps(data)) as srcDS: | ||
| tmpfile = f"/vsimem/{uuid.uuid1()}.json" | ||
| LOGGER.debug("Translate GeoJSON into a JSONFG memory file") | ||
| gdal.VectorTranslate(tmpfile, srcDS, format="JSONFG") |
There was a problem hiding this comment.
Well once you read it into GDAL, any vector driver transform can occur. Wondering if would be possible to make any output format in the same spirit of the OGR provider - formatter config only barrier to add Shapefile, KML, etc. as an output format for pygeoapi GeoJSON.
|
This Pull Request has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days. |
|
@francbartoli given #2144 looks like this can be now implemented as a standalone formatter. Are you able to update accordingly? |
|
pygeoapi meeting 2026-05-15
|
Overview
This PR adds support to the most recent JSON-FG specification
0.3. It returns JSON-FG formatted payload with the following conformance classes:http://www.opengis.net/spec/json-fg-1/0.3/conf/corehttp://www.opengis.net/spec/json-fg-1/0.3/conf/types-schemasA new formatter has been added to the core for that scope and must rely on
GDAL>=3.12which supports0.3(not yet released as of today). As a consequence, this is a breaking change for our dependencies chain and cannot be merged untilrasteriowill support that version as well.This potentially might be relaxed after the merge of this branch https://github.com/geopython/pygeoapi/tree/formatters to have the formatter configurable at resource level and so the GDAL requirement needed only if it is configured.
Related Issue / discussion
Additional information
Dependency policy (RFC2)
Updates to public demo
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)