# Requested resource was not found Error Message

**URL:** <https://opendataforum.transport.nsw.gov.au/t/requested-resource-was-not-found-error-message/2198>\
**Category:** App development\
**Created:** [December 10, 2020, 3:33pm UTC](https://opendataforum.transport.nsw.gov.au/t/requested-resource-was-not-found-error-message/2198 "2020-12-10T15:33:15Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jxeeno](https://sea1.discourse-cdn.com/flex019/user_avatar/opendataforum.transport.nsw.gov.au/jxeeno/32/210_2.png) [@jxeeno](https://opendataforum.transport.nsw.gov.au/u/jxeeno)\
**Post date:** [December 12, 2020, 11:10am UTC](https://opendataforum.transport.nsw.gov.au/t/requested-resource-was-not-found-error-message/2198/6 "2020-12-12T11:10:17Z")

</div>

Hi Mike,

Did some debugging and it looks like the issue is with slight differences in underground tunnel alignments between polyline you’re passing into the API vs OpenStreetMap (which is what the toll calculator’s mapping data is based on).

You can specify manually specify a match accuracy using the `"accuracy"` parameter in the JSON payload. For your polyline, 30m seems to work ok:

```auto
{
	"polyline": "noenE}ayy...",
	"accuracy": 30
}

```

---

_[View the full topic](https://opendataforum.transport.nsw.gov.au/t/requested-resource-was-not-found-error-message/2198)._