{"action":"created","issue":{"url":"https://api.github.com/repos/OSGeo/proj.4/issues/307","labels_url":"https://api.github.com/repos/OSGeo/proj.4/issues/307/labels{/name}","comments_url":"https://api.github.com/repos/OSGeo/proj.4/issues/307/comments","events_url":"https://api.github.com/repos/OSGeo/proj.4/issues/307/events","html_url":"https://github.com/OSGeo/proj.4/issues/307","id":106687487,"number":307,"title":"API extension request: fwd3d and inv3d","user":{"login":"piyushrpt","id":8147682,"avatar_url":"https://avatars.githubusercontent.com/u/8147682?v=3","gravatar_id":"","url":"https://api.github.com/users/piyushrpt","html_url":"https://github.com/piyushrpt","followers_url":"https://api.github.com/users/piyushrpt/followers","following_url":"https://api.github.com/users/piyushrpt/following{/other_user}","gists_url":"https://api.github.com/users/piyushrpt/gists{/gist_id}","starred_url":"https://api.github.com/users/piyushrpt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/piyushrpt/subscriptions","organizations_url":"https://api.github.com/users/piyushrpt/orgs","repos_url":"https://api.github.com/users/piyushrpt/repos","events_url":"https://api.github.com/users/piyushrpt/events{/privacy}","received_events_url":"https://api.github.com/users/piyushrpt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-16T02:49:58Z","updated_at":"2015-09-16T14:15:03Z","closed_at":null,"body":"Hi,\r\n     I'm trying to include support for a custom coordinate system used in radar image processing. The coordinate transformation from the custom projection to geodetic / geocentric coordinates is hard to accomplish easily using the current mechanisms available in proj.4 . I would suggest extending the API to include fwd3d and inv3d functions. Presence of these functions can be checked for in pj_transform and in their absence one can seamlessly fall back on the exist fwd / inv functions. \r\n\r\nI have a proof of concept working on a github fork (custom projection details will be filled in soon)\r\nhttps://github.com/piyushrpt/proj.4\r\n\r\nAny recommendations / suggestions are welcome. \r\n\r\nPiyush"},"comment":{"url":"https://api.github.com/repos/OSGeo/proj.4/issues/comments/140753925","html_url":"https://github.com/OSGeo/proj.4/issues/307#issuecomment-140753925","issue_url":"https://api.github.com/repos/OSGeo/proj.4/issues/307","id":140753925,"user":{"login":"hobu","id":87751,"avatar_url":"https://avatars.githubusercontent.com/u/87751?v=3","gravatar_id":"","url":"https://api.github.com/users/hobu","html_url":"https://github.com/hobu","followers_url":"https://api.github.com/users/hobu/followers","following_url":"https://api.github.com/users/hobu/following{/other_user}","gists_url":"https://api.github.com/users/hobu/gists{/gist_id}","starred_url":"https://api.github.com/users/hobu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hobu/subscriptions","organizations_url":"https://api.github.com/users/hobu/orgs","repos_url":"https://api.github.com/users/hobu/repos","events_url":"https://api.github.com/users/hobu/events{/privacy}","received_events_url":"https://api.github.com/users/hobu/received_events","type":"User","site_admin":false},"created_at":"2015-09-16T14:15:03Z","updated_at":"2015-09-16T14:15:03Z","body":"I think there will be general enthusiasm for this implementation (I'm certainly supportive), but you will have to clearly outline the API additions, and more importantly, \"public\" API changes required to implement these transforms. proj.4 is a very old and stable (in both good and bad ways) library, and changes often have unrecognized ripple effects in long-dead-but-still-used software that depends upon it.\r\n\r\nA writeup to the proj list http://lists.maptools.org/mailman/listinfo/proj that describes these items along with any discussion by those who care will be needed before being able to merge this. Assume that the next proj.4 release, 4.9.3, is probably February to March 2016, so you should expect to be able to include it in that."}}