<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Igor,<br>
      <br>
      exactly in those areas I have a problem of understanding the OSM
      license :)<br>
      <br>
      > If you store the elevation data in the original grid-based
      form<br>
      <br>
      No, as explained, I do intent to calculate edge weights based on
      OSM and elevation data. Is this a trivial change?<br>
      <br>
      And then I "store" this mixed weights in-memory but this is only a
      configuration to make it storing on disc. And would it make a
      difference? I read somewhere that "storing" could be also
      in-memory with the rise of NoSQL databases this makes indeed sense
      ...<br>
      <br>
      > Except, of course, if you intend to offer the routing as some
      kind of high-availability web service <br>
      > which would allow somebody to reconstruct the original
      elevation data using web scraping.<br>
      <br>
      What did you mean here? This would make a difference for the
      elevation provider license not for the OSM license (?)<br>
      <br>
      <br>
      > Of course, all of this also depends on you getting the
      approval/agreement from the CGIAR data owner <br>
      > to use the elevation data for commercial purposes.<br>
      <br>
      Of course, but I think this would be another issue. I would like
      to understand the OSM implications first :) !<br>
      <br>
      Regards,<br>
      Peter.<br>
      <br>
    </div>
    <blockquote
cite="mid:CA+CKBJHO4m90ObytqaRoEEVS9B1xOnHNnn1NaJS3cUER9_5aJg@mail.gmail.com"
      type="cite">I'm not an expert, but I think it largely depends on
      your definition of the "routing database". If you store the
      elevation data in the original grid-based form and you request
      elevation data on-demand for lat/lon coords without long-term
      storing of lat/lon + elevation pairs, then I don't really see the
      two data sources "infecting" one another in legal terms.
      <div>
        <br>
      </div>
      <div>Except, of course, if you intend to offer the routing as some
        kind of high-availability web service which would allow somebody
        to reconstruct the original elevation data using web scraping.</div>
      <div><br>
      </div>
      <div>Of course, all of this also depends on you getting the
        approval/agreement from the CGIAR data owner to use the
        elevation data for commercial purposes.</div>
      <div><br>
      </div>
      <div>Best regards,</div>
      <div>Igor Brejc<br>
        <br>
        <div class="gmail_quote">On Thu, Jul 4, 2013 at 1:01 PM, Peter K
          <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:peathal@yahoo.de" target="_blank">peathal@yahoo.de</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000">
              <div>It is "enhanced SRTM" from cgiar: <a
                  moz-do-not-send="true"
                  href="http://srtm.csi.cgiar.org/" target="_blank">http://srtm.csi.cgiar.org/</a><br>
                <br>
                E.g. see: <a moz-do-not-send="true"
                  href="http://srtm.csi.cgiar.org/SRTM_FAQ.asp"
                  target="_blank">http://srtm.csi.cgiar.org/SRTM_FAQ.asp</a>
                -> <i>"Can I use this data for commercial use? </i><i>If
                  interested in using this data for commercial purposes
                  please email </i><i><a moz-do-not-send="true"
                    href="mailto:a.jarvis@cgiar.org" target="_blank">Andy
                    Jarvis</a></i><i>.</i>"<br>
                <br>
                Regards,<br>
                Peter.<br>
                <br>
              </div>
              <div>
                <div class="h5">
                  <blockquote type="cite"><font face="Default Sans
                      Serif,Verdana,Arial,Helvetica,sans-serif"><br>
                      If it's SRTM it's just public domain isn't it? So
                      if the resulting database is under ODBL I can't
                      see that being a problem.<br>
                      <br>
                      Very much IANAL.<br>
                      <br>
                      Nick<br>
                      <br>
                      <font color="#990099">-----Peter K <a
                          moz-do-not-send="true"
                          href="mailto:peathal@yahoo.de" target="_blank"><peathal@yahoo.de></a>
                        wrote: -----</font>
                      <div style="padding-left:5px">
                        <div
                          style="padding-right:0px;padding-left:5px;border-left:solid
                          black 2px">To: <a moz-do-not-send="true"
                            href="mailto:legal-talk@openstreetmap.org"
                            target="_blank">legal-talk@openstreetmap.org</a><br>
                          From: Peter K <a moz-do-not-send="true"
                            href="mailto:peathal@yahoo.de"
                            target="_blank"><peathal@yahoo.de></a><br>
                          Date: 04/07/2013 09:05AM<br>
                          Subject: [OSM-legal-talk] Elevation / SRTM
                          data<br>
                          <br>
                          <div><font face="Courier
                              New,Courier,monospace">Hi there,<br>
                              <br>
                              how would like to know how I could
                              integrate SRTM data with OSM data. It<br>
                              is not for a mapping service where I could
                              overlay the elevation<br>
                              curves/data and keep it separate. It is
                              for my routing engine<br>
                              GraphHopper where I would need to do the
                              following:<br>
                              <br>
                               * to calculate the distance I take the
                              latitudes and longitudes from<br>
                              OSM, to guess the speed I take the highway
                              and other tags. Then, with<br>
                              the help of the SRTM data I modify this
                              distance and speed to be more<br>
                              real world.<br>
                               * to create an elevation profile of the
                              resulting path. This should be<br>
                              simple (?) as the elevation data could be
                              in a separate database and<br>
                              just fetched on demand.<br>
                              <br>
                              Will the resulting routing database fall
                              under ODbL which the providers<br>
                              probably do not want as their elevation
                              data could be guessed or even<br>
                              recalculated (with a bit effort)?<br>
                              <br>
                              Sorry, if this is a stupid question. I'm
                              really new to OSM licensing<br>
                              world :) and there was a similar question
                              but this was regarding hill<br>
                              shading and the old license:<br>
                              <a moz-do-not-send="true"
href="http://gis.19327.n5.nabble.com/OSM-legal-talk-ASTER-or-no-ASTER-td5715399.html"
                                target="_blank">http://gis.19327.n5.nabble.com/OSM-legal-talk-ASTER-or-no-ASTER-td5715399.html</a><br>
                              <br>
                              Regards,<br>
                              Peter.</font><br>
                          </div>
                        </div>
                      </div>
                    </font></blockquote>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>