Welcome! There is no limit to what you can spend your time on, so you certainly need to find out what you enjoy the most.

I phrased it as mapping every single space for dramatic effect. :) Realistically it's more likely to see several blocks of parking spaces than hundreds, just that in some rare cases it's possible and justified to map every one.

keinseier,
This is a benefit for all data consumers, not just renderers, it's just the most obvious example. Your argument can be used to shoot down virtually all use cases for relations. The point is that relations can make highly difficult situations easy to process for computers. You're asking quite a lot from data consumers to process all the connecting parking aisles and try to calculate what parking areas belong together.

However I do feel like there should be a more general purpose relation, which basically allows for breaking down complex objects into small objects with finer detail. Simple applications just join all members together, and perhaps the smarter ones would sum capacity=# in the case of parking, but more sophisticated apps could route a handicapped driver right to where they can park. This is almost just a multipolygon, but not quite.

Haha, for most, yes. But it's good to start thinking about these things. I think it's very useful for a routing engine to be able to direct a handicapped driver to an appropriate spot. This doesn't require mapping every single space individually, but mapping blocks of spaces makes sense.

Great work, and very impressive! I'm your neighbor over in Virginia, and while I haven't worked on any state wide projects yet, I have some in mind, such as checking county borders. Keep it up!