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 extent property inside of the IItemAdd interface is set to be number[][], but the REST API docs looks to require the extent to be either a comma separated list of numbers or an array of numbers [xmin,ymin,xmax,ymax] as per the item parameters docs
If we pass in an extent as number[][], e.g. [[xmin,ymin],[xmax,ymax]], then the extent is incorrect in the request made to createItemInFolder, e.g.
Note:
This behaviour has changed since "@esri/arcgis-rest-portal": "2.13.1" where previously extents of the format number[][] were correctly included in the additem request made to the portal.
Many of our existing Webmap items store the extent in their item definition as number[][], as shown in the below image, meaning we are having to write extra code to fix the definitions into number[] when publishing new webmaps which use these as a template.:
The text was updated successfully, but these errors were encountered:
version: 3.03
The extent property inside of the IItemAdd interface is set to be number[][], but the REST API docs looks to require the extent to be either a comma separated list of numbers or an array of numbers [xmin,ymin,xmax,ymax] as per the item parameters docs
If we pass in an extent as number[][], e.g. [[xmin,ymin],[xmax,ymax]], then the extent is incorrect in the request made to createItemInFolder, e.g.
Note:
This behaviour has changed since
"@esri/arcgis-rest-portal": "2.13.1"
where previously extents of the format number[][] were correctly included in the additem request made to the portal.Many of our existing Webmap items store the extent in their item definition as number[][], as shown in the below image, meaning we are having to write extra code to fix the definitions into number[] when publishing new webmaps which use these as a template.:
The text was updated successfully, but these errors were encountered: