Whatever you choose to do, understanding how your data looks, feels, and scales is going to be important.įrankly, assuming bike rides are often short, I suspect that calculating one or more bounding boxes for the bike ride, fetching all points of interest within the box, and then doing all further processing locally is going to be your best option. So I think it is going to depend on the nature of your data quite a bit.
Recording isn't paused but the location stays the same for a considerable time.There is a location where the recording was paused, thus causing a gap in the recorded data.Some special cases exist where the destination should be relatively easy to determine.
Now this is really easy if you have a track that goes from location A to B but my tracks are usually round courses where the start and end location are the same. I'm especially interested in the possible intended destination of a trip. Since there usually is a GPS track available I was wondering if and how I could extract possible visited towns or special locations during the trip. I'm looking for ways to generate more value from the data that was recorded. I'm creating a visualization tool for workout data, specializing on bicycle rides.