The link to Bing Maps mentioned in the README is dead. Wonder why it hasn't been fixed, as the project looks active.
Old link: https://docs.microsoft.com/bingmaps gives a 404.

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

In this page: https://docs.microsoft.com/en-us/bingmaps/rest-services/routes/calculate-a-distance-matrix#api-limits
We are told that

A billable transaction is generated for every 4 cells in a matrix, rounded up to the nearest whole integer

It shows the formula to calculate billable transactions for distance matrix requests as

Total # of billable transactions = Ceiling(# origins * # destinations * 1/4)

Using an example of 2 origins and 5 destinations, the docs calculates the total billable hours as 5
Ceiling(0.5 * 2 * 5 ) = 5

I am wondering where the 0.5 came from, isn't the correct calculation meant to be:
Ceiling(2 * 5 * 0.25) = 3

0.5 is also used when calculating billable transactions for a matrix with a histogram. I stared at this page a very long time, either I have completely forgotten my basic math or I may be missing something. So I'd appreciate any help.
PS: if this is an actual issue can I make a PR? It'll be my first OSS contribution.

I use the tile system class as documented here

This has been working well for years. However recently a bug was reported which boiled down to a lat lng of length x would generate a different key then asking for a key of length x+1.
This violates the rule that removing characters at the end gets you a key to a bigger tile that enconmpasses the smaller one.

I've added a sample test case that fails given the code that's on the page right now.

break the tiles.txt