You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal of this data structure is to easily allow the addition/removal of new attributes and its corresponding information. The UI should be generated from this dataset.
Every attribute should contain things like:
DELFI id
Name and description/question.
The corresponding OSM tag
Allowed values and value type
Values contain optionally a list of child attributes that will be shown if the particular value is selected (attributes are referenced via DEFLI id)
The order of the values describes the usage of the value (high usage means low index)
In question:
Always provide a value selection but also always allow custom values?
Example JSON data structure
{
id: 2,
name: "Bahnsteig Typ",
details: "",
tag: "amenity",
values: [
{
value: "1",
name: "item 1",
image: "nameoftheimage.svg",
details: "some further details that describe this attribute",
children: [3, 5]
},
{
value: "2",
name: "item 2",
image: "nameoftheimage2.svg",
details: "some further details that describe this attribute"
},
...
]
}
The text was updated successfully, but these errors were encountered:
For consistency, inherit documentation and error prevention/validation ideally a JSON schema (http://json-schema.org/) should be worked out here.
Each value should also contain a boolean attribute that indicates if the data/tag is an official OSM tag and can therefore be directly transferred to OSM.
The goal of this data structure is to easily allow the addition/removal of new attributes and its corresponding information. The UI should be generated from this dataset.
Every attribute should contain things like:
In question:
Example JSON data structure
The text was updated successfully, but these errors were encountered: