Hi,
I wanted to try out the new DJI workflow, but there are two peculiar things that prevent it from working:
1) Step 2 just gets skipped over with a checkmark next to it and step 3 open to work on. I can go back to step 2, but why does it skip over it? Also, it cannot show me the points required for the job, because it does not know at this point how many files I want to process.
2) When I get to step 4 to upload images, and I click on the underlined text to do so, it sort of flashes the box below, but does not present a file selection dialog. No way to tell it what files I want to upload.
Is this a Mac problem? I have not tried it under windows.
Mac Catalina or Mojave, Safari and Firefox tested.
I can use the old workflow just fine, but thought you might like to know that the new one looks pretty bad. I am a long time user, and not scared off.. but if I were just trying you out... this would send me packing right away.
Here is some debugging info gathered in Filrefox 73.0.1, mac OS Mojave 10.14.6
I am seeing the same blank box for step 4.
Safari 12. or Firefox 71 MacOS Mojave.
I have tried these two browsers and get similar errors.
I have been using test images that have successfully uploaded before.
Here are some Firefox debugging snippets:
After selecting a file in Step 1 we get these
======
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. georef
Empty string passed to getElementById(). 10 bdc2f52da370.js:3:1064
Source map error: Error: request failed with status 403 Resource URL: https://s3-us-west-1.amazonaws.com/static.mapsmadeeasy.com/platform_files/CACHE/js/bdc2f52da370.js Source Map URL: jquery-2.0.3.min.map
Resetting Total Images index.js:29567:51
Undefined index.js:29567:51
Empty string passed to getElementById(). 5 bdc2f52da370.js:3:1064
Error: Invalid picker params filestack_error.ts:38:4
e filestack_error.ts:38
t picker.ts:711
picker picker.ts:752
picker client.ts:206
onload d98df6b29f91.js:50
handleBinaryFile db84dd724ec4.js:157
onload db84dd724ec4.js:158
======================
Step 2 is already marked as checked.... so I will pass it over...
======
Step 3 These error messages:
Empty string passed to getElementById(). 5 bdc2f52da370.js:3:1064
Empty string passed to getElementById(). 5 bdc2f52da370.js:3:1064
Empty string passed to getElementById(). 5 bdc2f52da370.js:3:1064
Empty string passed to getElementById(). 10 bdc2f52da370.js:3:1064
=====
Step 4 clicking the header gets this error:
Empty string passed to getElementById(). 5 bdc2f52da370.js:3:1064
Hope this helps.
Keith
الرجاء تسجيل الدخول لترك تعليق.
I think I figured it out... Files exported from Lightroom will not work in the new DJI-specific workflow... even if they came from DJI originals.
- If I select a Lightroom-exported file in Step 1, then in Step 4 the file choose box does not appear... it is just a blank white box.
- If I select a DJI original file in Step 1, then Step 4 works.
I put more detail in comments on this other thread.
When using the new workflow it assumes that ALL of the original tags are intact. It is likely that Lightroom, or any other image management software, might not be writing all the tags that are needed. The new workflow looks at some of the DJI specific XMP in an attempt to estimate GSD and footprint size. If that isn't there it could be causing what you are seeing.
From the Data Collection guidelines that are agreed to at the time of upload:
"EXIF Tags Intact - EXIF tags should not be modifed by 3rd party image processing software. We need all the of the tags the camera originally places in the image files. Photoshop, Photos, Photo Manager and lots of other softwares have been known to corrupt the tags."
https://www.mapsmadeeasy.com/data_collection
The new DJI specific workflow relies on a few DJI placed tags that are not checked in the Classic workflow. This is why they will still work with the old version.
It may be possible to get Lightroom to leave your tags alone. This has been discussed elsewhere on the forum but not with respect to the new workflow.
Zane, thanks for your explanation.
I realize, from looking at the history of discussion on this topic that it is not your job to help make Lightroom exports work... makes sense.
For other users who might be trying to accomplish the same thing, I will report here some attempts that FAILED. Maybe somebody can build on this or save themselves some time trying.
The idea was to use exiftool to copy all metadata from the original DJI files into the lightroom exports. None of the variations that I tried were accepted by the New DJI Workflow.
Case 1) The files as exported by Lightroom with "Include: All Medata" selected. This gives the behavior I originally described - MME's Step 1 accepts the file, but then fails at Step 4. Comparing the metadata in the LR exported file to the DJI showed many differences. Lightroom adds stuff, and leaves out several sections. Here is the exiftool command I used to examine the metadata in the files
exiftool -a -s -G D.jpg
You can look up these options in the exiftool documentation: https://exiftool.org
Case 2) use exiftool to copy everything at once. (This failed to actually copy all of the metadata, and it left in a lot of stuff that Lightroom had added.)
# exiftool -TagsFromFile D.jpg '-all:all>all:all' L.jpg
MME's DJI workflow rejected L.jpg at step 1 in this case, giving warning that it needed a file from a recent DJI camera.
Case 3) Use exiftool to wipe out all the extra stuff Lightroom added, and then to add in each of the missing fields from the DJI original file explicitly. This also failed at step 1 with a warning to use a recent DJI camera.
In conclusion, I still do not know exactly what metadata the MME DJI workflow is looking for and have given up trying to load Lightroom exported files through the new DJI workflow. That's fine. The old workflow still accepts them. Hope this helps someone else in their process.
Here is the case 3 exiftool command with all the explicitly named fields:
exiftool -all= -TagsFromFile D.jpg \
-exif:all \
-XMP:About \
-XMP:CamReverse \
-XMP:CreateDate \
-XMP:FlightPitchDegree \
-XMP:FlightRollDegree \
-XMP:FlightYawDegree \
-XMP:Format \
-XMP:GimbalPitchDegree \
-XMP:GimbalReverse \
-XMP:GimbalRollDegree \
-XMP:GimbalYawDegree \
-XMP:HasCrop \
-XMP:HasSettings \
-XMP:Make \
-XMP:Model \
-XMP:ModifyDate \
-XMP:RelativeAltitude \
-XMP:RtkFlag \
-XMP:SelfData \
-XMP:CalibratedOpticalCenterX \
-XMP:CalibratedOpticalCenterY \
-XMP:Version \
-XMP:AbsoluteAltitude \
-XMP:CalibratedFocalLength \
-XMP:AlreadyApplied \
-XMP:XMPToolkit= \
L.jpg
If you are interested in exploring this yourself, here are my example files
D.JPG is from DJI Pantom 4 Pro
L.JPG is the same, exported from Lightroom at 25% resolution with "Include All Metadata" selected in the export dialog
Keith
Thanks for the detailed follow up. There is a lot of good info there. I can't imagine that here isn't some way to set up Lightroom to stop mangling the original tags.
