I'm asking in relation to doing field surveys in low bandwidth/high data cost locations.
If I was to avoid caching and instead download/upload as I go, in terms of map tiles, quests and uploads, roughly how much data would I expect to consume if I was using the app out in the field for 2 hours
Note that it depends not on time but on (a) area covered by mapping (b) density of OSM data in this area.
Note also that with known mapping area you can run quest download using WiFi and fetch map tiles and upload quest after returning what allows to not use mobile data at all.
It also depend on whatever user requests additional quests manually or is it processing all downloaded quests before downloading more.
But overall data usage is low, I would estimate it to be around 1MB/h for walking around (with massive differences depending on factors that I mentioned).
Thank you for those details. I'm aware of the prep you can do before going
out into the field but the folks who will be using this will likely not
have wifi at all, so I'm looking at worst case. Where its (wifi) available,
I'll be encouraging them to use it
On Mon, Feb 12, 2018 at 5:05 PM, Mateusz Konieczny <[email protected]
wrote:
It also depend on whatever user requests additional quests manually or is
it processing all downloaded quests before downloading more.But overall data usage is low, I would estimate it to be around 1MB/h for
walking around (with massive differences depending on factors that I
mentioned).—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/westnordost/StreetComplete/issues/861#issuecomment-364949591,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6K21wst8ph1F3fJM0qW-Xm_PXcPWMgks5tUFNSgaJpZM4SCKQ4
.
Can't give an estimate, I never tested it out. As @matkoniecz said, it also depends. But you are free to post your results here, so we can have an estimate in the future.
I can tell you that uploading quest answers is very light on data, I would say around 300B per answer (and around 1kB if there is a conflict). Of course, if you leave notes with attached pictures, this is a different story, that would be around 300kB per photo.
Also, to optimize the process for least amount of data usage, you can disable all quests in the options that you are not immediately interested in and scale up the map tile cache to max.
By the way, where would that be? Without Wi-Fi and high data cost?
I'm currently in Lesotho with the MapLesotho project. We've mapped the
country using aerial imagery over the last 4 years and are now looking on
expanding the gathered data with field surveys. Trying to identify the best
tools to use. We're currently looking at Mapillary (where data is
available) Field Papers and StreetComplete and OSMTracker.
We're putting together some material for additional quests that would see
us using StreetComplete more than either of the other tools if implemented.
These are mainly to do with the composition of buildings (usage and
construction materials) but I'll save details on those for the pull
requests.
btw, loving the app. I was waiting years for something like this
On Mon, Feb 12, 2018 at 5:30 PM, Tobias Zwick notifications@github.com
wrote:
By the way, where would that be? Without Wi-Fi and high data cost?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/westnordost/StreetComplete/issues/861#issuecomment-364957803,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6K2_PHnxB_SqSLm2ww1rzN00VY9cOBks5tUFkwgaJpZM4SCKQ4
.
Wow, that sounds cool!
Are you aware of POSM (=portable OSM)? See ticket #30.
I'm looking at one right now :)
On Mon, Feb 12, 2018 at 6:18 PM, Tobias Zwick notifications@github.com
wrote:
Wow, that sounds cool!
Are you aware of POSM (=portable OSM)? See ticket #30
https://github.com/westnordost/StreetComplete/issues/30.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/westnordost/StreetComplete/issues/861#issuecomment-364974311,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6K2zhInxyvmw-ZZKqpC93fA11Wkj4iks5tUGRggaJpZM4SCKQ4
.
To expand on
density of OSM data in this area
StreetComplete runs an overpass query, with a very small request and response depending on how many quests may be created. For example, for "add surface" quest - for city with fully mapped surface or forest without roads response will contain no elements so it will be tiny.
For place with hundreds of roads with unpaved surface StreetComplete will get reply describing road for every quest, so data usage will be higher.
Similar thing happens with map tiles - in remote places tiles may be empty, in well mapped city center each map tile may have significant amount of data.
So doing exactly the same (loading map and running scan for the same quests) in two different places may give wildly different results.
I never tested it but I expect data usage to be dominated by downloading map data, followed by usage during downloading quests and tiny usage for uploading answers (assuming that photo uploading feature is not heavily used).
I asked one of the team who has his data monitored (work phone) and he said
that it's less data than apps that run in the background which do periodic
updates so it definitely looks to be manageable but you make a good point.
I can account for it in the instructions that I'm working on for the team.
Hopefully that should mitigate against any major issues.
I will, however, ask him to run an extreme set of quest requests and
navigate through a significant amount of areas just to put some numbers
around it.
I'll report back and let you know, for future reference
Thank you
On 12 Feb 2018 19:44, "Mateusz Konieczny" notifications@github.com wrote:
To expand on
density of OSM data in this area
StreetComplete runs an overpass query, with a very small request and
response depending on how many quests may be created. For example, for "add
surface" quest - for city with fully mapped surface or forest without roads
response will contain no elements so it will be tiny.For place with hundreds of roads with unpaved surface StreetComplete will
get reply describing road for every quest, so data usage will be higher.Similar thing happens with map tiles - in remote places tiles may be
empty, in well mapped city center each map tile may have significant amount
of data.So doing exactly the same (loading map and running scan for the same
quests) in two different places may give wildly different results.I never tested it but I expect data usage to be dominated by downloading
map data, followed by usage during downloading quests and tiny usage for
uploading answers (assuming that photo uploading feature is not heavily
used).122 https://github.com/westnordost/StreetComplete/issues/122 is also
related to this issue
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/westnordost/StreetComplete/issues/861#issuecomment-365002577,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6K2-kt8E3DLX-esCA76OD45X2D3-cKks5tUHhngaJpZM4SCKQ4
.
For worst case scenario you may try some major, well mapped city (highest data density).
So, I am going to close this issue as the question asked was answered as far as we can provide the answer. But still you are invited to post any of your findings here to know that for the future! :-)
Most helpful comment
I'm currently in Lesotho with the MapLesotho project. We've mapped the
country using aerial imagery over the last 4 years and are now looking on
expanding the gathered data with field surveys. Trying to identify the best
tools to use. We're currently looking at Mapillary (where data is
available) Field Papers and StreetComplete and OSMTracker.
We're putting together some material for additional quests that would see
us using StreetComplete more than either of the other tools if implemented.
These are mainly to do with the composition of buildings (usage and
construction materials) but I'll save details on those for the pull
requests.
btw, loving the app. I was waiting years for something like this
On Mon, Feb 12, 2018 at 5:30 PM, Tobias Zwick notifications@github.com
wrote: