-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generating factories out of WKT v1 (geotools epsg.properties) #4
Comments
I have also considered using the different definition files (WKT, Proj4js, Proj.4) to derive the coordinate reference systems. If you want to generate the EPSG codes with already existing projections and transformations, I would be happy about pull requests. The area function can simply always return true and then cause no harm. But I'm not really happy with the structure anymore and I'm thinking about releasing a new version. |
alright, lets see if i manage to drive this generation to some meaningful results to post a pull request. |
let me follow up on this and brainstorm together how to go about it. as an example i'm looking at one of the provided definitions from GeoTools:
am i assuming right that this would result in:
and |
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) |
hi,
i'm toying with the idea of tapping into geotools wkt epsg.properties and script/generate transformation factories for each definition. or simply parse wkt1, not decided yet.
perhaps parameterize MGI -> helmert with parameters from TOWGS84 definitions.
and then instrument transverseMercator with PROPERTY values.
how do you see it, would it be working approach en mass? what would "area" function be then?
The text was updated successfully, but these errors were encountered: