<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 21, 2014 at 3:45 PM, Serge Wroclawski <span dir="ltr"><<a href="mailto:emacsen@gmail.com" target="_blank">emacsen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
> OSM maps of DC now just look a bit bizarre.<br>
<br>
</div>The MapBox folks seemed to have figued this out US-wide and<br>
re-contract the road names and the directional identifiers.</blockquote></div><br>Mapbox has an exception for DC that contracts names.</div><div class="gmail_extra"><br></div><div class="gmail_extra">While I agree with the paradigm to manage data in a way that is conducive for consuming it, you can use it to construe the argument for _and_ against expansion of DC-like abbreviations (NW, NE, SW, SE quadrants).</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">- If you expand DC-like abbreviations, then you need to contract them when making a map. Now how do you find out systematically which ones are the DC-like abbreviations you need to contract on a global map? </div>
<div class="gmail_extra">- Say you contracted DC-like abbreviations, now you need to somehow find out how to feed them into text to speech.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Agreed that DC map looks odd now on OSM.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>