data-geonet migration: wget not correctly following redirects #150
Description
We've received this question from one of our beloved end users, in relation to https://github.com/GeoNet/help/blob/main/data-access-changes/data-geonet.md
Logging this here in case others will encounter the same problem
We have an automated script that downloads the sitelogs of the GeoNet stations to make sure that we use the right station metadata in the IGS SINEX combinations. It currently uses the following wget command:
wget -e robots=off --no-check-certificate -m -np -l1 -nd -A log,txt https://data.geonet.org.nz/gnss/sitelogs/logsI tried to update the command as follows:
wget -e robots=off --no-check-certificate -m -np -l1 -nd -A log,txt https://gamma-data.geonet.org.nz/v1/data/gnss/sitelogs/logsThe redirection was followed, but the command then failed with an error 404:
--2026-02-19 11:28:13-- https://gamma-data.geonet.org.nz/v1/data/gnss/sitelogs/logs Resolving gamma-data.geonet.org.nz (gamma-data.geonet.org.nz)... 3.104.180.119, 16.176.212.15 Connecting to gamma-data.geonet.org.nz (gamma-data.geonet.org.nz)|3.104.180.119|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://geonet-meta.s3-ap-southeast-2.amazonaws.com/share/sitelogs/logs [following] --2026-02-19 11:28:14-- https://geonet-meta.s3-ap-southeast-2.amazonaws.com/share/sitelogs/logs Resolving geonet-meta.s3-ap-southeast-2.amazonaws.com (geonet-meta.s3-ap-southeast-2.amazonaws.com)... 3.5.165.174, 3.5.165.44, 52.95.131.186, ... Connecting to geonet-meta.s3-ap-southeast-2.amazonaws.com (geonet-meta.s3-ap-southeast-2.amazonaws.com)|3.5.165.174|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2026-02-19 11:28:15 ERROR 404: Not Found.
Could you please advise on how to automatically download all the site logs from your new server?