• 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.

Problem vegetation

Hi,
curiosity,
you wrote that it took 1 minutes? ..... :eek:

To me it took 10 minutes, but that pc you have?
I have a Q9550 8 GB of RAM 64-bit Win7 ....:rolleyes:

Antonio.
:)
 
I mean the importing took 1 minute. So that's about the same on your machine.

Split grid takes so long because you are processing quite a big area at once.
 
Haaaa ..... ok I realized that we had put one minutes to process everything ... I'm sorry ... I misunderstood.
However, even putting DontprocesHoles does not change much the result
(at least with vegetation) I did not see big differences.
On the other hand now with the import of OSM data is as accurate as the vegtazione set in the SPC file.
Thank you very much. ;)

Antonio.
 
The old IMPORTOSM step didn't process holes either, so compared to that you'll see the same kind of output if you disable the processing of holes.
 
Hi
with the latest release I found a new problem with italy shape files from geofabrik

enter loop into this step:
SUBTRACTFEATURES | FTYPE = POLYGON; VEGETYPE = Forest | BUILDINGS Buildings = | 2.0 | MINAREAPOLY

I've tried adding the option DONTPROCESHOLES on importing, but loop equally

this does not always happen, but only in certain areas, so maybe are causing the problem some vegetation polygons

Screenshot in attachment

thanks
Chris
 

Attachments

  • loop.jpg
    loop.jpg
    335.1 KB · Views: 423
Hi Chris,

The step to subtract features from each other can take a lot of time. I also see that in my own configuration.

Did you put it after the SPLITGRID step that is better for the performance?

How big is the area you are processing at once?
 
Hi Arno
splitgrid is at the beginning of the process
the area has the dimensions of a LOD8, the configuration is always the same, and the process usually ends in 6 or 7 minutes, while this morning has worked almost 2 hours and it always stop at the same point (with the new version R2716)
I will do further tests with other areas

Thank you

Chris
 
Hi Arno,
I have a little problem:
wanting to use the data to create polygons leisure = garden vegetation in cities
I tried to load in leisure spc file:
IMPORTOGR | sicilia.osm | @ @ 2, @ 3 @, @ @ 4, @ 5 @ | building; landuse, natural, leisure | NOREPROJ | DONTPROCESHOLES

but unfortunately some parameters in the configuration file interprets the polygons garden / leisure as well as building and puts me in both the vegetation is the building in the same place.

I've tried everything from 2 days but I can not figure out what to add in filters to not let him do the building with polygons "garden".

Any idea?
And 'possible to use leisure or is it better that I give up?

I'll send you the spec file used and one shot of the problem.

Antonio.



 

Attachments

Hi,

Using the polygons from leisure should not be different from other polygons. So I would see it should be possible.

Do you know where those extra buildings come from? If I check your script I don't think they can be part of the leisure vegetation polygon, so they must somehow come from your building rules. I guess those buildings are still there if you don't include the leisure=garden polygons.

So question is from which rule they come...
 
Hi Arno,

The buildings appear in all polygons labeled " garden" (parks , public gardens, private gardens ... etc ... etc ...).
In practice Scenproc creates buildings with those polygons, in addition to creating even the vegetation polygon with the configuration that I sent you .

If I do not include "leisure" from the line:IMPORTOGR|sicilia.osm|@2@;@3@;@4@;@5@|landuse;natural;leisure;building;highway|NOREPROJ|DONTPROCESHOLES
it does not create garden (vegetation polygon) and even building in the park,as you have guessed .
While not putting references to create polygons vegetation , but including "leisure" in IMPORTGR | leisure ........... ..........buildings appear in polygons "garden".
So I think the error is that my script interprets the polygon "garden" as well as building as well as vegetation .
So I can not even use the "park " because they too are under the label "leisure" as the "garden" , or any other object which stands under "leisure" .

The question is which filter to use to tell sceproc not use polygons "garden " to create building?

This shot is loaded with "leisure" in IMPORTGR and without references with polygons of vegetation



this without loading "leisure" ... the buildings are not created



The area of the example is a park in the city of Catania .... but the gardens are in all cities ....

Antonio.
 
:(

I do not know if you can be of help but I have tried to remove all references to polygons
and loaded into only building = * Attributes,
only load "leisure" in IMPORTGR:

IMPORTOGR|sicilia.osm|@2@;@3@;@4@;@5@|building;landuse;natural;leisure|NOREPROJ|DONTPROCESHOLES

# SET buildtype

# Set Attribute BUILDINGS Buildings for all
AddAttribute | building = * | BUILDINGS | Buildings

# Set Attribute buildtype ComplexBuild for all
AddAttribute | BUILDINGS =Buildings | buildtype | ComplexBuild

# Set Attribute buildtype RectBuild for rectangular building
AddAttribute | BUILDINGS= Buildings; FNUMVERT = 4; FNUMPERPANG = 4 | buildtype | RectBuild

But scenaproc continues to create building in all polygons "leisure"
This seems strange to me? .....

Antonio.
 

Attachments

Hi,

I would have to try it here, just from looking at the configuration I can't find the mistake. There must somehow be some building features in the area to get those buildings.
 
Hi,
Neither do I understand what creates the building in the gardens,
In any case I partially solved this way:
ADDATTRIBUTEIFINSIDE | FTYPE = POLYGON | leisure = garden | BUILTYPE | *
ADDATTRIBUTEIFINSIDE | FTYPE = POLYGON | leisure = garden | BUILDCAT | *

although it is not a solution in my opinion ....

Thanks Arno.
Antonio.
 
Hi,

Humm, assigning a value of * would be confusing. Because attribute=* would not select them. But if it works...
 
Hi Arno,
but in the end I think that something has changed with the latest release of scenproc,
I do not think I had this problem before, at least with the OSM file,
out of curiosity I tried to uaser your configuration file that is in the tutorial
of scenproc this:

IMPORTOGR|sicilia.osm|@2@;@3@;@4@;@5@|building;landuse;natural;leisure|NOREPROJ|DONTPROCESHOLES
SPLITGRID|AGN|building=*
#
CREATEAGNPOLYVEG|FTYPE=POLYGON;landuse=forest|{7e1bd65a-abbd-49ce-8e14-0e3ad28439bb}
#CREATEAGNPOLYVEG|FTYPE=POLYGON;landuse=orchard|{2ce948be-5b15-4fa2-8d2e-4b2939cd18a5}
#CREATEAGNPOLYVEG|FTYPE=POLYGON;landuse=conservation|{bc6396b0-6e51-4a4f-ab4f-5386c84609a6}
#CREATEAGNPOLYVEG|FTYPE=POLYGON;natural=scrub|{2fde0277-1697-4dab-b481-c3985c80596f}
#CREATEAGNPOLYVEG|FTYPE=POLYGON;natural=wood|{7dc6ef4e-92a5-4d0d-b94b-212dd1fa936d}
#CREATEAGNPOLYVEG|FTYPE=POLYGON;leisure=garden|{2368c260-177d-4af7-94d4-da882778108f}
#
CREATEAGNGENBUILD|FTYPE=POLYGON;building=*;FWIDTH<20|{5ae04eb6-934c-4f63-bb48-5e7dee601212}|MAXRATIO=2
CREATEAGNGENBUILD|FTYPE=POLYGON;building=*;FWIDTH>20|{6089A0BD-CED1-4c47-9A9E-64CDD0E16983}
#
#create agn files
EXPORTAGN|FSX|D:\liguria\scenproc_x64\texture


or only added a little vegetation (but also without the result is the same)
everything seems normal to you?
In practice turns any polygon in the building, I do not know what to think ....

Antonio.

Shot...

 
Hi,

I'll try to reproduce the problem. But might take a few days before I have time.
 
Hi Arno

I'm also trying to import osm file (I'm doing the same job of antonio ;))
I have found that not all tags are read correctly
I tried to import the file sicilia.osm with QGIS (sicilia_points2) and the shape file (sicilia_0_p) generated by scenproc with this code

IMPORTOGR|I:\GIS\regioni_OSM\sicilia.osm|@2@;@3@;@4@;@5@|*|NOREPROJ|DONTPROCESHOLES
ADDATTRIBUTE|FTYPE=POINT|SPpow|SPpow

SPLITGRID|1

# set point POWERTYPE
ADDATTRIBUTE|SPpow=SPpow|POWERTYPE|PowerPoint

#export to shp for debug
EXPORTSHP|SPpow=SPpow|power



for the same feature (point), scenproc insert the tag "power=tower" in "other_tags"
see attach

maybe can help you to solve import problems

hello
Chris
 

Attachments

  • sicilia.jpg
    sicilia.jpg
    289.2 KB · Views: 420
Hi,

I have fixed the issue with the power=tower attribute now. That was due to the configuration of the OGR library. You need to download the full version (not the update one) of scenProc to get the fix.

I'll be looking into the building issue tonight...
 
Hi,

I have found the bug that gave the extra houses. Features without a building attribute would still get an empty string as value for that attribute. That's why they got selected by building=* and you got more houses. If you download the development release tomorrow it will work as it should again.
 
Back
Top