3 ms·
This is absolutely great, but I have two observations: 1. Google's embedded maps & API are significantly faster than their own maps on https://maps.google.com/
by lucideer 9y ago
This is absolutely great, but I have two observations:
1. Google's embedded maps & API are significantly faster than their own maps on https://maps.google.com/ https://maps.google.com/. That particular team seems to have just recently fired or re-assigned every developer with any knowledge or - more likely, interest in - performance
2. I would guess the performance of the openstreetmap.org tileservers are the biggest bottleneck in your example. Their own website says "The tile service comes with no guarantee as to availability or speed", which is why alternative hosts of that dataset are so proliferate. Including a few alternative OSM tile hosts like opencyclemap, Mapbox, Mapzen, &c. could be very interesting.
- mistermann 9y agoAre you saying the maps API (which this demo uses) is fast, but the maps website itself is slow? That 100% matches my experience. But how could that be?
- GoToRO 9y agoThe API maps and google.com/maps are different products. Maybe they reuse some code but they do not have the same features. On google.com/maps if you search for a teritory (like a country) you will get a red border arround that teritory. On API maps developers asked for this feature for years and it is still not available.