KeyError: "Unable to open object (object 'Solar_Zenith_Angle' doesn't exist)"

[HlEvag]

When running image_correct.py, an error appears that "Solar_Zenith_Angle" does not exist. And the input AOP data is shown in the figure, which contains "Solar_Zenith_Angle" (Path: /GRSM/Reflectance/Metadata/Logs/170441）. Why？

[HlEvag]

Are there any requirements for the NEON.h5 file structure？Is there a specific location for the relevant code？

[oldmanye007]

Both 'Solar_Azimuth_Angle' and 'Solar_Zenith_Angle' in NEON AOP are stores as attributes (numbers) in 'Logs', not dataset.
The structure in AOP for anc data can be found here
https://github.com/EnSpec/hytools/blob/4200569bf1620d04993997bdba74e58342772f59/hytools/io/neon.py#L58C45-L58C65
Here is how the numbers are turned into array

hytools/hytools/base.py

Line 478 in 4200569

if anc in ['solar_zn','solar_az']:

[HlEvag]

Thank you for your reply! In fact, for the AOP dataset, I only modified this part:

hytools/scripts/configs/image_correct_json_generate.py

Lines 21 to 24 in 4200569

	# config_dict['file_type'] = 'neon'
	# images= glob.glob("/data1/temp/ht_test/*.h5")
	# images.sort()
	# config_dict["input_files"] = images

Change:

However, when running image_correct.py, "KeyError: Unable to open object (object 'Solar_Azimuth_Angle' doesn't exist)" appears, which is incorrect, and the path of 'Solar_Azimuth_Angle' in the AOP data is as follows:

How can I adjust the code to ensure it works? Looking forward to your reply!

[oldmanye007]

Can you provide more information on the goal of using HyTools, especially the reason why you apply hytools on the Level 3 reflectance products? Hytools is designed for processing Level 1 reflectance (DP1), and correcting the topographic and BRDF effect in the images. The execution of the script "*image_correct.py*" is more or less equivalent to converting DP1 to DP3 product (Level 3). If you have DP3 reflectance products, you do not need to re-process them.

…

On Thu, Aug 14, 2025 at 8:22 AM HL_DL ***@***.***> wrote: *HlEvag* left a comment (EnSpec/hytools#22) <#22 (comment)> Thank you for your reply! In fact, for the AOP dataset, I only modified this part: https://github.com/EnSpec/hytools/blob/4200569bf1620d04993997bdba74e58342772f59/scripts/configs/image_correct_json_generate.py#L21-L24 Change: image.png (view on web) <https://github.com/user-attachments/assets/1c3f195a-5a29-41d0-9188-5822ca4c9343> However, when running image_correct.py, "KeyError: Unable to open object (object 'Solar_Azimuth_Angle' doesn't exist)" appears, which is incorrect, and the path of 'Solar_Azimuth_Angle' in the AOP data is as follows: image.png (view on web) <https://github.com/user-attachments/assets/7a3c1c5d-9aae-4f87-a09a-05da1ff05e5c> How can I adjust the code to ensure it works? Looking forward to your reply! — Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEO2NVAKEQ2WATRWGHLIUD3NSERZAVCNFSM6AAAAACDSKKT22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOBYGQ2DENJRG4> . You are receiving this because you commented.Message ID: ***@***.***>

[HlEvag]

AOP data for L3 products prior to 2022 only underwent calibration, orthorectification, and atmospheric correction, and did not include BRDF and topographic correction.

[oldmanye007]

I downloaded some L3 tiles and found that it is not easy to correct them. The reason is that data in an image tile is from multiple flightlines, each of which has a unique solar zenith and azimuth angle. The case in your provided image has only one flightline ('170441'), but other tiles are not in that case. I cannot find the lookup location for each pixel in the H5 file that tells us which flightline that pixel is from and what are its solar illumination angles (zenith and azimuth). There are two options I recommend: 1, use L1 flightline-based AOP instead of L3 tile-based AOP; or 2, wait for the release of the re-process L3 product from NEON

…

On Sun, Aug 17, 2025 at 9:43 PM HL_DL ***@***.***> wrote: *HlEvag* left a comment (EnSpec/hytools#22) <#22 (comment)> AOP data for L3 products prior to 2022 only underwent calibration, orthorectification, and atmospheric correction, and did not include BRDF and topographic correction. image.png (view on web) <https://github.com/user-attachments/assets/9b8d5a45-6357-4dd0-bd81-d84d2c793926> — Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEO2NUNEQEDZ4CXVFAJXUD3OE4TRAVCNFSM6AAAAACDSKKT22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJUHEZDANRSHA> . You are receiving this because you commented.Message ID: ***@***.***>