GRAV Frontmatter is agnostic as long as the yaml syntax is correct. This means you can use the Frontmatter to store data structures âunknownâ to GRAV. The GEO data structure you expose here cannot be handled by GRAV out of the box and I donât know if thereâs a plugin that allows you to handle this. Whatâs probably needed is a dedicated plugin and / or field type for this data or you have to rewrite the data structure to adapt to whatâs available out of the box in GRAV. GRAV offers exhaustive information on fields, types, collections and their usage in pages: Learn GRAV: Forms
the way I have approached this is to use a list at the features level
header.features:
name: Features
type: list
style: vertical
label: Features
then create a custom heading underneath
.geometry.type:
type: select
label: Select one of the following geometry types
default: Point
.type:
type: hidden
default: "Feature"
.properties.hours:
type: text
label: Enter Opening Hours
Iâm still to work out how to create the coords yet, but with a little persistence Iâm sure ill get there
I did try the Array field originally but overlooked the value only, it works but I need the value to be saved as a number and not a string i.e. 174.7676 instead of â174.7676â
to resolve the other issues is used this to save my data I used a field sets for geometry and properties worked like a charm using lists just didnât work with other sublevel items