On 18 June 2010 12:19, SteveC <span dir="ltr"><<a href="mailto:steve@asklater.com">steve@asklater.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Jun 17, 2010, at 10:11 PM, Ben Last wrote:<br>> Generally "hey, my street's not in the right suburb"<br>well at least this one is what I want to capture, super simply, and have a queue to be fixed. Right now we don't capture it _at all_ and it's a tragedy.</div>
do you agree?</blockquote><div><br></div><div>Well, fixing it isn't trivial, since there may be a bunch of reasons why it's wrong (or it may not actually be wrong!). We could store these and forward to OSM, but as has been mentioned, we don't want to bounce our users over to the OSM site (because we don't want them to have to be registered with OSM) and sending such comments programatically is not simple. But I do agree that it's valuable feedback <u>if</u> there is the capacity to respond to it.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> , or "hey, why isn't my street shown?", or "How come your address search doesn't find my house by number?"<br>these ones can be at least helpful tertiary to the above, but step one is the above.</div>
</blockquote></div><br>Actually, I think it's the other way around. The biggest issue with OSM for the use cases that concern me right now is that its usability to locate an address is pretty limited. Improving that is the single thing ("step one") that would make it better (again, for my use cases). So having streets with correct names and at least some numbering data helps a lot.<div>
<br></div><div>Cheers</div><div>b</div><div><br>-- <br>Ben Last<br>Development Manager (HyperWeb)<br>NearMap Pty Ltd<br><br>
</div>