<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Can we please leave it as USPS? Other shippers UPS, FedEx, and DHL are also abbreviated.<div class="">The “expand abbreviations” rule is really for street addresses, not everything in OSM.</div><div class=""><br class=""></div><div class="">Taginfo can show you what values are currently stored in the `operator` tag:</div><div class=""><a href="https://taginfo.openstreetmap.org/keys/operator#values" class="">https://taginfo.openstreetmap.org/keys/operator#values</a></div><div class=""><br class=""></div><div class="">If we were to switch the `operator` field in iD over to a taginfo-based autocomplete, 2 things would happen:</div><div class="">1. It would show exactly the results in the url above, which contains all the operators (not just the postal ones). It would not be a good list to pick from.</div><div class="">2. The taginfo service would crash. We’ve been asked by Jochen not to do lookups against tags with a lot of distinct values (like “name” and “operator”) because queries like this are resource intensive.</div><div class=""><br class=""></div><div class="">Thanks, Bryan</div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 6, 2018, at 6:44 PM, Leif Rasmussen <<a href="mailto:354lbr@gmail.com" class="">354lbr@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Hi Peter,<div class="">I would like to do the operator value conversion this weekend, but would also like to make sure to listen to all the reasons for not expanding USPS. These include having the tagging style as consistent as possible, the long version being harder to type, a list of semicolon separated expanded operators being too long, and more. These are valid concerns, which should be addressed before anything else happens. </div><div class="">First, for keeping the tagging style as consistent as possible, each post box will be given the tag "operator:wikidata"="Q668687". This way, even if the operator=* tags are changed later on, all post boxes will still be consistent and easy to querry.</div><div class="">Second, for making sure that the operator tag is not too hard to type, I think that adding a taginfo based autocomplete to the operator=* field in iD could solve this. I would have to open an issue about that on Github, though.</div><div class="">Third, another fear was that a list of expanded operators separated by semicolons would be hard to work with. I have no easy solution for this. Perhaps, iD could have something to organize the operator tags into blocks, rather than just text like other fields.</div><div class="">I would like to convert the tags this weekend, so please let me know if you have any suggestions for how to make the conversion less problematic.</div><div class="">Thank you, </div><div class="">Leif Rasmussen</div></div></div>
_______________________________________________<br class="">Talk-us mailing list<br class=""><a href="mailto:Talk-us@openstreetmap.org" class="">Talk-us@openstreetmap.org</a><br class="">https://lists.openstreetmap.org/listinfo/talk-us<br class=""></div></blockquote></div><br class=""></div></body></html>