On Mon, Jan 22, 2018 at 4:14 PM, Martin Koppenhoefer
wrote:
> 2018-01-22 17:25 GMT+01:00 Fernando Trebien :
>> - sett: hewn stones with flat top, wide filled gaps, comfortable to
>> cycle and walk on, uncomfortable on high heels [today's image
On Mon, Jan 22, 2018 at 3:59 PM, Tobias Knerr wrote:
> On 22.01.2018 17:25, Fernando Trebien wrote:
>> - sett: hewn stones with flat top (...) [2] (...)> - cobblestone: hewn
>> stones with slightly arched top (...) images [3]
> and [4]
>
> I don't believe requiring mappers
2018-01-22 17:25 GMT+01:00 Fernando Trebien :
> - paving_stones: blocks or stones with smooth flat top, tight gaps
> [same images as today]
>
ok
> - sett: hewn stones with flat top, wide filled gaps, comfortable to
> cycle and walk on, uncomfortable on high heels
On 22.01.2018 17:25, Fernando Trebien wrote:
> - sett: hewn stones with flat top (...) [2] (...)> - cobblestone: hewn stones
> with slightly arched top (...) images [3]
and [4]
I don't believe requiring mappers to make a distinction between these
two is a good idea. Let's look at your images:
>
Seems to be a good idea for me.
Requires rushing of real cobblestones, but solves problem of mixing setts
colloquially named cobblestone and real cobblestone.
So we stop pretending that current tags are correctly used and increase
changes that we can distinguish cobblestone and uneven sett.
On
Hello,
Following from this analysis [1], I would like to propose that we
abandon cobblestone:flattened, define the new value cobblestone:raised
for a rare case, and redefine existing values as follows:
- paving_stones: blocks or stones with smooth flat top, tight gaps
[same images as today]
-