[latkin]

In case others gave up, it took about 2.5 minutes to load my (midsize city) hometown from OpenStreetMap. So hang in there.

[remram]

Probably going to hit the paradox here, where most people are going to request a place where many people live, even though most places are small.

I probably have no chance, living in NYC.

[zactato]

I would expect the opposite with a basic LRU cache before the fetch to OSM

[remram]

That's fair unfortunately it's not what happened :-(

[dotancohen]

I'm in a city well under 50,000 people not in the Americas nor Europe. The site gave a message that it was retrieving the data from OSM, then rendered the map faster than the browser would render a png. Very impressive.

[sandworm101]

I'm at 10 minutes now, for a town of <15k. Render time might depend more on total area than number of lines to draw. Update: gave up after 20min. Something might be wrong with the particular city.

[fnordpiglet]

Render time for Seattle is a blink of the eye which has both area and density. I think the time people is observing is loading the raw data from open street map itself.

[Capricorn2481]

Because they cache the biggest cities in the world.

> To improve the performance of download, I indexed ~3,000 cities with population larger than 100,000 people and stored into a very simple protobuf format. The cities are stored into a cache in this github repositor

[flufluflufluffy]

About 2 seconds for me to load and draw Los Angeles. It’s definitely the load time/network latency, depending on where it’s loading from. This is amazing! I might use it for a custom map or something

[NavinF]

That's surprising. It only took me a couple of seconds to load NYC on my iPhone over 5G

[zipping1549]

Some cities are cached and NYC is going to be in it for sure.