Fix issue with linestring with less than 3 points failing to ingest in CMR #41
Comments
|
where is this happenings? seems like were able to generate the footprint, is it happening in the metadata aggregator step where we try to ensure the orientation of the points? |
|
Per Tim's email to Jack, here are more collections with good vs. bad Forge workflows: Hi Jack, There are forge executions from these 6 collections that are completing. I'm listing a sample granule that succeeded along with it's collection so you can compare. collection: SWOT_L2_NALT_OGDR_2.0 collection: SWOT_L2_NALT_IGDR_2.0 collection: SWOT_L2_RAD_IGDR_2.0 collection: SWOT_L2_RAD_OGDR_2.0 |
|
@sliu008 To answer your question, here is Tim's original email, and I've copied the steps in the Execution to show it failed on Step 26 below: From: Mcknight, Tim (US 398N-Affiliate) timothy.b.mcknight@jpl.nasa.gov Hi Jim and Simon, Getting alot of these errors in Forge (627 today) Listing an example granule below. granule: SWOT_IPR_2PfP025_373_20241216_063401_20241216_072528 error: {"errorMessage":"An error occurred in the Cumulus Message Adapter: java.lang.IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined" Tim AWS SWOT OPS Console - Forge Workflow - Execution f3c9e2e8-13b3-4fbf-aac3-6250153bab04 9 | ChoiceStateEntered | FootprintChoice | | 00:00:00.287 | Dec 17, 2024, 11:42:46.309 (UTC-08:00) |
|
Another email from Tim: Hi Jim and Simon, Ops has recently cited seeing the "Ring has fewer than 3 points" error for these 6 SWOT collections in the Forge workflow. SWOT_L2_RAD_IGDR_2.0 SWOT_L2_NALT_IGDR_2.0 Now in Cumulus Ops we are getting the same error for collection JASON_3_L2_OST_OGDR_GPS___F and G during the Forge workflow. sample granule: error: {"errorMessage":"An error occurred in the Cumulus Message Adapter: java.lang.IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined" Tim |
Around 25% of granules are failing.
Suggested fix: Add an extra point in the line to give it 3+ points.
Reported here:
https://wiki.jpl.nasa.gov/pages/viewpage.action?pageId=1047760594
SWOT NALT granules failing in forge since December 18th
Contemporaneous success/fail cases
collection: SWOT_L2_NALT_OGDR_2.0
successful granule: SWOT_OPR_2PfS027_025_20250114_140108_20250114_154122
failed granule: SWOT_OPR_2PfS027_027_20250114_154229_20250114_162717
"An error occurred in the Cumulus Message Adapter: java.lang.IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined"
$ java -cp ./footprint_0.10.0.jar FootprintCLI granules/SWOT_OPR_2PfS027_027_20250114_154229_20250114_162717.nc SWOT_L2_NALT_OGDR_2.0.cfg > test.txt
$ cat test.txt | grep "Process retrieved footprint" -A 1 > out.wkt
$ cat SWOT_OPR_2PfS027_027_20250114_154229_20250114_162717.wkt (ingest failed)
MULTILINESTRING ((19.9403 -23.1022, 27.4928 24.3991, 33.0238 45.3443, 36.959 53.7749, 41.7918 60.495, 47.808 65.8524, 55.1811 70.0057, 70.7739 74.6958, 91.9001 77.226, 117.9707 77.4506, 140.8738 75.1775, 155.1512 71.5736, 165.9668 66.1902, 173.9744 58.7027, 180 48.4088), (-180 48.4088, -178.8149 45.477)) <<< PROBLEM HERE
$ cat SWOT_OPR_2PfS027_025_20250114_140108_20250114_154122.wkt (ingest succeeded)
MULTILINESTRING ((46.7582 -17.8424, 53.0282 22.501, 57.7399 42.01, 60.8914 50.0237, 64.6427 56.6179, 69.089 61.975, 74.4699 66.3832, 82.4342 70.5879, 92.4623 73.776, 104.8163 76.0129, 119.6639 77.3308, 137.1218 77.6418, 154.1271 76.787, 168.4201 74.8779, 180 71.9343), (-180 71.9343, -171.6046 68.3104, -164.7619 63.5712, -159.2781 57.5706, -154.7985 49.9105, -151.2873 40.7214, -148.3058 29.1515, -139.7413 -23.3688, -134.7964 -43.1898, -131.0289 -52.0625, -126.4373 -59.1069, -120.7318 -64.7369, -113.7542 -69.1163, -105.3025 -72.452, -95.1172 -74.9167, -68.3411 -77.5396, -37.5618 -76.6712, -24.7803 -74.9254, -14.1496 -72.327, -7.2595 -69.676, -1.3748 -66.3796, 3.5214 -62.442, 7.7115 -57.6493, 14.2401 -45.1536, 19.1828 -27.0064))
The text was updated successfully, but these errors were encountered: