License Clarification and PRs about gdal HOT 2 CLOSED

1. That's a good point, when I put this repository together I didn't expect it to get much more than personal use. I used a license file from another project without paying too much attention. I've updated the license to standard MIT.
2. The repo has languished for a while as our company has not used Go extensively. I've brought it up to speed with outstanding PRs, fixed issues with newer versions of GDAL, and merged from more active forks, but don't have the resources to bring this up to the level that I'd like.
3. I agree about SWIG, after some time fighting with it I realized that writing manual wrappers would be much simpler, and the API for GDAL is fairly stable. I don't know how interested the GDAL maintainers would be, they recently dropped the PHP and Ruby bindings so they seem to be going in the other direction.

from gdal.

re:3, let me see what I can do -- I think there are a number of people that would be interested in having a golang binding for gdal

from gdal.