3161 only for parking=surface

[maro-21]

Continuing my post #626 (comment) and other posts in that thread,
and also #1722
I would like to again ask for change this issue, because it generates a lot of issues and a lot of false positives and it suggests wrong values out of nowhere. So:

• It should check ONLY amenity=parking with parking=surface because only these parking lots need parking aisles.
• Currently there are many parking=* values, so it should NOT suggest adding parking=street_side. Why it does?!
  http://osmose.openstreetmap.fr/en/map/#item=3161&zoom=16&lat=51.15494&lon=16.89976&level=1%2C2%2C3&tags=&fixable=
  This text is even contradictory, because in the title it suggests adding a road, and in the content it suggests adding value parking=street_side:
  
  These parking values don't need an access way:
  underground
carports
garage_boxes
sheds
lane
street_side
on_kerb
half_on_kerb
shoulder
layby
• Don't raise this issue for parking lots WITHOUT parking= because when you don't know what kind of parking it is, you don't know if you need to add a road, and in most cases you don't need to, because surface parking lots are already in the minority. The majority are small street parking lots.
  I would suggest not to have issues for amenity=parkings without any parking=* because there would be too many of them. There is a StreetComplete task to choose the parking type. So Osmose will work only for Surface parking lots.

[Famlam]

The purpose is to suggest either adding parking=* or adding a highway through the parking lot. I guess we can improve the wording to make this more clear.

I think for 3 out of 4 of the cases I've seen, street_side is the correct solution. Maybe 1 out of 10 needs ways. The residue needs a different parking=*

P.s. parkings like underground parkings definitely have an access way.

[maro-21]

The purpose is to suggest either adding parking=* or adding a highway through the parking lot.

I would separate the two and make separate issues for them.

The issue that parking=surface has no access road is important.

But that the amenity=parking tag is missing parking is a lower priority issue. This is not an error. Property tags can be added indefinitely, so the fact that something else can be added to an object is an issue of least priority. Besides, one can easily search for it in Overpass Turbo, or in StreetComplete, which one can't do if there is no road to the parking lot.