Hi
no it was a mistake.
Basicly atm there is one huge nested map, that holds all required
information:
nodemap[Objekt-ID][Timestamp] = (lat, lon)
lat/lon is atm stored as double. The suggested memory layout is as follows:
1. An Array with a 32bit Pointer for each Node-ID
2. A
I think the memory problems occured during the osm-history-importer [1]
process
Some people were successfull in building the database for limited areas,
but France is extract is huge in comparison.
Is there a way to limit RAM usage for such large files during import ?
[1]
Hi all,
I'm searching history statistics of the french territory contributions in
order to make some graphics about :
- Number of named roads
- Numbers of house numbers
- Number of kilometers of different types of roads (highway, primary,
secondary, tertiary, residential).
I tried OSMIUM with
I suggest you to use osm-history-splitter (to obtain some places) and
osm-history-renderer
https://github.com/MaZderMind/osm-history-renderer
Togheter with osm-history-renderer there is the program osm-history-import
This create for you some postgis tables, with this table you can query the
On Mon, Jul 16, 2012 at 01:28:50PM +0200, Aurélien FILEZ wrote:
I'm searching history statistics of the french territory contributions in
order to make some graphics about :
- Number of named roads
- Numbers of house numbers
- Number of kilometers of different types of roads (highway,
5 matches
Mail list logo
