I think it is “Data and Time (original)”. ![]() Yes the first processing step after ffmpeg extracting images is to write a time/date EXIF tag. Your post here though does look like the pre dashes are malformed so could be worth another try. I don’t have the code installed here so I cant check the syntax or help. That may introduce an error that can be hard over-ridden by “video_start_time”. "MAPPhotoUUID": As I vaguely remember “use_gps_start_time” is about using the gps data start in lieu of the filename being the date/time. Does anyone if I’m missing something in my code that would fix that? , When I run the code all the date gets packed into the EXIF tag imageDescription instead of their respective tags. My issue now is that Mapillary won’t accept the photos, since they are missing EXIF data about capture time and the GPS data is not stored correctly? I would have uploaded a screenshot, but that doesn’t seem to be possible in this forum. mapillary_tools video_process -import_path "images/" \ I couldn’t get it to work, so I went with -use_gps_start_time. One of the changes I made was removing -video_start_time. I made some adjustment to the code above, which did give me geotagged photos from my GoPro. Just uninstalled it and reinstalled it -duh, silly me. Update: I got the script to work after I installed some xcode package. My command looks like this: mapillary_tools video_process -import_path "images/" \ Mapillary import tool: error: argument tool: invalid choice: ‘video_process’ (choose from ‘process’, ‘upload’, ‘process_and_upload’)ĭoesn’t seem like mapillary has the “video_process” command anymore? Usage: see -h for available tools and corresponding arguments, add -advanced to see additional advanced tools and/or arguments and -version to see version. So I’m getting this error when I try to use the command: I havent run this command myself since the older python version. There may be multiple videos rather than one and they may not be seamless. There is a gopro option in the tools (README.md) that I would assume reads its own gps data. Keep in mind that I do not know GoPro and/or its 360 format. eg load various images into Viking to make sure they match OSM features positions. I suggest trying the process (only) step so you can ascertain it has all worked prior to upload. If you are having start date/time extraction problems, pointing the camera at an accurate (to seconds) clock at the start will give a reference for manual entry. There are various online calculators around if needed. Xxxxxxx is the date/time in epoch notation (seconds since midnight ). –user_name “mapillary_username” -advanced Mapillary_tools video_process -import_path “path/to/images” ![]() Looking at the README.md here GitHub - mapillary/mapillary_tools: Command line tools for processing and uploading Mapillary imagery If you have multiple video files, you can automate them by writing a script. Python mapillary_tools upload -import_path $video_directory Python mapillary_tools process -import_path $video_directory -user_name $user_name -advanced -geotag_source gpx -geotag_source_path $gpxfile -rerun -sub_second_interval $sample_interval You will only be prompted for your mapillary ID and password the first time you run it. Python mapillary_tools sample_video -video_import_path $video_file -video_sample_interval $sample_interval -video_start_time $millisec_utc -advancedĪdd location information etc. Mapillary_tools, which runs on Python, allows you to process videos, add location information, and upload them.Įxtract a still image from the video with the following command. ![]() I also took a video while driving in a car and uploaded it to mapillary.įirst of all, you need a GPX format log that records your driving position.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |