The only good thing about AFDC data import is that it is better than nothing. So if there are no active editors around, the map will still get updated with very low quality AFDC data. It seems that AFDC bureaucrats live in a parallel universe where all DCFC charging stations are rated at 50 kW. They obviously use the outdated definition of DCFC. Here is one example, but I could quote many more:
OCM-283674 - AFDC (CCS1, 50 kW, x6)
OCM-296794 - the real location (CCS1, 350 kW, x6, over 100 metres away)
https://imagizer.imageshack.com/img922/9439/3SdxHN.png
https://imagizer.imageshack.com/img923/2985/f8o7qc.png
https://imagizer.imageshack.com/img923/1351/Fi5U1A.png
https://imagizer.imageshack.com/img924/96/CclUQr.png
https://www.instantstreetview.com/@50.446921,-104.55221,154.47h,5p,1z,PLYJfURhI-6M8nUFqtaUTQ
In this case I deliberately created a duplicate location to clearly demonstrate the problem and also because, from my experience, editing those AFDC locations is a risky proposition as the edits are often overwritten with the old data during subsequent AFDC import. So creating a new, duplicate location and then deleting the one from AFDC is a safer approach, except that the deleted AFDC location might later reappear. The most effective workaround to deal with those AFDC locations is to change their operational status to “Planned For Future Date”.
How often is AFDC data imported? Those imports can create a real mess in the database of 50 kW charging stations. The good news here is that 100 kW+ database is not affected at all.