By continuing to use this website, you are agreeing to our use of cookies to personalise the services we offer you.
Welcome, Guest. Please login or register.
Did you miss your activation email?
Geolives forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - livfoss

Pages: [1] 2 3 4
iOS - SityTrail mobile applications / SityFit data loss?
« on: February 09, 2019, 03:00:23 pm »
I'm using the SityFit health application on my iPhone. I use it to supplement the data I get on the SityTrail apps, and I've been doing so for a long time. Recently I upgraded my phone from an iPhone 7 to an iPhone XS. Apple have a very simple migration tool called Quick Start, which transfers pretty much everything from the old phone to the new - including passwords, photos etc. But apparently it doesn't transfer the data that I had in my SityFit application, so I've lost my history of steps etc.

Is there any way around this?


I just got a (presumably) automated message while opening SityTrail FR on my iPhone 5, running iOS 10, asking me to rate the app. I followed the links,  but I couldn't find a way of rating it, nor could I update my own review which dates from 2012 - I would have said nice things! Does anyone know how to get the App Store to cooperate with editing reviews or posting completely new ones? Not sure if this is a fault with the App Store or the app itself, which as far as I'm concerned is still going strong and remains very useful.

No answers to show-stopping issues on this forum for ten days. The big issue with Open Street Map tiles is mentioned on the French forum but not so much as an acknowledgement here. I love the Sity apps but the support appears to be falling apart. Please help.

As of 11 July 2016, one can't print a trail from SityEditor if you choose  :(Open Street Map, because somehow the access rules provided by MapQuest have changed. See

When are Geolives going to deal with this? As of now, one can't print a map based on Open Street Map, for example one crossing the boundary between countries. PLEASE REPLY TO THIS ASAP!!

SityEditor / Re: Route plan
« on: July 13, 2016, 08:23:51 pm »
Hi - if you're still there. I love the idea, but using a trail of about 50km generated by SityTrail NL, I got a file around 800kb. So your app wouldn't work for me unless you can up it by an order of magnitude! Are you still working on it?

I have produced a series of trails of a trip through Holland by bike. I just noticed that the reporting of the time by the "Calculate" operation on the Editor seems to generate wrong results, unless the Editor cleverly notices when one has stopped moving (as a bike computer would do). In one example, the difference between start and finish times in the raw GPX file is 432 minutes, but is reported as 189 minutes!

Is this a bug or a feature?

This morning I upgraded my iMac to Mac OS El Capitan 10.11.5, and I then opened the SityTrail Editor and downloaded a trail which I had been working on yesterday. I made a couple of small changes (total distance, some text) and tried to save, but the 'save' action won't terminate - it just says "Please wait". I have tried this on the most recent versions of Safari, Google Chrome and FireFox and the result is always the same.

I then tried to print the trail using the Open Street Map maps  (the only one that I can use since the trail covers two countries), and instead of seeing the whole map, I saw a small amount of real map, plus a series of tiles with the 'MapQuest' logo and a text explaining that something changed on 11 July.

Can you help with these two issues? I just don't know how to proceed.

I have not analysed the original GPS data, but I could. My guess is that there will not be any inaccuracies of this magnitude, and the information displayed on the iOS app is just wrong. Would it help if I did this analysis?

It is possible to change the colour of the trail recording using the editor - for example from red to blue, to avoid confusion with existing map elements like main roads. However, when I try to print, the trail colour always goes back to the original red. Is there any way to make the colour 'stick'?


I've just done a cycle tour in Holland using SityTrail NL. The GPS recording of the route on the map is accurate as always, but the summary of the elevation data is nonsense! For example, on one daytime summary, the app says I did 1427m uphill and 2643m downhill. Holland is notoriously flat, and has a lot of territory a few metres  below sea level! When I put this data into the SityTrail editor, it is soon corrected to uphill 118, downhill 115. The elevation profile ** from the GPS** pretty much looks like this more credible data. Is this a bug in the iOS app?


Actually, having re-worked my calculations, I see that I am not out all that far: about 5 percent, perhaps. That could be explained by different degrees of accuracy being used in the two calculations, as many individual distances between points are quite small and so are sensitive to variations in precision in the arithmetic.

I'm doing some analysis of .gpx files, and I realise that knowing two points (latitude, longitude) on the Earth's surface doesn't tell you the distance between them. For that you need a formula (algorithm). A popular one which is fairly accurate for short distances is Haversine. If you don't mind telling me, which algorithm does the Web Editor use? I can't make my distances the same as yours - they are out by quite a large margin, so I'm curious to know.

thanks for any info

Given the number of users you have, I have no idea why I'm almost the only person asking questions in English, but here comes another one:

I just uploaded a little trail and clicked 'Compute' to update the statistics. This gave a time of 121 minutes. I then printed out the same trail and got a time of 2h24mins, which is 144 minutes (isn't it?). The second time was correct, as far as I can see. To confirm, I downloaded the .gpx file, and the first recorded time is


and the last is


Which makes the time difference 2h24I believe. Accordingly I was able to update the computed statistics by hand; but since the data was there, why was the computation wrong?


Thanks Patrick - this worked for the computer display, but it didn't work for the printout, which remains red. That and the fact that there seems no way to change the line thickness means that my trail is still very hard to see when I present it as a handout. I had to use an outliner to mark up the trail by hand. Is there any workaround for this issue?



I just laboriously drew a trail representing a two-day bike ride which I did without GPS. The trail came out in the default red and is therefore rather hard to see on the IGN map where many roads are that colour: so I changed the colour to blue. Although the trail was selected at the time (all of its points showing), it stayed red.

Is there a way to change the colour of an already-drawn trail?


Pages: [1] 2 3 4