I'm impressed that it worked so smoothly after I entered Tokyo. Fully expected my phone's browser to crash at any time as it proceeded to download 34MB of data. Scrolling and zooming didn't even stutter.
It also appears to render footpaths in parks etc, which makes it look a bit weird in places - the monochrome rendering made it hard for me to find locations and the landmarks I am used to seeing (i.e. major parks and green space) were hard to find as they had "roads" criss-crossing them (when they don't in real life)
It filters to ways with the "highway" attribute, which has possible values including "footway", "bridleway", "steps", and "corridor" in addition to the ones you'd expect with the American definition of the word ("motorway", etc)
I was surprised to see that it included the structure of a garden maze in my local park that is totally unmaintained and that I’ve never seen anybody enter.
It rendered my dead-end, private driveway. Does this mean that the data doesn't distinguish "roads" from other paths, that the data has some errors, or that the program is rendering more than just labeled "roads"?
Readit News
I've done a thing with the same base idea in the past, and absolutely love the style of those things, especially if there are enough roads available to get a more dense shape: https://christian.rinjes.me/posts/2020-11-25-tokyo-street-ar...
https://wiki.openstreetmap.org/wiki/Key:highway?uselang=en
https://github.com/anvaka/city-roads/blob/08a21bce05ad2b08d4...