-
Notifications
You must be signed in to change notification settings - Fork 7
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
Change camera parameters in the grammar to have meaningful values #17
Comments
I can look into this. Would you like to change the EPSG for the entire project, or just the grammar(and convert it to EPSG:3395 for internal manipulation)? |
Hi @GMMULLER, if we add a coordinate conversion from EPSG:4326 to EPSG:3395 in |
Hey Sajal, sorry for the late reply I didn't see the notification. The idea is to change the EPSG just for the grammar and convert it to 3395 for internal manipulation. I'm not sure if I understand what you mean by adding the conversion to |
I see, by "adding a conversion" I meant inserting a function that converts the EPSG to/from 3395. I'm currently going over the logic flow in GrammarPanel.tsx file, it looks like we can convert the EPSG from the user friendly format to 3395 in applyGrammar. Also, did you mean camera.ts at the end? |
Yep, that is probably the way to go. Sorry I meant camera.ts haha |
Hi @GMMULLER, since the 4326 coordinate system will have only the x and y coordinates, how should the value for the z-coordinate be assigned after converting the input to 3395? |
So the z coordinate is not considered in the conversion. It is in meters so you can just attach it to the output. If the input is (x,y,z) the output will be (x',y',z) |
This is how the camera is currently specified in the grammar:
Even though that is the parameters used internally they should be exposed in a more friendly way to the user. One way to do that, for example, is using lat/long (EPSG:4326) instead of EPSG:3395 for the camera position. Internally the system still manipulates 3395
The text was updated successfully, but these errors were encountered: