• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX OSM file error or ScenProc error?? Or myself error?

jtanabodee

Resource contributor
Messages
3,912
Country
thailand
Hi Arno,
I am trying SceneProc to do autogen. This is my work flow:
1. Open website OpenStreetMap and go to the airport I am making (https://www.openstreetmap.org/export#map=14/8.1077/98.3212). Then I download the OSM file.

2. Open SceneProc and type the command line as the tutorial and the manual said.

OSM2.jpg


3. Then I click on Run command and everything runs smoothly and I get AGN file. Then I move this AGN file to the texture folder of the scenery. There is nothing else in the area, no exclusion at all just the Photoscenery.

OSM3.jpg


4. I get into FSX and I found nothing in the sim. So I open up the Annotator.exe and draw a vegetation polygon, then save.

OSM4.jpg


I found that the AGN file from Annotator and SceneProc were not the same.

OSM5.jpg


I compare the screen shot of Annotator and OpenStreetMap. They are the same area.

OSM6.jpg


What did I do wrong?
 
Last edited:

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
31,258
Country
netherlands
Hi,

The main issue is the tile size in the SplitGrid step. You split by 13 degree tiles. For AGN you better type AGN there.

Also you now make vegetation and buildings from all features in the osm file. You need to select forest and buildings.
 

jtanabodee

Resource contributor
Messages
3,912
Country
thailand
Thank you Arno for the information. I got the Autogen houses but not the vegetation.
Then I open QGIS and take a look on the data. The layers are only 4 and it seems to me that the house polygons and the landuse polygons are the same layer. I am not familiar with GIS data. Would you mind checking that for me, please? I have attached the file map (4).zip. If it is true, how can I solve this?

Before disable Polygon Layer.

Map01.jpg


After disable Polygon Layer:

Map02.jpg
 

Attachments

  • map (4).zip
    480.6 KB · Views: 172

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
31,258
Country
netherlands
For the forest you should be able to use the filter landuse="forest" in the step to create the vegetation. I'll check your data later to see if this area has different attributes than normal.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
31,258
Country
netherlands
Hi,

Besides landuse="forest" you also have polygons with landuse="orchard" in the data that might be interesting to place autogen trees on. So you could try as filter:

landuse="forest" Or landuse="orchard"
 

jtanabodee

Resource contributor
Messages
3,912
Country
thailand
Hi Arno,
I am getting used to the GIS software now. I found that most of the field with vegetation is under the attribute "other_tags". I filtered with this. Unfortunately, SceneProc refuse to filter under the attribute "other_tags". What should I do then?

scenProc01.jpg
 

jtanabodee

Resource contributor
Messages
3,912
Country
thailand
Anyways, those areas are beyond my photoscenery. But it would be nice if I know how to get filter of "other_tags" just in case that I extend my photoscenery area.
I got the vegetation already. Thanks for your wonderful tool.

scenProc02.jpg
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
31,258
Country
netherlands
Hi,

scenProc has an osmconf.ini file in it's gdaldata folder that disables the other_tag attribute, so it will not be there when load the OSM file in scenProc. You can add the leaf_cycle attribute in that ini file though so that it is loaded.
 

jtanabodee

Resource contributor
Messages
3,912
Country
thailand
I am not sure if I did it right. I have limited knowledge of computer and XML.
osmconf.ini file is down here. I don't know where to add leaf_cycle attribute.

#
# Configuration file for OSM import
#

# put here the name of keys for ways that are assumed to be polygons if they

are closed
# see http://wiki.openstreetmap.org/wiki/Map_Features
closed_ways_are_polygons=aeroway,amenity,boundary,building,craft,geological,historic,landuse,leisure,military,natur

al,office,place,shop,sport,tourism,other_tags

# comment to avoid laundering of keys ( ':' turned into '_' )
attribute_name_laundering=yes

# uncomment to report all nodes, including the ones without any (significant) tag
#report_all_nodes=yes

# uncomment to report all ways, including the ones without any (significant) tag
#report_all_ways=yes

[points]
# common attributes
osm_id=yes
osm_version=no
osm_timestamp=no
osm_uid=no
osm_user=no
osm_changeset=no

# keys to report as OGR fields
attributes=name,barrier,highway,ref,address,is_in,place,man_made,power,amenity,religion,natural,other_tags
# keys that, alone,

are not significant enough to report a node as a OGR point
unsignificant=created_by,converted_by,source,time,ele
#

keys that should NOT be reported in the "other_tags" field
ignore=created_by,converted_by,source,time,ele,note,openGeoDB:,fixme,FIXME
# uncomment to avoid creation of

"other_tags" field
#other_tags=yes
[lines]
# common attributes
osm_id=yes
osm_version=no
osm_timestamp=no
osm_uid=no
osm_user=no
osm_changeset=no

# keys to report as OGR fields
attributes=name,highway,waterway,aerialway,barrier,man_made,power
# keys that should NOT be reported in the

"other_tags" field
ignore=created_by,converted_by,source,time,ele,note,openGeoDB:,fixme,FIXME
# uncomment to

avoid creation of "other_tags" field
#other_tags=yes
[multipolygons]
# common attributes
# note: for multipolygons,

osm_id=yes instanciates a osm_id field for the id of relations
# and a osm_way_id field for the id of closed ways. Both

fields are exclusively set.
osm_id=yes
osm_version=no
osm_timestamp=no
osm_uid=no
osm_user=no
osm_changeset=no

# keys to report as OGR fields
attributes=name,type,aeroway,amenity,admin_level,barrier,boundary,building,craft,geological,historic,land_area,land

use,leisure,man_made,military,natural,office,place,shop,sport,tourism
# keys that should NOT be reported in the

"other_tags" field
ignore=area,created_by,converted_by,source,time,ele,note,openGeoDB:,fixme,FIXME
#

uncomment to avoid creation of "other_tags" field
#other_tags=yes
[multilinestrings]
# common attributes
osm_id=yes
osm_version=no
osm_timestamp=no
osm_uid=no
osm_user=no
osm_changeset=no

# keys to report as OGR fields
attributes=name,type
# keys that should NOT be reported in the "other_tags" field
ignore=area,created_by,converted_by,source,time,ele,note,openGeoDB:,fixme,FIXME
# uncomment to avoid

creation of "other_tags" field
#other_tags=yes
[other_relations]
# common attributes
osm_id=yes
osm_version=no
osm_timestamp=no
osm_uid=no
osm_user=no
osm_changeset=no

# keys to report as OGR fields
attributes=name,type
# keys that should NOT be reported in the "other_tags" field
ignore=area,created_by,converted_by,source,time,ele,note,openGeoDB:,fixme,FIXME
# uncomment to avoid

creation of "other_tags" field
#other_tags=yes
 
Last edited:

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
31,258
Country
netherlands
In the [multipolygons] section you will find a line that is called attributes. You need to add it to the end of that line.
 

jtanabodee

Resource contributor
Messages
3,912
Country
thailand
Just like this ?:

[multipolygons]
# common attributes
# note: for multipolygons,

osm_id=yes instanciates a osm_id field for the id of relations
# and a osm_way_id field for the id of closed ways. Both

fields are exclusively set.
osm_id=yes
osm_version=no
osm_timestamp=no
osm_uid=no
osm_user=no
osm_changeset=no

# keys to report as OGR fields
attributes=name,type,aeroway,amenity,admin_level,barrier,boundary,building,craft,geological,historic,land_area,land

use,leisure,man_made,military,natural,office,place,shop,sport,tourism, leaf_cycle

So I can add other attributes if they seem to be appropriated here, can't I?
 
Last edited:

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
31,258
Country
netherlands
Yes, that's right. You can add others as well.

After adding them you can use them without the other tags, so just leaf_cycle="value"
 

jtanabodee

Resource contributor
Messages
3,912
Country
thailand
Thank you, Arno. I have tried that and it works perfectly.
I was wondering if we can use SceneProc to make lines for roads and traffic, coast lines and water or even landclass in case that we don't use photoscenery and autogen. So that those vegetation on Photoscenery will be seamless with landclass that is built by GIS data.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
31,258
Country
netherlands
Making terrain vectors is something I have in development, but it has not been released yet.

Landclass is not in my planning yet.
 
Last edited:

jtanabodee

Resource contributor
Messages
3,912
Country
thailand
Hi Arno,
One other thing that would be good if you can implement. If the building foot print can import into 3d program (Gmax/ 3dsmax/SketchUp) would be good. Since some of the buildings are complex in 2d shape and they need to be modeled by hand. If you can filter the complex buildings (something like more than 10 vertices in a single polygon), it would be wonderful.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
31,258
Country
netherlands
There is an experimental step (you need to enable experimental in the options) called Create3DBuilding that can extrude a footprint into a box and export it to mdl. You can then load them into your modeling tool.
 
Top