-
Notifications
You must be signed in to change notification settings - Fork 152
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
[FEA] High-accuracy re-projection #55
Comments
High accuracy coordinate projection uses high precision formulae, iterative (in case of E/N to Lat/Lon), to provide surveying & civil engineering quality coordinate conversion. It is used in conjunction with transformations where necessary. These formulae take into account the eccentricity of the Earth and other factors. GIS systems, and many off the shelf Python libraries, use simpler approximate formulae for speed. These are ok for most purposes such as overview maps (e.g. election results) but in UK they have an RMS error of +/- 7m (23 ft) and can be up to 20m (70ft) out in places. In my work I am labelling satellite imagery from ESA and NASA, for deep learning models, which uses the UTM coordinate system combined with labels from UK surveys that are in the OSGB36 BNG system. I need high accuracy to ensure that the labels are accurately placed on the images for object detection and image classification. These 2 guides explain more with worked examples. Although written for UK, the techniques work for Transverse Mercator type east/north coordinate systems. A_Guide_to_Coordinate_Systems_in_Great_Britain.pdf Transformations_and_OSGM15_User_Guide.pdf For Conical coordinate system used in USA, France, Australia and New Zealand, different formulae area needed. This explains more with formulae: Again, happy to share code. I already have these implemented. |
This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d. |
This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. |
The second ask from @MurrayData. Perhaps you could be more specific?
The text was updated successfully, but these errors were encountered: