There is a basic misunderstanding somewhere in the question. There is no, really no, shortage of good ideas for OSM in general and for the website specifically. Matter of fact every self respecting OSMer can probably produce a list with multiple man-centuries worth of work of nice-to-have items in the time frame of a couple of minutes. The scarce resource is developer resources time and attention and the practical consideration of limiting complexity to a (with the available resources) manageable level. As a consequence feature requests tend to be taken far more serious if: - you provide code yourself - you convince somebody else to code - you pay somebody to code - you convince somebody else to pay somebody to code I'm not aware of a feature that has been coded and tested in a reasonable way being turned down to date, however the additional complexity and resource consumption considerations might still lead to a feature not being integrated.

There is a basic misunderstanding somewhere in the question. There is no, really no, shortage of good ideas for OSM in general and for the website specifically. Matter of fact every self respecting OSMer can probably produce a list with multiple man-centuries worth of work of nice-to-have items in the time frame of a couple of minutes. The scarce resource is developer resources and the practical consideration of limiting complexity to a (with the available resources) manageable level. As a consequence feature requests tend to be taken far more serious if: - you provide code yourself - you convince somebody else to code - you pay somebody to code - you convince somebody else to pay somebody to code I'm not aware of a feature that has been coded and tested in a reasonable way being turned down to date, however the additional complexity and resource consumption considerations might still lead to the a feature not being integrated.

There is a basic misunderstanding somewhere in the question. There is no, really no, shortage of good ideas for OSM in general and for the website specifically. Matter of fact every self respecting OSMer can probably produce a list with multiple man-centuries worth of work of nice-to-have items in the time frame of a couple of minutes. The scarce resource is developer resources and the practical consideration of limiting complexity to a (with the available resources) manageable level. As a consequence feature requests tend to be taken far more serious if: - you provide code yourself - you convince somebody else to code - you pay somebody to code - you convince somebody else to pay somebody to code I'm not aware of a feature that has been coded and tested in a reasonable way being turned down to date, however the additional complexity and resource consumption considerations might still lead to the feature not being integrated.