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

and another one request... FILTERCROSSINGFEATURES

Vogel

Vogel

Messages
211
Country
france
with OSM filtering It's a reoccurring problem for me: building crossing each other.
Would be helpful to add a function that avoid crossing ?
maybe option to define percentage of crossing area tolerated 0%,10 %, 20%, 30 %.
or maybe we can choose which building gets higher priority Big one or small one ?

FILTERCROSSINGFEATURES or FILTERCROSSINGPOLYGON

just an idea... what do you think about it ?
 
Last edited:
Hi,

Are the footprints really overlapping or only in the autogen after making it a rectangle?

And you want to drop some footprints? Or use the subtract function to make them not overlapping?
 
Even if I see overlapping building in my AGN tile, some time the overlap is about 95% and some times just a corner of one building overlap another building. May be it come after making rectangle by scenproc but in this case I think overlapping is very Partially (<10%). Most of time the problem come from shapefiles or OSM source (or the way I filter those) where some polygons could overlap each other.

So I think that this option should drop directly some footprints/features... and keep only the smallest or biggest one which overlap.
 
Last edited:
Hi,

Would you have a screenshot of the problem? Of some of the OSM data and the resulting autogen. I prefer to understand the real problem, before I start making some new step.
 
What the lat/lon? Then I can check how the footprints look in OSM.

If I see this I think just removing the smallest polygons when two buildings overlap might work. That's also not so hard to code.
 
Hi Arno and sorry for the delay,

new pictures in order to compare OSM Features & AGN objects

Corsica: LAT: 42.608083 LON: 8.861944




Corsica: LAT: 42.611548 LON: 8.891208




I hope it could help you...

thank you Arno.

Vogel
 
Hi,

I see, some footprints are quite irregular. So it makes sense that the rectangles created from them overlap.

I think the easiest is to make a step to detect overlapping polygons and then remove the smallest one.

Or would you prefer adding an attribute to filter then out instead of removing them?
 
Hi Arno,

good question Arno but hard to find the good answer... :confused:

I think that give an attribute will give more "flexibility". But as the goal is to remove one of the two or more polygon(s) which overlap together if twice have the same attribute like "overlap=1" it would be hard into the script to choose the one to delete.
May be it would be better to set at start what is the "priority order" biggest to smallest or smallest to biggest 1/sort polygon's list with this priority order 2/keep only polygon if it not overlapt with another one (before in the list)... And may be add an option to setup the tolerated percent of overlapping (more code and more timemachine).

But don't worry with that request, I'm affraid that it will be to heavy to code that I though...

thank you Arno.
 
Hi,

Thanks for the feedback. I'll see if I can make something simple first, we can always extend it. Checking if they overlap should not be too hard.

Sorting the from big to small, or the other way around and only testing in that order is a nice idea.
 
Thanks ;)

To keep it simple, knowing that my main objective is to eliminate as a priority the buildings that overlap a lot, I think at first it would be faster to test only the center of the polygon to see if it does not overlap with part of another (inclusive of a test point in a polygon).
 
Hi,

Performance wise I think the point in polygon function might take more performance than a simple test if the edges of the polygons intersect. But I'll see.
 
I'd really like a similar function! :rolleyes:

This is my idea to filter overlapping buildings (to be inserted after agn creation and before export):

REMOVEOVERLAPAGN|filter|minPerc|remSize

filter: AGNTYPE
minPerc: minimum overlap coverage percentage
remSize: remove SMALLEST or GREATEST

example:

REMOVEOVERLAPAGN|AGNTYPE=AGNGenericBuilding|25|SMALLEST

:)
 
Hi,

This feature is still on the wishlist. I think it makes more sense to check for the overlapping before making the autogen. In a way it's filtering your data. This can be done in a GIS tool, but I would prefer to let scenProc do it as well in the future. Like I wrote before, I still need to think about the best approach.
 
You must log in or register to reply here.
Back
Top