-
Notifications
You must be signed in to change notification settings - Fork 185
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
How to make generated terrain consistently square? #62
Comments
Hi, thanks for sharing this.
After reviewing code, I think, this can be done in a relatively simple way. More specifically, we can clip the generated terrain along |
Sweet! I'm delighted to hear that. I was able to tweak the fetch code to always return more tiles to fill in the square if there were only 2 tiles returned, but that's inefficient and has been resulting in too-large terrain that doesn't focus on my core area of focus. I think I just don't have the three-js chops to figure out how to do that clipping. Really appreciate it and interested to see what the solution looks like. |
With live - https://w3reality.github.io/three-geo/examples/clip/index.html |
Hiya! I've been a heavy user of three-geo for a while, and overall love it— I have one thing that I've been battling against for a while and am having trouble wrapping my head around.
I realize three-geo works in tiles. I'm visualizing GPS tracks, which can sometimes cross multiple tiles. When this happens, I usually wind up with a rectangular terrain object, like this:
What I really want is for my generated terrain to ALWAYS be perfectly square. In an ideal world, I would be able to clip the terrain to a size irrespective of tile boundaries. I realize that may be difficult, and would settle for the ability to force additional tiles to download to complete a square.
Any advice? Thank you!
The text was updated successfully, but these errors were encountered: