<div dir="ltr"><div>Hi Tom<br><br>Thanks for giving the link to existing tickets ! <br></div>+1 for 1181 ;)<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/4/22 Tom MacWright <span dir="ltr"><<a href="mailto:tom@macwright.org" target="_blank">tom@macwright.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Peter,<div><br></div><div>Please read the previous posts and the linked tickets. Here's the one for you: <a href="https://github.com/systemed/iD/issues/1181" target="_blank">https://github.com/systemed/iD/issues/1181</a></div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 22, 2013 at 11:30 AM, Peter Wendorff <span dir="ltr"><<a href="mailto:wendorff@uni-paderborn.de" target="_blank">wendorff@uni-paderborn.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi.<br>
<br>
As far as I see it's entirely possible to add free tags (there's an<br>
expand link/button that shows other tags).<br>
But IMHO it's not enough, because that only shows tags that are not<br>
included elsewhere in the presetted tag stuff.<br>
The problem with this is, that for the presetted stuff it's (or at least<br>
seems to be) impossible to get the raw tags out of it, preventing to<br>
learn them (yes, novice mappers should not have to, but IMHO they should<br>
be able to understand the raw tags).<br>
<br>
So this tag list should IMHO show all tags, not only those not exposed<br>
already by even more human readable UI translations.<br>
<br>
regards<br>
Peter<br>
<br>
<br>
Am 22.04.2013 16:50, schrieb Tom MacWright:<br>
<div><div>> Hi Martin,<br>
><br>
>> it seems as if doesn't expose way membership to the user currently. In<br>
> any area with multipolygons or turn restrictions or, likely more difficult<br>
> to fix, other types or relations, mappers will really break a lot without<br>
> even being able to notice.<br>
><br>
> It doesn't expose relations in the UI, but does not break them and makes<br>
> the same relatively smart choices as P2 when users make operations on ways<br>
> and nodes in relations.<br>
><br>
> "break a lot" is unfounded and untrue: users have been testing iD for weeks<br>
> now and we are not seeing significant problems from this approach.<br>
><br>
>> +1 in case of feature X, but freeform tagging is one of the key features<br>
> that really make osm what it is<br>
><br>
> What's the assertion here, that iD doesn't support freeform tagging? That's<br>
> entirely incorrect: read the issues and look at the user interface. iD<br>
> supports freeform tagging: just click 'other' and use the tags UI if you<br>
> don't want to use presets.<br>
><br>
> Tom<br>
><br>
><br>
> On Mon, Apr 22, 2013 at 10:45 AM, Martin Koppenhoefer <<br>
> <a href="mailto:dieterdreist@gmail.com" target="_blank">dieterdreist@gmail.com</a>> wrote:<br>
><br>
>><br>
>><br>
>><br>
>><br>
>> On 22/apr/2013, at 16:25, Tom MacWright <<a href="mailto:tom@macwright.org" target="_blank">tom@macwright.org</a>> wrote:<br>
>><br>
>>> For super-advanced editing, there will always be JOSM.<br>
>>><br>
>>> iD does handle relations, though it does not support a relations editing<br>
>> UI at the moment: search for 'relations' in the issue tracker and the<br>
>> commits. There has been a ton of work on the existing relations support,<br>
>> how it interacts with pre-existing relations, and plans for simpler<br>
>> interfaces for editing relations.<br>
>><br>
>><br>
>> it seems as if doesn't expose way membership to the user currently. In any<br>
>> area with multipolygons or turn restrictions or, likely more difficult to<br>
>> fix, other types or relations, mappers will really break a lot without even<br>
>> being able to notice.<br>
>><br>
>><br>
>>><br>
>>> Yes: iD has room to grow. But I don't think that the 'a front page<br>
>> editor must include X feature that I think is important' is a useful<br>
>> criteria. If you ask whether an editor has been tested, used, deployed, and<br>
>> generally regarded as safe, iD fits that goal.<br>
>><br>
>><br>
>> +1 in case of feature X, but freeform tagging is one of the key features<br>
>> that really make osm what it is<br>
>><br>
>> Cheers,<br>
>> Martin<br>
><br>
><br>
><br>
</div></div><div><div>> _______________________________________________<br>
> dev mailing list<br>
> <a href="mailto:dev@openstreetmap.org" target="_blank">dev@openstreetmap.org</a><br>
> <a href="http://lists.openstreetmap.org/listinfo/dev" target="_blank">http://lists.openstreetmap.org/listinfo/dev</a><br>
><br>
<br>
<br>
_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@openstreetmap.org" target="_blank">dev@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/dev" target="_blank">http://lists.openstreetmap.org/listinfo/dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/dev" target="_blank">http://lists.openstreetmap.org/listinfo/dev</a><br>
<br></blockquote></div><br></div>