Skip to content

Home

Jump to bottom
Huidae Cho edited this page May 31, 2021 · 26 revisions

Welcome to the ProjPicker wiki!

Project workflow

The project started on May 5, 2021 and will end in July 31, 2021.

  1. Understand the database proj.db
  2. Extract all bboxes from proj.db
  3. Create a new spatialite database that contains all densified bboxes (number of points as a parameter).
    • Created a sqlite3 database because bboxes are rectangular in lat/long
  4. Create spatial indexing
    • rtree-oop: Used the rtree module, but not sure how it handles reversed west and east cross the antimeridian
  5. Implement the reverse intersection search from a pair of lat/long to a list of selected densified bboxes
    • Not needed because bboxes are rectangular in lat/long
  6. Return all coordinate systems that contain the input lat/long
    • rtree-oop: Supports point intersection
    • main: Supports points, polylines, polygons, and bounding boxes within operations
  7. Implement GUIs
    • ArcGIS Pro Toolbox
    • Web
    • Desktop

If we have more time,

  1. Do research and find major agencies and products
  2. Relate coordinate systems with this information
  3. Output this information with selected coordinate systems in step 6 above

Future ideas

  1. Heuristic search for a coordinate system using non-lat/long coordinates from an unspecified coordinate system and approximate location names? How can we find that coordinate system?

Discussions

https://github.com/OSGeo/grass/issues/1253#issuecomment-776849517

WKT2 has a optional EXTENT::BBOX attribute -- "the geographic bounding box is an approximate description of location". For a given CRS, it shouldn't be too complicated to implement a qgis-like solution. The other way around, all CRS' for a given coordinate, is more complicated as you need some kind of searchable database for this. There is a SE post on this topic, see the section "EPSG.io" for possible database solution.

Clone this wiki locally