Jump to content
Sign in to follow this  
Followers 5
jadefalcon

Background Data Usage - Why?

Recommended Posts

I used the Geocaching.com app for Android this week and noticed curiously that the app used .24GB of foreground data and .44GB of background data. What is the purpose of this app using almost 1/4 of my data allotment for just background data?

Share this post


Link to post

the app doesn't store an map data, so any time you are using it is constantly pulling map data.

Share this post


Link to post

Have you been making use of the new Trails map type? It uses more data than the default google map type since the maps aren't in google's hyper-efficient vector format (which we're looking into ways to use!)

Share this post


Link to post

?!

 

Is "Trails" a new map we haven't seen on www.geocaching.com/map ?

 

The "Trails" maptype on mobile corresponds to the "Geocaching" maptype on the web. They're provided by our own servers instead of going through a third party service

Share this post


Link to post

?!

 

Is "Trails" a new map we haven't seen on www.geocaching.com/map ?

 

The "Trails" maptype on mobile corresponds to the "Geocaching" maptype on the web. They're provided by our own servers instead of going through a third party service

Why call identical maptypes by two different names? Would that not be confusing for a new user transitioning between mobile and web devices?

 

Random somewhat unrelated thought:

I downloaded the most recent version of the Geocaching App just for fun. Why is there no open-source topographic map? Many outdoor enthusiasts (like myself) rely on accurate topographic maps to navigate pretty much any outdoor terrain off the sidewalk. The Google Maps Terrain layer seems useless because the contour lines disappear at a certain zoom level. Even the OpenCycleMap (while not my favourite OpenStreetMap layer) would be much better than what there is currently.

Share this post


Link to post
Why call identical maptypes by two different names?
"I'll tell you!... I don't know. But it's a tradition... and because of our traditions... Every one of us knows who he is and what Groundspeak expects him to do."

 

Would that not be confusing for a new user transitioning between mobile and web devices?
Yeah, but it's just one of the examples where Groundspeak's free app uses different terminology from the web site and from every other app. And the discrepancies have been pointed out, so at this point, I think it's intentional.

Share this post


Link to post
Why call identical maptypes by two different names?
"I'll tell you!... I don't know. But it's a tradition... and because of our traditions... Every one of us knows who he is and what Groundspeak expects him to do."

 

I get it - Best line today.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 5

×