Error in requesting specific RGTs and cycles
See original GitHub issueI was trying to download different cycles of ground tracks of interest by passing a cycle list and a track list. I know a similar issue has been discussed before, but when I tried to get multiple RGTs of one cycle, the returned dataset contains all the tracks in between the RGT numbers of this track list, instead of only returning the two RGTs I am interested, e.g. tracks ‘0415’, ‘0598’ in cycle 7:
short_name = 'ATL06'
spatial_extent = [-61.7189, -83.5349, -60.7723, -83.3023]
date_range = ['2019-07-30','2020-11-28']
#region_a = ipx.Query(short_name, spatial_extent, date_range)
ipx.Query(short_name, spatial_extent, date_range, cycles='07', tracks=['0415','0598']).avail_granules(ids=True)
The above code will return:
[['ATL06_20200422180234_04150711_003_02.h5',
'ATL06_20200426034538_04670711_003_02.h5',
'ATL06_20200426175414_04760711_003_02.h5',
'ATL06_20200430033716_05280711_003_02.h5',
'ATL06_20200430174552_05370711_003_02.h5',
'ATL06_20200504173733_05980711_003_02.h5']]
When querying multiple RGTs from different cycles, I will receive KeyError: ‘feed’
:
ipx.Query(short_name, spatial_extent, date_range, cycles=['06', '07'], tracks=['0415','0598']).avail_granules(ids=True)
---------------------------------------------------------------------------
KeyError Traceback (most recent call last)
<ipython-input-5-b506fd9b44e5> in <module>
----> 1 ipx.Query(short_name, spatial_extent, date_range, cycles=['06', '07'], tracks=['0415','0598']).avail_granules(ids=True)
/anaconda3/envs/icepyx/lib/python3.7/site-packages/icepyx/core/query.py in __init__(self, dataset, spatial_extent, date_range, start_time, end_time, version, cycles, tracks, orbit_number, files)
167 self._reqparams.build_params()
168 # update the list of available granules
--> 169 self.granules.get_avail(self.CMRparams, self.reqparams)
170
171 # ----------------------------------------------------------------------
/anaconda3/envs/icepyx/lib/python3.7/site-packages/icepyx/core/granules.py in get_avail(self, CMRparams, reqparams)
165 # print(results)
166
--> 167 if len(results["feed"]["entry"]) == 0:
168 # Out of results, so break out of loop
169 break
KeyError: 'feed'
Any idea why? I was also wondering if it’s possible to only return the tracks with specific cycle numbers and RGT numbers that I passed in the Query class. Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
2021-04-01_t2_udfs_rtgs_v2-2.pdf - European Central Bank
RTGS has a concept of error handling in place. The requested action is not processed and RTGS provides the user with detailed information ......
Read more >Frequently Asked Questions - Reserve Bank of India
How does the NEFT system operate? Ans: Following is the step-wise flow of NEFT transaction. Step-1: An individual / firm / corporate willing...
Read more >Reducing risk and increasing resilience in RTGS payment ...
Real time gross settlement (RTGS) reduces counterparty credit risk in payments by settling transactions gross, one by one in real time, instead of...
Read more >2. EOD Maintenances - Oracle Help Center
EOD ensures that once End of Cycle processing starts, each function that will be run in the specified sequence will be executed automatically....
Read more >Bank of England's Real-Time Gross Settlement Service
takes place within defined clearing cycles at specific points during the RTGS operating day. Therefore, no volume data are available.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello @dpyles97 and @icetianli. I just merged #148 into development, which allows searches by orbital parameters. I haven’t tried these updates with your specific use cases, but I wanted to reopen the conversation to let you know this functionality was available and reopen the conversation if we’d like to think about implementing a way to query/order data as you’d like.
Great, thanks @JessicaS11 for keeping us updated! I am happy to help with this when the
orbit_numbers
is solved by the CMR team.