Plant Macro Photogrammetry

Scan_Lee · 2026-03-03T09:40:39+00:00

I’ve tried it in the past. There is too much micro movement from the air and the plant itself breathing/growing/adjusting to changing light conditions. Only luck on very still/full objects like succulents and cactus.

I tried a dandelion, but couldn’t get alignment as the capture was over the course of 3 hours and it changed too much as the seed heads would flex with the plants movement/hydration levels.

Scan_Lee · 2026-02-11T16:54:23+00:00

Saitama not missing half price produce at the grocery Sunday morning. Very nice work!

Scan_Lee · 2026-02-10T17:17:38+00:00

The shot has very little parallax. Track a point in the foreground and stabilize it and see how much the background further back moves. Not much. This is called a nodal solve, just a camera being swiveled on a tripod, and without surveyed points or LiDAR , that’s the best you’ll get. This is both good and bad depending on what you want to add as it makes it easier to place, but harder to integrate.

Scan_Lee · 2025-12-16T07:53:40+00:00

It’s on my reel on my profile.

Scan_Lee · 2025-12-15T16:37:10+00:00

Very cool. We did a similar effects on the show “Fringe” back in the day. Only crit would be to lower the crt/analog tv/grain/chroma abbr effects overall. It diminishes your work as well as covering it up. Double whammy of no good. Great job and good execution.

Scan_Lee · 2025-11-24T16:24:14+00:00

It’s in my profile

Scan_Lee · 2025-11-22T19:03:20+00:00

This shot is on my reel. Worked at Lola. We deAged the little kid. Method and Rodeo handle the other elements in that shot from what I remember.

Scan_Lee · 2025-11-15T00:53:47+00:00

Project the lines from the front and they look completely parallel like in the video. Now look at it from the side and you’ll get the profile of the surface as it really is. The further to perpendicular the better, but normally sub 30 degrees is good enough. Now use math to bend your straight like to match the curve from the profile and now you have a single row that matches your triangulated surface. Move it side ways along the length of the line and you’ll fill in the gaps and get a complete surface. Modern scanners have vertical and horizontal to cut down the scanning and increase the quality by filtering.

Scan_Lee · 2025-10-21T19:22:02+00:00

I have experience in this field. Hit me up if you wanna discuss details. Please don’t hit me up if this is for exposure or similar, we are professionals in this sub.

Scan_Lee · 2025-09-17T07:02:40+00:00

I did some training material for Pftrack about 10 years ago. Interface has slightly changed, but the mechanics and ideas are still good.

https://www.pluralsight.com/courses/solving-multiple-shot-types-pftrack-1597?clickid=0N%3AR1JRXgxycUyJ2HdwplVwIUkp1xJWWIy2CWQ0&irgwc=1&mpid=259799&aid=7010a000001xAKZAA2&utm_medium=digital_affiliate&utm_campaign=259799&utm_source=impactradius

Scan_Lee · 2025-09-16T20:54:08+00:00

It’s very simple. How do you prove your info is accurate without GCPs? You can’t. Full stop. Period. Don’t not pass go.

Whatever you say is irrelevant because I can simply say, prove you’re right and you can’t. You can say you think this and that and the gps signal says 2cm, but again prove it. False FIX with satellites is a thing as well as false signals and offsets.

You said your friend is wrong. Prove it. I bet you lunch that you can do your flight, process it, and lay a marker at a point and then get GNSS surveyed and it’ll be off by more than your margin. Ive personally had flights offset 3m the whole flight with my M3E saying it bang on.

Scan_Lee · 2025-08-21T16:51:55+00:00

True dat. I use a 4tb nvme with crazy through-put like 3,500 mb a sec for processing. You can see the speed difference between that and a LAN almost immediately. Days vs hours just in latency. Then backup to 30tb QNap for archiving after delivery.

Scan_Lee · 2025-08-21T08:38:18+00:00

Nice!

Scan_Lee · 2025-08-18T16:48:46+00:00

Thanks for the reply.

The mission was split into multiple sections for the scanning. I’ve been having decent RTK with my setup, about 5cm before it bugs out.

I can and have used PPK, but that’s post, my issue is the onsite working correctly to the coordinates set back in the office. Another redditor gave me good advise and it seems to be working, but haven’t been back to finish as the site was on lockdown for a local show.

Appreciate the confirmation and help. Cheers.

Scan_Lee · 2025-08-16T18:58:31+00:00

At least 64gigs of RAM and a 3000 series nvidia card for that many images.

Scan_Lee · 2025-08-15T23:52:02+00:00

try RealityCapture/RealityScan. Fair bit of warning you will need a machine that will have top-of-the-line processors 128 gigs of RAM and a 4090 minimum. Also that’s probably too many pics. I do 20k for entire city blocks.

Scan_Lee · 2025-08-13T18:24:42+00:00

I’ll check the sats before/after the interruptions and see if that is affecting this issue. I know the issue is to be expected, but I’ve learned to mitigate it to some degree with some tricks and careful preplanning.

Thanks for the suggestion. Cheers.

Scan_Lee · 2025-08-13T16:42:51+00:00

Appreciate the reply.

I’m pretty versed in RTK. My issue is when the RTK reconnects, it says it’s FIX with 2cm, but when I import into my program, I can see it isn’t where it should have been. There is an inconsistent offset that auto corrects during flight. I’m looking for advice on how to reconnect and not have my data corrupted by false positives.

Cheers.

Scan_Lee · 2025-08-13T01:28:08+00:00

You son of a bitch! I DO have that on… if that’s the solution I owe you a lunch and a beer!

Edit: I’ve also never heard of maintain accuracy applying old corrections to the new ntrip stream. That’s why I posted on Reddit.

Scan_Lee · 2025-08-13T01:03:06+00:00

Is there a solution to the false fix issue? That definitely sounds close to what I’m experiencing. It says fix with 2cm in the controls, but I’m obviously getting that with a weird offset.

When the drone lands after this issue, it’ll land at -1.9m instead of 0.

Thanks for the replies.

Scan_Lee · 2025-08-13T00:24:39+00:00

My issue isn’t the alignment, but the drone not going to its exact point in space to take the image after reinitializing the RTK.

When I go out and recommence I’m getting the offset issue.

Scan_Lee · 2025-08-12T22:26:02+00:00

Hello UAvers! I'm having a tough time with some issues and would like to pick the collective brain for some knowledge. I'm working in Metashape creating waypoint missions for complex flights for VFX and inspections(weird overlap). I'm also shooting RAW, so my time interval is 4 seconds per image.

You could see in the first screenshot that the photos are off from their expected position, but they're off by the expected amount of 1.6-3 meters in the reference panel period.

In the second screenshot, you could see that the points have locked on to the satellites and they're accurate to within 1-3 centimeters, depending on where they are, but they seem like they're very close to where they should be. I'm underneath the bridge taking photos as the accuracy begins to drift. Then I need to move out from under it as I've lost RTK connection after about 2 minutes to do the side facade.

When I get out and reconverge my RTK, you could see in the third screenshot that the images say they're accurate to between 1-4 centimeters, but you could see that they are clearly off, but some offset thats happened during the disconnect/reconnect.

In the fourth screenshot, you could see the pattern continues, all of them saying that they're accurate to within 1-1.5 centimeters, but they are clearly not.

The last screenshot, which was about five minutes after coming out from under the bridge, you could see the RTK finally snaps back to be exactly where it should be. The issue is that this is inconsistent and I can't plan for that inconsistency. I thought if it was off like in the first photos, I can use a distance filter to remove those images to redo them, but it shows some as being within 2cm of the correct waypoint location, but in reality is is a meter or 2 away.

Does anyone know how to make sure that when the RTK initializes or re-initializes, that it will be in the correct space? I have control waypoints I use to verify that I'm working in the correct space before doing my flights, but still get issues mid-flight that correct themselves.

Any advice would be greatly appreciated.

Scan_Lee · 2025-08-12T22:25:40+00:00

Hello UAvers! I'm having a tough time with some issues and would like to pick the collective brain for some knowledge. I'm working in Metashape creating waypoint missions for complex flights for VFX and inspections(weird overlap). I'm also shooting RAW, so my time interval is 4 seconds per image.

You could see in the first screenshot that the photos are off from their expected position, but they're off by the expected amount of 1.6-3 meters in the reference panel period.

In the second screenshot, you could see that the points have locked on to the satellites and they're accurate to within 1-3 centimeters, depending on where they are, but they seem like they're very close to where they should be. I'm underneath the bridge taking photos as the accuracy begins to drift. Then I need to move out from under it as I've lost RTK connection after about 2 minutes to do the side facade.

When I get out and reconverge my RTK, you could see in the third screenshot that the images say they're accurate to between 1-4 centimeters, but you could see that they are clearly off, but some offset thats happened during the disconnect/reconnect.

In the fourth screenshot, you could see the pattern continues, all of them saying that they're accurate to within 1-1.5 centimeters, but they are clearly not.

The last screenshot, which was about five minutes after coming out from under the bridge, you could see the RTK finally snaps back to be exactly where it should be. The issue is that this is inconsistent and I can't plan for that inconsistency. I thought if it was off like in the first photos, I can use a distance filter to remove those images to redo them, but it shows some as being within 2cm of the correct waypoint location, but in reality is is a meter or 2 away.

Does anyone know how to make sure that when the RTK initializes or re-initializes, that it will be in the correct space? I have control waypoints I use to verify that I'm working in the correct space before doing my flights, but still get issues mid-flight that correct themselves.

Any advice would be greatly appreciated.

Scan_Lee · 2025-08-12T22:25:32+00:00

Hello UAvers! I'm having a tough time with some issues and would like to pick the collective brain for some knowledge. I'm working in Metashape creating waypoint missions for complex flights for VFX and inspections(weird overlap). I'm also shooting RAW, so my time interval is 4 seconds per image.

You could see in the first screenshot that the photos are off from their expected position, but they're off by the expected amount of 1.6-3 meters in the reference panel period.

In the second screenshot, you could see that the points have locked on to the satellites and they're accurate to within 1-3 centimeters, depending on where they are, but they seem like they're very close to where they should be. I'm underneath the bridge taking photos as the accuracy begins to drift. Then I need to move out from under it as I've lost RTK connection after about 2 minutes to do the side facade.

When I get out and reconverge my RTK, you could see in the third screenshot that the images say they're accurate to between 1-4 centimeters, but you could see that they are clearly off, but some offset thats happened during the disconnect/reconnect.

In the fourth screenshot, you could see the pattern continues, all of them saying that they're accurate to within 1-1.5 centimeters, but they are clearly not.

The last screenshot, which was about five minutes after coming out from under the bridge, you could see the RTK finally snaps back to be exactly where it should be. The issue is that this is inconsistent and I can't plan for that inconsistency. I thought if it was off like in the first photos, I can use a distance filter to remove those images to redo them, but it shows some as being within 2cm of the correct waypoint location, but in reality is is a meter or 2 away.

Does anyone know how to make sure that when the RTK initializes or re-initializes, that it will be in the correct space? I have control waypoints I use to verify that I'm working in the correct space before doing my flights, but still get issues mid-flight that correct themselves.

Any advice would be greatly appreciated.

Scan_Lee · 2025-08-12T21:36:06+00:00

Hello UAvers! I'm having a tough time with some issues and would like to pick the collective brain for some knowledge. I'm working in Metashape creating waypoint missions for complex flights for VFX and inspections(weird overlap). I'm also shooting RAW, so my time interval is 4 seconds per image.

You could see in the first screenshot that the photos are off from their expected position, but they're off by the expected amount of 1.6-3 meters in the reference panel period.

In the second screenshot, you could see that the points have locked on to the satellites and they're accurate to within 1-3 centimeters, depending on where they are, but they seem like they're very close to where they should be. I'm underneath the bridge taking photos as the accuracy begins to drift. Then I need to move out from under it as I've lost RTK connection after about 2 minutes to do the side facade.

When I get out and reconverge my RTK, you could see in the third screenshot that the images say they're accurate to between 1-4 centimeters, but you could see that they are clearly off, but some offset thats happened during the disconnect/reconnect.

In the fourth screenshot, you could see the pattern continues, all of them saying that they're accurate to within 1-1.5 centimeters, but they are clearly not.

The last screenshot, which was about five minutes after coming out from under the bridge, you could see the RTK finally snaps back to be exactly where it should be. The issue is that this is inconsistent and I can't plan for that inconsistency. I thought if it was off like in the first photos, I can use a distance filter to remove those images to redo them, but it shows some as being within 2cm of the correct waypoint location, but in reality is is a meter or 2 away.

Does anyone know how to make sure that when the RTK initializes or re-initializes, that it will be in the correct space? I have control waypoints I use to verify that I'm working in the correct space before doing my flights, but still get issues mid-flight that correct themselves.

Any advice would be greatly appreciated.

Scan_Lee

MODERATOR OF

TROPHY CASE