Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the original gpx files for identifiable and public tracks #5

Open
Zverik opened this issue Apr 3, 2013 · 4 comments
Open

Use the original gpx files for identifiable and public tracks #5

Zverik opened this issue Apr 3, 2013 · 4 comments
Milestone

Comments

@Zverik
Copy link

Zverik commented Apr 3, 2013

I know there are points in the DB for identifiable tracks, but it would be much better to have all the additional information — hdop/vdop, waypoints, course and speed etc. Check this one track for example.

Of course, file names should not be preserved, but they must be included in metadata.xml.

Also note that some tracks may be stored in gz/zip/some other compressed format. Those should be unpacked: only gpx files should be included in gpx dump. To speed up the process the generation process of a dump may leave previously extracted identifiable and public gpx files instead of recreating them (and this concerns other types as well): changing a track isn't possible, only deleting it entirely.

@Zverik
Copy link
Author

Zverik commented Apr 16, 2013

As it turns out, original file names could be not only for gpx files, but also for archives. In this case I suggest updating metadata.xml format. The filename field should contain not name in the archive, but the original file name. Inside <gpxFile> entry there should be an array of <gpx filename="..." /> pointing to all extracted files. In case of a single gpx file that would be it. In case of an archive all files should be unpacked to a subfolder.

@iandees
Copy link
Owner

iandees commented Apr 16, 2013

The plan was to not unpack the original GPX archives, only to normalize them to .gz or similar. If we unpack everything we'll have to make a change to the metadata file, yes.

@Firefishy
Copy link
Contributor

I like the metadata.xml format as-is. Revealing the source files is not an option. The filename normalisation requirement would be insane.

@Zverik
Copy link
Author

Zverik commented Apr 17, 2013

Why it's not an option to write source file names in xml file? The names of gpx files in the archive can remain numeric: it wouldn't matter if there's another source for that information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants