GRB import low hanging fruit

The GRB import process currently seems focused on handling merge conflicts and adding as much metadata as possible. I think there are areas where this process is “perfect is the enemy of good”.
Consider a rural area with no buildings mapped. Automatically importing unambiguous data here would immediately provide 80% of the value for casual map consumers. With unambiguous data here I mean most building outlines, addresses, some metadata, everything that doesn’t hit corner cases.

How would this help casual users? For example, when I go for a bike ride, I can chose my route based on how many buildings there aren’t. Better map, better bike ride.

1 post - 1 participant

Read full topic

Ce sujet de discussion accompagne la publication sur