On 01/-10/-28163 08:59 PM, Tom Hughes wrote: > On 21/06/10 16:00, Nic Roets wrote: > >> All that remains is for someone with a little bit of programming >> experience to volunteer. Make a copy of the osm.org website* and add >> routing buttons. Then write some code that converts the routing engine >> output to a few formats. Open Layers, GPX, human readable text should >> be enough. > > No. Whatever solution is adopted should absolutely not involve making a > copy of the web site. It should be an addon to the web site, not a copy > of it.
My guess would be that Nic meant: Fork (i.e. copy) the git rails_port repository. Add the desired functionality and then once done try and get it merged back into trunc. So the usual development way to get new functionality into the main site. In case someone would try and do it, it would probably be a good idea to make the frontend code as backend agnostic as possible. In that case it may even be possible for people to choose which routing engine they want to use. Be it gosmore, some other yet to be written opensource routing engine, open route service, or even a commercial provider like cloudmade's routing. Then the decision of which routing engine scales well enough and supports sufficient richness in OSM routing tags to warrent being run on OSMF hardware becomes a somewhat separate issue from the coding of the front end and might at least allow the ball to get rolling. Kai > > Tom > _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
