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
At present, codem will attempt to register an AOI to a foundation dataset, and attempt to identify key-point matches over the entirety of both inputs. This can lead to poor results when the AOI is of a significant area with many features. To address this issue, we propose adding a --bounds argument that would added, where the contents could be relayed to the respective pdal reader.
The text was updated successfully, but these errors were encountered:
graph TD;
B{Fnd CRS Defined?} -->|No| C(Prompt user for approximate <br>bounding box foundation <br>as background)
B -->|Yes| G{AOI CRS Defined?}
C --> E(Clip Foundation to Boudning Box +/- 20%)
G -->|No| C
G -->|Yes| H{Same As Foundation?}
H -->|No| I{Transformation Exists or <br> Enough Known Info}
I -->|No| C
H -->|Yes| J(Compute Bounding Box <br> as Floating Dataset <br> +/- 50%)
I -->|Yes| J
J --> K(Clip Foundation <br>to Bounding Box)
At present, codem will attempt to register an AOI to a foundation dataset, and attempt to identify key-point matches over the entirety of both inputs. This can lead to poor results when the AOI is of a significant area with many features. To address this issue, we propose adding a
--bounds
argument that would added, where the contents could be relayed to the respective pdal reader.The text was updated successfully, but these errors were encountered: