upload-scripts
upload-scripts copied to clipboard
kartaview
Upload tracks taken on Waylens cameras
Recently Telenav and OSM US made a partnership to give out cameras to OSM contributors. It would be nice if we could upload tracks from this partnership using a fully FLOSS stack. I can submit example layouts to be used for these scripts
Hey @gappleto97, we don't really have someone to work on that in the near future unfortunately. But to make sure we're on the same page, can you share the FLOSS examples you were thinking about? Not sure how that differs to the scripts on this repo ( I know Waylens is not currently supported, but not sure what FLOSS involves extra )
I meant the layout of things on the SD card. Directory structures, file types, etc.
FLOSS = Freely Licensed Open Source Software
File management is under Waylens firmware's control where we can't really do much ( it's being used by the non-OSC Waylens cameras as well )..
Is there any documentation about how data is structured in the .idx files? The images are just in a 1 FPS video stream and would be trivial to pull out using ffmpeg or similar. But the GPS info seems to be in the .idx files and it isn't in plain text and is mixed with syslog output as well.
@ToeBee I was able to get a parseable CSV by using Waylens Studio and selecting the "Export Raw Data" option:
This produces a CSV file like this: https://docs.google.com/spreadsheets/d/1AVzWMV3tckRaN-YqWxL5pVK7hZGBzQzsh3CHYLVn2wE/edit?usp=sharing
CSV columns:
- TimeSinceEpoch(s)
- PlayTime(s)
- Frame Index
- GPS Update
- Accuracy (hdop)
- Accuracy (vdop)
- Latitude
- Longitude
- Altitude (m)
- GPS Speed (MPH)
- Heading
- OBD Update
- RPM
- OBD Speed (MPH)
- Pressure from OBD(kPa)
- Throttle Position (%)
- Boost (inHg)
- Coolant Temperature (Celsius)
- Oil Temperature (Celsius)
- Telemetry Update
- Pitch (rad)
- Roll (rad)
- accX (G)
- accY (G)
- accZ (G)
- gyroX (Dps)
- gyroY (Dps)
- gyroZ (Dps)
- YAW (rad)
- Pressure from Telemetry(kPa)
And here are some rough notes I took the last time I attempted to sort this out -- looks like the last time I touched this was in July 2018. I ran out of time before I actually got it all tied together but this is probably a good starting point for others: https://gist.github.com/jalessio/6ccbc203fc80540c24b984600831b644
This workflow requires using the Waylens Studio GUI app at the beginning to produce the CSV, which is not ideal since it requires manual steps. It would be much better if one could parse the files directly from the SD card, but I didn't make any attempt at that.
We can easily make a script to parse this and generate exif data.
@bogdans-telenav per your comment on 2/14/19 is this something you're still willing to do? If you don't want to take it on yourself, I'll give it a try but in that case any pointers you can provide would be a great help in getting started. Thanks!
As there is a process that the waylens uploads the recordings to telenav servers, telenav should have the spec of the incoming files to parse and geo-ref them?
