AnalyzeMyTrack! help

Geodatabases

Currently, reverse geocoding for each country is done using the GeoNames database.
Slovakian database is an exception, as it contains data both from GeoNames (cca 7000 entries) merged with hiking.sk POIs (cca 2000 entries, obtained with kind agreement of Ľubo).

GeoNames contains mostly municipalities and lacks touristic points. If you can provide larger database of touristic POIs anywhere in the world, please contact me.

Notes on gpx log processing

Inserted gpx log consists of series of points, its content can be following (two points of a track are displayed here):

gps annotation

Each point has a latitude, longitude, (optional) elevation, date, time and other attributes. AnalyzeMyTrack! treats whole log file as a single track, ingoring multiple track segments or waypoints. Elevation is an optional attribute of a track point – in case of missing elevation, "real distance" between two points is computed in the same way as "flat distance", using the haversine formula.

How reverse geocoding works?

Geodatabase consists of thousands data points with text labels. Each entry represents a geographical place with latitude, longitude and name. Thus, each minucipality, disregarding its real size, is represented only as a sigle point.

Your track is represented as a series of points. Fitting the points from your track to geographical entries in the geodatabase is done in following way:

gps annotation

Precision parameter determines size of the circular window around a point when searching for named geopoints.

Understand the data table

Analysis provided by AnalyzeMyTrack! includes a table which may look like following:

data table example

Data entries (rows) in the table have following meaning:

(*) Relevance is fraction of distance between current data point and geopoint found in database, divided by value of precision. For example, if precision is set to 1.0km and distance between currently analyzed track point and some geopoint found in dabatabase (like "Vrakuna" in the example) is 0.56km, relevance is 44%. If relevance is 100%, the distance is 0.0km, if relevance is 0%, the distance between current track point and found municipality in database is equal to precision.

Note that one entry in the table usually merges more points of your track.

Preset a country in the country list?

The country list is quite long, contains 242 countries, thus selecting desired country can be a pain. AnalyzeMyTrack! employs hostip.info database and predefines a country in the list according to your IP address. However, IP tracking is not accurate and, additionally, your gpx log can be located in different country than your current location.

Due to this reasons, you can force country selection is the list via following URL:
http://my-track.net/?country=name

For example, if you want United States of America to be predefined in the country list, the URL is:
http://my-track.net/?country=United_States_of_America

Note that the country name must be written as is in the country list (case-sensitive) and spaces must be replaced by underscore characters.

Handling gpx parser error

"GPX parser error" indicates problem with processing the gps log. The reasons can be following:

Otherwise, please send the gpx log to peter at my-track dot net in order to determine your problem