Geolocation in Speckle stream

Making Speckle
, , ,
4

I can see a benefit in the coordsys being stored as a branch level rather than stream level.

Scenario:

  1. User 1 commits geometry to “Main” branch EPSG:27700 Cartesian coordinates (generic CAD in UK)
  2. User 2 receives geometry and aggregates with mapping data and commits to “reprojected” branch as EPSG:3035 (used for GPS in Europe)

Both are correct but the second will have been projected. These are less about translating with a line from one point to another, but simultaneously correct but incompatible branches.

If it is global at a stream level, the shared context is more tenuous.

If it is set (and reset) per commit, that is conceptually burdonsome on the viewer (human or machine)

7 Likes