howard at hobu.co
Tue Aug 23 09:23:58 EST 2016
On Jun 9, 2016, at 8:02 AM, Kristian Evers <kreve at sdfe.dk> wrote:
> #389: +1 on the NOMERGE. The discussion on github makes it clear to me that this is a projection that is made specifically for one particular older proprietary software package which is not in widespread use (so it seems to me at least). On top of that the documentation of the projection is not very good or publicly available (apart from a PDF attached to the github discussion). The submitter of the PR has not been able to explain what the benefits of merging his additions are, except for making it easier for the Navionics company to maintain their codebase.
I understand your frustration. Please know that the consensus seems to be to not include the Navionics projection for this release for a number of resolvable reasons:
1) It is a proprietary projection that appears to be single-use within the context of Proj.4's ecosystem. There is some question about its rigor and validity, but that is beside the point considering it is in use already.
2) It is unclear if there is a lot of public-readable data at rest in this coordinate system
3) It is unclear who is benefitting by its inclusion in Proj.4 beyond Navionics
The first one is for the Proj.4 project to consider. Do we allow single-use projections? Inclusion of a projection into the codebase assumes the project is responsible for maintaining it going forward. As Thomas and Kristian recently experienced, there are a lot of these if you have to touch them all.
The second one is for Navionics to answer. Are there (or will there be) open source software for reading data in Navionics format(s) that makes open source support of its projection a significant convenience factor for users?
The third is related to the second. Is the inclusion of this projection is simply to ease Navionics use of proj.4 and maintenance of its software stack? If so, it seems too special for inclusion. If it is to ease the transition of letting users' data out of proprietary formats and access to that data to the open source ecosystem, the case for its inclusion is stronger. The ticket traffic on this aspect is ambiguous.
If there is some consensus after more discussion, it is still possible to include this projection into the codebase in a future release. We want to be careful about tossing proprietary projections over the wall into Proj.4 without clear external use cases and when they appear to be single-use in the context of Proj.4 and its ecosystem.
> I’ve added a new projection to the code, tested and installed on my laptop. It works.
> I would like to push it for you approval but, following the instructions fromhttps://github.com/OSGeo/proj.4/blob/master/HOWTO-RELEASE ,
> I’m unable to perform latest passages.
> I’m stuck after the “make dist-all”
> Which is the way to send those changes to you ?
> Matteo Pasquini
> OPS - Production Agent
> Skype :<image001.png> Pasquini.Matteo
> Mobile: 331-595-8761
> <image003.jpg><image004.jpg> <image005.jpg> <image006.jpg>
> Proj mailing list
> Proj at lists.maptools.org
More information about the Proj