[Geoserver-devel] [JIRA] (GEOS-10028) Allow to customize ComplexGeoJsonWriter encoding of nested element and non mandatory attributes

GeoServer GeoServer Developer
1

Marco Volpini created an issue

GeoServer / ImprovementGEOS-10028

Allow to customize ComplexGeoJsonWriter encoding of nested element and non mandatory attributes

Issue Type:

ImprovementImprovement

Assignee:

Marco Volpini

Created:

19/Apr/21 12:34 PM

Priority:

MediumMedium

Reporter:

Marco Volpini

Currently the ComplexGeoJsonWriter allows to encode nested Feature as complex property only if their type is NonFeatureTypeProxy. That is a concept strictly related to AppSchema and indeed the NonFeatureTypeProxy requires a[ FeatureTypeMapping to be passed to the constructor|https://github.com/geotools/geotools/blob/f397555ae183955411154b521f1e3442c9865d2e/modules/extension/app-schema/app-schema/src/main/java/org/geotools/data/complex/config/NonFeatureTypeProxy.java#L43].
Moreover when a nested Feature is encoded as a property the type name is encoded as “@dataType” attribute
which is not mandatory for the GeoJSON standard.
The goal is to add an extension point so that other plug-in that serve complex features (eg. schemaless-features community module) can have control over this encoding behaviour.
The current encoding suited for AppSchema complex features will be mantained as default.

Add Comment

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS

This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100157-sha1:a901420)

Atlassian logo