Michael P. Gerlek

@ARolek - what would you like the proj API to support, to give you this use case? Do you want proj strings, or something else?

Do we have a means to generate the proj string from an arbitrary SRID? Or are you thinking about just hardcoding in support for a handful of well-known epsg codes?...

the `proj4go` part of this thread has been moved to https://github.com/go-spatial/proj4go/issues/3

We timed just the Forward() operation, using the BenchmarkConvert* tests in package operations and using the code in PROJ4's example app. Inputs are (12.0,55.0). The runs were done on mpg's...

I didn't save the files, but here's some anecdotal snips from my the scrollback of my terminal window: ----------------------------------------------------------------- ``` Showing top 10 nodes out of 63 flat flat% sum%...

@wonderchook If someone could provide me with a list of proj strings or EPSG codes that would be great. Proj4 can do a lot, and I just need to make...

Right, @arolek, that's the key question... Usually you're going to want to convert from 4326 (in degrees) to some other epsg code (in meters), and that's what the "minimal" API...

"3857 to 3395" would be one of the fancier cases, where we need to drop back to 4326 first. Not supporting those sorts of operations in general, but I can...

Proj is a low-level library and so it expects you to know to ask for the right things. If you want to go 3857->3395, it’s really up to you to...