XAPI currently requires about 400Gb disk space, FYI. 80n On Sat, Oct 3, 2009 at 11:04 PM, Tim Alder <tim.alder(a)s2002.tu-chemnitz.de>wrote;wrote:

Maybe have a copy of the OSM data for the Tools? Atm. Cassini only has a Postgis-DB, no real OSM-DB, and as far as i understood the concerns about ptolemy beeing a production box, cassini won't get any db-access to it. Peter

XAPI has real nice functionallty. I.e. if you want to know the path of a long river or a street, you can get it simple and fast via XAPI, also if this object has more than one way. With OSM API instead you need to download ALL datas in a bbox and filter than and the bbox-size is very limited. So I could NOT work with the normal OSM-API for Query-to-map or something else. The XAPI runs for a long time very well, so the software seems ok und we should give it a chance. If it makes too much problems we can stop the experiment each time. I know that the highest priority project part is to get the OSM-maps into Wikipedia, so if XAPI installation would be a real problem for the live system, we should stop it. (Only an idea: Perhaps XAPI could run only on one core and reduce so the risk for the stability of the whole system. ) If we would have enough harddrive space we could run XAPI on cassini instead of ptolemy, there we could also try to program the XAPI functionality with Postgis on an optimize database layout. (For my application I don't need timestamp and editor for each node, so we can perhaps reduce the space requirements.) Other maps need perhaps also alternative database layouts and so need alternative layouts. More space we could also use to save tile for lower zoom levels of our experimental maps, etc. Greetings Kolossos Marcin Cieslak schrieb:

Dnia 05.10.2009 Peter Körner napisał: Ptolemy is importing full planet.osm for a week already. We're looking at what's wrong with the import. Previously it failed after only 2 days of import. -- << Marcin Cieslak // saper(a)saper.info >>