Skip to content
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.

Sign up for GitHub

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

Jump to bottom

mapproject and user-supplied nodata filed #75

Closed
oleg-alexandrov opened this issue Jun 26, 2013 · 1 comment
Closed

mapproject and user-supplied nodata filed #75

oleg-alexandrov opened this issue Jun 26, 2013 · 1 comment

Comments

@oleg-alexandrov
Copy link
Member

Currently mapproject takes as input a --nodata-value command line option, but does nothing with it. Need to decide the best way to use this. Presumably, if the input image does have a nodata field in its tif/cub header, that one should be always used, both on input and output. If that one is missing, we assume all data is valid on input, but use the user-suppled --nodata-value at output only.
@oleg-alexandrov
Copy link
Member Author

This was a quick enough. The --nodata-value field will be used both on input and output unless specified in the input image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@oleg-alexandrov