<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 05/13/2013 02:18 PM, Marc Gemis
wrote:<br>
</div>
<blockquote
cite="mid:CAJKJX-Tch0g9oVYd9uXP8GfZjpAyL-ky9eTHuTwqQgrPzpWg3A@mail.gmail.com"
type="cite">
<div dir="ltr">Glenn,
<div><br>
</div>
<div>did you take a look at <a moz-do-not-send="true"
href="http://wandelknooppunt.be">wandelknooppunt.be</a> ? It
shows all the walking network nodes. You can click on the
nodes and it compiles a route from that, following the walking
network routes between the numbered nodes. A similar thing
exists for cyclist.</div>
</div>
</blockquote>
Ok, that was my first thought, so you just put in waypoints and ask
for a route to be created, makes sense, fairly easy.<br>
<br>
<blockquote
cite="mid:CAJKJX-Tch0g9oVYd9uXP8GfZjpAyL-ky9eTHuTwqQgrPzpWg3A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="">The user should be able to compose his/her route.
That's what walking/cycling networks are for. this is not
routing in the traditional sense where you only give start and
end-point.</div>
<div style="">I remember reading on this mailing list that it is
great so see all the cycling/walking networks in Flanders. It
is great that the data has been inserted, but now the data is
shown in a boring way. You cannot interact with it. (i.e.
compose a route). And the site that shows it does not let you
visualize all the other important aspects for planning a walk
/ cycling trip. That's why I think it would be nice to show to
Tourisme Vlaanderen, that all this data can be combined. <br>
</div>
<div style=""><br>
</div>
<div style="">
<div>You cannot "beat" Tourisme Vlaanderen to display all
walking networks. They can do that themselves, and probably
better, more complete and more up-to-date. Why would they
donate their data to OSM ? If they (or someone else) can get
more out of it (because there is other data as well), they
might see benefits to donate data. </div>
<div><br>
</div>
</div>
<div style="">I believe some of the sites I mention have their
source code in the public domain. So you will probably find
the way they treat the opening hours in some git repository.</div>
<div style=""><br>
</div>
</div>
</blockquote>
I don't think it's a matter of implementation (not for me at least)
but having all datasources at hand. I'll take a look at the repo's
I can find on them. It will eventually boil down to having access
to payload data (or not).<br>
<br>
<blockquote
cite="mid:CAJKJX-Tch0g9oVYd9uXP8GfZjpAyL-ky9eTHuTwqQgrPzpWg3A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="">
</div>
<div style="">All data in the sites I mention is already in OSM,
no need to access other sources. Opening hours is a tag in
OSM, so the data can be inserted. There is somewhere a
proposal to improve the current tagging, but that's more for
monthly schemes.</div>
</div>
</blockquote>
Sure, I was having those tags in my mind, but I know it's just not
entered a lot by contributors, even in my own little town, I hardy
pay attention to (entering) those opening hours. My point was it
should come from somewhere and even if it was at our disposal
-easily- there is still the question, how accurate/up-to-date is it
at any given time.<br>
<br>
<blockquote
cite="mid:CAJKJX-Tch0g9oVYd9uXP8GfZjpAyL-ky9eTHuTwqQgrPzpWg3A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="">As usual, the data is far from complete.</div>
</div>
</blockquote>
That's my problem with some other idea's I'm playing with, there is
lots of data out there in OSM you could mash with, but end-users
tend to drop out when they feel like it's incomplete and are missing
out on some things.<br>
<blockquote
cite="mid:CAJKJX-Tch0g9oVYd9uXP8GfZjpAyL-ky9eTHuTwqQgrPzpWg3A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style=""><br>
</div>
<div style="">I'm not an entrepreneur, so I have no business
plan at all :-) And maybe "killer" app is not the right
wording for this, just my idea that the power is in the
combinatie of the data, not in inserting a lot of one type of
data and getting that back out.<br>
</div>
</div>
</blockquote>
<br>
So, we'll end up selling T-shirts ;-)<br>
<br>
I'll give it some more thought, perhaps delivering 80% of this could
be done in 20% of the time (80/20 rule) , but the remaining 20% will
probably eat 80% of the time spent on this.<br>
<br>
Glenn<br>
</body>
</html>