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

ask for FILTERDUPLICATEPOINT...

Vogel

Vogel

Messages
211
Country
france
Hi,

It is possible to add an option to remove duplicate point (like filterduplicateline) with the possibility to remove point with or without the same "Altitude";

Code: 
FILTERDUPLICATEPOINT|Z_on
or
FILTERDUPLICATEPOINT|Z_off
 
Hi,

Yes, that should be possible. Would you only want to filter them when they are exactly the same or also when they are very close to each other?
 
Great ! if we can setup the "snap" distance, it would be much better for sure ;)
 
I've added it to the wish list :)
 
Hi,

Do you use the step to filter duplicate lines in your configuration?

In recent builds I have hidden all steps that I designed to make grounds polygons instead of autogen (to not confuse users). The filter duplicate lines step is one of them. But if it's useful to make autogen I can put it back of course.
 
Hi,

No, I don't realy use filterduplicateline cause at that time the result was not what I've expected. Finaly, I don't know if this type of filter should not be better to be used as final step on xmlobject or agnobject instead of point. In fact, my first goal was to avoid 2 or more object on the same place (Tree on building, light on light, etc.). What's your mind on that ?
 
Hi,

These filter steps were supposed to be used early in the process. So remove duplicate lines (or points) before making making autogen objects out of them. I made it when I was using scenProc for ground polygons, not autogen. In that case I had source data where there were sometimes two lines on top of each other at exactly the same location. Those I wanted to filter out.

So I think that won't work for buildings and vegetation that overlap. That's a problem I recently encountered in my test area as well. I still have to see how I am going to fix that in scenProc. But I don't think the filter duplicate object steps would really help there, because that's really for two features that are exactly the same.
 
Hi,

I need to check. It might still be on the list.
 
Yes, it's still on the wishlist.

I'm not sure how to handle points close to each other yet. Which one is the right location in that case?
 
So what behavior would you expect when a couple of points are very close to each other? Which one should be kept and which should be filtered out?
 
this is a very good question
i have to give it some thought before i answer
im sure other dev's have some thoughts as well
 
Just to start the ball rolling
how about the following logic

Select a single feature at a time as a base encore
Then run a check for point of all other features
against the center of the point from the encore feature we selected

Filterduplicatepoints;ENCOR=trunk;filter=2

2 is the radius in meters from the main feature center point

This step can then be repeated with the next feature as the encore
 
Yes, that would work.

But it would depend on the order of the points in the original data which point is kept and which are removed. I'm not sure if that is desirable. But maybe it's good enough.
 
if we are assuming the points were placed with a feature name initially; and with predefined spacing
running randomly between the encore feature points shouldn't be an issue (i think)

i guess the order of processing is critical;
what is subtracted from what first
probably a matter of personal preference
 
Last edited:
Hi,

What I mean is assume you have some duplicate point that have slightly different coordinates. Should the step take the average position of those or just pick the first point and remove the others that are within the threshold? In the last case the resulting position depends on which of the duplicate points was first "found".
 
hmm.... ok
what if we use the original source file to guide the order (use lines to remove duplicate points)
when we first execute place point along line; we end up with point but we also have the original lines
we can possible guide "remove duplicates point" off the original lines file instead of point
in other words; follow the lines from the lines files and remove duplicated from the points file; with the line order logic as the encore

maybe something like expect logic?
expected off the main line and spacing selected
FILTERPOINTSALONGLINE|SOURCELINEFILE|FTYPE=LINE;type=residential|POINTSFILE|Expected|200;200|5;5|100|OFFSET=2|IGNOREFILTER=feature.name.to.ignore
 
Last edited:
You must log in or register to reply here.
Back
Top