data-geonet migration: need to add trailing slash to obtain directory listing

[elidana]

We received another user request relative to the planned migration of the GeoNet Data API (https://data.geonet.org.nz), planned for the 17th of March 2026 (NZ time).

Hello GeoNet team,

We have been accessing GeoNet for RINEX data by getting a listing of files on a given day or hour, and then selecting which files to download. With the new API, I'm having trouble listing files, e.g. with the following URL:

https://gamma-data.geonet.org.nz/v1/data/gnss/rinex/2026/058

I get redirected to https://geonet-open-data.s3-ap-southeast-2.amazonaws.com/gnss/rinex/2026/058 as expected, but then I get this error:

<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>gnss/rinex/2026/058</Key>
<RequestId>2HC2516YJ018V5TX</RequestId>
<HostId>sQCAmfFR5KZ/HeXI3+/95lVn9VPiAj5ucDGNrqN9w6FMw1opSuXQY3fvCB60oSTPOrBTvMik26+/rgldiTUakBgUfJaxdiCB</HostId>
</Error>

Further to this, a colleague of mine noted that directory listings were working for them, and we realized the difference is the lack of a trailing slash in my URL. We may be able to update our automation to enforce a trailing slash, but it would make compatibility with other GNSS data services easier if the trailing slash was not required. Would this be feasible to implement on your end?

Any help you can provide would be greatly appreciated.

Thank you!

[elidana]

As the user correctly identified, when the user or application need to list the content under a specific "folder", a trailing slash (/) need to be added to the URL.

We believe this is a useful feature that can help distinguishing a listing request vs a download request.

Would be good to have examples of the other data centers to understand a bit better this compatibility issue the user has identified.

We are updating the migration document to hopefully make this more clear.