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
Is your feature request related to a problem? Please describe.
Currently when user draws new features all attribute keys-value pairs need to be retyped manually. This is tedious and we dont provide any checking for key names, if values correspond to a type (number, date etc.), but treat everything as a string. Also we don't check if mandatory attributes are present.
Describe the solution you'd like
A new layer level string property "schema" in json schema format which describes the properties.
Currently GEOSON schema doesn't restrict what's inside "properties" - see {type: 'object'} which is basically any in typescript.
An editor panel/dialog callable from our query panel or layer editor panel which would list and provide editing of all the possible feature attributes by parsing the aforementioned schema string, their type, limits in case of number, mandatory/optional status etc.
Validator functions in query panel which check if user enters the data correctly, if some attribute is not missing etc. We could also use the schema to generate the placeholder textboxes for newly drawn features.
Describe alternatives you've considered
none so far
Feature Request
Is your feature request related to a problem? Please describe.
Currently when user draws new features all attribute keys-value pairs need to be retyped manually. This is tedious and we dont provide any checking for key names, if values correspond to a type (number, date etc.), but treat everything as a string. Also we don't check if mandatory attributes are present.
Describe the solution you'd like
Currently GEOSON schema doesn't restrict what's inside "properties" - see
{type: 'object'}
which is basicallyany
in typescript.This type: 'object' would be possible to substitute with our schema such as:
query
panel which check if user enters the data correctly, if some attribute is not missing etc. We could also use the schema to generate the placeholder textboxes for newly drawn features.Describe alternatives you've considered
none so far
Additional context
There has been some work done from others: https://theodi.org/article/geojson-schema-publishing-a-prototype/
A couple npm packages are dealing with json schema in general: https://www.npmjs.com/search?q=json-schema-editor
We would be interested only in a part of this schema - the one describing "properties" of a feature.
The text was updated successfully, but these errors were encountered: