<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Put some comments in line against web-etiquette<br>
<blockquote
cite="mid:CAJKJX-RY4DTArB2G4KZ01jdbtcNnk4xvswnfsj3P-zWsMwnO_Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="">My "killer" application to show them would be a
single website that combines the following functionality:</div>
<div style=""><br>
</div>
</div>
</blockquote>
If you really want a killer App, you should make this in HTML5,
which brings local storage (offline use) and other goodies to make
it feel like an app on your smartphone, it's cross compatible , so
Iphone maniaks can use it as wel as Android nuts. You only develop
it once. <br>
<br>
<blockquote
cite="mid:CAJKJX-RY4DTArB2G4KZ01jdbtcNnk4xvswnfsj3P-zWsMwnO_Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="">a) walking routes (both knooppunten and local
routes) with distance as <a moz-do-not-send="true"
href="http://openwandelkaart.nl">openwandelkaart.nl</a></div>
<div style="">b) background of <a moz-do-not-send="true"
href="http://hikebikemap.de">hikebikemap.de</a> ( I love the
hill shading) (and it's faster than openwandelkaart)</div>
<div style="">c) route creation as on <a moz-do-not-send="true"
href="http://wandelknooppunt.be">wandelknooppunt.be</a> (not
OSM based)</div>
<div style="">d) tourist information</div>
<div style=""> d1) hotels, pubs, restaurants, attractions with
links to their websites & opening hours</div>
<div style=""> (see <a moz-do-not-send="true"
href="http://openlinkmap.org">openlinkmap.org</a> and <a
moz-do-not-send="true"
href="http://www.netzwolf.info/kartografie/osm/time_domain/map_opening">http://www.netzwolf.info/kartografie/osm/time_domain/map_opening</a>)</div>
<div style=""> d2) the direct link to mijnlijn for busses (see
<a moz-do-not-send="true" href="http://openlinkmap.org">openlinkmap.org</a>)</div>
<div style=""> d3) historic buildings, etc as in <a
moz-do-not-send="true"
href="http://geschichtskarten.openstreetmap.de/historische_objekte/">http://geschichtskarten.openstreetmap.de/historische_objekte/</a>
with images, wikipedia links (also in openlinkmap), protected
monuments, etc.</div>
<div style=""> d4) picnic sites, benches, sidewalks, road
quality, other information important to walking/hiking</div>
<div style=""><br>
</div>
<div style="">I would not focus on getting only their data into
OSM, (nor De Lijn, nor Onroerend Erfgoed), but show an app
that combines all this data with the data we have today. It's
the combination of all this data that makes OSM great, not the
individual pieces that each institute has themselves. </div>
<br>
</div>
</blockquote>
<br>
Pretty good idea, I could actually do this, just trying to get my
head around the good old 'time' problem. points a, d1, d2, d3, d4
could be easily done. That's what amenity's are for. Extracting
the OSM data to support this is quite trivial with Overpass API.<br>
<br>
The opening hours is probably a more difficult part to tackle, there
are plenty of sites that deliver this, but where that data comes
from, if it is accurate and up to date is a big '?'-mark. I'm sure
OSM data isn't as detailed enough for this.<br>
<br>
Concerning points: b and c, that will require figuring out where
that background comes from and look into some policies. Route
creation, I'm not sure why you mention not OSM based, but what I do
know is that there are quite some awesome open source routing
implementations around that could generate this.. Perhaps I don't
quite get your idea behind it (Do we 'invent' some routes, or do we
just stock up known trails to follow).<br>
<br>
The only non-technical thing I'm wondering about is , do you have
some sort of business idea behind it. If it were self-sufficient,
so if in some way a business model could make this pay for itself
(in terms of computer power behind it). Would love to hear it.
But in essence, it's just taking the very best stuff out of those
different sites and mash it into something better.<br>
<br>
Glenn<br>
</body>
</html>