Osm2city.py: Difference between revisions

Jump to navigation Jump to search
m
filed status sections under news
m (→‎Features: LM works)
m (filed status sections under news)
Line 12: Line 12:
It has been tested with Dresden, Germany (EDDC) and Innsbruck, Austria (LOWI). Both areas are now populated with about 50,000 buildings. Rendering this in FG is quite demanding. The FG process eats ~2.8GB RAM when flying in those areas, the download is ~50 MB each.
It has been tested with Dresden, Germany (EDDC) and Innsbruck, Austria (LOWI). Both areas are now populated with about 50,000 buildings. Rendering this in FG is quite demanding. The FG process eats ~2.8GB RAM when flying in those areas, the download is ~50 MB each.


== Status 10/2014 ==
== News ==
=== Status 10/2014 ===
New features:  
New features:  
* textures reside in a separate [https://gitorious.org/fg-radi/osm2city-data repository]
* textures reside in a separate [https://gitorious.org/fg-radi/osm2city-data repository]
Line 19: Line 20:
* SKIP_LIST can contain OSM_IDs
* SKIP_LIST can contain OSM_IDs


== Status 06/2014 ==
=== Status 06/2014 ===
I'm currently adding textured roads, railroads, intersections and bridges.
I'm currently adding textured roads, railroads, intersections and bridges.


Line 40: Line 41:
}}
}}


== Status 04/2014 ==
=== Status 04/2014 ===
[[File:LOWI with OSM buildings from FL300.jpg|thumb|Aerial view of LOWI, with 60k OSM buildings]]
[[File:LOWI with OSM buildings from FL300.jpg|thumb|Aerial view of LOWI, with 60k OSM buildings]]
Following Mathias' suggestion at FS Weekend 2013, I've now changed the code such that it merges all buildings per (osm2city) tile into one object, reducing the number of drawables from O(10k) to O(10). That indeed gives a nice speed-up. In fact, I'm overwhelmed by what's possible now -- here's a scene looking down at LOWI from FL300 showing 60k buildings. Plain Scenery 2.0 gives 19 fps on i7 Intel HD 5000 2560x1440. With buildings framerate goes down to 14.
Following Mathias' suggestion at FS Weekend 2013, I've now changed the code such that it merges all buildings per (osm2city) tile into one object, reducing the number of drawables from O(10k) to O(10). That indeed gives a nice speed-up. In fact, I'm overwhelmed by what's possible now -- here's a scene looking down at LOWI from FL300 showing 60k buildings. Plain Scenery 2.0 gives 19 fps on i7 Intel HD 5000 2560x1440. With buildings framerate goes down to 14.
Line 47: Line 48:
The second scene, approaching LOWI from the east, went from 30 fps without buildings down to 20 fps.
The second scene, approaching LOWI from the east, went from 30 fps without buildings down to 20 fps.


== Status 10/2013 ==
=== Status 10/2013 ===
Currently data is processed offline beforehand. Basically, it parses the OSM
Currently data is processed offline beforehand. Basically, it parses the OSM
xml, generates a list of building outlines, discards some based on their area,
xml, generates a list of building outlines, discards some based on their area,
153

edits

Navigation menu