|
Hey, I'm just about to setup a server with the overpass API. I had a look at the installation guides and all quote, that with minutely updates and metadata the DB size is up to 150GB and that without updates and metadata one could push this down to 50gb.. So I decided to go with 130GB server harddisk, because I do not want metadata and minutely updates.. But what I see is that I get ~93gb of database size when I create the database without metadata. I use the cloning-mechanism. This is a bit too much, how can I reduce the size of the database? Do I have more options on this when I create the DB on my own (saying from a planet.osm file directly, not by cloning)? I need ~50 gb for other data on the server, so I would need the Overpass database to consume max. 80gb And also I'm still a bit confused because the documentation states: "40 GB of hard disk space (80-100 GB if you want minutely updates, less if you use a smaller extract file)" |
|
The Overpass installation instructions explain how you can import from a Planet file, but this probably won't achieve what you want since the planet file includes every piece of information in OpenStreetMap and will almost certainly mean a larger DB. If you're only interested in one country or area, you could import an Planet file extract, such as those available from Geofabrik, but you won't be able to keep this up to date with diffs. Equally you could download the entire Planet and filter out any data you aren't interested in using Osmosis, but this will be slow and will still need lots of disk space for the two Planet files you will end up storing. The simplest answer is probably just to get a bigger hard drive, especially since the amount of data in OpenStreetMap is only going to get larger over time. Hello Jonathan, thanks for the information. As you perhaps noticed I'm pretty new to all this stuff :) OK, so what I want is data of the whole globe, but not all data.. Mainly I need all kinds of streets and only basic topographic data. So I'll try to create my own planet file with osmosis. CPU/Ram and disk space is no big manner here, I can create the file on a workstation with enough ressources and then transfer it to the server. Thanks again! Florian
(04 Jul '13, 12:36)
sequarell
|
I'm just importing greece-latest.osm.bz2 (about 200MB) but after importing the data the database is almost 10GB. How will that scale if I import the whole planet? Greece is less than 1% of the whole planet but my db is already about 8% of the estimated total planet db size.
@kgaitanis: from where do you got the estimate? Keep in mind, that OSM is growing. Could it be that the estimate is quite old?
well in that case if my db keeps growing at the same pace while I'm adding regions to it, it should take more than 1TB for the whole planet. I'm just making quick calculations here assuming that greece represents 1% of the planet (in reality it should be less). Can anybody tell me how much disk space is needed for the database for the whole planet? I mean with recent data.