When starting AAT the first time it shows the main view. That's basically a list of sub-views you can open. The first 3 entries are "Copckpit A, Cockpit B, and Map" if you have one of these open you can cycle through them with the down arrow. The right arrow switches trough the different pages of the view you are in.
In the map view the down arrow is in the main bar (tap the top area of the map). For zooming and navigating tap the bottom area of the map. For grid, search, overpass etc. tap the right area of the map. For the draft editor tap the left side of the map. The track that gets currently recorded is always displayed on the map.
Now once you have stopped the tracker go back to the main view with your phones back button. Then select Track list to show a list of all recorded GPX tracks. Every track has a preview image if you tap on this image you'll get a context menu for this GPX-file. Here you can for example select this track for one of the 4 overlay slots. You can display any recorded track by taping the text area of the list entry. (Always go back to the list with the phones back button). In the track view there are again different pages (graph, summary and map) and you can cycle trough all tracks with the up and down arrow.
There are different pages in the Track list view (Access them with < ... > ). This pages offer a map as an alternative to the track list, summary information and filter options.
AAT does not automatically remove downloaded map tiles. This is to...
- reduce network traffic as much as possible.
- reduce battery drain.
- speed up the map view.
This means that you have to remove old tiles manually from time to time.
Go to Settings->Map Tiles
to remove old map tiles.
- Download maps and render themes from one of these map providers:
OpenAndroMaps,Freizeitkarte or Mapsforge - Store extracted maps in the directory
maps
or in one of its subdirectories.
Example:maps/OAM/
containsAlps.map
- Store extracted themes in a subdirectory of the directory containing the corresponding maps.
Example:maps/OAM/OAM/
containsandromaps_cycle.xml
,symbols/
,patterns/
and other files.
- Inside AAT open the map settings dialog. (
Settings->Map Tiles
). - Select the directory that contains the map files (In this example
maps/OAM/
will be listed). - Select a render theme.
- Disable Mapnik and enable Mapsforge in
Menu->Map
.
AAT let's you create and view files in GPX format. This files are exchangeable with many other applications. They can also be edited in a text editor. These and other files are stored in subdirectories of the data directory. You can choose the location of the data directory from the settings. The structure of the data directory is as follows:
aat_data/activity[0-4]
- tracked activitiesaat_data/log
- activity that gets tracked at the momentaat_data/nominatim
- search result from OpenStreetMap Nominatimaat_data/osm_features
- OSM Features original file and parsed filesaat_data/overlay
- overlays such as planned tracks or search resultsaat_data/overpass
- queries from the OSM Overpass serveraat_data/dem3
- cached Digital elevation data from the Shuttle Radar Topography Mission and other sources
AAT lets you query the Overpass API. Any result of a query can be saved to aat_data/overlay
. It then can be displayed as an overlay inside the map-view whenever needed.
[amenity=restaurant]
will get you list of all restaurants located inside the area that was visible on the map-view before opening the Overpass dialog.
AAT uses the formula time[hours] * MET * weight[kg]
to calculate the kcal used for a specific activity.
MET stands for metabolic equivalent. The higher the value, the more energy you would use
for this specific activity. A complete list of activities and MET values can be found here.
Both MET and weight can be provided in the settings dialog. The MET value is leading the activity's name. For example: 6.8 bicycling, leisure, moderate effort
For questions, feedback and bugreports report an issue or send an e-mail to [email protected]
You can open a pull request or send me your translation as e-mail or publish them as an issue report.
Resources (like text and icons) are located in app/src/main/res.
English text strings are in this file: /app/src/main/res/values/strings.xml
German translations are in this file: /app/src/main/res/values-de/strings.xml
- To add a new language just add a
value-<language code>
directory containing astrings.xml
file. - Use the English (original) strings.xml as a template.
- Use the same structure (order) as in the original file
- You don't have to translate everything. Just remove an entry and English is used as a fall back.
- You can modify existing strings.
- You can add new suggestions for strings.
- If a ° gets displayed somewhere inside the app it means the string is not yet in the resource file (only in java code). See app/src/main/java/ch/bailu/aat/util/ToDo.java