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

[Suggestion] Universal Transverse Mercator Projection #77

Closed
LexSong opened this issue Apr 5, 2020 · 4 comments
Closed

[Suggestion] Universal Transverse Mercator Projection #77

LexSong opened this issue Apr 5, 2020 · 4 comments

Comments

@LexSong
Copy link
Contributor

LexSong commented Apr 5, 2020

Wikipedia: Universal Transverse Mercator

The UTM system divides the Earth into 60 zones, each 6° of longitude in width.
The amount of distortion is held below 1 part in 1,000 inside each zone.

I wrote a script to demonstrate what it looks like if we put all the zones together into one single map:
world

Each zone is 668,224m east to west, 20,000km south to north, or 41,764 by 1,250,000 chunks in Minecraft. I think it's an interesting alternative way to map the whole world while keeping the distortion minimal. The boundaries between the zones will be an issue. However, we should be able to config what zone each chunk should belong to, and to put boundaries into oceans or deserts, for example.

@orangeadam3
Copy link
Owner

Any projection needs to be a bijective mapping (not having duplicate locations) and in terms of overall distortion, this seems fairly similar to equirectangular. Look at the size of Antarctica. There is always distortion, some maps are just better at hiding it.

@LexSong
Copy link
Contributor Author

LexSong commented Apr 5, 2020

Locally distortion should be minimal. Just look at the size of Iceland, British Isles, and Svalbard. Globally the map would look like equirectangular projection. However, we duplicate high latitude regions instead of distorting them.

We could avoid duplication and just filling the gaps with oceans, but I would argue that it may actually look worse:
Image

I don't see bijective mapping is an issue here. Each zone should be a bijective mapping and we could easily determine the zone number by checking the longitude.

@orangeadam3
Copy link
Owner

It does need to be bijective because a reverse function is also required. You are welcome to fork and try to implement the version with oceans filling the gaps. Projections are just child-classes of GeographicProjection (I could give you more details if you are interested). I can't promise bte would adopt it but I would be happy to add it as an option to my mod.

@LexSong
Copy link
Contributor Author

LexSong commented Apr 6, 2020

Close this issue as #82 is merged

@LexSong LexSong closed this as completed Apr 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants