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
This applies to all objects which have multiple key-value pairs of the same key. An attribute layer is just a special object which has the same problem: Of e.g. multiple entries for SPEED_LIMIT_METRIC, only the first will be shown in GeoJSON.
To remedy this, we need to think of a strategy to present multi-value object keys. This could mean to render multi-value object fields as a key-list pair. However, this would make some queries harder. Any previous query for key.value would need to be written as key.value or key.*.value.
Alternatively, we can move to a JSON renderer which does not prohibit keys from being emitted redundantly - perhaps we go back to speedyj for this one.
The text was updated successfully, but these errors were encountered:
This applies to all objects which have multiple key-value pairs of the same key. An attribute layer is just a special object which has the same problem: Of e.g. multiple entries for
SPEED_LIMIT_METRIC
, only the first will be shown in GeoJSON.To remedy this, we need to think of a strategy to present multi-value object keys. This could mean to render multi-value object fields as a key-list pair. However, this would make some queries harder. Any previous query for
key.value
would need to be written askey.value or key.*.value
.Alternatively, we can move to a JSON renderer which does not prohibit keys from being emitted redundantly - perhaps we go back to speedyj for this one.
The text was updated successfully, but these errors were encountered: