<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "><span>> </span><span style="color: rgb(69, 69, 69); font-family: arial, helvetica, sans-serif; font-size: 14px; ">All I'm saying is that we must not focus solely on the map - it's bad</span></div><span style="color: rgb(69, 69, 69); font-family: arial, helvetica, sans-serif; font-size: 14px; ">> enough if our mappers already do that ;)</span><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "> </div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; ">Ok, let's focus on routing. There's been discussion and agreement before (several years now)</div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; ">that having routing
integrated in OSM.org in some way would be valuable to mappers </div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; ">because <span style="font-size: 12pt; ">it allows mappers to check the viability of OSM data for routing. </span></div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal; "><span style="font-size: 12pt; ">Tiles and nominatim integration on OSM.org provide a similar function.</span></div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal; "><span style="font-size: 12pt; "><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal; ">Routing has not been
integrated ad hoc. It's complicated both in terms of back end and interface.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal; ">We need a realistic and practical plan for routing to be integrated into OSM. We need to try another strategy.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal; "><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal; ">The most promising strategy right now is the model we employed for the redaction bot, hiring someone to lead the effort.</div><div style="color: rgb(0, 0, 0); font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style:
normal; "><span style="font-size: 12pt; "><br></span></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "><br></div><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; ">* Mikel Maron * +14152835207 @mikel s:mikelmaron<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Frederik Ramm <frederik@remote.org><br> <b><span style="font-weight: bold;">To:</span></b> osmf-talk@openstreetmap.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Thursday, August 23, 2012 3:10 PM<br> <b><span style="font-weight:
bold;">Subject:</span></b> Re: [Osmf-talk] Question to board members<br> </font> </div> <br>
Hi,<br><br>On Thu, 23 Aug 2012 22:13:18 +0300<br>Rich <<a ymailto="mailto:richlv@nakts.net" href="mailto:richlv@nakts.net">richlv@nakts.net</a>> wrote:<br>> we don't send a message like that, it's just human nature - no<br>> reward, no motivation.<br><br>Yep. I'm all for more rewards! But those can come in many forms, and<br>Jaakko was specifically saying that people don't map what is not SHOWN<br>ON THE MAP, which is only one of many potential forms of reward.<br><br>> in a similar manner i have every now and then not mapped things i<br>> know won't show up.<br><br>That's because the map is a nicer reward than, say, some<br>simple statistic saying "Rich has contributed 1024 nodes today". But<br>there could be many other forms of reward, for example nicer and more<br>meaningful statistics broken down by areas or whatever. "Rich has<br>contributed 25% of routing-specific data in the area you are<br>viewing". (Where routing-specific data
= turn restrictions, speed<br>limits, access restrictions - all hugely important stuff that is<br>difficult to show on any map, even at z20.)<br><br>All I'm saying is that we must not focus solely on the map - it's bad<br>enough if our mappers already do that ;)<br><br>Bye<br>Frederik<br><br><br>_______________________________________________<br>osmf-talk mailing list<br><a ymailto="mailto:osmf-talk@openstreetmap.org" href="mailto:osmf-talk@openstreetmap.org">osmf-talk@openstreetmap.org</a><br><a href="http://lists.openstreetmap.org/listinfo/osmf-talk" target="_blank">http://lists.openstreetmap.org/listinfo/osmf-talk</a><br><br><br> </div> </div> </blockquote></div> </div></body></html>