<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    yes, add to the wiki page and help fix it<br>
    <br>
    On 6/21/2011 6:56 PM, James Mast wrote:
    <blockquote cite="mid:SNT141-w18CF1FE9BB1D27A5DB1E55BF500@phx.gbl"
      type="cite">
      <style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
      <div dir="ltr">
        <style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
        <div dir="ltr">
          <style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
          <div dir="ltr">
            Steve, are you still accepting other
            requests on areas that need to be updated? I would suggest
            Northern
            Ontario between Toronto and Sudbury. On both the Ontario 69
            and
            Ontario 11 highway corridors, brand new expressway
            alignments are
            being built in several different areas. Unfortunately, the
            Bing imagery in that area is very
            poor and really out dated. The zoom of what is available is
            too far
            out to even be useful even if the new highways were shown on
            it
            under-construction. Heck, even Google doesn't have imagery
            that shows
            the brand newly opened segment of Ontario 69/400 in the
            Parry Sound
            area. Somebody has already put a rough alignment of it in
            OSM, but
            it's way off in a few places since I know it's missing an
            exit along
            it from research on another highway related project I'm
            working on.<br>
            <br>
            <p style="margin-bottom: 0in;">-- James </p>
            <br>
            <br>
            <p style="margin-bottom: 0in;">> Date: Tue, 21 Jun 2011
              11:26:16
              -0700<br>
              > From: <a class="moz-txt-link-abbreviated" href="mailto:steve@asklater.com">steve@asklater.com</a><br>
              > To:
              <a class="moz-txt-link-abbreviated" href="mailto:talk-us@openstreetmap.org">talk-us@openstreetmap.org</a><br>
              > Subject: [Talk-us] overwhelmed with
              responses on the imagery priorities<br>
              > <br>
              > I had tons of
              emails in response to my request for ideas of where we <br>
              > could
              prioritise imagery. This is not to be taken that we will <br>
              >
              prioritise based on your input but that's my hope.<br>
              > <br>
              >
              I've put the salient bits of every email in here:<br>
              > <br>
              >
              <a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/Bing/Priorities">http://wiki.openstreetmap.org/wiki/Bing/Priorities</a><br>
              > <br>
              >
              If you can help me figure this in to a coherent page with
              some idea
              of <br>
              > how to prioritise all the requests that would help me
              take this to the <br>
              > next stage.<br>
              > <br>
              > Thanks<br>
              >
              <br>
              > Steve<br>
              > <br>
              >
              _______________________________________________<br>
              > Talk-us
              mailing list<br>
              > <a class="moz-txt-link-abbreviated" href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
              >
              <a moz-do-not-send="true"
                href="http://lists.openstreetmap.org/listinfo/talk-us">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
            </p>
          </div>
        </div>
      </div>
    </blockquote>
  </body>
</html>