So I’ve been looking at the duplicate waypoint issue that affects the simulator when you load Navigraph information. For my purposes, I’ve chosen a waypoint called ARIYA that is used on the LOC DME 26R approach at KMIA. The only reason I chose this is because it is one of the flickering/flashing/blinking/strobing waypoints on the map.
I’ve looked at the ARINC latest CIFP file from the FAA and it appears that ARIYA was last changed in the 2008 cycle based on the last four characters in its record. It is coded as a terminal waypoint; a named intersection.
My question to someone like @Stephendoc9443 is what is special about certain waypoints that cause the duplication. There has to be a difference in the coding of the FS2020 data that causes the database to create a duplicate entry, otherwise all waypoints (and perhaps other data) would be duplicated across the board. How do we work out what it is? I would like to know how it was coded prior to this cycle, and whether or not the standard data is up to date. I’m assuming not, otherwise we wouldn’t be having this discussion 
I’ve been looking at the source JavaScript in NearestWaypoint.js and there’s a query formed around the SimVar interface that queries the nearest waypoints. Other modules deal with airports, NDBs, intersections, etc.
It uses the query result to form the resulting data that is displayed on the moving maps. There is no duplicate detection in that code, but if something were added in the interim we could prevent the flickering that annoys so many people. The only problem I see is identifying which of the duplicated entries is the correct one.
My only clue is in the file SvgWaypointElement.js, where the method _refreshLabel() references something called SVGForeignObjectElement which seems to try to determine if the label of the waypoint is overloaded. I am assuming that community data may be classed as “foreign”, but I’m guessing of course.
So, does anyone have any ideas on if we can provide an interim solution until Asobo gives us a permanent fix?