OpenStreetMap import: Difference between revisions
Jump to navigation
Jump to search
m (→Object types: addend a column what is currently in OSM) |
(→Object types: new: churches & petrol stations) |
||
Line 136: | Line 136: | ||
| align="right" | 3,302,125 | | align="right" | 3,302,125 | ||
| align="right" | 6,252,586 | | align="right" | 6,252,586 | ||
|- | |||
! Churches | |||
| | |||
* <tt>anemity==place_of_worship</tt> | |||
| Models/Misc/generic_church.ac | |||
| align="right" | 298 | |||
| align="right" | 644,805 | |||
|- | |||
! Petrol Station | |||
| | |||
* <tt>anemity==fuel</tt> | |||
| Models/Commercial/Petrolstation1.ac | |||
| align="right" | 28 | |||
| align="right" | 244,986 | |||
|} | |} | ||
Revision as of 12:41, 20 January 2015
Started in | 11/2013 |
---|---|
Description | Improved autogen support for FlightGear using OSM data |
Contributor(s) | radi, vanosten, Soitanen, portreekid |
Status | Under active development as of 02/2016 |
Topic branches: | |
$FG_SRC | https://gitlab.com/osm2city/osm2city/ |
fgdata | https://gitlab.com/osm2city/osm2city-data/ |
OpenStreetMap use in FlightGear |
---|
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 | In OSM 25.03.2014 | |
---|---|---|---|---|
Antennas |
|
Models/Communications/radio-*.xml |
36,126 |
56,307 |
|
Models/Communications/fernmeldeturm_gruenwettersbach.xml | 1 584 | 2,905 | |
Chimneys |
|
Models/Industrial/generic_chimney_01.xml | 6,486 | 10,080 |
Cooling towers |
|
Models/Power/coolingtower.xml | 251 | 379 |
Lighthouse |
|
Models/Misc/generic-lighthouse.xml | 5,148 | 6,658 |
Obelisks |
|
Models/Misc/generic_monument_01.ac | 57 | 117 |
Power pylons |
|
Models/Power/generic_pylon_*.ac | 2,760,804 | 5,465,288 |
Radomes |
|
Models/Communications/radome-*.xml | 37 | 59 |
Tanks |
|
Models/Industrial/GenericStorageTank*m.xml | 46,993 | 689 90,774 3,847 |
|
Models/Industrial/Gasometer.xml | 4,423 | 11,527 | |
Survey points |
|
Models/Misc/trigpoint.xml | 271,676 | 281,804 |
Traffic signs |
|
Models/StreetFurniture/Stop-Sign.ac | 68,443 | 128,354 |
Water towers |
|
Models/Industrial/water-tower.ac | 17,132 | 31,366 |
Windturbines |
|
Models/Power/windturbine.xml | 79,636 |
121,228 |
|
Models/Power/vestas-v80-sea.xml | 39 |
1344 | |
|
- | 3,928 | 5,961 | |
Total | 3,302,125 | 6,252,586 | ||
Churches |
|
Models/Misc/generic_church.ac | 298 | 644,805 |
Petrol Station |
|
Models/Commercial/Petrolstation1.ac | 28 | 244,986 |
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.
- Ambush (talk) 11:37, 15 December 2013 (UTC) It's right way to get GIS data from one worldwide specialized source with excellent support from a large community. If OSM have not some data existing in real world, it's better to add this data to OSM and get it back instead of support two GIS databases with duplicates.
- 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, 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.