-
Notifications
You must be signed in to change notification settings - Fork 27
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
CARS supports PleiadesNeo stereo imagery? #13
Comments
Another note: |
Hello @lionlai1989, You are right : OTB currently doesn't not support Pleiades Neo Data so CARS too. In order to work around the problem, you must :
NB : To check it works once you have modified the RPC, you can try on a small data using otbcli_ExtractROI : https://cars.readthedocs.io/en/stable/faq.html#how-to-create-cars-compatible-roi-input-data-with-otb :
Regards, |
Hello @lionlai1989, have you tried with the recommendations ? Can we close the issue ? |
I close this issue : @lionlai1989 If you require any further information, please feel free to (re) open it. |
Hi team of CARS:
I've been testing CARS with PNeo (PleiadesNeo) data lately and found that there exists few issues.
IndexError: index -1 is out of bounds for axis 0 with size 0
:My guts feeling tells me that the warnings and errors here are related to the goemodel file (RPC*.XML). Thus, I compare the PNeo's RPC file with Pleiades RPC file and find that tags of PNeo and Pleiades are not exactly the same. Here is the mapping:
So, I manually modified the RPC file and make sure that tags of PNeo looks exactly the same as Pleiades'. And rerun the pipeline.
In 1., I described what modification is made and rerun the pipeline. Here is the output:
htop
to observe that the program was using only 1 CPU (but 8 CPUs are assigned in config.json).22-10-11_13h15m_sensor_to_full_res_dsm.log
:content.json
. The resolution of PNeo data is 0.32 meter. In PNeo metadata fileDIM*.XML
,But the CARS's output file
content.json
shows:It looks like the target resolution should be entered by users. How can I do it?
config.json
:It's a bit long. Thank you for your patience. 😄
The text was updated successfully, but these errors were encountered: