Queensland Department of Transport and Main Roads (TMR) has traffic and road condition information captured in the QLDTraffic system that is available for use via GeoJSON feeds.
These feeds cover Hazards, Crashes, Congestion, Flooding, Roadworks and Special Events and Web Cameras details.
The QLDTraffic system can be viewed here: https://qldtraffic.qld.gov.au/
The API is publicly accessible. Details on accessing QLDTraffic’s traffic and road condition information via GeoJSON can be found in the QLDTraffic website API specification found here: https://www.data.qld.gov.au/dataset/131940-traffic-and-travel-information-geojson-api
I would like to see this integration consume the events from https://api.qldtraffic.qld.gov.au/v2/events?apikey=3e83add325cbb69ac4d8e5bf433d770b and to display events within a nominated radius on the Home Assistant map, with event information such as Suburbs / Localities, Roads, Description, What to expect, and a last updated timestamp.
Thanks for the suggestion, but unfortunately the GeoJSON component in Home Assistant only displays data from the “title” key in the feed’s properties. The QLDTraffic feed doesn’t use “title” 
In the existing GeoJSON component, it would be great if we could customise which key(s) it would display!
Unfortunately the GeoJSON standard does not really specify anything other than the geolocation data format. Even the title is a custom field.
It’s great that there is such a detailed documentation of the API, but I don’t think that the existing GeoJSON integration could be easily extended to support that API. It’s a complex structure, and it appears to require the use of an access key. The best approach from my point of view would be to create a new integration based on that API.
I currently use the existing GeoJSON integration to consume this feed, but I just end up with a bunch of “unnamed devices” on my map. If I could just get the existing GeoJSON to look at, for example, the “event_type” key instead of “title”, that would be a massive improvement!
Ultimately a new integration based on the API with more information would be awesome.
Has anyone found a solution to the “unnamed device” issue? I’ve tried everything, even using a json template in the “entity_namespace”