This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 73%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
For routing is it possible to calculate a route that avoids a particular polygon area?
Yes, the POST API of the Azure Maps route service allows you to pass in a MultiPolygon into the body of the request that contains one or more (max 10) polygons to avoid: https://learn.microsoft.com/en-us/rest/api/maps/route/post-route-directions#request-body However, the individual polygons have to be rectangles.
Thanks for the response.
Just to confirm, it is only possible with rectangles, free form polygons & circles are not supported?
So, for example, as part of the request body include this to avoid a polygon area? (currently getting 400 Bad request for the below).
{
"avoidAreas": [
{
"type": "MultiPolygon",
"coordinates": [
[
-1.4165496826156811,
54.01438225967408
],
[
-1.381530761716931,
54.01438225967408
],
[
-1.381530761716931,
54.00550517857593
],
[
-1.4165496826156811,
54.00550517857593
],
[
-1.4165496826156811,
54.01438225967408
]
]
}
]
}
Managed to get it working, above object was incorrect.
According to the docs, it says only rectangles. You can have multiple rectangles (several polygon rectangles in a multi-polygon). You could calculate a bounding box rectangle for circles and free form polygons as a work around. For complete polygons you could calculate a couple of rectangles to approximate the polygon area with less empty space.