Glenn, did you take a look at wandelknooppunt.be ? 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. 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. 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.
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. 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. 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. As usual, the data is far from complete. 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. m m. On Mon, May 13, 2013 at 1:41 PM, Glenn Plas <gl...@byte-consult.be> wrote: > Put some comments in line against web-etiquette > > My "killer" application to show them would be a single website that > combines the following functionality: > > 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. > > a) walking routes (both knooppunten and local routes) with distance as > openwandelkaart.nl > b) background of hikebikemap.de ( I love the hill shading) (and it's > faster than openwandelkaart) > c) route creation as on wandelknooppunt.be (not OSM based) > d) tourist information > d1) hotels, pubs, restaurants, attractions with links to their websites > & opening hours > (see openlinkmap.org and > http://www.netzwolf.info/kartografie/osm/time_domain/map_opening) > d2) the direct link to mijnlijn for busses (see openlinkmap.org) > d3) historic buildings, etc as in > http://geschichtskarten.openstreetmap.de/historische_objekte/ with > images, wikipedia links (also in openlinkmap), protected monuments, etc. > d4) picnic sites, benches, sidewalks, road quality, other information > important to walking/hiking > > 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. > > > 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. > > 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. > > 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). > > 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. > > Glenn > > _______________________________________________ > Talk-be mailing list > Talk-be@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-be > >
_______________________________________________ Talk-be mailing list Talk-be@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-be
