-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add overview archive to imagery config #2545
Conversation
This pull request introduces 6 alerts when merging 1f0dc2b into e331835 - view on LGTM.com new alerts:
|
c150bc1
to
82af401
Compare
epsgcodes default to the old NZTM when using epsg:2193
|
||
export interface ConfigImageryOverview { | ||
/** Path to overview archive */ | ||
path: string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be relative path?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we update the comment to say this is a relative path from the imagery.uri?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting thought, maybe we should check if it starts with ./
then join it or allow it to be absolute? s3://foo/bar/overviews
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be better. I would like to have the option to put overview in different location.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine, and tested good. Maybe just one comment change. Otherwise looks good to me.
No description provided.