mcbroken-archive VS factbook.json

Edge computing will enable applications like predicting when kitchen equipment—such as fryers and its notorious McFlurry ice cream machines—is likely to break down, Rice said.

It is not hard to know if a machine is broken. There is an entire map dedicated to this, which shows state-wide broken rate as high as 40% for some states.

https://mcbroken.com/

If you know these machines are broken and they are not being fixed, what use will be to know what machines will break in the future? This is not a technology problem, this is a business and people problem. Another case of companies using AI to garner positive marketing, instead of improving their service and customer's experience.

Try mcbroken.com.

There is a hot mic admission by Taylor representatives that the McFlurry machine was designed specifically to increase maintenance costs to extract more money from franchisees.

Working McFlurry machine map: https://mcbroken.com

The McBroken is a real time website that lets you know the exact location of every working and non-working McDonald's ice cream machine.

Maybe checkout factbook to see if it fits your needs? The source data is from the CIA’s The World Factbook, which is fairly robust. Not sure if it’ll contain local administrative districts or municipalities though.

i am thinking about mapping some of factbook.json into triples.

I have been searching high and low for a (relatively) simple and straightforward server that loads an arbitrary JSON document sitting on disk and exposes its contents as a REST API (sort of like a JSONpath). Because I'd like to query JSON documents on my servers (e.g., the World Factbook as JSON), and optionally search them without having to load everything into a database.

Good point. See the F.A.Q. entry - Q: Why not just use the ISO country codes? Not a bug, a feature request.