<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm using leaflet in this 5.000 POI map to show the distribution of
estates in Iceland<br>
<br>
<a class="moz-txt-link-freetext" href="http://osm.hlidskjalf.is/map-estates.php#7/64.767/-18.666">http://osm.hlidskjalf.is/map-estates.php#7/64.767/-18.666</a><br>
<br>
It seems adequate although zooming slows a bit down, each node is
clickable but at the moment only contains the name.<br>
<br>
<br>
<div class="moz-cite-prefix">Þann 17.9.2014 23:32, skrifaði Bryce
Nesbitt:<br>
</div>
<blockquote
cite="mid:CAC9LFPe_w_0B8tjZWBY0M_y+WTBrhdPYq49372mSUgzBij7-hg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>What's the best way to create a global "single point of
interest" map, with OSM?<br>
<br>
<br>
I'm thinking something like this local pay phone map:<br>
<a moz-do-not-send="true"
href="https://a.tiles.mapbox.com/v4/brycenesbitt.j82lj086/page.html?access_token=pk.eyJ1IjoiYnJ5Y2VuZXNiaXR0IiwiYSI6ImNFME9IckkifQ.Nd85HRRFP3Jy3gx8nQ3ATA#14/37.8699/-122.2603">https://a.tiles.mapbox.com/v4/brycenesbitt.j82lj086/page.html?access_token=pk.eyJ1IjoiYnJ5Y2VuZXNiaXR0IiwiYSI6ImNFME9IckkifQ.Nd85HRRFP3Jy3gx8nQ3ATA#14/37.8699/-122.2603</a><br>
But global, and with all the tags for each node shown when the
node is clicked on.<br>
</div>
<div><br>
<br>
</div>
<div>Or this global drinking water map:<br>
<a moz-do-not-send="true"
href="https://www.google.com/fusiontables/embedviz?q=select+col3+from+1usHO73s_NDGKOx-2jbj0xtSHuHjxvWVo_2MvX_o&viz=MAP&h=false&lat=41.571877511144756&lng=-83.65702047624372&t=1&z=4&l=col3&y=2&tmplt=2&hml=GEOCODABLE">https://www.google.com/fusiontables/embedviz?q=select+col3+from+1usHO73s_NDGKOx-2jbj0xtSHuHjxvWVo_2MvX_o&viz=MAP&h=false&lat=41.571877511144756&lng=-83.65702047624372&t=1&z=4&l=col3&y=2&tmplt=2&hml=GEOCODABLE</a><br>
<br>
</div>
<div>But it feels wrong to use Google maps as the backdrop for
OSM data, despite the advantages (the map above has 35,000
nodes many with photos, and yet it is snappy fast on any
browser).<br>
<br>
</div>
<div>What's a better way to do this?<br>
<br>
</div>
<div><br>
----------------------------------------------------------------------------------------------------------------------------<br>
</div>
<div>Note: The mapbox map started with an overpass API query.<br>
<br>
The fusion table example was an extract from the planet file,
merged into a fusion table. Google's servers create and cache
bitmaps with the POI's. User clicks look up the matching
data. Thus it renders as fast as a slippy map, but has all
the POI's readily available.<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk">https://lists.openstreetmap.org/listinfo/talk</a>
</pre>
</blockquote>
<br>
</body>
</html>