OpenStreetMap import: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Add gasometer and winmill, total number of objects)
No edit summary
Line 1: Line 1:
With the upcoming license change, we'll be able to use [[OpenStreetMap]] data in the official [[FlightGear]] [[scenery]]. Some of the most interesting things to '''import from OpenStreetMap''' are shared objects (generic models like windturbines, power lines, water towers).  
With the recent license change, we'll be able to use [[OpenStreetMap]] data in the official [[FlightGear]] [[scenery]]. Some of the most interesting things to '''import from OpenStreetMap''' are shared objects (generic models like windturbines, power lines, water towers).  


This article lists open questions, ideas and planes related to the import process.
This article lists open questions, ideas and planes related to the import process.
Line 105: Line 105:


== Questions/problems ==
== Questions/problems ==
* Should we remove shared objects that are currently in the database, if they are not present in OpenStreetMap?
* Should we remove shared objects that are currently in the database, if they are not present in OSM?
*: {{thumbs down}} [[User:Gijs|Gijs]] 16:18, 14 September 2012 (EDT): OSM still lacks a lot of data, so we cannot state that something doesn't exist if it isn't included in the OSM data. We can be fairly sure though that something exists (or existed) if it is present in OSM.
* In order to prevent us from adding duplicates, a certain radius around the (OSM) object location should be checked for the presence of objects. What would be a good radius?
* In order to prevent us from adding duplicates, a certain radius around the (OSM) object location should be checked for the presence of objects. What would be a good radius?
* In what group should the objects end up? There is an "OSM" group, but there are also specific "WINDPOWER" and "POWER" groups.


== Import process ==
== Import process ==
# Retrieve a node from the OSM data.
#* OSM data is already available in the database (not yet ODbL), so we can take the data directly from there, rather than re-importing from OSM.
# Assign a corresponding FlightGear model (from the [[#Object types]] table).
#* Skip the node if their is no fitting object.
# Check for duplicates within ... meters from the object location.
# ...
# ...
# Check for duplicates.
# For power pylons: Run <code>pylon-headings.pl</code> (from [https://gitorious.org/fgscenery/tools scenerytools]) to properly align the pylons in the direction of their cables.
# ...
# ...
# Run <code>pylon-headings.pl</code> to properly allign power pylons with their cables.
# Calculate elevation.
# ...
# ...
# Push to object database
# Push to object database.


[[Category:Scenery enhancement]]
[[Category:Scenery enhancement]]

Navigation menu