OpenStreetMap import: Difference between revisions
Jump to navigation
Jump to search
(Add gasometer and winmill, total number of objects) |
No edit summary |
||
Line 1: | Line 1: | ||
With the | 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 | * 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. | |||
# ... | # ... | ||
# | # 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. | ||
# ... | # ... | ||
# | # Calculate elevation. | ||
# ... | # ... | ||
# Push to object database | # Push to object database. | ||
[[Category:Scenery enhancement]] | [[Category:Scenery enhancement]] |
Revision as of 20:18, 14 September 2012
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.
Object types
This table lists models from the FlightGear scenery database, together with a corresponding OSM tag.
Tag | Model | Number of objects | |
---|---|---|---|
Antennas |
|
Models/Communications/radio-*.xml |
36,126 |
|
Models/Communications/fernmeldeturm_gruenwettersbach.xml | 1 584 | |
Chimneys |
|
Models/Industrial/generic_chimney_01.xml | 6,486 |
Cooling towers |
|
Models/Power/coolingtower.xml | 251 |
Lighthouse |
|
Models/Misc/generic-lighthouse.xml | 5,148 |
Obelisks |
|
Models/Misc/generic_monument_01.ac | 57 |
Power pylons |
|
Models/Power/generic_pylon_*.ac | 2,760,804 |
Tanks |
|
Models/Industrial/GenericStorageTank*m.xml | 46,993 |
|
Models/Industrial/Gasometer.xml | 4,423 | |
Survey points |
|
Models/Misc/trigpoint.xml | 271,676 |
Water towers |
|
Models/Industrial/water-tower.ac | 17,132 |
Windturbines |
|
Models/Power/windturbine.xml | 79,636 |
|
Models/Power/vestas-v80-sea.xml | 39 | |
|
- | 3,928 | |
Total | 3,233,645 |
http://taginfo.openstreetmap.org/keys/ lists all tags.
Questions/problems
- Should we remove shared objects that are currently in the database, if they are not present in OSM?
- 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 what group should the objects end up? There is an "OSM" group, but there are also specific "WINDPOWER" and "POWER" groups.
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.
- ...
- For power pylons: Run
pylon-headings.pl
(from scenerytools) to properly align the pylons in the direction of their cables. - ...
- Calculate elevation.
- ...
- Push to object database.