-
Notifications
You must be signed in to change notification settings - Fork 18
add EPSG:31370 #263
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
add EPSG:31370 #263
Conversation
the conversion method use Lambert Conic Conformal, but I couldn't find reference to it in the code. Is it currently missing? |
Thank you for the PR @tcarion !
That is right. We need to implement the formula first, in order to attach the correct CRS type to the EPSG code instead of the generic The formula is well-documented in the link shared, but I would make sure they match the formulas in the official EPSG guide. Do you think you have some time to work on this new |
Sure, I can try to help! Do you think I should do this here or rather create another PR? |
Another PR would be great. That way we can focus the review on the formulas
and behavior. You could leave this PR open and rebase later after the
formula is available.
Em qua., 30 de abr. de 2025, 09:56, Tristan Carion ***@***.***>
escreveu:
… *tcarion* left a comment (JuliaEarth/CoordRefSystems.jl#263)
<#263 (comment)>
Sure, I can try to help!
Do you think I should do this here or rather create another PR?
—
Reply to this email directly, view it on GitHub
<#263 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZQW3NJNZTE3O76HWQTK6T24DB7DAVCNFSM6AAAAAB4FNNMLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBRHA4DMOJXGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@tcarion I believe we can map the new CRS type to the EPSG code now 🙂 |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #263 +/- ##
==========================================
- Coverage 91.90% 91.85% -0.06%
==========================================
Files 40 40
Lines 1754 1755 +1
==========================================
Hits 1612 1612
- Misses 142 143 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
src/get.jl
Outdated
@@ -90,6 +90,7 @@ end | |||
@crscode EPSG{27700} shift(TransverseMercator{0.9996012717,49.0°,OSGB36}, lonₒ=-2.0°, xₒ=400000.0m, yₒ=-100000.0m) | |||
@crscode EPSG{28355} shift(TransverseMercator{0.9996,0.0°,GDA94}, lonₒ=147.0°, xₒ=500000.0m, yₒ=10000000.0m) | |||
@crscode EPSG{29903} shift(TransverseMercator{1.000035,53.5°,Ire65}, lonₒ=-8.0°, xₒ=200000.0m, yₒ=250000.0m) | |||
@crscode EPSG{31370} shift(LambertConic{90.0°,51.1667°,49.8333°, RNB72}, lonₒ=4.3675°, xₒ=150000m, yₒ=5400088m) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The table of parameters in the EPSG database is the following:
I believe we should add the .013
decimal values to xₒ
and the .438
decimal values to yₒ
given the sensitivity of these formulas and potential error propagation.
It is unfortunate that other parameters are given in DMS. Could you please elaborate on the method used to convert to decimals?
For the parameters, I changed them to be the same as the projstring given by proj:
Do you think I should precise this in the comments? Also, I would like to add the transformation from BD72 to WGS84 in |
Perhaps a short comment explaining the choice can help future contributors. We can explain that the EPSG database shows parameters in DMS, and because of that we opted for the C PROJ parameters.
That could be done in a separate PR for better review. |
reference: https://epsg.org/crs_31370/BD72-Belgian-Lambert-72.html