Hi Koen,<br><br>We are not lawyers, but the whole idea of having a freely available map is to enable the use you are describing. The whole project is in the process of changing the license to ODBL. Normally this should be good news, as it's meant to clarify how the data can be used. I'm afraid you're going to have to wade through some wiki pages and maybe ask your questions and describe your doubts on <a href="mailto:legal-talk@openstreetmap.org" target="_blank">legal-talk@openstreetmap.org</a>.<br>
<br><a href="http://wiki.openstreetmap.org/wiki/Open_Database_License" target="_blank">http://wiki.openstreetmap.org/wiki/Open_Database_License</a><br><br>Basically what it all comes down to is that you have to put a mention somewhere accompanying the map or the data to accredit the Openstreetmap project and that you have to license your improvements to the data under the same license.<br>
<br>Of course you can PRESENT a mix of both OSM data and proprietary data. The easiest way is probably to work with layers in that case. It's not a problem that the application doing the combining and the presenting is proprietary, as long as credit is given where credit is due.<br>
<br>Oh, I see Gerard already described it a lot more eloquently than I did...<br><br>On the input side, I think it's best your contributors all create OSM accounts and enter their data directly into the OSM database.<br>
<br>Cheers,<br><br>Jo<br><br><div class="gmail_quote">2011/8/22 Koen Mannaerts [<a href="http://fietsnet.be" target="_blank">fietsnet.be</a>] <span dir="ltr"><<a href="mailto:koen@fietsnet.be" target="_blank">koen@fietsnet.be</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<font face="Verdana">Hi Jo</font>, Kurt,<br>
<br>
Thanks heaps for helping!<br>
<br>
The most pressing question is about the OSM license. I'm still not
entirely sure what OSM considers a derivative or produced work.<br>
The idea is that our contributors will extend, complete or correct
the OSM map, as far as trajectory information is concerned: nodes,
the rcn relationships, highway, bicycle, foot keyvalues, ...<br>
Periodically, Fietsnet will import all this data, connect it to
other sources (external like meteo and event poi's, internal like
statistics and usage data), and generate graph and track tiles.
These binary tiles will be used by the publicly available, yet
proprietary, routeplanner application.<br>
<br>
I'm not sure OSM's license allows for this scenario.<br>
<br>
Kind regards,<br><font color="#888888">
<br>
Koen</font><div><div></div><div><br>
<br>
<br>
<br>
<br>
Jo wrote:
<blockquote type="cite">Hi Koen,<br>
<br>
That is great news! We always like to work together with other
groups. Many of the cycle node networks
(fietsknooppuntennetwerken) are already in OSM, but more eyes and
hands will certainly improve the map. We have many more of the
small roads (wandelpaden/fietspaden) than Googlemaps, so I believe
it will be a lot better as a background layer for your route
planner.<br>
<br>
If you want to organise a presentation for your members, I'd be
happy to come and explain how to enter the data (preferably with
JOSM, since it is a lot more convenient to enter route relations).
I can also explain how to convert a selection of routes into a gpx
file, which can then be used in a GPS device for navigation.<br>
<br>
I can also offer help with 'importing' the data from your GIS to
OSM as a semi automated process.<br>
<br>
Cheers,<br>
<br>
Jo<br>
<br>
<div class="gmail_quote">2011/8/21 Koen Mannaerts [<a href="http://fietsnet.be" target="_blank">fietsnet.be</a>]
<span dir="ltr"><<a href="mailto:koen@fietsnet.be" target="_blank">koen@fietsnet.be</a>></span><br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">Hi, I'm Koen from Fietsnet.be. Since 2007
Fietsnet is a rather popular routeplanner for the cycle node
network in Belgium and the South of the Netherlands. It's an
independent and non-commercial project by cyclists.<br>
<br>
Currently we maintain our spatial information in a private
GIS, but we're considering to shift this toOpenStreetMap.
Using OSM may enable new opportunities for the Fietsnet
routeplanner, such as covering a larger area, deviating from
the established cycle node networks, creating turn-by-turn
navigation instructions and using richer road attributes. OSM
may also benefit from this initiative, as Fietsnet has a large
user base of active cyclists and we've set up a process to
reliably translate user feedback in an adapted map. I.e. we
may change our process to quickly adapt and sanitize OSM data
based on our current data and user feedback.<br>
<br>
We're new to OSM, and we have a lot of practical, technical
and legal questions about this move, too many and too boring
to include in this message. If you have experience with OSM,
and are willing to help us out in one of these area's, it
would be fantastic if you'd send us a <a href="mailto:mail%3Ameewerken@fietsnet.be" target="_blank">mail:meewerken@fietsnet.be</a>
<mailto:<a href="mailto:meewerken@fietsnet.be" target="_blank">meewerken@fietsnet.be</a>>.<br>
<br>
Let's do this!<br>
<font color="#888888">
<br>
--<br>
Koen Mannaerts | <a href="http://fietsnet.be" target="_blank">fietsnet.be</a><br>
<br>
_______________________________________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-be" target="_blank">http://lists.openstreetmap.org/listinfo/talk-be</a><br>
</font></blockquote>
</div>
<br>
</blockquote>
</div></div></div>
<br>_______________________________________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-be" target="_blank">http://lists.openstreetmap.org/listinfo/talk-be</a><br>
<br></blockquote></div><br><div style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;word-wrap:break-word;color:black;font-size:10px;text-align:left;line-height:130%">
</div>
<div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>