You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in order to facilitate comparison of spatial extent of metadata records, would be good to reproject the geometries to a common coordinate system, in order to reproject, the CRS information should be parsed. Unfortunately many records use a non conventional method to describe CRS.
extract crs
match CRS to known list of CRS (epsg.io api?)
if no crs is provided, assume 4326
extract bounds
reproject bounds
if projection fails, skip geometry
return projected geometry
Can be set up as a script to run as a CI-CD process, input is a database column, results are written to the same column
The text was updated successfully, but these errors were encountered:
in order to facilitate comparison of spatial extent of metadata records, would be good to reproject the geometries to a common coordinate system, in order to reproject, the CRS information should be parsed. Unfortunately many records use a non conventional method to describe CRS.
Can be set up as a script to run as a CI-CD process, input is a database column, results are written to the same column
The text was updated successfully, but these errors were encountered: