-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show indication that camera is triggering #1210
Comments
do you have a log you could provide with real data inside it? |
that is really cool |
just working on the right balance of what to display, and what not to display. |
new beta out. |
This is awesome! is this working ?
|
This is wonderful Michael! Thank you.
What are the purple polygons in the screen shot? |
1 - I will have to look into. 2 - the issue with numbers is there size, and if there are a large number of photos in the mission. I will need to look at the performance side, it is possible, just at what cost I need to determine. the purple squares are the estimated ground footprint, based on camera RPY and terrain altitude |
to see the squares try the grid with footprints turned on. this is a recent change, that may have gone unnoticed by many |
When I use the Survey Grid tool, and click on the Footprints, I see the shaded rectangles on the grid map just like always. Are you saying that this will activate a function that will allow me to see real time image footprints on the Flight Data map while flying? |
if you mouse over points, it will show the footprint. as well as the photo number |
Micheal, I like where this is going, but in reality its nearly impossible to visualize the individual footprints with the typical amount of overlap and sidelap. There must be a better way to present this information. What if we highlighted the just sidelap area and left out the rest of the footprint? Or somehow only display the areas where the sidelap drops below the target? What if we created a new field for minimum sidelap, and if the sidelap is calculated to drop below this threshold, then it is highlighted. For example, in mountainous terrain I choose a target sidelap of 75%, but I know I can live with as little as 50%. Then any areas with less than 50% are highlighted. I can then raise my altitude until all highlighting is gone. How do you get the purple footprints to show up on the Flight Data map? |
Micheal, thank you for your huge efforts bringing these desires to life. I am totally agree with the ideas of Iskess. If it increases the computational complexity instead of camera icons you can put only small dots with red,yellow and green color. We can understand that red is late, yellow is early and green is just in time taken photo. Onur... |
the camera icon's are not the complexity, the footprints are, as they terrain intersect. flightdata only displays after MAVLINK_MSG_ID_CAMERA_FEEDBACK message has been received. |
ive added green icons when the images are above CAM_MIN_INTERVAL, and red if they are bellow CAM_MIN_INTERVAL |
Michael, |
yes, this is all on current beta. UPDATE: added based on gridui camera selection |
When playing tlog in latest beta I can see trigger camera icons while the plane flies the flight lines. If I pause the playback, then resume, the waypoints and flight lines vanish. It appears that when I press pause, the map reverts to Lat/Long 0/0, and when I restart it, the map re-centers with all overlays removed. |
do you have a negative loiter radius? ive just fixed and uploaded a new beta |
Yes, it's loiter radius is negative for left turns. I will update and try again. Thank you. |
Here is my param file if that helps: |
i did fix the negative loiter issue, but forgot to post here. the workaround it just make it positive for the moment. |
Thanks Micheal, I did make the loiter positive to be able to fly the mission today. Thank you! |
could you provide your tlog? |
the CAM_MIN_INTERVAL is fixed as part of #1216 |
Excellent work! I will test this shortly but I really like the improvements for mapping and visualization of the cameras! |
Very nice. That makes the coverage MUCH easier to visualize. However the map detail is total obscured. There would need to be a way to toggle this on/off. A color legend would also be helpful. For example, Dark Blue = 1 image, Green = 4 images, Red = 6 images, etc |
yes it does need a legend, and I'm very aware of the obscured, as I said, its experimental. |
@IronDome2 this is not the place for questions like that. however to fix it try updating again, your install is likely missing some files. |
My apologies, will look into thanks. |
Mike, Thank you. Onur. |
@onurboy yes it slows it down, depending on the coverage area checking 3000+ point on ever render does cause a large slow down. I am aware and will be addressing. |
I am not sure how this used. Thanks |
ive seen it, and it doesn't show overlap, so don't like that implementation. |
I don't know for others, but most of the time I found overlap problems when doing missions that involve more than one flight. Most of the time it is hard to tell where the last flight ended. May be because I have not tried using segment splitting, usually if I many missions, I just create each mission separately. Each starting just at the end of the previous, hence the polygon footprint ensures that I am not leaving any gap between missions. Thanks again |
I like the enhance in the latest beta. Is this safe to use yet? |
Hi Iskess, It this the 'Camera Overlay' under right click on map? if so it is not working for me, thanks |
It works for me using MP 1.3.46 while playing back a tlog. |
Use MAVLINK_MSG_ID_CAMERA_FEEDBACK to provide an indication that the mapping camera is triggering as expected. This could be an icon on the HUD, or just a HUD user_item.
To take this a step further, show the time interval between triggers. Using distance based triggering, it is useful to know how the wind is affecting your triggering rate. If the rate gets too high due to a tailwind, the operator may consider slowing down the aircraft, increasing the altitude, or aborting the mission. In any case it's very helpful to be made aware that there may be a problem with your overlap.
The text was updated successfully, but these errors were encountered: