Past week I uploaded several large sequences using the web interface. Now I see that only the first 999 images are published?
What happended to the hundreds of other images I uploaded?? There are no images waiting to process anymore in my account.
(My sequences contain mostly more than 2500 images each)
Have experienced the same problem with the web uploader in New Edge recently.
Had in previous weeks found that of be it 2500 or 4500 pics in a batch, only some 999 were shown on the world map, even if I waited for like four days.
In the early hours of 16 June uploaded four smaller batches, of 995, 990, 986 and 978 photos respectively; when returning to the web uploader in the morning found that the Publish button referred to only 957, 934, 911 and 887 pics to be uploaded.
Had a similar experience a few days earlier - at which time I believed it might be my mistake, didnât make note of date/time - where of 991, 956 and 774 pics only 692, 711 and 596 were to be published.
Similar for the Desktop uploaded, where several sequences havenât appeared yet, in spite of having been uploaded ten or more days ago and Status in the app states âCompleteâ - will go over that list later, and specify which uploads have so far failed to appear, which only appeared in part.
@Brenna, @asturksever : would you be able to bring this to the attention of whoever does clever things with the upload server, please, as there are ten of thousands of pics waiting on my end, and as my internet account only supports 295kB/sec with a 100GB/mo cap (volume between midnight and 10am counting as half), any opportunity missed is âwasted foreverâ âŠ
Met vriendelijke groet (Dutch for âwith friendly greetingâ),
You are right. Now I tried to upload partial sequences below 999 files, after the upload the system even âforgetsâ a couple of files at the beginning or end of that sequence. Very strange things are happening. New upload procedures with bugs?
Recently, Mapillary has started to check duplicated files in order to prevent duplicated files. All uploading tools check duplications and uploading session fails if at least one image is a duplicate. You will be getting notification email regarding this file so you can remove these files for uploading your files without duplication. As you might know, Web and Desktop Uploader uses mapillary_tools as "engineâ there this duplication rule applies for uploading methods.
I strongly recommend you to use the latest version of Desktop Uploader (1.2.7) which filters duplicated images and does not upload these images to Mapillary if you have doubt that you might have duplication in your uploading folder.
If you are keen on to use Web Uploader. Web Uploader works simply like below;
1- Browse images
2- Review images
3- Upload images
4- Publish images
If there will be any duplication among your files, this session will be failed, your images will be uploaded but not published on Mapillary. You will be notified by email if there is any duplication with the file name and image key.
There are two ways to handle this duplication issue.
1-Removing your duplicated file from Mapillary
You can delete duplicated files from Mapillary. Iâm aware this is workaround solution at the moment.
If you have " A server error occurred " Clicking Try Again can help you to publish your images unless there are no duplication in your uploaded files.
2-Removing your duplicated file from your upload.
This solution requires re-uploading all imagery one again without duplication.
Please let me know if this helps. If you think that your successfully uploaded your images but they are not published yet, please contact support@mapillary.com for further clarification.
Best,
Said
HiâŠI am absolutely sure I removed my duplicates [consecutive images within 6 meters] before uploading. So it does not explain the 999 upload âlimitâ and forgetting quite some images.
Maybe can you tell me what the âduplicateâ criteria settings of the upload engine are?
Btw. I never received any emails about specific files being a duplicate.
I have a similar problem: only the first 999 or 1000 files are uploaded. Even more, after uploading other sequences, since several days ago I received the following error when I try to upload other images:
Processing of your upload failed
Some of the images in your upload failed to process. This means your upload will not be processed further and will not be published. Please remove the following images that failed to process, and start a new upload without them:
and a list of files, from the number 1001 to the latest file. But I cannot delete any files in the upload, the only action button is âStart new uploadâ, which raises tghe same error window once and again.
Mapillary / Facebook tries to limit the upload of duplicates (which I can understand very well) but the implementation of it seems not very well right now.
E.g. I always remove my duplicates within 6 meters in driving direction using python before uploading. So I checked which files were skipped in one of my latest sequence uploads and they were images in the reverse direction on the same road. So did their algorithm labelled them âduplicateâ? Strange.
And now the web uploader does not work any more.
I dare not use the desktop uploader.
It is going down the drain.
web uploader does still work for me today, but there seem to be a lot of changes that have been applied to their uploader. But It works for me when:
and even then several images are removed automatically after uploading, not sure whyâŠ
I am stuck in a vicious circle.
âSome of the images in your upload failed to process. This means your upload will not be processed further and will not be published. Please remove the following images that failed to process, and start a new upload without them:â
They really want me to search 30 files among 999 files.
Have they gone out of their mind ?
It is time to fire some people at Mapillary.
Releases are untested, and make things worse.
What are duplicates ?
Sorry for the frustrations everyone. I know the current workflow to handle this is far from ideal. Weâre working to resolve this.
Having a system to handle duplicate uploads was very important for us to improve the quality of data on Mapillary, but the way it has been implemented needs work.
In the meantime, Iâm curious to get a sense of what are the reasons people prefer the Web Uploader over the Desktop Uploader. Apart from those on Linux who have to use the Web Uploader, are there other things about the Web Uploader that make it your uploader of choice?
I think you should make clear that the Desktop Uploaded is the preferred method for uploading. Last time I tried to use the web uploader, for no good reason, to be honest, and it was slow, until it failed. Then I used the Desktop Uploader and it worked fine. Maybe you could mention this in the web uploader interface.
Do you have a sequence where images have been removed so I can check?
When I started contributing images for use in perfecting OpenStreetMap, Mapillary was suggested as the best place; at the time there was the choice between a legacy uploader, the web uploader, and some - -was it perl or python?- tools which were beyond my knowledge to use.
At some point a desktop uploader was mentioned in forum posts, tried (was it version 1.9.n?) which took very long (couple of hours) to prepare say 4400 images for upload, with no discernible gain in upload speed / reduction in time needed to upload, and in addition it created one folder per image with in each folder something like 23 files charting progress : deleting the 100.000 or so files from a 4400 pic upload takes yonks - irrespective whether the computer deletes 100 or 300 files per second.
= = =
Tried v 1.2.4, where I found that some sequences just didnât appear on the map - not even after like 3 or 4 days.
Found similar for the web uploader : in both instances like 999 or 1499 pics out of be it 2500 or 4400 were on display after three days.
Now diverge from desktop vs web uploader to duplicate removal : took the time to find the last pic in a batch which appeared on the map, then re-uploaded the remainder - there may well have been a duplicate at the junction between shown, and not shown on map. As long as it concerns a couple of pics overlap : just delete those : theyâre not malignant, are they?
And if I wanted to inflate the number of pics : upload the daily ride to the shops - different shop each day - would be far more effective.
Have couple of days ago sent a mail to support, c/o Saïd, with a number of incomplete sequences; some of these have now appeared, others seem lost forever.
Hope this helps? If not : ask!
Dear Peter,
Sent a mail, detailing a number of mislaid sequences to support@mapillary on Date: Sun, 21 Jun 2020 17:19:09 +0200 ; would be happy to copy+paste the list here?
= = =
Copy+paste from mail mentioned above :
= = =
Dear Support (frequently Dear Saïd),
Mentioned in a reply to a forum post on Saturday that parts of some series of uploaded photos were missing, and promised to look into this and compile a list at some point. Herewith a list of batches of photos uploaded over the past weeks; the date is the date the photos were taken.
This message was researched and written on the Saturday evening, held back to read again the next day, check for inconsistencies; have now seen Saïdâs message to Micmin and myself, not amended this message as I will respond to that separately.
Mapillary Desktop uploader
2020-04-15 - looks complete
2020-05-02 : more missing, but looks like uploaded via Web-browser uploader (as I canât see the . mapillary folder) : Mapillary does show from the start of the batch in my folder at 16:01 till 16:21 , and 16:51 - 16:57 ; thus missing 16:21 till 16:51 - south of the river Rupel, extends till east of the river Zenne, where there is a new flood control âpolderâ.
2020-05-02 : the 4424 item return journey along the Schelde river from 17:00 till 18:54 was uploaded according to the log files in the .mapillary folder, but only the 17:18 till 17:27 pics are shown on the green dots/line : any news on the remainder, please? Desktop Uploader shows the batch as Complete âŠ
2020-05-07 - incomplete : Desktop Uploader shows two batches, 3575 and 2522 pics = 6097 , while my folder contains 6843 ; Uploaded status = complete, gap in Mâs green dots/line between 17:52 and 18:00 - missing some 450 pics, [hence more must be missing (correct, had the GoPro running while waiting at the level crossing, from 18:21 till 18:26 = approx. 300 removed as you could barely see the grass grow ⊠)]
2020-05-09 - looks complete ; three batches : 606, 2350 and 5325 hero 2018 pics, canât see the TG5 single shots ??
2020-05-14 - looks complete ; 830 + 6434 pics, canât see the TG5 single shots ??
2020-05-16 - looks complete ; sequence cut has (fortunately!!) overlooked the TG5 single shots - still kilometres of connecting lines, but may be the only way for OSM mappers to find those âŠ
2020-05-30 - looks complete ; two batches : 3847 + 3805 hero 2018 pics, canât see the TG5 single shots ??
2020-06-01 - begin to see where things fall down : the single shots with the TG5 will have the same date/time and lat/lon values, as theyâre geotagged from the same Garmin etrex10 track-log- which is the most accurate I can get; take 2020-06-01 10-37-49 : in the Hero 2018 batch it shows just a narrow tarmac strip with a wide sand verge ahead, while in the TG5 batch it shows a sideways shot of a forest track, fence and gate.
OK. seem to have put a finger on the âlostâ TG5 pics on stretches of roads where Iâve taken single shots of particular details along or to the side of the road while the Hero was also running and either looking straight ahead or also pointed towards the same subject? Or did I?
2020-06-04 - here we have both the single pics connected by kilometres of lines (@sequence cut? actually, those lines may be the only way for OSM-mappers to find the TG5 pics!!) - does that disprove âŠ
Thatâs the end of the entries from the Desktop Uploader History page checked; now on to the various SD-cards and USB-sticks which I used to upload pics from a very energy efficient Pentium Silver 2-in-1 flip-book:
Mapillary Web-based Uploader
2020-04-18 : âbruyns gedaanâ : part visible, part not to be seen on mapillaryâs green lines/dots yet ; have split that into âpart doneâ and â2doâ. visible 15:27 - 15:44 then resumes at 16:24 - 16:41 ; there also are pics 15:44 till 15:51 and 16:02 - 16:07 which show ânewâ streets , the uphill struggle 16:07 till 16:11 barely adds to the sequence taken a couple of days earlier - different weather, thatâs all in retrospect - 16:15 - 16:19 is a different path, looks easy to cycle down to start with, then narrows and gets steeper, thus needs to be marked on OSM as unsuitable for general cycling , the rest 16:19 till 16:24 again largely the same as before apart from weather.
2020-04-18 bruyns paepe 2do : 16:41 - 16:44 is new , as is 16:54 - 16:57 which looks in more detail at the new development (the footpaths to the communal entrances are shown as service roads on OSM, but theyâre not ; there is a local OSM mapper in that area, so these may be superfluous) ; from 17:21 you get a back street, a new cycle path, and a road which was public but where part has now become private / no access. that series continues till it meets up with the beginning at 17:47, and it isnât clear why it isnât shown?
2020-04-19 : Mapillary shows 16:03 till 16:20 , but full batch was till 17:37 : what happened to the rest, please?
2020-04-26 : looks complete
2020-04-30 - starts at 14:54 and continues to 15:49 ,
2020-06-06 Zoersel hero 2018 : visible from start of batch till 12:33 , and from 12:43 : bit in between is also now a new âfietsstraatâ, despite having been photographed some weeks earlier, when it wasnât yet. [NOTE : this concerns the eastern part of the Kasteellei in Wijnegem, south of the Albertcanal]
2020-06-06 Zoersel TG5 : visible on Mapillary till 14:28 , then from 18:27 onwards (final pic shows how people thought about safety over the centuries : initially, a Holy Mother statue at the corner, then a little light over it, and now a 24/7 dome camera); the pics in the nature reserve may not show all that many traffic signs, but do contain images (for example of the circular wall around the pond, and of the âshelterâ which can help OSM, while the other pics do at the least show ânothing to see hereâ?
2020-06-12 Zoersel Halle : both the Hero 2018 and TG5 batches look complete
2020-06-14 : so far only uploaded four batches, each just under 1000 pics : 200614 5p1, 5p2, 5p3 and h01 with 995, 990, 986 and 988 pics, of which 957, 934, 911 and 887 were published (as stated on the âpublish nnn imagesâ screen) : what happened to the rest, please? Were the last ones omitted or , ? Yes, they were, missing from 12:17 till 12:22 , 14:22 till 14:36 and 17:32 - 18:04 in the TG5 series, and from 12:10 for the first Hero 2018 series - thus missing a new Fietsstraat (cycle street) behind the schools.
Couldâve thought of nicer ways to spend the Saturday evening, but these missing uploads are irksome, and forum posts by e.g. micmin and filip/philippe show that Iâm not the only one experiencing this problem, thus hope that by specifying the series of missing pics, and the approximate times (mapillary only shows the minutes, not the seconds for each pic) âthe support teamâ can put a finger on what causes the missing pics in some of the batches.
With as ever âVriendelijke groetâ, (Dutch for '; with friendly greeting),
First, how do I know the version of Desktop Uploader?
â
Around June 21, I intended to use the Desktop Uploader to upload 44 photos. There are no duplicates.
All photos are visible from the links below.
However, even a few days later, when I look at Map on Mapillary (Mapillary), even if I look at Feed and Uploads, the corresponding data does not exist.
I always delete the â.mapillaryâ folder, which is a group of log files, immediately because the disk system load is high.
So even after checking the photo folder after the fact, I wasnât sure if it was uploaded.
Therefore, I uploaded again those on 6/25.
I uploaded and âCompleteâ was indicated by Desktop Uploader, but again, the corresponding photo does not appear in the map, Feed, or Uploads.
After that, I received an email titled âMapillary images or videos you tried to import failedâ.
There was a description such as âduplicate image file(s) detected,â in the contents.
After that, I discovered the existence of this discussion on the bulletin board.
â
If I didnât upload it on 6/21, I donât know the reason for the failure indicated by âMapillary images or videos you tried to import failedâ.
Or if I was uploading on 6/21, I donât know why there isnât a corresponding photo on the map, Feed or Uploads.
In any case, I can be confident that this new feature is implemented incorrectly.
Iâm not going to follow the detailed steps of deleting each one and doing the upload operation again. The â.mapillaryâ folder has been deleted, so I think it is impossible to execute it.
I give up these data.
The same photo uploaded to Google Street View is fine, so itâs ok. (Google ããã)
I want to go to the next fun place early and shoot.
â
The attached photo is a screenshot of the âmapillary_import_summary.jsonâ file that I forgot to delete after the upload operation on June 25.
As you have attached, 44 photos have been uploaded.
If you look at âmapillary_import_summary.jsonâ, you will see 44 successes except for the step âimport_meta_processâ.
The â.mapillaryâ folder has been deleted, so the contents cannot be examined.
Using the desktop uploader files have failed to upload for two different reasons for me:
exiftool -thumbnailimage= IMG_nnn.jpg) to remove the offending thumbs the pictures get uploaded without problem.The latter happens to ~1-5% of my pictures varying by batch. Maybe this is also the cause of your lost pictures.
Mapillaryã«æ°ããªéè€ãã§ãã¯ãå°å
¥ãããŸããã
ã¢ããããŒãåŸãWebå
¬éããããŸã§ã®ã¹ãããã«å°å
¥ãããæ©èœã§ããããã§ãã
æ°èŠã«ã¢ããããŒãããç»åã«ã®ã¿é©çšãããŠããŸãã
æ¢ã«Webå
¬éãããŠãããã®ã«ã¯åœ±é¿ããªãããã§ãã
ãã®ããµãŒããŒåŽã§ã®ãå³ããéè€ãã§ãã¯ããšã¯ãã»ãã·ã§ã³å ã«ç»åã®éè€ããããšå€æããå Žåã«ã¯ããã®ã»ãã·ã§ã³å šãŠã®åçãWebéå ¬éã®ãŸãŸã§ä¿çããããšããæªçœ®ã§ãã
ã»ãã·ã§ã³ãšã¯ãä»ãŸã§ç§ãã·ãŒã±ã³ã¹ãšåŒãã§ãããã®ãšã»ãŒå矩ã®ããã§ãã
ãã ããã·ãŒã±ã³ã¹ã1000æãè¶
ããå Žåã«ã¯ã1000æçšåºŠããšã«åæãããã®ã1ã€ã®ã»ãã·ã§ã³ãšããŠæ±ã£ãŠããããã§ãã
ãã®å€å®ã¯ãã¢ããããŒãã®æäœããã¹ãŠå®äºããåŸã«è¡ããããã®ã§ãã
ææ°ããŒãžã§ã³ã® Desktop Uploader (1.2.7) ã§ã¯ããµãŒããŒåŽã§ã®ãå³ããéè€ãã§ãã¯ããšåçã®éè€ãã§ãã¯ãè¡ãããŠã
éè€ãšå€æãããç»åãé€ããã»ãã·ã§ã³ãšããŠã¢ããããŒããããããã§ãã
ã§ããããææ°ããŒãžã§ã³ã® Desktop Uploader ã䜿çšããã°ãã»ãã·ã§ã³ãäžžããšWebé衚瀺ã«ãªã£ãŠããŸã被害ã«ã¯éããªãã®ã ãšæããŸãã
ããããDesktop Uploader ã®ããŒãžã§ã³ãç¥ãæ¹æ³ãç§ã«ã¯ãããŸãããçŸåšã質åäžã§ãã
6/24é ã«PCã§ãDesktop Uploaderã®ææ°ããŒãžã§ã³ã䜿çšå¯èœã§ãããšãããããã¢ãããèŠãããšããããªãããšããèšæ¶ãããããŸããã
ãŸããWeb Uploader ã«ã¯éè€æé€ã®æ©èœã¯ãŸã åãã£ãŠããªãããã§ãã
ç§ã¯ããã¯äœ¿çšããŠããªããããasturkseverãæçš¿ãã以äžã®ã³ã¡ã³ããèªãã ãšããã«ãããšã
éè€ããç»åãæé€ããäžã§å床ã»ãã·ã§ã³ã®å
šç»åã®ã¢ããããŒãåŠçãè¡ãããšã§ãã¢ããããŒãåºæ¥ãããã§ãã
以äžã«asturkseverãæžããŠããããšãå
šãæ£ããã®ã ãšæããŸãã
http://mapillary.trydiscourse.com/t/web-uploads-not-arrived-cut-at-999-images/4165/4?u=potaro67v
ç§ã¯ãasturkseverããã¯Mapillaryã®äžã®äººã ãšã°ããæã£ãŠããã®ã§ãããããããããããããã¬ãã«ã®ãŠãŒã¶ãŒãªã®ã§ããããïŒïŒïŒ
ããããDesktop Uploader ã®ããŒãžã§ã³ã(1.2.7)ã§ããããšã®ç¢ºèªæ¹æ³ãç§ã«ã¯èŠã€ãããªãã®ã§ããã®ç¢ºèªæ¹æ³ã質åããŸããã
http://mapillary.trydiscourse.com/t/web-uploads-not-arrived-cut-at-999-images/4165/17?u=potaro67v
ãããã18æéçµã£ãçŸåšããŸã åçã¯ãããŸããã
ãã®ã³ã¡ã³ãã§ç§ã觊ããŠãããã©ãã«äŸã¯ã2mééã§æ®åœ±ããéæ¢ç»44æã§æ§æãããŠããã»ãã·ã§ã³ã§ãã
Google Street Viewãžã®ã¢ããããŒããæ£åžžã«ã§ããŠããããšã¯ãã³ã¡ã³ãäžã«ç€ºãããšããã§ãã
äœçœ®æ
å ±ã44æãšããã¹ãŠç°ãªã£ãŠããŸãã( = Exifæ
å ±ããã¹ãŠã®ç»åã§ç°ãªã£ãŠããããšããããšã§ã)
ãã®ãããªã»ãã·ã§ã³å
šäœããšã©ãŒãšããŠWebé衚瀺ã«ããŠããŸããšããããšã¯ãçŸåšã®
ãµãŒããŒåŽã§ã®ãå³ããéè€ãã§ãã¯ã
ããæããã«ééã£ãå€æãããŠããããšã瀺ããŠããŸãã
ãã®ãããªãéè€ãååšããŠããªããã»ãã·ã§ã³(ã·ãŒã±ã³ã¹)ããšã©ãŒã«ãªã件ã¯ãasturkseverã®ã³ã¡ã³ãäžã§ã¯æ³å®ããŠããŸããã
ãŸããäžèšã®æ²ç€ºæ¿ã§ã®ä»ã®ãŠãŒã¶ãŒã®åãã«ããéè€ãååšããªãã®ã«ã»ãã·ã§ã³äžžããšWebé衚瀺ãšãã被害ã«éã£ãŠããæ¹ãå€ãã®ã ãšæããŸãã
æ®å¿µãªããšã§ãã
ââ
ããŠãDesktop Uploader (1.2.7)(ãã¶ã)ã§ã®éè€ãã§ãã¯ã®æ©èœããã§ãã¯ããŸãã
ãã¹ããè¡ã£ãçµæãããç§ã¯çŸåšã®åŠçå
容ã«ã€ããŠä»¥äžã®ãããªæšæž¬ãããŸããã
â éè€ã®å€å®ã¯ãEXIFæ å ±ã®ã¿ã§è¡ã£ãŠãã(ç»åã®å 容ã¯èŠãŠããªã)
ãã®æšæž¬çµæã¯ãç§ãçŸåšç¬èªã«è¡ã£ãŠããåç»åŠçïœã¢ããããŒãã®äœæ¥ã«ã¯åœ±é¿ããªããšããããšã瀺ããŠããŸãã
åãããå€ãã®Desktop Uploader å©çšè
ãå®æ³°ã§ãã
ç§ã¯ãã®çµæã«æºè¶³ã§ãããŸãä»æ§å€æŽãããããšããããŸããããã«ã
ãã®åæã¯ãDesktop Uploader ãéåžžã®æ¹æ³ã§äœ¿çšããå Žåã«ã¯ããããééããã»ãã·ã§ã³ã¯ãµãŒããŒã§Webé衚瀺ã®æªçœ®ããªãããããšã¯ãªãããšãããã®ã§ãã
ã€ãŸãããµãŒããŒãããDesktop Uploaderã®ã»ããå€å®åºæºãå³ãããããŸãã¯åäžã§ããããšãåæã§ãã
ããã§ã¯ãªãå Žåã«ã¯ãäžæ¬æã«ã»ãã·ã§ã³äžžããšWebé衚瀺ã«ãªã£ãŠããŸã被害è
ãé »çºããããšã«ãªããŸãã
ç§ã¯å¯ŸåŠã§ãããã©ãäžè¬ã®æ¹ã
ã被害ãåãããšå¯åæ³ã§ãã
ãã¹ãçšã®ç»åã¯ãã®ããã«ããŠæºåããŸããã
ããŠããã¹ããå§ããŸãã
â01.(5æ) ããŒãã«
1f-5f
Publish Completed
æå»è¡šèšã¯è€æ°æã§åäžã§ã(4.91fpsã®ãã)ãããããã¹ãŠã®åçãã¢ããããŒãåºæ¥ãŸããã
äœçœ®æ
å ±ã¯ãé£æ¥ããåçã§ã¯ã»ãã®10cmçšåºŠã®å·®ã§äžŠãã§ããŸãã
â02.(6æ) éãç»åã§EXIFæ
å ±ãåããã®
6f-11f
1æããã¢ããããŒããããŸããã§ããã(6fã®ã¿)
ãã®çµæãããéè€ã¯EXIFã§å€æããŠãããã®ãšæšæž¬ã§ããã
Desktop Uploaderæäœã®ã¹ã¯ãªãŒã³ãã£ãã㣠: bandicam 2020-06-27 01-16-59-885 - YouTube
â03.(7æ) æ¢ã«ã¢ããããŒãæžã¿ã®ãã®ãšäžéšéè€ãããã®
1f-5f,12f,13f
Desktop Uploaderã¯ãç»åãã¡ã€ã«ã®ãã©ã«ãåãããã®ã¢ããªå
ã§èšé²ããŠãããšèããããŸãã
ãã®ãããåäžãã©ã«ã(ãã¹)ããã®è€æ°åã®ã¢ããããŒãã¯ãåŠçããã«ãšã©ãŒãè¿ããŸãã
ãããããã©ã«ãå(ãã¹å)ãç°ãªãã°å¥ã®ãã®ãšããŠæ±ã£ãŠãããŸãã
ãŸããDesktop Uploaderå
ã§ã®éè€ãã§ãã¯ã¯PCã®ã¿ã§ã®å€æã§ãããMapillaryãµãŒããŒã«ã¢ããããŒãæžã®ç»åãšã®ãã§ãã¯ã¯è¡ãããŠããªãããã§ãã
ãã®ãããã¢ããããŒãåã«éè€ãã¡ã€ã«ãã«ãããããããšã¯ãªãã7ç»åãã¹ãŠãã¢ããããŒããããŸããã
Desktop Uploaderæäœã®ã¹ã¯ãªãŒã³ãã£ãã㣠: bandicam 2020-06-27 05-54-57-468 - YouTube
ãããŠããµãŒããŒã§ã®ãã§ãã¯ã«ããéè€ãçºèŠããããšã®ãšã©ãŒã¡ãŒã«ãå±ããŸããã
ãšã©ãŒã¡ãŒã« : Dropbox - File Deleted
ãã®ã»ãã·ã§ã³ã¯ã7æå
šãŠãWebé衚瀺ã§ãã
Dropbox - File Deleted
â04.(2æ) éè€ãé€ããŠããåäžãã©ã«ãã䜿çšããŠå床ã¢ããããŒã
12f,13f
(1f-5fãäžæŠéé¿ããŠã03ã®ãã¹ããšåäžãã©ã«ãããã¢ããããŒãããŸããããã°ã¯ãã®ãŸãŸã«ããŠãããŸã)
Desktop Uploaderæäœã®ã¹ã¯ãªãŒã³ãã£ãã㣠: bandicam 2020-06-27 06-15-59-832 - YouTube
ãFolder already uploadedãã®ãšã©ãŒã«ãªããŸãã
(ãã®åŸãäžæŠéé¿ãã 1f-5fãå
ã«æ»ããŸãã)
ãã®ãããªãšã©ãŒã«ãªã£ãå Žåã«ã¯ããéè€ãããã¡ã€ã«ãåé€ããŠããå床ã¢ããããŒãããããšãããWeb Uploader ã®ãããªååŠçæ¹æ³ã¯åºæ¥ãªããšããããšã§ãã
â05.(2æ) Webé衚瀺ã®æ¢ã«ã¢ããããŒãæžã¿ã®ãã®ãšäžéšéè€ãããã®
12f,13f
ãã¹ã03ã§ã¢ããããŒãæžã§ãããWebé衚瀺ã«ãªã£ãŠãã2ç»åã䜿çšããŸãã
Desktop Uploaderã®æäœã¯å®äºããŸããã
Desktop Uploaderæäœã®ã¹ã¯ãªãŒã³ãã£ãã㣠: bandicam 2020-06-27 06-25-09-304 - YouTube
Dropbox - File Deleted
Mapillary
â06.(8æ) åäžã®ç»åã§ãEXIFã®ã¿ç°ãªããã®(åäžæå»ã®ç»åã¯ãã)
14f-21f
ãã ããç»åã¯14fã®ãã®ãå
šãŠã«ã³ããŒãã14f-21fã®EXIFã¯ãã®ãŸãŸäœ¿çšããã
Desktop Uploaderã®æäœã¯å®äºããŸããã
Desktop Uploaderæäœã®ã¹ã¯ãªãŒã³ãã£ãã㣠: bandicam 2020-06-27 06-52-24-077 - YouTube
Dropbox - File Deleted
Mapillary
(åãç»åã§ãäœçœ®æ
å ±éãã®8æã§ã)
ä»æ¥ã®ãã¹ãã¯ãããŸã§ã
ãã®ä»æ§ãå€åãªããªãã°ãç§ã®çŸåšã®äœæ¥ã«ã¯ãªãã®é害ã«ããªããŸããã
ããäžé±éã®ãã©ãã«ã移è¡æã®äžæçãªãã®ã§ããããšãæåŸ
ããŸãã
ãã®èŠ³ç¹ãšãã¹ãå
容ãšãããã«å
¬éããŠããŸã£ãããã§ããããç¹ã«ãã¹ã06ã«ã€ããŠã¯Mapillaryããã¯ããé¡ãããªããããããŸãããã
ããããããç§ã«ãšã£ãŠã¯å€§äºãªããšãªã®ã§ãã
åç»ã3åæ¯ã«åå²ããªããé·æéåºæ¥ãä»çµã¿ããç§ã¯æã£ãŠããŸãã
ãã®åå²æã«å
ããªæéã®ééãåºæ¥ãŸãããã®ééããããŒãã¬ãŒã (åäžã®ç»åã䜿çšããããç¡ãã§ããã)ã§åããããšãèªããŠãããããšãåŠçå¹çãé«ããªãã®ã§ãã
以äžãã¬ããŒãçµããã
I would like to introduce my first mass upload work (using a desktop uploader) after the introduction of a new strict duplicate check in Mapillary by last week.
There is no change in the operation method with the desktop uploader so far.
In addition, the trouble that causes various troubles for every 500 sheets is still occurring.
å é±ãMapillaryã«æ°ããªå³éãªéè€ãã§ãã¯ãå°å ¥ãããåŸã®ãç§ã®æåã®å€§éã¢ããããŒãäœæ¥(ãã¹ã¯ãããã¢ããããŒããŒäœ¿çš)ãã玹ä»ããŸãã
ä»ãŸã§ã®ãã¹ã¯ãããã¢ããããŒããŒãšãæäœæ¹æ³ã¯å€æŽãããŸããã
ãŸãã500æå»ã¿ã§æ§ã
ãªãã©ãã«ãçºçãããšããé害ã®ååšã«ãå€åã¯ãããŸããã
ãããŠãåãEXIFæ
å ±ãæã€ç»åãã«ãããããŠããŸãããšããåäœãã以åãšã®éãã¯ãããŸããããã®æ©èœã¯ä»¥åããã€ã³ããªã¡ã³ããããŠããŸããã
ãã¹ã¯ãããã¢ããããŒããŒã䜿çšããŠãäœçœ®æ
å ±ãä»å ãã2983æã®éæ¢ç»ãã¢ããããŒãããäŸã瀺ããŸãã
ãã¹ã¯ãããã¢ããããŒããŒã®ããŒãžã§ã³ãç¥ãããã®ã§ãããç§ã«ã¯ããã調ã¹ãæ¹æ³ããããŸããã
ãã¹ã¯ãããã¢ããããŒããŒã䜿çšããããšãããšãã«ãææ°çãååšããŸãããšããã¡ãã»ãŒãžãèŠãèšæ¶ããããŸãããå
·äœçã«ã¯ã©ã®ããã«ã¢ããããŒããããã®ããç§ã«ã¯ããããŸããã
ã§ã¯ãã¢ããããŒãæã®ã¹ã¯ãªãŒã³ãã£ããã£ã瀺ããŸããéå±ãªåç»ã§ãã®ã§ãæå»ããšã®èŠç¹ãå ã«æžããŠãããŸãã
00â04" ã¢ããããŒãåŠçéå§ããŸãã¯äºåã®æºåã«ããªãæéãæãããŸãã
05â08" ãµãŒããŒãžã®è»¢ééå§ãã¢ããããŒãé床ãé
ãã§ãã
31â31" 500æãç®åã«ããŠãã¢ããããŒããæ¢ãŸããŸãã
50â20" äœåãã¢ããããŒããã£ã³ã»ã«ãããŠããå床ã¢ããããŒããéå§ããããšã«ãã£ãŠãå
ã«é²ãããšãåºæ¥ãŸãã
1:05â30" ãã£ãšãæ¬æ¥ã®ã¢ããããŒãé床ã«éããŸãããããããç§ã®ãããã¯ãŒã¯ã®èœåãã£ã±ãã§ã¯ãããŸãããMapillaryåŽã®åãå
¥ããé
ãã ãã§ãã
1:06â10" 1000æã§ã
1:12â20" 1500æã§ãããªã«ããµãŒããŒåŽã§ããŒã¿åãå
¥ããèºèºããŠããããšãæ³åã§ããŸãã
1:18â43" 2000æã§ãã
1:25â00" ããã2500æã¯äœäºããªãééããŸããã
1:29â05" ã¢ããããŒãå®äºããŸããã
ã¢ããããŒãããçµæã® Street-level Imagery ã¯ä»¥äžã®ããã«ãªããŸããã
以åã®ã³ã¡ã³ã( http://mapillary.trydiscourse.com/t/web-uploads-not-arrived-cut-at-999-images/4165/19?u=potaro67v ) ã®ããã¹ãâ06ãã§ç¢ºèªãããã£ãã®ã¯ã以äžã®URLããå§ãŸã30ãã¬ãŒã ã®ãããªãåç»ã®èªååå²ã«ããã®ã£ãããåããç§ç¬èªã®åŠçãžã®å¯ŸåŠã§ããã
https://www.mapillary.com/map/im/fnyhu94bjnE87ErqqOna6U
çŸåšã®ãå³éãªéè€ãã§ãã¯ãã§ããç¡äºã«ãç§ãæã£ãéãã® Street-level Imagery ãäœæãããŠããŸããå®å¿ããŸããã
ãã®ããã«ãMapillaryã·ã¹ãã ã¯ãæ¢åã®ç°åžžã®ååšãå«ããŠä»ãŸã§ãšåãåäœãããŠãããšç§ã¯èããŠããŸãã
ããããæ°ããªå³éãªéè€ãã§ãã¯ã®å°å
¥äœæ¥ãè¡ãããŠããæéã§ããæ°æ¥éã«ã¯ãMapillaryã®ã¢ããããŒãã·ã¹ãã å
šäœ(ç¹ã«ãµãŒããŒåŽ)ã®åäœã«ã¯ç°åžžãååšããŠãããšæããŸãã
åãæ¹æ³ã§ã¢ããããŒãããã·ãŒã±ã³ã¹ãéè€ãšã©ãŒã«ãªããŸããã
以åã®ã³ã¡ã³ã ( http://mapillary.trydiscourse.com/t/web-uploads-not-arrived-cut-at-999-images/4165/17?u=potaro67v )ã§ã觊ããŠããéãã以äžã®ãããªã¡ãŒã«ãå±ããWebã«ã¯æªã ã«å
¬éãããŠããŸããã
I received an email titled âMapillary images or videos you tried to import failedâ.
There was a description such as âduplicate image file(s) detected,â in the contents.
ãã¹ã¯ãããã¢ããããŒããŒã§ã¢ããããŒããããããŒã¿ã¯ãä»åã€ã³ããªã¡ã³ãããããå³éãªéè€ãã§ãã¯ãã§ãšã©ãŒã«ãªãããšã¯ãªãã¯ãã§ãããšç§ã¯èããŠããŸãã
ããããç§ã¯ãéè€ãšã©ãŒãšå€æãããŠWebå
¬éãä¿çãããŠããããŒã¿ãæã£ãŠããŸãã
ä»ã®ãŠãŒã¶ãŒã«ãåœç¶ãåæ§ã®é害ãçºçããŠãããšæãããŸãã
ãã°ãã¡ã€ã«ã¯ãç§ã®ããªã·ãŒã«ããããã¢ããããŒããå®äºãããåé€ãããããšã«ããŠããŸãã®ã§ããã°ã®ç¢ºèªã¯ç§ã®æå
ã§ã¯äžå¯èœã§ãã
ãããMapillary瀟å¡ã®æ¹ããã®ç°åžžã«èå³ãæã£ãŠããããªãã°ããµãŒããŒå
ã§ã®ç§ã®ããŒã¿ãçŽæ¥èª¿ã¹ãŠãã ããã
ç§èªèº«ããªã«ãäœæ¥ãè¡ã£ãŠããã®ç»åã®åã¢ããããŒããªã©ã®å¯ŸåŠãããäºå®ã¯ãããŸãããããšããšãããã®ããŒã¿ã«ã¯éè€ãšå€æãããèŠçŽ ã¯ååšããŠããŸããã
ç§ã®ä»¥åã®ã³ã¡ã³ãã« dropboxã®ãªã³ã¯ãèŒããŠãããç§ãã¢ããããŒãããåç(ãããŠãWebå
¬éãä¿çãããŠããåç)ã¯ãããã確èªã§ããŸãã
ä»åã®æ°æ©èœã€ã³ããªã¡ã³ãã®ããã®éæž¡æã®æéã¯ãããªã«é·ããªãã¯ãã§ãã
ãã®æéã«çºçããå
šãšã©ãŒ(ãããŠãWebã«å
¬éããªããšããæªçœ®ããããŠããããŒã¿)ã«ã€ããŠããµãŒããŒåŽã§èŠçŽããè¡ãããšããç§ã¯ææ¡ããŸãã
æåŸã®éšåã®ã¿ãè±èš³ããŠä»å ããŸãã
In this way, I believe that the Mapillary system behaves the same as before, including the presence of existing anomalies.
However, I think that the operation of the entire Mapillary upload system (especially the server-side) was abnormal during the several days during which the new strict duplicate check was being introduced.
A sequence uploaded in the same way resulted in a duplicate error.
As mentioned in the previous comment (http://mapillary.trydiscourse.com/t/web-uploads-not-arrived-cut-at-999-images/4165/17?u=potaro67v ), as below, I received an email and it is not published on the Web yet.
I received an email titled âMapillary images or videos you tried to import failedâ.
There was a description such as âduplicate image file(s) detected,â in the contents.
I believe that the data uploaded by the desktop uploader should not fail with the âstrict duplicate checkâ that implemented this time.
However, I have data that has been placed on NO web publishing due to a duplicate error.
Of course, other users were likely to have similar failures.
By my policy, the log files are âdeleted when the upload is completed because the amount of log files is hugeâ, so it is impossible for me to check the log file.
If a Mapillary engineer would be interested in this anomaly, please look directly at my data on the server.
I have no plans to do anything to re-upload these images. Originally, there was no element judged to be duplicate in these data.
Iâve included a dropbox link in my previous comment, and you can see the photos I uploaded (and photos pending web publishing).
The transition period for implementing this new feature should not be that long.
I suggest doing a server-side review of all errors (and any data that youâre prepared not to publish on the web) that occurred during that period.
