Merge #1311 into master
This commit is contained in:
@@ -25,8 +25,8 @@ Background Info
|
||||
===============
|
||||
|
||||
The Overviewer's task is to take Minecraft worlds and render them into a set of
|
||||
tiles that can be displayed with a Google Maps interface. This section goes over
|
||||
how Minecraft worlds work and are stored.
|
||||
tiles that can be displayed with a Leaflet interface. This section goes over how
|
||||
Minecraft worlds work and are stored.
|
||||
|
||||
A Minecraft world extends indefinitely along the two horizontal axes, and are
|
||||
exactly 256 units high. Minecraft worlds are made of voxels (volumetric pixels),
|
||||
@@ -455,12 +455,12 @@ quickly become too much data to handle at once. (Early versions of the
|
||||
Overviewer did this, but the large, unwieldy images quickly motivated the
|
||||
development of rendering to individual tiles).
|
||||
|
||||
Hence choosing a technology like Google Maps, which draws small tiles together
|
||||
to make it look like one large image, lets rendering even the largest worlds
|
||||
possible. The Overviewer can draw each tile separately and not have to load the
|
||||
entire map into memory at once. The next sections describe how to determine
|
||||
which chunks to render in which tiles, and how to reason about tile ↔ chunk
|
||||
mappings.
|
||||
Hence choosing a technology like Google Maps or Leaflet, which draws small
|
||||
tiles together to make it look like one large image, lets rendering even the
|
||||
largest worlds possible. The Overviewer can draw each tile separately and not
|
||||
have to load the entire map into memory at once. The next sections describe
|
||||
how to determine which chunks to render in which tiles, and how to reason
|
||||
about tile ↔ chunk mappings.
|
||||
|
||||
Tile Layout
|
||||
-----------
|
||||
|
||||
@@ -19,10 +19,10 @@ supporting mod blocks is not trivial.
|
||||
Can I view Overviewer maps without having an internet connection?
|
||||
-----------------------------------------------------------------
|
||||
|
||||
Not at the moment. The Overviewer relies on the Google maps API to display
|
||||
maps, which your browser needs to load from Google. However, switching away
|
||||
from Google Maps is something that will most likely be looked into in the
|
||||
future.
|
||||
Yes, absolutely. The Overviewer switched away from the Google Maps API and
|
||||
now uses Leaflet. All files which Overviewer needs are included in the output,
|
||||
so even if you have no internet connection, you will still be able to view the
|
||||
map without any issues.
|
||||
|
||||
When my map expands, I see remnants of another zoom level
|
||||
---------------------------------------------------------
|
||||
|
||||
@@ -19,7 +19,7 @@ Introduction
|
||||
============
|
||||
The Minecraft Overviewer is a command-line tool for rendering high-resolution
|
||||
maps of Minecraft worlds. It generates a set of static html and image files and
|
||||
uses the Google Maps API to display a nice interactive map.
|
||||
uses Leaflet to display a nice interactive map.
|
||||
|
||||
The Overviewer has been in active development for several years and has many
|
||||
features, including day and night lighting, cave rendering, mineral overlays,
|
||||
@@ -64,7 +64,7 @@ Features
|
||||
|
||||
* Choose from four rendering angles.
|
||||
|
||||
* Generates a Google Maps powered map!
|
||||
* Generates a Leaflet powered map!
|
||||
|
||||
* Runs on Linux, Windows, and Mac platforms!
|
||||
|
||||
|
||||
Reference in New Issue
Block a user