Thanks, Stefan and Ian for your answers! I still after an own OSM server which would offer OSM API, OSMXAPI and a front end with tiles (and rendering). Yet, I'm still wondering about the zoo of tools OSM is using. I can imagine that this becomes unmaintainable. Would'nt it be worthwhile to rewrite everything in a single well known language (like Ruby or Java)? Could perhaps be a Summer of Code project.
Anyhow, please correct me about my investigations especially regarding OSM API software: OSM-API software used by official openstreetmap servers: * OSM API Rails Port (Ruby) - : http://wiki.openstreetmap.org/wiki/The_Rails_Port * Osmxapi code (MUMPS language ?%&[EMAIL PROTECTED]) http://wiki.openstreetmap.org/wiki/Osmxapi Alternatives? * ROMA - read-only-map-api (Java?): http://wiki.openstreetmap.org/index.php/Read_Only_Map_API * handlerosm (C?): http://repo.or.cz/w/handlerosm.git Stefan 2008/10/30 Stefan de Konink <[EMAIL PROTECTED]>: > On Thu, 30 Oct 2008, Shaun McDonald wrote: > >> Um, you have significantly modified the table schema compared to what >> the main osm db uses. What have you done to the ways? > > The initial work removed all the was and only required nodes and relations > to function. While it was still able to output node, ways and relations in > the OSM way. Because I cannot give this idea momentum I have changed it > back. Due to the id collisions that will happen... but in essence; the > complete way structure can be rewritten with a relation that has a > relation_tag with a way key. > > > Anyhow the version that is now in the VM and online there has the insert > code from 'osmparser'. This will output the database schema, and code, and > is compatible with the current model. > > > Stefan > > _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
