Malte Wrogemann

Is it already possible to add alternative texts?

I have also considered using the different definition files (WKT, Proj4js, Proj.4) to derive the coordinate reference systems. However, many projections and transformations (e.g. GRID-based transformations like OSTN15_NTv2_OSGBtoETRS) are still...

```go epsg31285 := Helmert(6377397.155, 299.1528128, 601.705, 84.263, 485.227, 4.7354, -1.3145, -5.393, -2.3887).TransverseMercator(13.333333333333336, 0, 1, 450000.0, 0) ```

If I convert to yaml, I don't have this problem (so its a json thing). But the general question remains...

I will take a look at this. EDIT: It's not that easy because env.Dict is used. It would therefore only be possible after refactoring.

An update to v1.3.2 would probably fix the Int-Float issue of he BurntSushi/toml package. But I dont dare to edit the modules.txt file :weary:

I've added support for NTv2. At the moment OSTN15_NTv2_OSGBtoETRS.gsb and BeTA2007.gsb are available :rocket: :rocket: ```go package main import ( "fmt" "github.com/wroge/wgs84/v2" ) func main() { transform := wgs84.Transform(wgs84.EPSG(4326), wgs84.EPSG(27700)).Round(3)...

That's a lot for me to look at, thanks for your effort! I will get back to you as soon as I have some more time....

Hi, sorry, I just got around to looking at the pull request. It looks to me like you can also add the coordinate systems to the wgs84.Repository (e.g. the EPSG()...

Okay, that makes sense. Then I could remove wgs84.Repository and we would just provide a function "EPSG(code int) wgs84.CoordinateReferenceSystem". I could clean up all the other issues with the package...