You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the most problems (detection but also performance) occur, due to a bad georeferencing or more precise, the clipping processes of the uploaded sketch.
At the moment there are 7 markers(globes) on the map with only 4 distinct once, also for right now the globs are only a support and not neccesary/mainly used for the clipping process, we need to change this!
There is a "standard" how to handle image detection/transformation with standardized markers. For example ArUco Markers (not sure what it stands for).
And opencv bring aruco marker generation and detection out-of-the-box.
Currently the most problems (detection but also performance) occur, due to a bad georeferencing or more precise, the clipping processes of the uploaded sketch.
At the moment there are 7 markers(globes) on the map with only 4 distinct once, also for right now the globs are only a support and not neccesary/mainly used for the clipping process, we need to change this!
There is a "standard" how to handle image detection/transformation with standardized markers. For example ArUco Markers (not sure what it stands for).
And opencv bring aruco marker generation and detection out-of-the-box.
We can complete get rid of the
and can use only the markers for clipping/transformation!
The text was updated successfully, but these errors were encountered: