<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 24, 2021 at 8:59 PM Andrew Davidson <<a href="mailto:theswavu@gmail.com">theswavu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 21/5/21 9:23 pm, Andrew Harvey via Talk-au wrote:<br>
> <br>
> For now the iD preset doesn't show the any inherited attributes, so<br>
> it will prompt mappers to supply these fields. While it might be<br>
> redundant, it's also not wrong, would you go so far as removing these<br>
> fields other mappers manually add?<br>
<br>
Ideally, if we agreed that anything beyond addr:street was not <br>
necessary, we would ask the iD developers to change the AU address <br>
format to:<br></blockquote><div><br>I'd make a polite argument there is still value in at least the suburb, possibly postcode being still provided. When exporting data via overpass as CSV; it's not currently easy or obvious to appropriately bring in the parent attributes; even if it is for a Real Human looking at the map.<br>There's a fair number of use cases for "data in a spreadsheet friendly format" I feel.<br><br>Yes, it does come with a maintenance problem when suburbs change or postcodes merge, but I feel that's one problem for one set of folks - us maintainers - vs a repeated problem for many simple data consumers.<br>Ideally, as maintainers, we would over time semi automated this with tooling (much like the proposed import)</div></div></div>