The complex part, the new storage system:
Version 9.x uses the Android SDK level that forces apps to use the private storage of each app, restricting the options to access the root of internal storage and SD.
This prevents keeping the maps/tracks,... where the app has always had them.
One of the important consequences of this change is that if private folders are being used, and the app is uninstalled, ALL data is deleted, so it is important to keep a copy of important data.
Not everything is lost! The Android file browser (Files) does not make it easy to access and copy operations in the app's folders. But there are browsers, such as Explorer: Explorer that can access the app folders, in the path:
If you want to see all of your waypoints, you can go to Waypoint >Manage. From this page you can change the properties, delete and export the waypoint. To see all of your waypoints in map, select the waypoints and go to show in map (1) and if you want to export your waypoints press Export (2). All of your exported waypoints will be stored in internal storage (by the default it stored in oruxmaps/geocaches).
oruxmaps download folder
DOWNLOAD
https://t.co/QXyCEaEydh
1. Offline map location on phone
For the new K3 App Offline map development, would it be possible to use the same map location as Oruxmaps uses?
Because Oruxmaps und Kurviger using the same maps, and Orux stores the map in Android 11+ in Android folder /android/data/com.oruxmapsDonate/files/oruxmaps/mapfiles an its not possible to change it from android folder, just possible to add another subfolder.
With the K2 app I can not access the /android/data folder while selecting the map. I would be nice this would be possible to safe storage space on the phone.
Is there a way to use a more user friendly folder on Android? I am having trouble with enumerators not being able to find the right place - even before multiple project support (which is great by the way!)
I know there are technical reasons for having migrated away from a main ODK folder for instances (not sure I really understand them!), butt drilling down to Android/data/
org.odk.collect.android/files/ is more difficult than my folk using ODK Collect are comfortable with.
Personally having multiple places for the mbtiles file to reside would not be great (it sounds like you plan to have a general folder and project specific folder) - because I know that if it can go wrong, it will. And the non-human-readable format of the project names on the device complicates things further (as highlighted by Florian_May above)... Finding yourself out in the field in the wrong project space needing to move mbtiles on the device is stressful enough, but getting someone to do that while they are on the phone to you asking why they can't see the map (when they've finally got signal) is a nightmare. Speaking from experience!
The other useful thing would be the possibility of downloading mbtiles directly from a Central server (maybe this is a different feature request) - if there were a function to upload mbtile as 'media' with a form definition, and for ODK Collect to download and transfer that to the appropriate folder, that would be a great step forward too. And would solve my hassles above...
The other useful thing would be the possibility of downloading mbtiles directly from a Central server (maybe this is a different feature request) - if there were a function to upload mbtile as 'media' with a form definition, and for ODK Collect to download and transfer that to the appropriate folder, that would be a great step forward too
My confusion is probably around why ODK can't write to a device when other Apps seem to do so - for example Viewranger (other navigation apps are available!) appears to be able to read / write data in an arbitrary folder named 'viewranger', so that is the naive assumption I was working on - ODK is the only I use that requires me to delve into the /Android/data.... folder. Apologies if that sounds 'challenging', I'm just revealing my level of stupidity rather than questioning anyone's competence!
My new-best-friend navigation app called Orux Maps allows me to use mbtiles, so if I could point to the folder that ODK used for Layers it would save needing two copies of the file on my device, and then I could navigate efficiently between recording stations...
I understand that putting instances in the /Android/data/... folder means that other apps can't access anything, which is great from a confidentiality or Data Protection perspective, so if that's the main constraint preventing use of other locations on the device for other functions, then that's a compromise worth living with. As always I live in hope of having cake and eating it...
My confusion is probably around why ODK can't write to a device when other Apps seem to do so - for example Viewranger (other navigation apps are available!) appears to be able to read / write data in an arbitrary folder named 'viewranger'
Making use of a common UI method of locating a file or folder would be good, for example, as an alternative to requiring the files to be placed in an ODK folder? Any process that is familiar helps, in my experience.
First download OruxMaps program to your device. Then load OruxMapsDesktop program to your computer. Set the map file (generated by Fetch_map) as calibration file and just generated hillshaded map as image file. Select a suitable destination directory and create map. After a while, the just created map (a whole folder) can be moved into your mobile devices 'mapfiles' folder which is inside oruxmaps folder. If there is too little space left on your device, you can configure oruxmaps to use some folder at external memory card as map folder. After the map folder has been moved to your phone or tablet, you can use OruxMaps to browse for the just generated map and select it. OruxMaps can be used to navigate on the hillshaded map and record travelled path.
Another much used map app is Oruxmaps. You find Oruxmaps Donate from Google Play, it costs about three euros. However, at
www.oruxmaps.com you can download the free version (.apk file) and transfer it to your mobile phone. This is handy if you want to check first if you can make the app to work and do you like it. If you do like, why not donate the small sum for the developer?
The "Windows" version is the .img file and can be directly copied or installed to the Garmin folder on your GPS (on older, single mapset devices mapname may need to be renamed gmapsupp.img), or copied to Orux/mapfiles folder. Orux is available on the Google Play Store or for free at the authors website, To view in Basecamp on Windows use the "Mac" version, after extracting and opening to mapaname.gmap, mapset can be placed in the Windows C:/ProgramData/Garmin/Maps folder (may need to un-hide and create) or installed to Mac using it's install process.
Linux: you can use Qlandkarte GT, its sucessor QMapShack or MapEdit++ (the latter is for Windows, but works fine under wine). You can also use MapSource with wine and load maps running the auto-install file (wine OpenStreetMap_*.exe) or copying *.gmap folder into .wine/drive_c/ProgramData/GARMIN/Maps/
First of all, download file for GPS of the country you want from Downloads page and unzip it. You'll get a file called gmapsupp.img. The easiest way to have the map in your Garmin device is copying file gmapsupp.img in the external SD/micro SD card of the device, within a folder called Garmin (create it if it doesn't exist); in some models gmapsupp.img file must be copied into Map folder instead of Garmin folder (note Map folder may be hidden). This method is also recommeded because in case of any problem with the map, removing the card and restarting device will be enough to solve it. To copy it use a card reader (faster) or connect your device to the computer with a suitable cable, in 'Mass storage' mode (slower).
Another theme is Voluntary UK which looks a bit like an OS Landranger map. You'll have to download it manually, though, on to your PC. Scroll dwon that page and look for Voluntary_Atlas.zip. Download, then unzip it. Then drag and drop the folder on to your Android device (connect it with the USB cable) into the mapstyles folder
These files can be placed on the Android device in the directory.../oruxmaps/tracklogs - you might want to create sub-directories of thisdirectory to make the route files easier to find (e.g. by country or region).
With the macOS App Store version of the Cartograph app both files have to be located in the user's downloads folder (due to sandbox restrictions). The download folder is located under "/Users/your_user_name/Downloads".
After you have Orux Maps installed on your Droid phone, locate the following folder and extract the maps to a folder within this directory. Each map source that you obtain from this site, wheter Earth, Terrain or both, requires that it have its own folder within MAPFILES. Folder Structure: \oruxmaps\mapfiles\MAP SOURCE FOLDER
Example: If you download 'Teton Mountain Range Earth Terrain.zip' it will extract into two folders as shown below. If you only wish to use one of the two map sources then you only need to copy the map source folder that you plan to use to your oruxmaps/mapfiles folder. There cannot be another folder between the Earth & Terrain folders and the mapfiles folder. Earth and Terrain are considered two seperate map sources and should be structured accordingly.
When clicking into the terrain folder above the structure will appear as follows. Each number value (e.g. 10 through 15) represents the set of tiles that are provided as part of the map source. The higher the number the greater the resolution and the higher the file count.
Copy or move the unzipped files to a folder where you would like to have Mobile Atlas Creator installed. On computers running Windows please make sure not to install MOBAC into Program Files sub-directory!
f448fe82f3