-
Notifications
You must be signed in to change notification settings - Fork 26
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
Position and scale #13
Comments
We had an excellent article on georeferencing and our custom coordinate
system on our old website. Unfortunately the Internet Archive didn't
archive it. I'm trying to figure out if anyone saved a copy.
http://web.archive.org/web/20110727075931/http://www.me-dem.org/index.php?option=com_content&view=category&id=34:mapping-articles&Itemid=33&layout=default
…On Wed, Dec 11, 2019 at 3:36 AM hellricer ***@***.***> wrote:
When you overlay Middle-earth data over the real world, it shows up in
Africa near 0°N 0°W. Moreover, the map seem to be shrunk exactly by half —
one pixel in the 100m DEM covers area of 200x200m on the map. Distances
mentioned in texts as well as scale-bars on maps confirm this as well.
It would be nice to reposition/reproject it to match with Europe better
while keeping the shape of the map intact.
Note that there are several hints from Tolkien and there have been various
attempts to interpret them. Some resources to start:
- Re-reading the Map of Middle-earth: Fan Cartography's Engagement
with Tolkien's Legendarium
<https://scholar.valpo.edu/journaloftolkienresearch/vol6/iss1/4/>
- The consequences of making Middle-earth round
<https://mapsburgh.tumblr.com/post/112701741801/the-consequences-of-making-middle-earth-round>
- Georefencing Middle Earth
<http://gisninja.blogspot.com/2012/12/georeferening-middle-earth.html>
- Some attempts found on reddit: [1]
<https://www.reddit.com/r/lotr/comments/316t5p/i_projected_middleearth_at_the_correct_scale_onto/>,
[2]
<https://www.reddit.com/r/MapPorn/comments/1iqp1a/middle_earth_with_european_countries_at_the_same/>
- Chapter *Round Versus Flat* in The Atlas of Middle-earth by Karen
Wynn Fonstad
Note: I have no idea how to fix this, but I thought we should at least
acknowledge the problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#13>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB4EFB6WOJ2QM6C4O4Q4Z3QYDGEFANCNFSM4JZNRLLA>
.
--
-- Hebrews 2:14-16 Therefore, since the children share in flesh and blood,
He Himself likewise also partook of the same, that through death He might
render powerless him who had the power of death, that is, the devil, *and
might free those who through fear of death were subject to slavery all
their lives.*
|
I've found some posts on Cartographer's Guild which are probably related to this. |
The Middle-Earth map annotations by Tolkien and the illustrator Pauline Baynes which were revealed in 2015 could be a good starting point for placing the locations in the correct places vis-a-vis the real world: This annotation in particular is very interesting: References to latitudes by Tolkien were already known. But this gives us information on the longitude of a location, i.e. that Minas Tirith's longitude is near that of Belgrade. Taking Minas Tirith as the reference point (mapping its latitude to that of Ravenna and its longitude to that of Belgrade), the rest of Middle-Earth can be placed on the map as well, via their relative positions compared to Minas Tirith. |
When you overlay Middle-earth data over the real world, it shows up in Africa near 0°N 0°W. Moreover, the map seem to be shrunk exactly by about half. Distances mentioned in texts and scale-bars on maps confirm this as well.
It would be nice to reposition/reproject it so it matches with Europe better while keeping the shape of the map intact.
There are several hints from Tolkien and there have been various attempts to interpret them. Some resources to start:
Note: I have no idea how to fix this, but I thought we should at least acknowledge the problem.
The text was updated successfully, but these errors were encountered: