<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 4/30/15 7:45 AM, SK53 wrote:<br>
    </div>
    <blockquote
cite="mid:CAELijW9JX658mc5FW_KFH4c4KbAPvyuVrXyOoLG6rY3qU24JFA@mail.gmail.com"
      type="cite">
      <meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>
                    <div>Hi Richard,<br>
                      <br>
                    </div>
                    I've always presumed that you would create different
                    ways for surface=clay, surface=asphalt with
                    appropriate time intervals. This gets potentially
                    very messy for city streets which may go
                    surface=dirt =>gravel
                    =>compacted=>cobblestone=>asphalt along
                    with changes in lighting, width, lanes etc. (Not to
                    mention names). I deliberately avoided this type of
                    issue when I looked at <a moz-do-not-send="true"
href="http://sk53-osm.blogspot.co.uk/2014/05/editing-historical-road-layouts.html">Derby
                      Road as an example</a>.<br>
                    <br>
                  </div>
                  These changes are far more frequent than the actual
                  geometry of the way.<br>
                  <br>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    given shared geometries, one could argue that we<br>
    should share nodes between the ways. i usually avoid<br>
    that in OSM but in this case it seems appropriate.<br>
    <br>
    JOSM can support selecting one of the the stacked ways,<br>
    but it's still obnoxious. still, it might do for now.<br>
    <br>
    <blockquote
cite="mid:CAELijW9JX658mc5FW_KFH4c4KbAPvyuVrXyOoLG6rY3qU24JFA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div><br>
              </div>
              With respect to dates, I like the stuff suggested by
              Trevor.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    don't think i've seen that. pointer or link?<br>
    <blockquote
cite="mid:CAELijW9JX658mc5FW_KFH4c4KbAPvyuVrXyOoLG6rY3qU24JFA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>Last thought would be: Would it be feasible to introduce
            some feature to support temporal queries in the Overpass
            stack?<br>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    by temporal queries do you mean date ranges and before/after on tags<br>
    containing dates? probably, but i haven't looked at the actual
    overpass<br>
    code yet so i don't have any way of assessing difficulty. i can add
    it to the list.<br>
    <blockquote
cite="mid:CAELijW9JX658mc5FW_KFH4c4KbAPvyuVrXyOoLG6rY3qU24JFA@mail.gmail.com"
      type="cite">
      <div dir="ltr">PS. This is worth mentioning in your talk to show
        that examples are the way to discover issues/ways of doing
        things.<br>
      </div>
      <div class="gmail_extra"><br>
      </div>
    </blockquote>
    i was planning on discussing things that have been exposed that<br>
    we don't know how to do yet and potential approaches.<br>
    <br>
    richard<br>
    <pre class="moz-signature" cols="72">-- 
<a class="moz-txt-link-abbreviated" href="mailto:rwelty@averillpark.net">rwelty@averillpark.net</a>
 Averill Park Networking - GIS & IT Consulting
 OpenStreetMap - PostgreSQL - Linux
 Java - Web Applications - Search</pre>
  </body>
</html>