There are several cases where EPSG:4326 is assumed and parameter values are not converted. In some cases, returned values are in EPSG:4326 but not documented introducing the possibility of creating problems
Details
By adding documentation and an EPSG parameter, introduced problems when working with non-EPSG:4326 coordinate systems can be minimized
Completion Criteria
[ ] changes made as described under spatial.py of ticket drone-pipeline/#37 (see References below)
Tags: EPSG, Coordinate System, Spatial Reference
Description
There are several cases where EPSG:4326 is assumed and parameter values are not converted. In some cases, returned values are in EPSG:4326 but not documented introducing the possibility of creating problems
Details
By adding documentation and an EPSG parameter, introduced problems when working with non-EPSG:4326 coordinate systems can be minimized
Completion Criteria
References: https://app.zenhub.com/workspaces/ua-ag-data-science-5a57a3198339f11ba1c85775/issues/terraref/drone-pipeline/37 https://app.zenhub.com/workspaces/ua-ag-data-science-5a57a3198339f11ba1c85775/issues/terraref/drone-pipeline/55