Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Australia

Google Maps Deterring Outback Tourists, Say Small Firms (bbc.com) 123

Tourism operators in Australia claim inaccuracies in Google Maps are deterring potential visitors, by making remote attractions appear further away than they actually are. From a report: The Queensland government in north-east Australia has complained to Google, which says it will look into the issue. Firms looking to promote their small towns as remote tourist destinations say Google Maps inflates travel times. Outback businesses say errors in the map app can add hours to a journey. "People aren't coming to places because they think it takes too long, or they're missing opportunities to refuel and they're getting sent off on another road that has no fuel [outlets]," Robyn Mackenzie, of the Eromanga Natural History Museum, told national broadcaster ABC. "People will get frightened of travelling in the outback, because they don't have any confidence in the mapping," the general manager of the small town museum added.
This discussion has been archived. No new comments can be posted.

Google Maps Deterring Outback Tourists, Say Small Firms

Comments Filter:
  • You should be thanking Google Maps. In fact, Google should offer route inflation as a paid service.
    • by Anonymous Coward on Thursday January 17, 2019 @10:55AM (#57977272)

      Seriously though, nobody should be relying on Google Maps to plan a trip somewhere like the Outback. Outback steakhouse, sure. A place where taking a wrong turn or getting stranded could be fatal? Ask a human being. Google warns people when a store's operating hours may be different because of holidays, it would seem that a warning when traveling through the middle of freaking nowhere is warranted. "Consult local resources before making this trip or you may die." "Fragile ecosystem - do not deviate from marked paths!" "Seasonal access only - conditions out of season may be fatal."

      • by PrimaryConsult ( 1546585 ) on Thursday January 17, 2019 @11:49AM (#57977616)

        Same for driving through the US's deserts and mountain ranges. Even the interstates have some danger; they will warn you with things like "last fuel / cell reception for 80 miles".

        • by mjwx ( 966435 )

          Same for driving through the US's deserts and mountain ranges. Even the interstates have some danger; they will warn you with things like "last fuel / cell reception for 80 miles".

          You're under-estimating the vastness of Australia here comparing it to the relatively populous US. No fuel for 200 KM (130 miles) isn't just a thing, it's normal for many parts of Australia's highways. In the US it would be hard to find a place where you could drive for 200 KM and not find another town. I'm sure there are a few places but in Australia those places are everywhere. Australia is a country approximately the same size as the continental US with only 23 million people, almost all of whom live on

  • Ah'll visit that shit; just gotta lemme bring guns - Ah've seen Mad Max.

    -Likely no one anywhere

  • by OzPeter ( 195038 ) on Thursday January 17, 2019 @10:45AM (#57977208)

    In TFA it states

    In one case, the journey time from Birdsville, on the Queensland border, up to the Western Star Hotel in Windorah, in the centre of the state, was estimated to be close to 11 hours by Google Maps.
    After claims the time was inaccurate, Google changed the estimated time to about 7 hours and 45 minutes. But locals say the drive is closer to four hours with no stops.

    I just plotted out the same route in google maps and it told me 4 hours and 22 minutes. So either the story is wrong or google has been fixing things.

    But it makes me wonder* about people estimating times. Its a 380km journey and at 100km/hr that puts it at the 4 hour mark. I can't explain where 7 or 11 hours comes from,

    *Cue Stairways to Heaven

    • by Nidi62 ( 1525137 )

      In TFA it states

      In one case, the journey time from Birdsville, on the Queensland border, up to the Western Star Hotel in Windorah, in the centre of the state, was estimated to be close to 11 hours by Google Maps. After claims the time was inaccurate, Google changed the estimated time to about 7 hours and 45 minutes. But locals say the drive is closer to four hours with no stops.

      I just plotted out the same route in google maps and it told me 4 hours and 22 minutes. So either the story is wrong or google has been fixing things.

      But it makes me wonder* about people estimating times. Its a 380km journey and at 100km/hr that puts it at the 4 hour mark. I can't explain where 7 or 11 hours comes from,

      *Cue Stairways to Heaven

      To be fair to Google, with locals experienced in navigating and driving in the Outback it might be 4 hours. To a tourist in a rental car who has never been to the area before, may not be accustomed to road conditions (while I am sure there are some paved roads in the Outback I would assume there are also quite a few unpaved roads as well), and may take several stops out of an abundance of caution it might be a 6-7 hour drive. Personally I've heard enough stories that breaking down/running out of gas would

      • by OzPeter ( 195038 )

        In TFA it states

        In one case, the journey time from Birdsville, on the Queensland border, up to the Western Star Hotel in Windorah, in the centre of the state, was estimated to be close to 11 hours by Google Maps.
        After claims the time was inaccurate, Google changed the estimated time to about 7 hours and 45 minutes. But locals say the drive is closer to four hours with no stops.

        I just plotted out the same route in google maps and it told me 4 hours and 22 minutes. So either the story is wrong or google has been fixing things.

        But it makes me wonder* about people estimating times. Its a 380km journey and at 100km/hr that puts it at the 4 hour mark. I can't explain where 7 or 11 hours comes from,

        *Cue Stairways to Heaven

        To be fair to Google, with locals experienced in navigating and driving in the Outback it might be 4 hours. To a tourist in a rental car who has never been to the area before, may not be accustomed to road conditions (while I am sure there are some paved roads in the Outback I would assume there are also quite a few unpaved roads as well), and may take several stops out of an abundance of caution it might be a 6-7 hour drive. Personally I've heard enough stories that breaking down/running out of gas would be a concern to me in that area, especially if it is sparsely traveled.

        I can see tourists stopping along the way and being cautious of road conditions and taking longer than google estimates but it's googles estimates that are varying, not the reported times by tourists (which I can't see how google can know).

    • Comment removed based on user account deletion
      • by OzPeter ( 195038 ) on Thursday January 17, 2019 @11:13AM (#57977388)

        Could be that road conditions do not let you travel at 100KM on average.
        So most likely they think it was a road where 100KM was not possible. Here [google.com] a 450KM trip that would take 12.5 hours. 70KM more added 8 hours travel time.

        That actually could be the what is going on. The locals are taking route 14 in 4 hours, but the tourists are being directed along route 12 and 83 for what ever reason and take 12 hours. And I compared apples to oranges.

        One possible reason is that the locals are geared up for long distance driving with long range fuel tanks, but rental cars don't have them, so the locals can safely do a straight shot along a route with limited fuel stops and the tourists are being directed to the route that has more fuel stops that suit their shorter range tanks.

        • by mjwx ( 966435 )

          Could be that road conditions do not let you travel at 100KM on average.
          So most likely they think it was a road where 100KM was not possible. Here [google.com] a 450KM trip that would take 12.5 hours. 70KM more added 8 hours travel time.

          That actually could be the what is going on. The locals are taking route 14 in 4 hours, but the tourists are being directed along route 12 and 83 for what ever reason and take 12 hours. And I compared apples to oranges.

          One possible reason is that the locals are geared up for long distance driving with long range fuel tanks, but rental cars don't have them, so the locals can safely do a straight shot along a route with limited fuel stops and the tourists are being directed to the route that has more fuel stops that suit their shorter range tanks.

          That route looks like it goes across a section of unsealed road... Going 30 KPH would risk killing most vehicles on those rutted tracks, even a modded Land Cruiser would be plodding along. You'd be proper daft to be taking a rental Corolla on it.

          Also, a lot of rental car agreements in Australia prohibit taking cars far outside metropolitan areas. Certainly most of the cheap ones (stop laughing, I mean cheap for Australia) and doubly so around Perth.

          • by Cederic ( 9623 )

            You'd be proper daft to be taking a rental Corolla on it.

            That's exactly what I did. Shitty car but even a Corolla can handle a smooth unsealed surface.

            It's gravel or sand but it's not bumpy, it just isn't sealed. I get bigger potholes in the village I live in.

            60mph is perfectly safe, anybody doing 30kph isn't safe to drive anywhere.

            Also, a lot of rental car agreements in Australia prohibit taking cars far outside metropolitan areas. Certainly most of the cheap ones (stop laughing, I mean cheap for Australia)

            Mine was 'insured only in NSW' but I got them to add South Australia too, so that I could get nearer to Adelaide. They knew I was heading inland, they had no problem with it, and it was as cheap as I could find in Sydney.

    • by thegarbz ( 1787294 ) on Thursday January 17, 2019 @11:26AM (#57977460)

      Its a 380km journey

      For your search it is. Who is to say that when they made the search they got the same result? Now none of this is to say that Google is at "fault" but when a main road is closed in the outback you can easily change a route that adds hundreds of km to a journey. Likewise it can put you on a shitty dirt track that drops you down to 50km / hour.

      Last time I traveled through Far North Queensland Google took me off the highway and through Woodleigh Station. It cut 60km from my trip but at one point the road completely ceased to exist making the trip very slow and a short time later I was standing for 20min while 200 cattle were being herded around us and a cattledog was biting at my tires. We got to where we were going well over an hour later than the other car which left at the same time.

      Was Google at "fault"? No idea. Maybe the road was listed as closed, maybe the previous driver through the station raced through it at 100km/h and Google recorded the road as being faster. Maybe everyone else pulled over due to a road train passing on the highway and Google assumed there was an accident. Point is, from 4 hours to 7 hours is less than double the time and far worse than that does happen.

    • by AmiMoJo ( 196126 )

      100km/h seems optimistic for this road: https://goo.gl/maps/5u32Vbybed... [goo.gl]

      I'm no expert by in an ordinary car doing safe speeds on an unpaved gravel road I'd think half that, maybe 50 kph, is more reasonable.

      • by OzPeter ( 195038 )

        100km/h seems optimistic for this road: https://goo.gl/maps/5u32Vbybed... [goo.gl]

        I'm no expert by in an ordinary car doing safe speeds on an unpaved gravel road I'd think half that, maybe 50 kph, is more reasonable.

        You could easily do 100k on a road like that. Although once when I got to about 140k on a dirt road the car slowly started fish-tailing. I backed off to 100k and it was all good.

        • I was going down a gravel "highway" in Colorado several years back. It was in such good condition I looked down and found I was going 65 MPH. (I usually let the road conditions adjust my speed). Got scared, and slowed waay down. But the conditions let me go that fast.
      • I dunno, seems perfectly safe to me!

        https://www.youtube.com/watch?... [youtube.com]

    • There could be lot of sources of error. Maybe Google doesn't know it a 100 km/h and to be safe defaults to say 50 km/h for roads it has no information on. Maybe it's a map routing issue. In either case, it is good for areas to stay on top of these things.

      Just for kicks, I too google'd this place.
      https://www.couriermail.com.au... [couriermail.com.au]

      BirdsVille Development Rd is what you take to get the nice 4 hour drive. But read the article. It suggest keeping a speed of 80 km/h and watch out for rocks...

      I don't think it's irre

    • You can see here that OpenStreetMap reports a similar time [openstreetmap.org]: 7h25, for 532km, passing via a very long detour.

      Most likely, the router doesn't like the direct road, because part of it is tagged "unpaved", and that's estimated to around 20km/h.

    • by jrumney ( 197329 )
      Maybe at the time they did the search, there was a massive forest fire, or a storm coming. I'm thinking Google is smarter than some outback hick who thinks 380km is a 4 hour drive for tourists who aren't on best mates terms with the local traffic police.
    • by Cederic ( 9623 )

      I did this drive last month: https://www.google.com/maps?ll... [google.com]

      It didn't take 14 hours. It didn't take anywhere near 14 hours, even though I stopped and got out of the car a few times, stopped to take photographs a few times, encountered a sandstorm;

      Google's time calculations in Australia are fucked up.

  • From the article:

    "In one case, the journey time from Birdsville, on the Queensland border, up to the Western Star Hotel in Windorah, in the centre of the state, was estimated to be close to 11 hours by Google Maps.

    After claims the time was inaccurate, Google changed the estimated time to about 7 hours and 45 minutes. But locals say the drive is closer to four hours with no stops."

    OK so yes the original and even updated distance are a potentially bit long for a tank of gas while the four hours is not bad (ar

    • The point is the locals are quite right. Google shouldn't be estimating for tourists, they should be giving the time to destination assuming a direct path with no stops. Google shouldn't be making assumptions about your diet or the diet of your car.

      • Google maps never include fuel or rest or selfie stops, that would be ridiculous. Probably just some of the map data was incorrect and either caused a different route to be suggested or had wrong speed limits for example. Even if the limits were correct, they also don't assume you'd be speeding, which of course many are doing.

    • by ixuzus ( 2418046 )
      When you say potentially a bit long for a tank of gas you are thinking 380 km not 380 miles right? Four hours would be travelling within the speed limit if you don't stop.
  • by Anonymous Coward

    I think it's all the dingoes, spiders and drop-bears that are scaring away all the tourists!

  • There's no cellphone coverage there anyway, so you can't get at the wrong info.

  • In the Before Google era, people did not even know such places existed. Now they are complaining more tourists are not coming because of "errors" in Google. There is nothing wrong in the local governments spending their money to improve the Open maps initiative. If the competitor has more accurate data, it will force google to improve its offering, or be strangled by the invisible hand of the free market.

    Help build better, verified sources that will help ALL search engines. It will keep them on their toes

    • In the before google era there were travel agents and tourist information kiosk's that would help you plan an itinerary around the various places. You would see something like the Birdsville races on a travel show and then you would speak to tourist information or a travel agent to organise an itinerary that would include various stop offs around the region.
  • by Anonymous Coward

    Proper article https://www.abc.net.au/news/20... [abc.net.au]

  • I can't speak for Google Maps, but I can for Waze, another navigation app. I'd be surprised if Google Maps works differently.

    1) Trip times are a combination of historical trip times and current traffic conditions. Was this purported 11 hour trip time during a time of bad traffic?
    2) If there is no (cell) data reception, historical and current times don't get set. Default times for road segments are often extremely high.
    3) There's an option to "avoid unpaved roads". Presumably in the Outback there ar
  • It's not the distance nor the time that's keeping people from visiting, it's that there is nothing there. Sorry.

  • Traveling in the Australian outback is not like traveling in the continental United States, or Europe. The distances between any facilities, including sources of drinking water, are often vast, the traffic is minimal, cell phone reception is nonexistent outside major towns, and the roads are often unsealed or impassible without a four-wheel-drive vehicle, and the heat will kill you fairly quickly if you run out of water.

    Anyone planning to travel in Australia off the major highways needs to do more researc

Order and simplification are the first steps toward mastery of a subject -- the actual enemy is the unknown. -- Thomas Mann

Working...