linz / basemaps-config Goto Github PK

Hey LINZ team, I got an error parsing the latest datasets and looks like the s3 url path here for the latest rural dataset doesn't quite match the dataset "name" key here as it usually does. This is not a big deal as I can change key value pair I use when parsing the aerial.json but it would be great to know if they are generally expected to match or not before I make changes. Many thanks - Grant @ Scion Research

It looks like Bay of Plenty 0.125m Urban Aerial Photos (2015-2016) is prioritised over Bay of Plenty 0.1m Urban Aerial Photos 2018-2019).
Is there any particular reason for this?
Cheers
Dan

Hi basemaps team,

I noticed that the Bay of Plenty 0.1m Urban Aerial Photos (2018-2019) are behind the newer but lower resolution Bay of Plenty 0.2m Rural Aerial Photos (2021-2022) imagery. Just checking if this ordering is correct?

Thanks,
Grant

It appears the ordering for the Invercargill aerial imagry is prioritising the 0.1m imagery over the higher quality (and as far as I can tell, from the same time period) 0.05m imagery. For example: Default basemaps vs basemap with the 0.05m layer selected.

Hi LINZ team,
I noticed the BoP ordering issue seems to have crept back in. The imagery shown on the basemap is from the 2017 capture. But the most recent imagery is from the 2019 capture.
Thanks for the great work on this system.

For 3857 Hastings 2014 data 01ED828XHKJMQNW313CV3MBP2T has been configured instead. The correct job-id is 01ED82A7KFS8RMNPRYDQ60MCQ1

For 2193 Hastings 2014 data 01EDA3MQ7T1NQGSK0ES36JM2YY has been configured instead. The correct job-id is 01EDA3NK57VHJZG9RHWT87H9TJ

Wellington is both newer and higher resolution 7.5cm vs 10cm