@AHN
ik blijf erbij dat die jaartallen niet echt handig zijn in the URL. De km tiling is weliswaar heel handig maar dat jaartal bij AHN6 verprutst dat weer. AI zegt daar het volgende over:
The year is encoded in the AHN6 filename itself, but there is no simple deterministic formula from the tile number alone. The practical way is:
- Generate the tile:
206000_610000
- Try the newest known AHN6 year first:
https://fsn1.your-objectstorage.com/hwh-ahn/AHN6/01_LAZ/AHN6_2026_C_206000_610000.LAZ
- If HTTP 404 → try:
https://fsn1.your-objectstorage.com/hwh-ahn/AHN6/01_LAZ/AHN6_2025_C_206000_610000.LAZ
- If still 404 → fallback to AHN5:
https://fsn1.your-objectstorage.com/hwh-ahn/AHN5_KM/01_LAZ/AHN5_C_206000_610000.COPC.LAZ
That is effectively how the portal works as well: AHN6 is gradually published by acquisition year/region, and not all kilometer tiles exist for every year yet. AHN itself states that AHN6 is released incrementally in 1×1 km tiles.
