A idea for the next update (if possible), when processing is displayed (right upper corner), is it possible to add a time estimate? Sometimes it takes al lot of time to process (I prefer first a process before uploading), and with a estimate counter it’s easier to plan around.
And a estimate timer for the upload would also be very nice.
De GoPro Max has sometimes GPS is too noisy, is it possible to extract only the parts of the video which are good?
@4004 I haven’t paid much attention to it. I use photos, not videos, with my GoPros. Is there a reason you do so?
I do it because it feels like I get better pics. And when I’m out hiking it uses a lot less battery.
Thank you.
I also use interval photos - it was @osmplus_org that is using video on Insta360.
Arguments for photos are better bandwidth, generally better compression, easier editing, battery life, storage
There are several good reasons why some people love the GoPro Max.
For example, the Insta 360 X3 forces you to use video mode so that it can produce usable GPX tracks. GoPro is much more flexible and is probably the better choice for long distances by bike. Everyone has their own special needs.
Hello. Using Mapillary Desktop Uploader 4.6.0 I uploaded several videos from a 70MAi A800S dash cam, each with an individual GPS file obtained from the text file GPSData000001.txt. For some reason the video date and time are incorrect. They do not correspond to the real one and are about 8 hours less than the upload time. Mapillary
Thanks for letting us know! Is your time zone or the time you uploaded the images 8 hours away from UTC (https://www.utctime.net/)?
No. My time differs from UTC by 3 hours. The question is that it should not be the download date/time that is indicated, but the shooting date/time. And the shooting took place in May-August 2024.
I can say for sure that when I uploaded a video using mapyllary_tools (this was discussed here Using the 70mai A810 Dashcam for Mapillary - #26 by matsumi), the shooting date was indicated and the video was embedded in the chronological list of previously uploaded sequences.
OK, looks like the date issue was fixed in mapillary_tools so it will be included in the next release of the desktop uploader, as well. I’ll make a new post when 4.7.0 is out.
Just looked at my latest uploads and the uploader cut the first 160 sec of gps data so it’s totally messed up. (I used the video mode)
Gpx Data extrated with exif tool:
Any idea how to fix it?
I’m currently working on a series of 360 degree shots on Sellrainstrasse (Kühtai ski area). Mapillary This involves large amounts of data. When uploading several recordings, it sometimes happens that the automatic upload of an image sequence breaks off due to a malfunction. Instead of skipping over already successfully uploaded recordings when restarting, the desktop uploader starts again with upload 1, which then often ends in an endless loop. It would be very helpful if the Deskop Uploader allowed parallel uploads with a queue instead of in a series. Failed uploads would then only affect the respective task.
@Magnet could you share the raw file where you are seeing this issue (maybe via a Google Drive link) for us to debug?
@nikola - are you able to replicate or work with @osmplus_org to get more info on this endless loop situation?
@osmplus_org Can you check the settings screen to make sure “Skip uploaded files” is turned on? If that does not help, please send us your logs at support@mapillary.zendesk.com
That’s probably the solution, thank you very much.
==This passage is controversial==
Erfahre mehr unter: Fragen und Antworten » Forencods I found that Mapillary Windows Desktop Uploader can handle videos with a maximum duration of 5 minutes, or a maximum size of 40 GB. If these limits are exceeded, this will result in an error message or a repeated restart of the upload. Reduce the size of the file.
==This passage is controversial==
@osmplus_org - 5 minutes should not be an issue, I think you should be able to upload as long videos as you want, but filesize limitations probably do exist. @nikola , could you confirm the file size limit?
I don’t think there’s a file size limit. @osmplus_org can you share your logs so we can debug further?
| nikola
February 21 |
- | - |
I don’t think there’s a file size limit. @osmplus_org can you share your logs so we can debug further?
(Attachment log.log is missing)
(Attachment log.old.log is missing)
I noticed that my 50 Mbit upload internet connection does not have a continuous upload data stream. I am therefore now testing the use of the VPN to Stockholm, Sweden. Initial results are promising, upload interruptions have decreased. The question is, what is the exact location of Mapillary servers for contributors in Europe?
When I send the corresponding log file by email, I receive an error message by email that this file format is not permitted.
I should probably paste the log files here in the forum. These are very long in terms of content.
I never have a continuous upload stream, it’s always a burst. I have a 1 Gbit fiber connection, most of the time the bursts are around 200 to 300 Mbit.
