Currently in the JSON schema the detail_level property is defined as string. IMHO we should define allowed values as an enum type, to limit the possibilities and allow fully defined mappings for e.g. a map legend.
Until now we have the following values:
exact
rough
corridor
approximated
Maybe we could do something similar for the variant property.
Currently in the JSON schema the
detail_levelproperty is defined as string. IMHO we should define allowed values as an enum type, to limit the possibilities and allow fully defined mappings for e.g. a map legend. Until now we have the following values:Maybe we could do something similar for the
variantproperty.