We have been thinking about geolocation and want to do some development work for it in April. Please let me know what you think and if we’ve missed something.
Unfortunately we have to put our planned dev work for geolocation on the back burner due to higher priority development work that is directly required for our engineering projects
Geolocation in streams improves interoperability because it would enable correct geographic placement of models among different software packages. Next to interoperability, geolocation could support several other use cases, to name a few: portfolio overview of multiple models on a map, carbon calculations (distance to production and site), and structural calculations (load zones).
Initial workflows to focus on
- Revit → QGIS
- Civil3D → QGIS
- Bentley → QGIS
We believe the basic information required to capture the geolocation is:
- Location. There are two options:
- EPSG code (preferred)
- Latitude + Longitude (less precise)
- Offset from location (EPSG / Lat + Long). Offset in xyz + Rotation
- Scale (units)
We are thinking to put the required information in a Speckle geolocation object that is added to the Speckle commit object. (any thoughts on this?)
Clients - sending
We want to start by capturing the geolocation with the senders. Add a checkbox in the stream settings windows to send the geolocation. (should it be turned on / of by default?)
Ideally, we want to let the user define the location within the application itself. Then the connector can retrieve the info and add it to the stream.
If the location is undefined, show a popup with a brief description how to add the geolocation in that specific application.
Clients - receiving
Initially focus on getting the data correctly located in QGIS.