-
Notifications
You must be signed in to change notification settings - Fork 40
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
Unable to read metadata (l3a,l3b) #28
Comments
@lnicola please could you give a solution to this issue |
@smfcrts sorry for the late reply. Can you tell us what version of the system you are running and maybe attach a copy of that HDR file? |
Hello, |
@lnicola I sent a copy of attached HDR file,please have a look on it |
I'll think about it when I find some time, but I didn't see anything obviously wrong there. |
Thank you @lnicola |
@lnicola Hi, did you have a look on the HDR file, because i still have the same problem even if the L2A products are well generated. |
I couldn't see anything obviously wrong with the file. Can you upload the whole product somewhere (e.g. https://send.firefox.com) so I can pass it to my colleague who knows more about the L3A? In the meanwhile, can you test with fewer input products in that command line? Even a single one, if it allows you. Also, what happens if you remove the first product from that list? Do you get an error on the second one as well? |
I tested with only one product and it give the same error, and even if i remove the first one it give error on the second one. So which product should i upload? |
Either of them, I suppose. |
Do you think it could be a problem of permission? |
It might be. Does |
ok i'll try, what does cat do? |
It should display the contents of that file (it's an XML) to the console/screen. If you get a "Permission denied" error, it means it's not working. |
yes it works. |
Can you also try this? $ sudo yum -y install strace When it finishes, PS: I just noticed that your original command line has this:
Note the extra space before the closing quote. Assuming the file doesn't have a space in its name, you'll get a file not found error on it. On the other hand, you said you got the same error even after removing the first file, so... |
the error mention that it couldn't read file, not the file doesn't exit.So I'll try right now what you suggest. |
I'm pretty sure it's the same thing (it can't read a file that doesn't exist). |
I couldn't find the log file, it show information on terminal |
There should be a |
PLease find attached the log file log.txt |
The file you've attached is truncated:
It looks like you've opened the file with a text editor ( |
ah yes you're right |
because i run the command on sen2agri-service user, so how can i get the log file without using vim. |
Here is the file but i run the command line with user log.txt |
You can copy it to your account with e.g.
From the log: |
HI, I added synthalf to the command line.Please find attached the log.txt file |
Can you test it beforehand (without |
here is the log file without strace log.txt |
All right, at least it's starting now. Can you try with |
Here is the log file with strace -s256 -f log.txt |
So it's not a missing file nor a permission issue. Can you make an archive of the product and upload it somewhere like https://send.firefox.com? |
I was not able to upload the zip file through the link you sent |
Is it larger than 1 GB? If so, you can make an account there, or try a different service. |
I do, i created an account |
HI @lnicola , please did you have a look on the link |
I was able to reproduce the failure, and it seems to be related to the format of the product metadata. Specifically, we're now using a version of MAJA that outputs a different product format. If you look at https://logiciels.cnes.fr/fr/node/57?type=desc, you'll see two versions, "TM" and "noTM". We use the former, but you might have the other one. Your product is similar to MACCS (the predecessor of MAJA) products and we can actually open it, but we reject it because of an over-eager validation. You can test it by opening the product HDR file and changing <Source>
<System>MAJA</System>
<Creator>MAJA_L2_NOMINAL_CHAIN</Creator>
<Creator_Version>3.2.2</Creator_Version>
<Creation_Date>UTC=2019-11-04T00:57:14</Creation_Date>
</Source> to <Source>
<System>MACCS</System>
<Creator>MAJA_L2_NOMINAL_CHAIN</Creator>
<Creator_Version>3.2.2</Creator_Version>
<Creation_Date>UTC=2019-11-04T00:57:14</Creation_Date>
</Source> After making the change the processing started, at least. I couldn't let it finish because of unrelated reasons. We will probably fix the validation in a future version, but it might be easiest for you to just change the string in the HDR files. This can be done in an automated way. I can guide you through the process, if you want to take that route. |
Hi, what do you mean by the former one for maja output, it means you use
the version TM or noTM. So i have to change MAJA by MACCS? That 's it
Le jeu. 16 janv. 2020 à 17:09, Laurențiu Nicola <[email protected]>
a écrit :
… I was able to reproduce the failure, and it seems to be related to the
format of the product metadata. Specifically, we're now using a version of
MAJA that outputs a different product format. If you look at
https://logiciels.cnes.fr/fr/node/57?type=desc, you'll see two versions,
"TM" and "noTM". We use the former, but you might have the other one.
Your product is similar to MACCS (the predecessor of MAJA) products and we
can actually open it, but we reject it because of an over-eager validation.
You can test it by opening the product HDR file and changing
<Source>
<System>MAJA</System>
<Creator>MAJA_L2_NOMINAL_CHAIN</Creator>
<Creator_Version>3.2.2</Creator_Version>
<Creation_Date>UTC=2019-11-04T00:57:14</Creation_Date>
</Source>
to
<Source>
<System>MACCS</System>
<Creator>MAJA_L2_NOMINAL_CHAIN</Creator>
<Creator_Version>3.2.2</Creator_Version>
<Creation_Date>UTC=2019-11-04T00:57:14</Creation_Date>
</Source>
After making the change, the processing start, at least.
We will probably fix the validation in a future version, but it might be
easiest for you to just change the string in the HDR files. This can be
done in an automated way. I can guide you through the process, if you want
to take that route.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28?email_source=notifications&email_token=ALRSPNN5FZ6MOZQEZTJWVC3Q6CBDPA5CNFSM4JLJJRQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJETPEA#issuecomment-575223696>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALRSPNOX4IBDVXHOVBROQBTQ6CBDPANCNFSM4JLJJRQQ>
.
|
We use TM, I believe you have noTM.
Yes, in the |
So i change maja to TM, it will solve the problem
Le jeu. 16 janv. 2020 à 22:29, Laurențiu Nicola <[email protected]>
a écrit :
… Hi, what do you mean by the former one for maja output, it means you use
the version TM or noTM.
We use TM, I believe you have noTM.
So i have to change MAJA by MACCS? That 's it
Yes, in the System element. The Creator doesn't matter.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28?email_source=notifications&email_token=ALRSPNJSSQATUS7OCIYCIRLQ6DGTVA5CNFSM4JLJJRQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJFTWIA#issuecomment-575355680>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALRSPNLWANNX3572KEINR33Q6DGTVANCNFSM4JLJJRQQ>
.
|
It should, but you might as well replace that string in the |
yes you're right, so how can i do it automatically
Le jeu. 16 janv. 2020 à 22:36, Laurențiu Nicola <[email protected]>
a écrit :
… It should, but you might as well replace that string in the HDR files to
keep the L2A products that you already have.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28?email_source=notifications&email_token=ALRSPNIIVCYRKNXUWVMJE53Q6DHMBA5CNFSM4JLJJRQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJFUJVQ#issuecomment-575358166>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALRSPNM3ZVDFG3X7UDUQBB3Q6DHMBANCNFSM4JLJJRQQ>
.
|
Not really tested, but something like:
You might need |
ok i'll test it and i'll let you know, thank you
Le jeu. 16 janv. 2020 à 22:44, Laurențiu Nicola <[email protected]>
a écrit :
… Not really tested, but something like:
$ sudo su -l sen2agri-service
$ find /mnt/archive/maccs_def/morocco/l2a/ -maxdepth 1 -name "*.HDR" -print0 | xargs -0 sed -i 's|<System>MAJA</System>|<System>MACCS</System>|'
You might need -maxdepth 2 instead of 1.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28?email_source=notifications&email_token=ALRSPNLXNLCSAJWVIV4NZHLQ6DILLA5CNFSM4JLJJRQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJFVBPI#issuecomment-575361213>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALRSPNP7NTV5LA62P6Y4R6DQ6DILLANCNFSM4JLJJRQQ>
.
|
I've got this error
|
I'm not sure what that would happen. You ran it under the |
yes i ran under sen2agri-service system account and it have permission on that directory |
@lnicola I overcome the problem, I replace in the HDR files to keep the L2A products that I already have. But when i installed Maja3.2.2 TM and i downloaded the appropriate gipp file it give's me error that gip CMN00 not found. |
Hello,
I run L3A composite through command line:
/usr/bin/composite_processing.py --syntdate 20190901 --input "/mnt/archive/maccs_def/morocco/l2a/S2A_MSIL2A_20190813T112121_N0208_R037_T29SMS_20190813T114617.SAFE/S2A_OPER_SSC_L2VALD_29SMS____20190813.HDR " "/mnt/archive/maccs_def/morocco/l2a/S2B_MSIL2A_20190818T112119_N0208_R037_T29SMS_20190818T122949.SAFE/S2B_OPER_SSC_L2VALD_29SMS____20190818.HDR" "/mnt/archive/maccs_def/morocco/l2a/S2A_MSIL2A_20190823T112121_N0208_R037_T29SMS_20190823T114631.SAFE/S2A_OPER_SSC_L2VALD_29SMS____20190823.HDR" "/mnt/archive/maccs_def/morocco/l2a/S2A_MSIL2A_20190902T112111_N0208_R037_T29SMS_20190902T132637.SAFE/S2A_OPER_SSC_L2VALD_29SMS____20190902.HDR" "/mnt/archive/maccs_def/morocco/l2a/S2A_MSIL2A_20190912T112111_N0208_R037_T29SMS_20190912T114646.SAFE/S2A_OPER_SSC_L2VALD_29SMS____20190912.HDR" "/mnt/archive/maccs_def/morocco/l2a/S2B_MSIL2A_20190917T112119_N0208_R037_T29SMS_20190917T132014.SAFE/S2B_OPER_SSC_L2VALD_29SMS____20190917.HDR" "/mnt/archive/maccs_def/morocco/l2a/S2A_MSIL2A_20190922T112111_N0208_R037_T29SMS_20190922T114652.SAFE/S2A_OPER_SSC_L2VALD_29SMS____20190922.HDR" --res 10 --outdir "/mnt/archive/temp/20190901/29SMS/" --bands /usr/share/sen2agri/bands_mapping_s2_L8.txt --scatteringcoe /usr/share/sen2agri/scattering_coeffs_10m.txt --synthalf 25
It gave this error:
The following error occurred during application execution : /home/cudroiu/sen2agri/sen2agri-processors/ProductReaders/MetadataHelpers/src/MetadataHelperFactory.cpp:43:
itk::ERROR: MetadataHelperFactory(0x16a8810): Unable to read metadata from /mnt/archive/maccs_def/morocco/l2a/S2A_MSIL2A_20190813T112121_N0208_R037_T29SMS_20190813T114617.SAFE/S2A_OPER_SSC_L2VALD_29SMS____20190813.HDR
OTB app finished in: 0:00:04.178794
OTB application error
Please how can i overcome this issue
The text was updated successfully, but these errors were encountered: