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
addItem and updateItem both expect extent to be a flattened string instead of a bbox ( 1, 2, 3, 4 vs [[1, 2], [3, 4]] ). Apparently around two years ago we made a change to processParams ( #779 ) for catalog to allow array of arrays through. At that time it was decided to do that for all the cases so as to not make an explicit reference to a property. Unfortunately that has broken extent. What ends up happening is in the actual request the bbox is split into two different extent params, the create/update call succeeds, however the item ends up with an extent which is simply an empty array.
Reproduction
Will be provided
Logs
No response
System Info
v3.4.3
Additional Information
No response
The text was updated successfully, but these errors were encountered:
@benstoltz please implement the conversion from number[][] to string in the createItem and updateItem functions, and leave the processParams function as-is
Describe the bug
addItem
andupdateItem
both expectextent
to be a flattened string instead of a bbox (1, 2, 3, 4
vs[[1, 2], [3, 4]]
). Apparently around two years ago we made a change toprocessParams
( #779 ) for catalog to allow array of arrays through. At that time it was decided to do that for all the cases so as to not make an explicit reference to a property. Unfortunately that has brokenextent
. What ends up happening is in the actual request the bbox is split into two different extent params, the create/update call succeeds, however the item ends up with an extent which is simply an empty array.Reproduction
Will be provided
Logs
No response
System Info
Additional Information
No response
The text was updated successfully, but these errors were encountered: