@@ -96,7 +96,6 @@ Please report bug at <seb.marque@free.fr>.

   * multikey for every part of the device (actually only power on)

 * ![][0%] (TODO list, unsorted)

   * CDI/GPS: scale depending of the flight phase

-  * recenter the MFD depending of EIS width

   * Alerts

   * Flight planning (MFD)

   * Inset Map (PFD)

@@ -114,7 +113,8 @@ Please report bug at <seb.marque@free.fr>.

   * many more...

 # Installation

-Somewhere in the XML configuration of your aircraft, put only few lines

+Just `git clone https://sebmarque.hd.free.fr/git/seb/zkv1000` in your favorite Instrumentation-3d dir.  

+Then somewhere in the XML configuration of your aircraft, put only few lines as described below

 ## Create the `zkv1000` Nasal namespace

 In the `<nasal>` place of your aircraft configuration

@@ -146,8 +146,10 @@ To tells the zkv1000 which kind of engines equip your aircraft, and the associat

           <type>single-prop</type>

         </eis>

-Defaults to `none`, available entries are the `.nas` files located in `Nasal/EIS/` directory.

-If you want to add yours, just copy the `Systems/EIS/single-engine.svg`, modify it to fit your needs, and refer to it in a function named `displayClass.showEIS`, another very important function is `displayClass.updateEIS` (example in [zkv1000/Nasal/EIS/single-engine.nas](Nasal/EIS/single-engine.nas))

+Defaults to `none`, available entries are the `.nas` files located in `Nasal/EIS/` directory.  

+If you want to add yours, just copy the `Systems/EIS/single-prop.svg`, modify it to fit your needs, and refer to it in a function named `displayClass.showEIS`, another very important function is `displayClass.updateEIS` (example in [Nasal/EIS/single-prop.nas](zkv1000/Nasal/EIS/single-prop.nas))

+

+No matter of the EIS width, as the map size and center are computed relative to the EIS width automatically.

 ### Angle Of Attack (AOA)

 You can specify the stall AoA in order to display it in the dedicated display.

@@ -157,9 +159,9 @@ You can specify the stall AoA in order to display it in the dedicated display.

           <approach-aoa>4</approach-aoa>

         </alerts>

-Values are in degrees.

-If `<stall-aoa>` is not specified or equals to 0 (zero) the AOA display won't be accessible.

-The `<approach-aoa>` is optionnal, if present a blue marker is visible on AOA display (not in real GarminP1000)

+* Values are in degrees.

+* If `<stall-aoa>` is not specified or equals to `0` (zero) the AOA display won't be accessible.

+* The `<approach-aoa>` is optionnal, if present a blue marker is visible on AOA display (not in real GarminP1000)

 ## 3D models

 In the definition of your flightdeck (here are the values for the installation in the Lancair 235 in which I develop the device)

@@ -190,6 +192,23 @@ Actually there are only two "types of display": MFD or PFD, which is known by th

 Other devices as keyboard or non-display can also exists, as long as they don't have a `status` property...

 Not sur I'm clear on this point though :)

+## Map tiles origin

+By defaults the maps tiles come from `https://maps.wikimedia.org`, type `osm-intl` (please read [https://www.wikimedia.org/wiki/Maps]()), but you can choose your favorite one if you've got one. I've tested `opentopomap.org` and `thunderforest.com` (my favourite).

+You can tell the zkv1000 the tile server, type and eventually apikey by using `--prop:` option while starting FlightGear session:

+

+In case of apikey (or whatever added at the en of the URL):

+

+        --prop:/sim/online-tiles-server=tile.thunderforest.com

+        --prop:/sim/online-tiles-type=landscape

+        --prop:/sim/online-tiles-apikey=?apikey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

+

+or if there is no type, just use type `/`:

+

+        --prop:/sim/online-tiles-server=a.tile.opentopomap.org

+        --prop:/sim/online-tiles-type=/

+

+The only used protocol is `https` (check Nasal/map.nas).

+

 ## Switch it up

 You can use the multikey (souvenirs, thanks to Melchior having that much expended this feature years ago :)) service by typing:

 `:zo`