<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 16, 2015 at 7:42 PM, Richard Welty <span dir="ltr"><<a href="mailto:rwelty@averillpark.net" target="_blank">rwelty@averillpark.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<div>On 5/16/15 1:19 PM, Kotya Karapetyan
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Though I strongly disagree to the idea of "mapping
for the renderer", I agree that there is a huge problem: a lot
of data available in OSM database is effectively lost because
the renderers do not show it.</div>
</blockquote></span>
on the other hand, demanding that the rendering on
<a href="http://www.openstreetmap.org" target="_blank">www.openstreetmap.org</a><br>
be all things to all people is actually pretty unreasonable. the
current<br>
architecture which separates data from style is well considered and
in line<br>
with modern best practices; i haven't yet seen an argument that
would<br>
persuade me otherwise.<br>
<br></div></blockquote><div><br></div><div>The idea of mixing style and data was not implied! They are separate and should remain such. I was only complaining about inability to see the data, in whichever usably form. Currently there are two ways I can see some data: switch on editing (bad, because I can screw data up) or use the query tool (bad, because I cannot see the presence of a feature, I need to click the map to find it).</div><div> </div><div>Also I didn't mean that <a href="http://www.osm.org">www.osm.org</a> should be the place to show all data. It can well be a separate site.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
what we could use are more people doing projects like opencyclemap
and<br>
openfiremap and the like to bring out the data they care about in
formats<br>
that they like.<br></div></blockquote><div><br></div><div>Good idea. Though, for the sake of usability, it would be great to have a single site capable of showing everything. The problem is of course that OSM doesn't restrict tagging in any way, meaning that it's barely possible to create layers for different tags.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
<br>
my presentation at SOTM US will include examples of using leaflet,
jquery<br>
and overpass to create mashups of OHM and OSM data, and i'll be
making<br>
my javascript available on the ohm github repository under a 3
clause BSD<br>
license for anyone who wants to play.<br>
<br></div></blockquote><div><br></div><div>I will be very much interested in having a look. </div><div><br></div><div>Cheers,</div><div>Kotya</div></div></div></div>