[Potlatch-dev] GPX time elements

[Stellan Lagerstrom]

  On 2010-10-11 01:57, Craig Stanton wrote:
> In my case I know that the single trk is indeed a single track and should remain so. I've written my own pruner to cut out the extra data points and have created entirely valid file. Is there really no way that I can tell Potlatch or OSM that I have a valid file and the 3 minute rule shouldn't apply to long distance hikes? I've yet to hear of anyone that can walk a few hundred miles without a little down time. I'm probably going to put together a little php script to fake the time stamps on the locations but it seems strange that I'm having to change valid data to fit an assumption that doesn't cover it, what ever that time stamp was going to be used for it's now going to be totally useless. Granted it probably works very well for most car journeys, but hiking isn't exactly uncommon. Maybe the import procedure could have a check-box to turn off the automatic splitting feature, or radio buttons to split by time, split by trk or don't split at all.
Hundreds of miles of route should most definitely be split into shorter 
ways so that not all of it is returned for every request in the whole area.

If you're doing a lot of serious/big stuff, you probably should look at 
JOSM. Then you won't have to upload the track. Potlatch is primarily 
meant for beginners and casual use.


> On a side note, does any one know the reason for the OSM API requiring time data?
>
It is a very good indicator that the track is a an actual track, not, 
say, a plotted course, which likely contains copyrighted info from a 
road database. It is also a nice piece of information that can be used 
to derive speeds, stop signs etc.

-- 
/Stellan