<div dir="ltr"><div>Some jurisdictions do publish live traffic updates in GeoJSON, examples:</div><div></div><ul><li><a href="https://opendata.transport.nsw.gov.au/dataset/live-traffic-hazards">https://opendata.transport.nsw.gov.au/dataset/live-traffic-hazards</a></li><li><a href="https://www.data.qld.gov.au/dataset/131940-traffic-and-travel-information-geojson-api">https://www.data.qld.gov.au/dataset/131940-traffic-and-travel-information-geojson-api</a></li></ul><div></div><div>Note a lot of these API feeds are licenced CC-BY, so downstream consumers would need to comply with attribution requirements when synthesising OSM and live traffic datasets.<br></div><div></div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 9 Feb 2022 at 14:35, Michael Collinson <<a href="mailto:mike@ayeltd.biz">mike@ayeltd.biz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>
    <p>We have a reasonable if not perfect tagging system for a router
      to assess (and make assumptions) about the quality of a road for
      various types of vehicle in BEST CASE  conditions. motorway versus
      track, tracktype, asphalt versus gravel being the main ones.<br>
    </p>
    <p>From a router point of view it would be nice to dynamically place
      routing penalties on roads or stretches of road according to
      temperature, snow, rain, side wind (and ?). Simplistically, input
      "snow" and pick up from OSM tags advising "often impassable in
      snow" or "snow chains advised in winter" and then the router can
      decide how much penalty to apply given projected conditions and
      vehicle type.</p>
    <p>Sounds reasonably simple to devise and implement. I've played
      mentally with the same idea for suggesting footpath routes that
      vary depending on the weather.<br>
    </p>
    <p>More esoterically and more real time would be a community project
      to develop an open overlay database of transient data where the
      public and/or authorities can label osm ways with advisories
      quantitative enough for routers to again assess a routing penalty.
      The obvious starting point would be a simply "closed".<br>
    </p>
    <p><br>
    </p>
    <p>Mike<br>
    </p>
    <div>On 9/2/22 1:17 pm, Graeme Fitzpatrick
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">
        <div>Reading this article earlier:</div>
        <div><br>
        </div>
        <div><a href="https://www.abc.net.au/news/2022-02-08/google-maps-to-fix-routes-trapped-travellers-queensland/100805884" target="_blank">https://www.abc.net.au/news/2022-02-08/google-maps-to-fix-routes-trapped-travellers-queensland/100805884</a></div>
        <div><br>
        </div>
        <div>So what's the best way to avoid the same issues?</div>
        <div><br>
        </div>
        <div>
          <div>
            <div dir="ltr">
              <div dir="ltr">
                <div>
                  <div dir="ltr">Thanks
                    <div><br>
                    </div>
                    <div>Graeme</div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
Talk-au mailing list
<a href="mailto:Talk-au@openstreetmap.org" target="_blank">Talk-au@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/talk-au" target="_blank">https://lists.openstreetmap.org/listinfo/talk-au</a>
</pre>
    </blockquote>
  </div>

_______________________________________________<br>
Talk-au mailing list<br>
<a href="mailto:Talk-au@openstreetmap.org" target="_blank">Talk-au@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-au" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-au</a><br>
</blockquote></div></div>