The source tag should directly name the exact tag for which it specifies the
source, so it should be:
source:hiking_scale:awtgs=
From: Ian Steer
Sent: Wednesday, 9 February 2022 15:19
To: talk-au@openstreetmap.org
Subject: Re: [talk-au] Aust. Walking Track Grading System (AWTGS)
With
Thanks, fellas! It's not an utterly stupid idea then!
On Wed, 9 Feb 2022 at 14:46, Brendan Barnes wrote:
>
> If a road has definitive closure dates we might be able to utilise
> opening_hours. I tried to start something similar on Victorian Alps
> seasonal road closures, for example
>
>> I prefer hiking_scale:awtgs= as you know that it is a hiking scale ..
>> even if you don't know what awtgs is.
>>
>Fair comment.
>
>> Routes are a different problem while the worst one could be
>> included .. what happens if/when things change? Possibly better to leave
it off?
Absolutely Steva. Better routers make better decisions.
But yeah Graeme, my preference would be a router to read live GeoJSON
sources, for the most accurate "what's happening on the ground right now"
when considering traffic hazards. This is (relatively) easier for websites
and smartphone apps
On Feb 8, 2022, at 8:08 PM, Graeme Fitzpatrick wrote:
> Do routers "read" such things as flood-prone, intermittent & seasonal?
My "quick, off-the-cuff" answer would be: "better routers SHOULD." The real
answer is very much "check your particular router."
On Wed, 9 Feb 2022 at 14:02, Brendan Barnes wrote:
> Some jurisdictions do publish live traffic updates in GeoJSON, examples:
>
>- https://opendata.transport.nsw.gov.au/dataset/live-traffic-hazards
>-
>
>
On Wed, 9 Feb 2022 at 13:35, Michael Collinson wrote:
> 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
Some jurisdictions do publish live traffic updates in GeoJSON, examples:
- https://opendata.transport.nsw.gov.au/dataset/live-traffic-hazards
-
https://www.data.qld.gov.au/dataset/131940-traffic-and-travel-information-geojson-api
Note a lot of these API feeds are licenced CC-BY, so
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.
From a router point of view it would
Reading this article earlier:
https://www.abc.net.au/news/2022-02-08/google-maps-to-fix-routes-trapped-travellers-queensland/100805884
So what's the best way to avoid the same issues?
Thanks
Graeme
___
Talk-au mailing list
Talk-au@openstreetmap.org
On Tue, 8 Feb 2022 at 16:35, Warin <61sundow...@gmail.com> wrote:
> I prefer hiking_scale:awtgs= as you know that it is a hiking scale .. even
> if you don't know what awtgs is.
>
Fair comment.
> Routes are a different problem while the worst one could be included
> .. what happens
11 matches
Mail list logo
