Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support workflow for correctly matching the data with a Cesium context #81

Closed
priscavdsluis opened this issue Feb 28, 2024 · 1 comment · Fixed by #82
Closed

Support workflow for correctly matching the data with a Cesium context #81

priscavdsluis opened this issue Feb 28, 2024 · 1 comment · Fixed by #82
Assignees
Labels
new feature New feature request

Comments

@priscavdsluis
Copy link
Collaborator

priscavdsluis commented Feb 28, 2024

The workflow consists of the following:

  1. The user picks a WGS84 x,y, z coordinate (on Google maps for example). The point is the zone of interest.
  2. Internally these points are converted to the coordinate system of the original model (e.g. Amersfoort / RD New + NAP height)
  3. All the xyz-coordinates are shifted (subtracted) with the x-value, y-value and z-value of the point from step 2.

Config example:

	"shift_coordinates": {			--- optional
		"crs_transformation": {      --- optional
			"source_epsg": 7415,
			"target_epsg": 4979
		},
		"shift_x": 51.3,		
		"shift_y": 3.4,
		"shift_z": 40
	},

@priscavdsluis priscavdsluis self-assigned this Feb 28, 2024
@priscavdsluis priscavdsluis added new feature New feature request and removed triage labels Feb 28, 2024
@priscavdsluis
Copy link
Collaborator Author

priscavdsluis commented Mar 26, 2024

Make sure that compound CRS can be used, for example EPSG 32617 (WGS 84 / UTM zone 17N) + EPSG 5703 (NAVD88 height)

Edit: this will be done under #83

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature New feature request
Projects
None yet
1 participant