The incorrect placement is one issue, addressed in this thread. The problem is, with the exception of bespoke and third party airports, they’re fairly defaulted to a position around 1000’ down the runway. If you’ve ever flown into a small airport, you’ll quickly realize there is no default and they’re placed in all sorts of configurations to provide not only obstruction clearance, but to get the airplane safely down in a reasonable touchdown zone. 1000’ on a 3000’ runway makes for a dangerously long landing. You’re already outside the touchdown zone (1st third of the runway).
The missing elements are another issue, part of a larger scope of incorrect/missing runway lighting, including approach lights, centerline/TDZ lights, REIL, vasi when it should be papi, 4-box papi when it should be 2-box, etc. I believe, and have collected evidence to support this notion, that the database used to generate airports (along with the AI scrub) is 15+ years old.
The reason the threads are separate is because one involves scrubbing a database for all lighting types, however the database does not contain VASI/PAPI position, which will instead have to be hand placed (or better noted by the next AI scrub). If we treat it the same, the positioning will get lost in the noise of correcting/updating the database.