<section id="1.1-overview">
<h1><a class="header-anchor" href="#1.1-overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1.1 Overview</h1>
<section id="1.1.1">
<h3><a class="header-anchor" href="#1.1.1">1.1.1</a></h3>
<section class="reference">
<p>Welcome to the Infinite Flight Scenery Editor Manual! It is designed to help new entrants and current Editors with internal procedures, as well as cover the fundamental principles associated with all editing on Infinite Flight. <strong class="red">All Editors are expected to familiarize themselves with this manual and continue to do so during their time with The Scenery Editing Team.</strong></p>
<dl>
<dt>Must</dt>
<dd>The use of <strong class="red">must</strong> or <strong class="red">must not</strong> within this manual is considered <strong>MANDATORY</strong> and strict compliance is <strong>REQUIRED</strong>.</dd>
<dt>Should</dt>
<dd>The use of <strong class="red">should</strong> or <strong class="red">should not</strong> within this manual is considered <strong>ADVISORY</strong> and compliance is <strong>STRONGLY RECOMMENDED</strong>.</dd>
</dl>
</section>
</section>
<section id="1.1.2">
<h3><a class="header-anchor" href="#1.1.2">1.1.2</a></h3>
<section class="reference">
<p>The <a href="/guide" class="documentation-content-link">Infinite Flight User Guide</a> and <a href="https://community.infiniteflight.com/" class="documentation-content-link">IFC Forum</a> are additional tools that Editors <strong class="red">should</strong> utilize.</p>
</section>
</section>
<section id="1.1.3">
<h3><a class="header-anchor" href="#1.1.3">1.1.3</a></h3>
<section class="reference">
<p>Feedback is an essential part in the development &amp; upkeep of the Scenery Editor Manual, and can be submitted using the <a href="https://docs.google.com/forms/d/e/1FAIpQLSc3VbkH_YfBo6qhNZZwMkyMhKqiBc9WGZb79xewe_7LUy7juQ/viewform" class="documentation-content-link">Report Form</a>. Please ensure that you have checked the <a href="https://docs.google.com/spreadsheets/d/1H8fe59TpTjjBnzsOuCK50K25SqtHmZ5KQ2RP-EpHqMI/edit?usp=sharing" class="documentation-content-link">Feedback Status Spreadsheet</a> <strong>BEFORE</strong> submitting a new report to avoid duplicates (you can also check the progress of any reports that you have made using this). Any questions <strong class="red">should</strong> be sent to the Technical Writer (@RAH) via the IFC or the Scenery Editor Discord.</p>
</section>
</section>
<section id="1.1.4-the-goal-of-airport-editing">
<h2><a class="header-anchor" href="#1.1.4-the-goal-of-airport-editing"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1.1.4 The Goal of Airport Editing</h2>
<section class="reference">
<p>Airports are created to enhance the app, and the user experience is the top priority. Performance is a large part of that experience.
The goal is to make airports look as good as possible while preserving performance.
Editing is not a contest to see who can create the highest-detailed airport.
While extreme detail might look impressive in a screenshot, it degrades performance and ultimately hurts the overall user experience.
Every choice made should weigh the desire for detail against its impact on performance.
Remember: less can be more!</p>
</section>
</section>
</section>


1.1 Overview

<section id="1.2-abbreviations">
<h1><a class="header-anchor" href="#1.2-abbreviations"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1.2 Abbreviations</h1>
<section id="1.2.1">
<h3><a class="header-anchor" href="#1.2.1">1.2.1</a></h3>
<section class="reference">
<p>All abbreviations contained within this manual are listed below with their associated definition:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Abbreviation</th>
<th>Definition</th>
</tr>
</thead>
<tbody>
<tr>
<td>AIP</td>
<td>Aeronautical Information Publication</td>
</tr>
<tr>
<td>CLA</td>
<td>Contributor License Agreement</td>
</tr>
<tr>
<td>DM</td>
<td>Direct Message</td>
</tr>
<tr>
<td>FAA</td>
<td>Federal Aviation Administration</td>
</tr>
<tr>
<td>GA</td>
<td>General Aviation</td>
</tr>
<tr>
<td>G/S</td>
<td>Glideslope</td>
</tr>
<tr>
<td>ICAO</td>
<td>International Civil Aviation Organization</td>
</tr>
<tr>
<td>IF</td>
<td>Infinite Flight</td>
</tr>
<tr>
<td>IFC</td>
<td>Infinite Flight Community</td>
</tr>
<tr>
<td>ILS</td>
<td>Instrument Landing System</td>
</tr>
<tr>
<td>IRL</td>
<td>In Real Life</td>
</tr>
<tr>
<td>LLC</td>
<td>Limited Liability Company</td>
</tr>
<tr>
<td>LOC</td>
<td>Localizer</td>
</tr>
<tr>
<td>N/A</td>
<td>Not Applicable</td>
</tr>
<tr>
<td>OR</td>
<td>Official Review</td>
</tr>
<tr>
<td>OSM</td>
<td>Open Street Map</td>
</tr>
<tr>
<td>PR</td>
<td>Peer Review</td>
</tr>
<tr>
<td>RWY</td>
<td>Runway</td>
</tr>
<tr>
<td>SFC</td>
<td>Surface</td>
</tr>
<tr>
<td>UFN</td>
<td>Until Further Notice</td>
</tr>
<tr>
<td>ULD</td>
<td>Unit Load Device</td>
</tr>
<tr>
<td>WIP</td>
<td>Work In Progress</td>
</tr>
<tr>
<td>VC / VCs</td>
<td>Voice Channel / Voice Channels</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>


1.2 Abbreviations

<section id="1.3-aircraft-categories">
<h1><a class="header-anchor" href="#1.3-aircraft-categories"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1.3 Aircraft Categories</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Aircraft categories will be relevant in the process of editing taxiways <em>(see <a href="/guide/scenery-editor-manual/7.-taxiways/7.1-editing-taxiways" class="documentation-content-link">7.1</a> below)</em> and start locations <em>(see <a href="/guide/scenery-editor-manual/8.-start-locations/8.1-editing-start-locations" class="documentation-content-link">8.1</a> below)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="1.3.1">
<h3><a class="header-anchor" href="#1.3.1">1.3.1</a></h3>
<section class="reference">
<p>The following table outlines the different aircraft categories and how they are defined:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Aircraft Category</th>
<th>Wing Span (meters)</th>
<th>Outer Main Gear Wheel Span (meters)</th>
</tr>
</thead>
<tbody>
<tr>
<td>A</td>
<td>&lt; 15</td>
<td>&lt; 4.5</td>
</tr>
<tr>
<td>B</td>
<td>15 but &lt; 24</td>
<td>4.5 but &lt; 6</td>
</tr>
<tr>
<td>C</td>
<td>24 but &lt; 36</td>
<td>6 but &lt; 9</td>
</tr>
<tr>
<td>D</td>
<td>36 but &lt; 52</td>
<td>9 but &lt; 14</td>
</tr>
<tr>
<td>E</td>
<td>52 but &lt; 65</td>
<td>9 but &lt; 14</td>
</tr>
<tr>
<td>F</td>
<td>65 but &lt; 80</td>
<td>14 but &lt; 16</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="1.3.2">
<h3><a class="header-anchor" href="#1.3.2">1.3.2</a></h3>
<section class="reference">
<p>The following table outlines what aircraft within Infinite Flight fall into each aircraft category:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Aircraft Category</th>
<th>Current Aircraft in Infinite Flight</th>
</tr>
</thead>
<tbody>
<tr>
<td>A</td>
<td>CC19, C172, F16, F18S, F22, SPIT, SR22, TBM9</td>
</tr>
<tr>
<td>B</td>
<td>A10, CL35, CRJ2/7, C208, F14, P38</td>
</tr>
<tr>
<td>C</td>
<td>A318/319/320/321, BCS3, B712, B737/738/739, CRJ9/X, DH8D, E175/190</td>
</tr>
<tr>
<td>D</td>
<td>B752, B763, C130, C17, DC10, MD11</td>
</tr>
<tr>
<td>E</td>
<td>A332F/333/339, A346, A359, B742/744, B77L/77W/772, B788/789/78X</td>
</tr>
<tr>
<td>F</td>
<td>A388, B748</td>
</tr>
</tbody>
</table></div></section>
</section>


1.3 Aircraft Categories

10.1 Library

<section id="10.2-selection-and-placement">
<h1><a class="header-anchor" href="#10.2-selection-and-placement"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 10.2 Selection and Placement</h1>
<section id="selecting-and-placing-an-object">
<h2><a class="header-anchor" href="#selecting-and-placing-an-object"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Selecting and Placing an Object</h2>
<section id="10.2.1">
<h3><a class="header-anchor" href="#10.2.1">10.2.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>
<p>Scroll up/down the list on the right of the screen to see the object repository (the &quot;Library&quot; tab <strong class="red">must</strong> be selected)</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Select the object you wish to place by tapping it <strong>(1)</strong></p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Tap in the area of the airport that you want to add the object to (you may have to press and hold), this will place a white cursor <strong>(2)</strong>. Adjust this as required and then tap &quot;Add Object&quot; <strong>(3)</strong></p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>You might need to &quot;freeze&quot; lines and pavements to avoid these being selected when tapping on your screen. To do this tap &quot;Edit &gt; Freeze All Lines / Freeze All Pavements&quot;</p>
</dd>
</dl>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.2.1b.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.2.1b@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.2.2.1b@3x.png 3x" alt="Image 7.2.1.1 - Object Placement" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.2.1.1 - Object Placement</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
</section>
<section id="changing-orientation-of-an-object">
<h2><a class="header-anchor" href="#changing-orientation-of-an-object"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Changing Orientation of an Object</h2>
<section id="10.2.2">
<h3><a class="header-anchor" href="#10.2.2">10.2.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the object by tapping on or near the blue circle that is in the center of the object <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>The circle will turn magenta to indicate it has been selected. If there are multiple objects in close proximity, a list will appear so you can select the object you want</dd>
<dt>Step 3</dt>
<dd>Three circles will appear as well as a compass rose. Tap and hold on the circle <strong>(1)</strong> to move the object or to change height/orientation:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Circle</th>
<th>Function</th>
</tr>
</thead>
<tbody>
<tr>
<td>Center</td>
<td>Will move the object by dragging your finger to the desired location</td>
</tr>
<tr>
<td>Top (just above center circle)</td>
<td>Will adjust the elevation or altitude of the object</td>
</tr>
<tr>
<td>Outer</td>
<td>Will change the orientation of the object by dragging your finger in the direction you want to orientate it to</td>
</tr>
</tbody>
</table></div><p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.3.1b.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.3.1b@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.2.3.1b@3x.png 3x" alt="Image 7.2.2.1 - Changing Object Orientation" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.2.2.1 - Changing Object Orientation</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="copy--pasting-an-object">
<h2><a class="header-anchor" href="#copy--pasting-an-object"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Copy &amp; Pasting an Object</h2>
<section id="10.2.3">
<h3><a class="header-anchor" href="#10.2.3">10.2.3</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the object by tapping on or near the blue circle <strong>(1)</strong> that is in the center of the object <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>The circle will turn magenta to indicate it has been selected. If there are multiple objects in close proximity, a list will appear so you can select the object you want</dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Edit&quot; button <strong>(2)</strong> on the left of the screen and then Copy&quot; button <strong>(3)</strong></dd>
<dt>Step 4</dt>
<dd>Tap in the area of the airport that you want to add the copied object to (you may have to press and hold), this will place a white cursor <strong>(4)</strong>. Adjust this as required and then tap &quot;Paste&quot; <strong>(5)</strong></dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.4.1b.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.4.1b@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.2.4.1b@3x.png 3x" alt="Image 7.2.3.1 - Copy &amp; Pasting an Object" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.2.3.1 - Copy &amp; Pasting an Object</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="deleting-an-object">
<h2><a class="header-anchor" href="#deleting-an-object"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Deleting an Object</h2>
<section id="10.2.4">
<h3><a class="header-anchor" href="#10.2.4">10.2.4</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the object by tapping on or near the blue circle that is in the center of the object <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>The circle will turn magenta to indicate it has been selected. If there are multiple objects in close proximity, a list will appear so you can select the object you want</dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Delete Selection&quot; button <strong>(1)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.5.1b.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.5.1b@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.2.5.1b@3x.png 3x" alt="Image 7.2.4.1 - Deleting an Object" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.2.4.1 - Deleting an Object</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


10.2 Selection and Placement

<section id="10.3-properties">
<h1><a class="header-anchor" href="#10.3-properties"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 10.3 Properties</h1>
<section id="10.3.1">
<h3><a class="header-anchor" href="#10.3.1">10.3.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the object by tapping on or near the blue circle that is in the center of the object <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>The circle will turn magenta to indicate it has been selected <strong>(1)</strong>. If there are multiple objects in close proximity, a list will appear so you can select the object you want</dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Properties&quot; tab <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.3.1.1b.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.3.1.1b@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.3.1.1b@3x.png 3x" alt="Image 7.3.1.1 - Changing Object Properties" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.3.1.1 - Changing Object Properties</figcaption>
        </figure>
      </p>
<dl>
<dt>Step 4</dt>
<dd>You can then adjust the following properties:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Scale</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the scale of the object</td>
<td>Really useful for making objects match in size what you see from external sources (e.g. lighting AC units and blast deflectors etc.). The scaling on jet bridges <strong class="red">must not</strong> be changed</td>
</tr>
<tr>
<td>Orientation</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the orientation of the object</td>
<td></td>
</tr>
<tr>
<td>Animations</td>
<td>This will show if an object (such as a jetbridge) has built in animations</td>
<td></td>
</tr>
<tr>
<td>Latitude / Longitude</td>
<td>Current latitude/longitude of the object</td>
<td></td>
</tr>
<tr>
<td>Altitude</td>
<td>This shows the current altitude (in meters) of the object. Tap the number and then enter in a new value to adjust this</td>
<td>Always based on the bottom of the surface they you are working from. Can be adjusted here manually or go to &quot;Object &gt; Auto Altitude&quot; if you're doing layering for example</td>
</tr>
<tr>
<td>Name</td>
<td>You can name the object using this field</td>
<td></td>
</tr>
</tbody>
</table></div></section>
</section>
</section>


10.3 Properties

<section id="10.4-technical-locations">
<h1><a class="header-anchor" href="#10.4-technical-locations"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 10.4 Technical Locations</h1>
<section id="10.4.1">
<h3><a class="header-anchor" href="#10.4.1">10.4.1</a></h3>
<section class="reference">
<p>For the location of runways, localizers, glideslopes and other important objects, make maximum use of airport charts <em>(see <a href="/guide/scenery-editor-manual/3.-getting-started/3.1-first-steps#3.1.1" class="documentation-content-link">3.1.1</a> above)</em> and satellite imagery to ensure accurate placement.</p>
</section>
</section>
<section id="localizer">
<h2><a class="header-anchor" href="#localizer"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Localizer</h2>
<section id="10.4.2">
<h3><a class="header-anchor" href="#10.4.2">10.4.2</a></h3>
<section class="reference">
<p>The primary source for placement <strong class="red">should</strong> be satellite images as there may be variations, however the distances below may help with placement:</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/localizer.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/localizer@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/localizer@3x.png 3x" alt="Image 7.4.2.1 - Localizer Location" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.4.2.1 - Localizer Location</figcaption>
        </figure>
      </p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Localizer</th>
<th>Details</th>
</tr>
</thead>
<tbody>
<tr>
<td>When</td>
<td>Only when the airport has an ILS and/or LOC-Only approach</td>
</tr>
<tr>
<td>Where</td>
<td>Placed 1000ft from the runway threshold (opposite end to the ILS/LOC-Only approach - e.g. so if the ILS is for RWY36, the antenna would be at the end of RWY18) - take note that the threshold might be displaced, so it is 1000ft from the white piano key markings, not 1000ft from the concrete!</td>
</tr>
<tr>
<td>Orientation</td>
<td>As a rule of thumb, place the antenna so that it is perpendicular to the runway with the electrical box side facing away from the runway</td>
</tr>
</tbody>
</table></div><blockquote>
<p>The location of an additional red/white electrical box can be added but their locations vary significantly, if you can spot it on google maps or in some airport pictures that would be your best bet but it tends to be to one side of the LOC antenna and usually there is a bit of distance between them (i.e. not right next to each other like the G/S antenna)</p>
</blockquote>
</section>
</section>
</section>
<section id="glideslope">
<h2><a class="header-anchor" href="#glideslope"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Glideslope</h2>
<section id="10.4.3">
<h3><a class="header-anchor" href="#10.4.3">10.4.3</a></h3>
<section class="reference">
<p>The primary source for placement <strong class="red">should</strong> be satellite images as there may be variations, however the distances below may help with placement:</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/glideslope.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/glideslope@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/glideslope@3x.png 3x" alt="Image 7.4.3.1 - Glideslope Location" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.4.3.1 - Glideslope Location</figcaption>
        </figure>
      </p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Glideslope</th>
<th>Details</th>
</tr>
</thead>
<tbody>
<tr>
<td>When</td>
<td>Only when the airport has an ILS approach</td>
</tr>
<tr>
<td>Where</td>
<td>Placed 750 - 1250ft from the runway threshold (this time the approach end - e.g. if the ILS is for RWY36, it would be placed 750 - 1250ft from the threshold of RWY36) and between 250 - 650ft from the runway centerline (most of the time the location coincides with abeam the main touchdown zone markings) - again, have a look on google maps, if you zoom in you'll probably see which side it is on and what it is in-line with in terms of runway markings</td>
</tr>
<tr>
<td>Orientation</td>
<td>Place the antenna so that the white/grey aerials are facing the landing aircraft (see image below)</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Place a red/white electrical box behind the G/S antenna</p>
</blockquote>
</section>
</section>
</section>
<section id="landing-guidance-system-papi">
<h2><a class="header-anchor" href="#landing-guidance-system-papi"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Landing Guidance System (PAPI)</h2>
<section id="10.4.4">
<h3><a class="header-anchor" href="#10.4.4">10.4.4</a></h3>
<section class="reference">
<p>The Landing Guidance System is several lights that visually indicate the glidepath, this is used by the pilot to maintain the glideslope in the final stages of the landing. They are located close to the touchdown zone of the runway, follow the below steps to configure the PAPIs correctly:</p>
<dl>
<dt>Step 1</dt>
<dd>Add the Landing Guidance System object <em>(see <a href="/guide/scenery-editor-manual/10.-objects/10.2-selection-and-placement#10.2.1" class="documentation-content-link">10.2.1</a> above)</em></dd>
<dt>Step 2</dt>
<dd>The lights <strong class="red">must</strong> be adjusted so that they are in-line with the landing runway, this can be done by either using the circles <em>(see <a href="/guide/scenery-editor-manual/10.-objects/10.2-selection-and-placement#10.2.2" class="documentation-content-link">10.2.2</a> above)</em> or within the &quot;Properties&quot; tab (by either using the slider or &quot;+/-&quot; symbol)</dd>
<dt>Step 3</dt>
<dd>As well as this, the following properties must be adjusted:</dd>
</dl>
<ul>
<li>Runway Identifier (<strong class="red">must</strong> match the runway number)</li>
<li>Guidance Type (see Step 4)</li>
<li>Glideslope (see Step 5)</li>
</ul>
<dl>
<dt>Step 4</dt>
<dd>For the Guidance Type, this <strong class="red">must</strong> be changed dependant on the location of the PAPI (i.e. on the left or right side of the runway) and is shown below:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Guidance Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>VASI</td>
<td>TBD</td>
</tr>
<tr>
<td>PAPI4L</td>
<td>2 lights next to each other in a row, only to be used on the left side of the runway (if applicable)</td>
</tr>
<tr>
<td>PAPI4R</td>
<td>2 lights next to each other in a row, only to be used on the right side of the runway (if applicable)</td>
</tr>
<tr>
<td>Space Shuttle PAPI</td>
<td>Not Used</td>
</tr>
<tr>
<td>Tri Color VASI</td>
<td>TBD</td>
</tr>
<tr>
<td>Runway Guard</td>
<td>Not Used</td>
</tr>
</tbody>
</table></div><dl>
<dt>Step 5</dt>
<dd>The glideslope, this <strong class="red">must</strong> be changed to match the glideslope angle used IRL although by default, this is usually 3 degrees</dd>
</dl>
</section>
</section>
</section>
<section id="vor">
<h2><a class="header-anchor" href="#vor"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> VOR</h2>
<section id="10.4.5">
<h3><a class="header-anchor" href="#10.4.5">10.4.5</a></h3>
<section class="reference">
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>VOR</th>
<th>Details</th>
</tr>
</thead>
<tbody>
<tr>
<td>When</td>
<td>Only when the airport has a <strong>co-located</strong> VOR (i.e. a VOR within the airport boundaries)</td>
</tr>
<tr>
<td>Where</td>
<td>You will need to look at charts to work out roughly where the VOR is located, I would then go onto google maps and zoom in on that location (using the satellite option) to work out the exact location, you will also be able to tell from this if it is a large or small one (large: it's bigger than the other one and has loads of antenna coming out from the center - small: much more compact and does not have as many antenna sticking out)</td>
</tr>
<tr>
<td>Orientation</td>
<td>I don't think anyone would really notice so I wouldn't worry about this!</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>
<section id="holding-point-lights">
<h2><a class="header-anchor" href="#holding-point-lights"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Holding Point Lights</h2>
<section id="10.4.6">
<h3><a class="header-anchor" href="#10.4.6">10.4.6</a></h3>
<section class="reference">
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/holding-point-lights.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/holding-point-lights@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/holding-point-lights@3x.png 3x" alt="Image 7.4.5.1 - Holding Point Light Location" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.4.5.1 - Holding Point Light Location</figcaption>
        </figure>
      </p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Holding Point Lights</th>
<th>Details</th>
</tr>
</thead>
<tbody>
<tr>
<td>When</td>
<td>At <em>most</em> airports</td>
</tr>
<tr>
<td>Where</td>
<td>Each side of a runway holding point in-line with the yellow holding point lines</td>
</tr>
<tr>
<td>Orientation</td>
<td>The lights need to be facing the aircraft, not the runway!</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>
<section id="tower-view-points">
<h2><a class="header-anchor" href="#tower-view-points"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Tower View Points</h2>
<section id="10.4.7">
<h3><a class="header-anchor" href="#10.4.7">10.4.7</a></h3>
<section class="reference">
<p>Selecting different cameras as a pilot or controller can be done as shown in the <a href="/guide/getting-started-guide/pilot-user-interface/cameras" class="documentation-content-link">Getting Started Guide</a>. The ATC Tower view is created by adding a &quot;View Point&quot; <em>(see <a href="/guide/scenery-editor-manual/10.-objects/10.2-selection-and-placement#10.2.2" class="documentation-content-link">10.2.2</a> above)</em>.</p>
</section>
</section>
<section id="10.4.8">
<h3><a class="header-anchor" href="#10.4.8">10.4.8</a></h3>
<section class="reference">
<p>Once the view point has been added, the view point <strong class="red">must</strong> be placed within the centre of the 3D tower object. If there are multiple towers, a view point <strong class="red">must</strong> be added for every tower.</p>
<blockquote>
<p>Only the first viewpoint in the object list is selected in-app and so that first view point added must be placed in the &quot;main&quot; ATC Tower</p>
</blockquote>
</section>
</section>
<section id="10.4.9">
<h3><a class="header-anchor" href="#10.4.9">10.4.9</a></h3>
<section class="reference">
<p>With every view point added, Editors <strong class="red">must</strong> change the camera view <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.5" class="documentation-content-link">2.1.5</a> above)</em> to check that the view point is located correctly within the tower. The altitude of the view point can be changed to ensure that it is at the correct height to match the view point of the tower itself <em>(see <a href="/guide/scenery-editor-manual/10.-objects/10.3-properties#10.3.1" class="documentation-content-link">10.3.1</a> above)</em>.</p>
</section>
</section>
</section>
<section id="top-tips">
<h2><a class="header-anchor" href="#top-tips"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Top Tips</h2>
<section id="10.4.10">
<h3><a class="header-anchor" href="#10.4.10">10.4.10</a></h3>
<section class="reference">
<ul>
<li>Have a look online to see if you can find airport images that will help with object placement</li>
<li>Look up the charts for an airport, in particular the ground charts as these will often show the location of windsock(s), the tower(s), cargo area(s) and fire station(s)</li>
<li>Using multiple satellite maps for cross-referencing</li>
<li>The tips above on localizer and glideslope locations are for standard approaches ONLY. Places like LOWI are a special case - if in doubt, just ask!</li>
</ul>
</section>
</section>
</section>
</section>


10.4 Technical Locations

<section id="10.5-model-lines">
<h1><a class="header-anchor" href="#10.5-model-lines"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 10.5 Model Lines</h1>
<section id="10.5.1">
<h3><a class="header-anchor" href="#10.5.1">10.5.1</a></h3>
<section class="reference">
<p>Using the &quot;Model Line&quot; tool, you can add a series of objects along a line. Each line section <strong class="red">must</strong> be at least as long as the object you are adding to it (e.g. if one section of fence is 4m long, the model line needs to be at least 4m) otherwise the object will stick out. Use this to create long portions of fencing.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Whenever you connect buildings/lines/pavements, you <strong class="red">must</strong> use the &quot;Snap&quot; function to avoid gaps and/or overlapping <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.4" class="documentation-content-link">2.1.4</a> above)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="creating-a-model-line">
<h2><a class="header-anchor" href="#creating-a-model-line"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Creating a Model Line</h2>
<section id="10.5.2">
<h3><a class="header-anchor" href="#10.5.2">10.5.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Tap &quot;Object&quot; and then &quot;Create Model Line&quot; <strong>(1)</strong></dd>
<dt>Step 2</dt>
<dd>The properties tab will open on the right of the screen, choose the object you want to use for the model line by tapping &quot;Model Ref Name&quot; and then selecting the desired object from the list</dd>
<dt>Step 3</dt>
<dd>Tap in the area of the airport that you want a model line <strong>(2)</strong>, the first node will be placed</dd>
<dt>Step 4</dt>
<dd>Continue to tap to add nodes <strong>(3)</strong>, a model line will continue to be drawn between the nodes</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.2.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.2.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/9.5.2.1a@3x.png 3x" alt="Image 10.5.2.1 - Creating a Model Line" class="documentation-image-lightbox-link" >
          <figcaption>Image 10.5.2.1 - Creating a Model Line</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="editing-an-existing-model-line">
<h2><a class="header-anchor" href="#editing-an-existing-model-line"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Editing an Existing Model Line</h2>
<section id="10.5.3">
<h3><a class="header-anchor" href="#10.5.3">10.5.3</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the model line by tapping on or near the line, you may have to select the model line from a drop down list if there are multiple items in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Tap the &quot;Modify Shape&quot; button on the right side <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>The line will turn magenta when selected and nodes will appear</dd>
<dt>Step 4</dt>
<dd>By tapping a node it will turn magenta <strong>(2)</strong> to show it has been selected <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 5</dt>
<dd>You can then tap, hold and then drag your finger on the screen to move the node(s) into the desired position</dd>
<dt>Step 6</dt>
<dd>When editing is complete, tap &quot;Modify Shape&quot; to deselect it (you will be unable to edit other model lines without doing this)</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.3.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.3.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/9.5.3.1a@3x.png 3x" alt="Image 10.5.3.1 - Editing Model Lines" class="documentation-image-lightbox-link" >
          <figcaption>Image 10.5.3.1 - Editing Model Lines</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="movingchanging-orientation-of-a-model-line">
<h2><a class="header-anchor" href="#movingchanging-orientation-of-a-model-line"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Moving/Changing Orientation of a Model Line</h2>
<section id="10.5.4">
<h3><a class="header-anchor" href="#10.5.4">10.5.4</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the model line by tapping on or near the model line <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the model line from a drop down box if there are multiple in close proximity. The outline of the model line will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>If you have only just made the model line then just tap &quot;Modify Shape&quot; to deselect this and the model line will be selected</dd>
</dl>
<dl>
<dt>Step 3</dt>
<dd>Two circles will appear as well as a compass rose. Tap and hold on the circle <strong>(2)</strong> to move the model line or to change orientation:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Circle</th>
<th>Function</th>
</tr>
</thead>
<tbody>
<tr>
<td>Center</td>
<td>Will move the model line by dragging your finger to the desired location</td>
</tr>
<tr>
<td>Outer</td>
<td>Will change the orientation of the model line by dragging your finger in the direction you want to orientate it to</td>
</tr>
</tbody>
</table></div><p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.4.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.4.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/9.5.4.1a@3x.png 3x" alt="Image 10.5.4.1 - Moving/Changing Orientation of a Model Line" class="documentation-image-lightbox-link" >
          <figcaption>Image 10.5.4.1 - Moving/Changing Orientation of a Model Line</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="model-line-properties">
<h2><a class="header-anchor" href="#model-line-properties"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Model Line Properties</h2>
<section id="10.5.5">
<h3><a class="header-anchor" href="#10.5.5">10.5.5</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the model line by tapping on or near the model line <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the model line from a drop down box if there are multiple in close proximity. The outline of the model line will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Properties&quot; tab <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.5.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.5.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/9.5.5.1a@3x.png 3x" alt="Image 10.5.5.1 - Changing Model Line Properties" class="documentation-image-lightbox-link" >
          <figcaption>Image 10.5.5.1 - Changing Model Line Properties</figcaption>
        </figure>
      </p>
<dl>
<dt>Step 4</dt>
<dd>You can then adjust the following properties:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Model Ref Name</td>
<td>Tap to select the object you want to be paced with the model line</td>
<td>Only use fences or similar at this time</td>
</tr>
<tr>
<td>Spacing</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the spacing between objects</td>
<td>This needs to be same as the length of the fence segment (i.e. 12.00 for a 12m fence)</td>
</tr>
<tr>
<td>Orientation Offset</td>
<td>Tap the &quot;+/-&quot; symbols to rotate the objects on the line around their individual center</td>
<td>The default offset of 90.0 will ensure fences are joined properly (it is recommended not to change this)</td>
</tr>
<tr>
<td>Center Offset</td>
<td>Tap the &quot;+/-&quot; symbols to shift the objects away from the zero node</td>
<td>This needs to half the length of the fence segment (i.e 3.00 for a 6m fence)</td>
</tr>
<tr>
<td>Latitude / Longitude</td>
<td>Current latitude/longitude of the object</td>
<td></td>
</tr>
<tr>
<td>Altitude</td>
<td>This shows the current altitude (in meters) of the model line. Tap the number and then enter in a new value to adjust this</td>
<td>Altitudes of model lines cannot be changed</td>
</tr>
<tr>
<td>Name</td>
<td>You can name the model line using this field</td>
<td></td>
</tr>
</tbody>
</table></div></section>
</section>
</section>
<section id="deleting-a-model-line">
<h2><a class="header-anchor" href="#deleting-a-model-line"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Deleting a Model Line</h2>
<section id="10.5.6">
<h3><a class="header-anchor" href="#10.5.6">10.5.6</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the model line by tapping on or near the model line <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the model line from a drop down box if there are multiple in close proximity. The outline of the model line will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap &quot;Delete Selection&quot; from the edit buttons <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.6.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/9.5.6.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/9.5.6.1a@3x.png 3x" alt="Image 10.5.6.1 - Deleting a Model Line" class="documentation-image-lightbox-link" >
          <figcaption>Image 10.5.6.1 - Deleting a Model Line</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


10.5 Model Lines

<section id="10.6-objects-dos-and-donts">
<h1><a class="header-anchor" href="#10.6-objects-dos-and-donts"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 10.6 Objects Dos and Don'ts</h1>
<section class="reference">
<p>Below is a table containing what you do need to edit and what you do not edit, while working with buildings</p>
<p>Do and Do Not</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th><i class="icon check circle"></i> DO</th>
<th><i class="icon times circle"></i> DO NOT</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i> Add objects around the airport in realistic setups</td>
<td><i class="icon times circle"></i> Place objects within the gate area (i.e. no objects beyond “the white line”)</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Use the object line tool to add long portions of fencing</td>
<td><i class="icon times circle"></i> Abuse objects to create building shapes or mimic other objects (e.g. don’t sink busses into ground/buildings to fake trains or use fuel tanks to simulate cupolas etc.)</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add aviation related objects outside the airport boundary (e.g. Kai Tak Checkerboard, VORs, Localizer antennas) provided they are properly aligned with the terrain (i.e. no clipping/floating)</td>
<td><i class="icon times circle"></i> Avoid placing ULDs on the ground (i.e. not on a dolly) in gate areas, this is only found in storage/cargo areas</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Use excessive amounts of objects in one place (e.g. don’t create full parking areas with cars, use them sparingly in such areas or large solar panel arrays)</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Add Safedocks at gates/airports that do not have this feature available IRL</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Add objects outside the airport boundary</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Add any types of “easter eggs”</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Use construction equipment for temporary NOTAMS (e.g. anything that will not last more than 2 release cycles)</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Place vehicles in access roadways</td>
</tr>
</tbody>
</table></div></section>
</section>


10.6 Dos and Don'ts

<section id="11.2-stand-guidance">
<h1><a class="header-anchor" href="#11.2-stand-guidance"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 11.2 Stand Guidance</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>You may find it useful to zoom out to ensure that the stand guidance is pointing towards (and in-line with) the start location (in-line is defined as within +/- 5 degrees). The nearest start location (within 60m) that is in-line with the stand guidance, will be paired</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="11.2.1">
<h3><a class="header-anchor" href="#11.2.1">11.2.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Scroll up/down the list on the right of the screen to see the object repository (the &quot;Library&quot; tab <strong class="red">must</strong> be selected)</dd>
<dt>Step 2</dt>
<dd>Select the &quot;Safedock T1&quot; under &quot;Stand Guidance&quot;</dd>
<dt>Step 3</dt>
<dd>Tap in the area of the airport that you want to add the object to (you may have to press and hold), this will place a white cursor. Adjust this as required and then tap &quot;Add Object&quot;</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>You may find it easiest to place the stand guidance at the start location for that stand by tapping the start location (you may have to select the start location from a dropdown list)</dd>
</dl>
<dl>
<dt>Step 4</dt>
<dd>Three circles will appear as well as a compass rose. Tap and hold on circle to move the object or to change height/orientation:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Circle</th>
<th>Function</th>
</tr>
</thead>
<tbody>
<tr>
<td>Center</td>
<td>Will move the object by dragging your finger to the desired location</td>
</tr>
<tr>
<td>Top (just above center circle)</td>
<td>Will adjust the elevation or altitude of the object</td>
</tr>
<tr>
<td>Outer</td>
<td>Will change the orientation of the object by dragging your finger in the direction you want to orientate it to</td>
</tr>
</tbody>
</table></div><dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>The stand guidance <strong class="red">should</strong> be eye level with the aircraft that are designed to park at that stand, and <strong class="red">must</strong> be positioned in the correct location for that stand (this may be on the terminal building or even on a &quot;Generic Pole&quot;)</dd>
</dl>
<dl>
<dt>Step 5</dt>
<dd>The stand guidance <strong class="red">must</strong> be facing the start location, and in the correct orientation (i.e the side with sensors <strong class="red">must</strong> be facing the start location)</dd>
</dl>
</section>
</section>


11.2 Stand Guidance

<section id="11.3-jet-bridge-properties">
<h1><a class="header-anchor" href="#11.3-jet-bridge-properties"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 11.3 Jet Bridge Properties</h1>
<section id="11.3.1">
<h3><a class="header-anchor" href="#11.3.1">11.3.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the jet bridge by tapping on or near it <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the jet bridge from a drop down box if there are multiple items in close proximity. The outline of the jet bridge will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Properties&quot; tab <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/10.3.1.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/10.3.1.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/10.3.1.1a@3x.png 3x" alt="Image 11.3.1.1 - Jet Bridge Properties" class="documentation-image-lightbox-link" >
          <figcaption>Image 11.3.1.1 - Jet Bridge Properties</figcaption>
        </figure>
      </p>
<dl>
<dt>Step 4</dt>
<dd>You can then adjust the following properties for jet bridges in their stowed position (i.e. not connected to an aircraft):</dd>
</dl>
<blockquote>
<p>Animations are not listed below as these <strong class="red">must not</strong> be edited unless it is the height of a jet bridge base <em>(see x below)</em></p>
</blockquote>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Gates</td>
<td>Shows the gates that are assigned to the jet bridge</td>
<td>See 11.4 below</td>
</tr>
<tr>
<td>Stowed Arm Rotation</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the orientation of the jet bridge, it is based on a default position from the base/connector and rotates counter clockwise</td>
<td><strong class="red">Must</strong> be adjusted to avoid collisions</td>
</tr>
<tr>
<td>Stowed Arm Extension</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the stowed length of the jet bridge</td>
<td><strong class="red">Must</strong> be adjusted to avoid collisions</td>
</tr>
<tr>
<td>Stowed Head Rotation</td>
<td>Tap the &quot;+/-&quot; symbols to move the stowed head of the jet bridge</td>
<td><strong class="red">Must</strong> be adjusted to avoid collisions</td>
</tr>
<tr>
<td>Stowed Height</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the default height of the jet bridge when in the stowed position</td>
<td>The height <strong class="red">must</strong> be adjusted so that all aircraft doors that can park at that stand are reachable</td>
</tr>
<tr>
<td>Scale</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the scale</td>
<td>Scale <strong class="red">must not</strong> be changed unless it is to revert the jet bridge to a scale of &quot;1&quot; (<strong class="red">must</strong> be 1 for animations to work)</td>
</tr>
<tr>
<td>Orientation</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the orientation of the jet bridge animation range (shown as a green curved cylinder shape around the jet bridge itself)</td>
<td></td>
</tr>
<tr>
<td>Latitude / Longitude</td>
<td>Current latitude/longitude of the jet bridge</td>
<td></td>
</tr>
<tr>
<td>Altitude</td>
<td>This shows the current altitude (in meters) of the start location</td>
<td><strong class="red">Should not</strong> be changed</td>
</tr>
<tr>
<td>Name</td>
<td>You can name the jet bridge using this field</td>
<td>Not required at this time</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="adjusting-jet-bridge-base-height">
<h2><a class="header-anchor" href="#adjusting-jet-bridge-base-height"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Adjusting Jet Bridge Base Height</h2>
<section id="11.3.2">
<h3><a class="header-anchor" href="#11.3.2">11.3.2</a></h3>
<section class="reference">
<p>The slope of a jet bridge between the base and end is limited (especially an issue if the jet bridge is short), therefore the base height may need to be adjusted to allow all applicable aircraft types that can spawn at that start location. Below is an example of a jet bridge which has not been adjusted to accommodate narrow body aircraft.</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.5.7.1b.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.5.7.1b@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.5.7.1b@3x.png 3x" alt="Image 11.3.2.1 - Jet Bridge Base Too High for Narrow-Body Aircraft" class="documentation-image-lightbox-link" >
          <figcaption>Image 11.3.2.1 - Jet Bridge Base Too High for Narrow-Body Aircraft</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="11.3.3">
<h3><a class="header-anchor" href="#11.3.3">11.3.3</a></h3>
<section class="reference">
<p>To do this, the following steps can be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Select the jet bridge base by tapping on or near the blue circle <strong>(1)</strong> that is in the center of it <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>If there are multiple objects in close proximity, a list will appear so you can select the jet bridge base</dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Properties&quot; tab <strong>(2)</strong> on the right side of the screen and then the &quot;+&quot; symbol next to &quot;Animations&quot; <strong>(3)</strong></dd>
<dt>Step 4</dt>
<dd>A drop down list will appear, tap the &quot;+&quot; symbol next to &quot;Height&quot; <strong>(4)</strong></dd>
<dt>Step 5</dt>
<dd>This will further expand and by tapping this <strong>(5)</strong>, will allow you to change the height of the jet bridge base</dd>
<dt>Step 6</dt>
<dd>Whilst the jet bridge base is still selected (which has the adjusted height) - use the rectangle selection tool <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em> or &quot;Edit &gt; Selection (Add)&quot; to select all remaining jet bridge elements that you want the height adjusted for</dd>
<dt>Step 7</dt>
<dd>Tap &quot;Jet Bridge&quot; and then &quot;Adjust Jet Bridge Alt&quot;</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>Due to a bug with glass jetbridges, using &quot;Adjust Jetbridge Alt.&quot; to connect an end section to a base, the end section will end up 0.060 too low. A workaround is to place the base 0.060 too high, use &quot;Adjust Jetbridge Alt.&quot; and lower the base by 0.060 afterwards.</dd>
</dl>
<dl>
<dt>Step 8</dt>
<dd>The height will be changed for all selected jet bridge elements to the same as the height of the jet bridge base</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.5.6.1c.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.5.6.1c@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.5.6.1c@3x.png 3x" alt="Image 11.3.3.1 - Adjusting Jet Bridge Height" class="documentation-image-lightbox-link" >
          <figcaption>Image 11.3.3.1 - Adjusting Jet Bridge Height</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="a380-gates">
<h2><a class="header-anchor" href="#a380-gates"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> A380 Gates</h2>
<section id="11.3.4">
<h3><a class="header-anchor" href="#11.3.4">11.3.4</a></h3>
<section class="reference">
<p>If the start location has three jet bridges, it will try to join the third jet bridge to door U1L (Upper 1 Left) of the A380. Editors <strong class="red">should</strong> try to raise the base of the jet bridge <em>(see <a href="/guide/scenery-editor-manual/11.-airport-gates/11.3-jet-bridge-properties#11.3.3" class="documentation-content-link">11.3.3</a> above)</em> as well as the stowed height <em>(see <a href="/guide/scenery-editor-manual/11.-airport-gates/11.3-jet-bridge-properties#11.3.1" class="documentation-content-link">11.3.1</a> above)</em> to reduce the angle of the jet bridge when connected to the aircraft door.</p>
</section>
</section>
</section>
</section>


11.3 Jet Bridge Properties

<section id="11.4-jet-bridge-animations">
<h1><a class="header-anchor" href="#11.4-jet-bridge-animations"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 11.4 Jet Bridge Animations</h1>
<section id="11.4.1">
<h3><a class="header-anchor" href="#11.4.1">11.4.1</a></h3>
<section class="reference">
<p>Once the start locations and jet bridges have been added, and the stowed positions of the jet bridges have been adjusted, Editors can move onto adding jet bridge animation. Below are the first steps that <strong class="red">must</strong> be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Check all start locations are named correctly. The following properties <strong class="red">must</strong> be correct before moving onto Step 2:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Property</th>
<th>Entry</th>
</tr>
</thead>
<tbody>
<tr>
<td>Terminal</td>
<td>e.g. Concourse/Terminal/GA/Cargo/Apron/FBO etc. [name/number]</td>
</tr>
<tr>
<td>Name</td>
<td>Gate [alphanumeric/number]*</td>
</tr>
</tbody>
</table></div><p>*<em>Editors <strong class="red">must</strong> ensure that terminal names (e.g. T1) are not included in the &quot;Name&quot; property</em></p>
<dl>
<dt>Step 2</dt>
<dd>Tap the &quot;Auto Assign Gates&quot; button to bind each jet bridge to a stand</dd>
<dt>Step 3</dt>
<dd>Above each jet bridge, it will show the start location(s) the jet bridge is assigned to (e.g. &quot;Terminal 5/Gate 515&quot;)</dd>
<dt>Step 4</dt>
<dd>If this is incorrect, tap the jet bridge required (if not already selected), then &quot;Properties&quot;. Under &quot;General&quot; there is the &quot;Gate&quot; tab, tap this</dd>
<dt>Step 5</dt>
<dd>The gates that are assigned to this jet bridge will be listed, these can be removed by tapping the &quot;-&quot; symbol next to it. If a gate needs to be added, enter the name of the gate by tapping the &quot;+&quot; symbol and then using the format &quot;Terminal Name/Gate Name&quot;</dd>
</dl>
<blockquote>
<p>Sometimes the auto assign function can incorrectly assign the jet bridge to a gate in close proximity that cannot be serviced by that jet bridge and therefore manual adjustment may be required</p>
</blockquote>
<dl>
<dt>Step 6</dt>
<dd>Check all start locations for jet bridges not reaching doors by tapping &quot;Jet Bridges &gt; Check Jet Bridges&quot;</dd>
<dt>Step 7</dt>
<dd>Below each start location, it will show the jet bridge status. The following color codes are used:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Code</th>
<th>Message</th>
</tr>
</thead>
<tbody>
<tr>
<td>&quot;All Airplanes OK&quot; - Green</td>
<td>For any start location that has a jet bridge, this <strong class="red">must</strong> be the code displayed</td>
</tr>
<tr>
<td>&quot;Jet Bridges [Aircraft Type* and Reason]&quot; - Amber</td>
<td>Readjustment of the jet bridge is required as it is unable to reach some doors of the aircraft type(s) listed (partial)</td>
</tr>
<tr>
<td>&quot;Jet Bridges [Aircraft Type* and Reason]&quot; - Red</td>
<td>Readjustment of the jet bridge is required as it is unable to reach any door of the aircraft type(s) listed</td>
</tr>
<tr>
<td>&quot;No Jet Bridges Available&quot; - Grey</td>
<td>Expected if the start location does not have a jet bridge</td>
</tr>
</tbody>
</table></div><p>*<em>No more than 2 aircraft types will ever be shown to avoid clutter</em></p>
<dl>
<dt>Step 8</dt>
<dd>If any start locations are not green (i.e amber or red), you <strong class="red">must</strong> adjust the jet bridges to make the doors reachable <em>(see 11.4.2 below)</em></dd>
<dt>Step 9</dt>
<dd>Check that Airport Properties <em>(see <a href="/guide/scenery-editor-manual/3.-getting-started/3.2-airport-properties#3.2.2" class="documentation-content-link">3.2.2</a> above)</em> has the &quot;Jet Bridges Available&quot; tick box selected (orange tick when selected) by tapping &quot;File &gt; Airport Properties &gt; Jet Bridges Available&quot;</dd>
</dl>
<blockquote>
<p>Jet bridges will not work in flight mode for pilots until this tick box is selected</p>
</blockquote>
</section>
</section>
<section id="adjusting-jet-bridges">
<h2><a class="header-anchor" href="#adjusting-jet-bridges"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Adjusting Jet Bridges</h2>
<section id="11.4.2">
<h3><a class="header-anchor" href="#11.4.2">11.4.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>All jet bridges <strong class="red">must</strong> be checked, adjust any jet bridge that are red, amber or grey (for a start location that has a jet bridge) by first tapping &quot;Jet Bridges&quot; and then &quot;Check Jet Bridges&quot;</dd>
</dl>
<blockquote>
<p>Editors <strong class="red">must</strong> ensure that even jet bridges that are green comply with Step 5 below</p>
</blockquote>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>Tap &quot;Jet Bridges&quot; and then &quot;Freeze Non Jet Bridges&quot; before attempting to move jet bridges, this freezes all other objects so you don't move something else by accident</dd>
</dl>
<dl>
<dt>Step 2</dt>
<dd>Tap the end of the jet bridge <strong>(1)</strong>, a green arc will appear that shows the animation range of the jet bridge <strong>(2)</strong></dd>
</dl>
<blockquote>
<p>The inner green curved line shows the minimum range of the center of the jet bridge rotation head when the jet bridge is fully retracted, and the outer green curved line shows the maximum possible extension of the jet bridge. Aircraft doors have to be within this green area to be reached by a jet bridge</p>
</blockquote>
<dl>
<dt>Step 3</dt>
<dd>In addition to the green arc, three circles as well as a compass rose are displayed. Use the outer circle to change the orientation of the jet bridge (and green arc) by tapping, holding and then dragging your finger on this circle <strong>(3)</strong>. This can be moved until the green arc is in an area that includes all applicable start locations</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.5.2.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.5.2.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.5.2.1@3x.png 3x" alt="Image 11.4.2.1 - Adjusting Jet Bridges" class="documentation-image-lightbox-link" >
          <figcaption>Image 11.4.2.1 - Adjusting Jet Bridges</figcaption>
        </figure>
      </p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>The &quot;Rotate Range +90&quot; button can be used to move the green arc by 90 degrees while the orientation of the stowed jet bridge will stay the same (e.g. this can be useful when the green arc is covering more of the terminal than the gate area)</dd>
</dl>
<dl>
<dt>Step 4</dt>
<dd>Re-tap &quot;Jet Bridges&quot; and then &quot;Check Jet Bridges&quot; and check to see that the locations are now shown in green <strong>(4)</strong></dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.5.2.3.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.5.2.3@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.5.2.3@3x.png 3x" alt="Image 11.4.2.2 - Check Jet Bridges" class="documentation-image-lightbox-link" >
          <figcaption>Image 11.4.2.2 - Check Jet Bridges</figcaption>
        </figure>
      </p>
<dl>
<dt>Step 5</dt>
<dd>Editors <strong class="red">must</strong> ensure that the green arc covers as much of the start location as possible <strong>(5)</strong>. If more of the green arc is in an unusable position (such as the terminal), it could limit the jet bridge range <strong>(6)</strong></dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/10.4.2.3a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/10.4.2.3a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/10.4.2.3a@3x.png 3x" alt="Image 11.4.2.3 - Correct Jet Bridge Set-Up" class="documentation-image-lightbox-link" >
          <figcaption>Image 11.4.2.3 - Correct Jet Bridge Set-Up</figcaption>
        </figure>
      </p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/10.4.2.4a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/10.4.2.4a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/10.4.2.4a@3x.png 3x" alt="Image 11.4.2.4 - Incorrect Jet Bridge Set-Up" class="documentation-image-lightbox-link" >
          <figcaption>Image 11.4.2.4 - Incorrect Jet Bridge Set-Up</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
</section>


11.4 Jet Bridge Animations

<section id="12.1-review-and-release-process">
<h1><a class="header-anchor" href="#12.1-review-and-release-process"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 12.1 Review and Release Process</h1>
<section class="reference">
<blockquote>
<p>When uploading a new version of a recently edited airport (i.e tapping &quot;Upload as Draft&quot; or &quot;Upload for Review&quot;), Editors will be required to submit a &quot;changelog&quot; which highlights what has been changed in that version. Changelogs <strong class="red">must</strong> be specific to ensure that it is clear what has been changed (e.g. &quot;Adjusted C19 jetbridge. Changed taxiway line type on Taxiway A&quot;). Additional details can be added to the IFC airport thread if required</p>
</blockquote>
</section>
<section id="12.1.1">
<h3><a class="header-anchor" href="#12.1.1">12.1.1</a></h3>
<section class="reference">
<p>In order to have your airport published in Infinite Flight, you <strong class="red">must</strong> submit your airport for review so it can be checked for compliance with all rules defined in this manual. To assist with Reviewer workload a two stage review process is available as shown below:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Review Type</th>
<th>Description</th>
<th>Who can Review</th>
</tr>
</thead>
<tbody>
<tr>
<td>Peer</td>
<td>A voluntary step in the review process that <strong class="red">should</strong> be done in order to get feedback from fellow Editors</td>
<td>Editor or above</td>
</tr>
<tr>
<td>Official</td>
<td>A mandatory review in which the airport <strong class="red">must</strong> be submitted before it will be included in a release cycle</td>
<td>Reviewer or above</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="12.1.2">
<h3><a class="header-anchor" href="#12.1.2">12.1.2</a></h3>
<section class="reference">
<p>Before submitting for a review, a Scenery Check <strong class="red">must</strong> be completed to ensure that the airport is compliant with the limits put in place (i.e. performance limitations, objects outside the boundary, naming issues/duplicates of gates etc.):</p>
<dl>
<dt>Step 1</dt>
<dd>Tap &quot;File &gt; Scenery Stats &gt; Scenery Check &gt; Check Scenery&quot;</dd>
<dt>Step 2</dt>
<dd>Any errors listed can then be found by tapping on an error and then &quot;Select Items&quot;</dd>
<dt>Step 3</dt>
<dd>You will then be able to see the selected item on the airport and decide if it needs to be changed</dd>
</dl>
</section>
</section>
<section id="peer-review">
<h2><a class="header-anchor" href="#peer-review"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Peer Review</h2>
<section id="12.1.3">
<h3><a class="header-anchor" href="#12.1.3">12.1.3</a></h3>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>In order to upload your airport as a draft or for review, changes have to be made since the last uploaded version (this can be as minor as moving a cone)</dd>
</dl>
<dl>
<dt>Step 1</dt>
<dd>Once an airport is completed, it <strong class="red">must</strong> be uploaded using &quot;File &gt; File Manager &gt; Upload as Draft&quot; <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.2" class="documentation-content-link">2.1.2</a> above)</em>. It can then be submitted for a &quot;peer&quot; review by posting a link to the IFC airport thread in the <em>#request-peer-review</em> Discord channel</dd>
</dl>
<blockquote>
<p>Editors conducting Peer Reviews <strong class="red">must not</strong> take more than 2 airports at any time, and <strong class="red">must</strong> ensure that they have the time available to conduct the review in a timely manner (i.e. time frames of when the review will be done <strong class="red">must not</strong> be mentioned as the Editor is expected to only conduct a Peer Review when they are available). If in doubt, the Editor <strong class="red">should</strong> leave the airport available for review <em>(see <a href="/guide/scenery-editor-manual/1a.-administration/1a.3-editor-rules#1a.3.1" class="documentation-content-link">1A.3.1</a> above)</em></p>
</blockquote>
<dl>
<dt>Step 2</dt>
<dd>Once feedback is received, the Editor can then work on these changes before either re-submitting for another peer review, or for an official review. All feedback related to a review (both peer and official) <strong class="red">must</strong> be conducted in the IFC airport thread to ensure a record is kept</dd>
</dl>
<blockquote>
<p>There is no limit on how many Peer Reviews can be given per airport, however Editors <strong class="red">should</strong> only submit their airport for review when they believe it is complete. If help or guidance is needed before an airport is complete, Editors <strong class="red">should</strong> utilize the <em>#help</em> Discord channel to ask specific questions related to their airport</p>
</blockquote>
</section>
</section>
</section>
<section id="official-review">
<h2><a class="header-anchor" href="#official-review"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Official Review</h2>
<section id="12.1.4">
<h3><a class="header-anchor" href="#12.1.4">12.1.4</a></h3>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>In order to upload your airport as a draft or for review, changes have to be made since the last uploaded version (this can be as minor as moving a cone)</dd>
</dl>
<dl>
<dt>Step 1</dt>
<dd>When the Editor is ready to submit for an &quot;official&quot; review, they can do this by using &quot;File &gt; File Manager &gt; Upload for Review&quot; <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.2" class="documentation-content-link">2.1.2</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Feedback will be given by a Reviewer in the IFC airport thread. If additional changes are required, these <strong class="red">must</strong> be resubmitted following the same process as outlined above. Feedback provided by reviewers is mandatory. If a change is requested, it <strong class="red">must</strong> be implemented for the airport to be considered ready for release.</dd>
<dt>Step 3</dt>
<dd>Once the airport is considered ready by the Reviewer, the airport will be marked as &quot;Ready for Release&quot; and will be included in a release cycle at some point</dd>
</dl>
<blockquote>
<p>Once your airport is &quot;Ready for Release&quot; it will not necessarily be released in the next cycle. This is because other factors also determine what is or isn't included in the release, more information can be found <a href="https://community.infiniteflight.com/t/airport-releases/653276" class="documentation-content-link">here</a></p>
</blockquote>
</section>
</section>
</section>
<section id="navigation-database-update">
<h2><a class="header-anchor" href="#navigation-database-update"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Navigation Database Update</h2>
<section id="12.1.5">
<h3><a class="header-anchor" href="#12.1.5">12.1.5</a></h3>
<section class="reference">
<p>Following an airport being approved and marked as ready for release, some changes may only be visible in-app after the next navigation database update is completed. This is usually at the same time as a release. This applies to:</p>
<ul>
<li>airport boundary</li>
<li>airport elevation</li>
<li>airport mini-map</li>
<li>runway information (such as approach types)</li>
<li>start locations</li>
<li>tower view point</li>
</ul>
<blockquote>
<p>e.g. when the airport boundary is changed, the elevation within this new section will only match the rest of the airport elevation after the navigation database update. This may mean that there will be floating or submerged buildings/objects in this new area</p>
</blockquote>
</section>
</section>
</section>
</section>


12.1 Review and Release Process

12.2 Editor Checklist

<section id="12a.1-overview">
<h1><a class="header-anchor" href="#12a.1-overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 12A.1 Overview</h1>
<section id="12a.1.1">
<h3><a class="header-anchor" href="#12a.1.1">12A.1.1</a></h3>
<section class="reference">
<p>The purpose of the Reviewer Team is to:</p>
<ul>
<li>Assist in the day-to-day operations of the Scenery Editing Team</li>
<li>Provide leadership and/or mentoring to individual Editors</li>
<li>Assign airports to Editors with the rank of Apprentice</li>
<li>Review editing quality via the &quot;Official Review&quot; process*</li>
<li>and Moderate the Scenery Editing Team Discord channel</li>
</ul>
<p>*<em>Reviewers <strong class="red">should not</strong> upload changes on behalf of the editors during the Official Review process without the editors' explicit consent in the interest of the editors' skill improvement and respect towards the editors' work, unless the issues found during the Official Review process are minor, not consistently present, and a new OR cycle for the airport would not be considered reasonable if they were left for the airport's editor to fix. Examples of minor issues are improperly snapped lines, buildings and/or pavements, and lines with 1 or more inaccurate properties. Reviewers are advised to use their judgement regarding the consistency and severity of the issues found proportionally to the size and complexity of the airport subject to review. For example, 3 improperly snapped lines would not be as big of an issue at KLAX, but they would be at a small GA field. If a Reviewer does decide to upload changes on behalf of the editors during the Official Review process, a summary of the changes made, preferably including screenshots, <strong class="red">should</strong> be provided for the sake of respect towards the editors' work.</em></p>
<p>To carry this out, Reviewers will be added to the following channel within Discord:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>#reviewer-info</td>
<td>Day to day posts (such as housekeeping) to be made in this channel by Staff and Moderators only</td>
</tr>
<tr>
<td>#reviewers</td>
<td>This channel is used to facilitate communications between all Reviewers for any purpose deemed necessary</td>
</tr>
<tr>
<td>#review-status</td>
<td>This channel is used to post progress on an airport review (including when it is started, finished, and when the changes are made and subsequently re-reviewed)</td>
</tr>
<tr>
<td>#role-assignments</td>
<td>This channel is used by Airport Moderators and Reviewers to assign and unassign themselves from notifications when a new ticket is created in #help-request <em>(see <a href="/guide/scenery-editor-manual/1a.-administration/1a.1-discord-communication#1A.1.2" class="documentation-content-link">1A.1.2</a> above)</em></td>
</tr>
<tr>
<td>#navigation</td>
<td>This channel is used to track changes made to Infinite Flight's ILS source file, located in a separate GitHub repository</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="12a.1.2">
<h3><a class="header-anchor" href="#12a.1.2">12A.1.2</a></h3>
<section class="reference">
<p>Reviewers are selected by the Airport Moderators based on a number of criteria, including, but not limited to:</p>
<ul>
<li>current standing within the Scenery Editing Team</li>
<li>contributions to the Scenery Editing Team</li>
<li>operational necessity</li>
<li>and/or the ability to assist in internal team affairs within a professional context</li>
</ul>
<blockquote>
<p>Reviewers may be demoted or removed from the Reviewer Team for any reason as deemed by the Airport Moderators (e.g. breach of trust, abuse of power, lack of commitment etc.)</p>
</blockquote>
</section>
</section>
<section id="12a.1.3">
<h3><a class="header-anchor" href="#12a.1.3">12A.1.3</a></h3>
<section class="reference">
<p>Reviewers <strong class="red">must not</strong> make any amendments to an airport that has been submitted for review under the Official Review process. Feedback must be provided to the Editor so that they can make the changes required <em>(see <a href="/guide/scenery-editor-manual/12.-review-and-release/12.1-review-and-release-process#12.1.4" class="documentation-content-link">12.1.4</a> above)</em>.</p>
<blockquote>
<p>It is acceptable to make very small amendments to an airport under the Official Review process if the Reviewer does not deem it necessary to highlight this as feedback to the Editor</p>
</blockquote>
</section>
</section>
</section>


12A.1 Overview

<section id="12a.1-reviewer-admin">
<h1><a class="header-anchor" href="#12a.1-reviewer-admin"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 12A.1 Reviewer Admin</h1>
<section id="how-to-pick-an-airport-to-review">
<h2><a class="header-anchor" href="#how-to-pick-an-airport-to-review"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Pick an Airport to Review</h2>
<section id="12a.1.1">
<h3><a class="header-anchor" href="#12a.1.1">12A.1.1</a></h3>
<section class="reference">
<p>The following procedure outlines how to pick an airport that is awaiting review:</p>
<dl>
<dt>Step 1</dt>
<dd>Go to the <a href="https://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and login using your IFC credentials (if required, login is normally automatic)</dd>
<dt>Step 2</dt>
<dd>From the navigation bar on the left of the screen, select &quot;Airports&quot; under &quot;Scenery Editing&quot;</dd>
<dt>Step 3</dt>
<dd>Select &quot;Waiting for Review&quot; from the top navigation bar</dd>
<dt>Step 4</dt>
<dd>Select the airport you wish to review by tapping on the three dots on the right of the airport and then change the status of the airport by tapping &quot;Mark as In Review&quot;</dd>
</dl>
<blockquote>
<p>Airports are ordered with the oldest airport first. Reviewers <strong class="red">should</strong> always select the oldest airport in the queue when choosing an airport to review (if in doubt, Reviewers <strong class="red">must</strong> raise this with fellow Reviewers and Airport Moderators). The only exceptions to this are when:</p>
<ul>
<li>the Reviewer has limited time available, and there is a smaller airport that could be reviewed within that timeframe, or;</li>
<li>an airport has been resubmitted for review following only minor changes that could quickly be re-reviewed by the same Reviewer</li>
</ul>
</blockquote>
</section>
</section>
</section>
<section id="how-to-review-an-airport">
<h2><a class="header-anchor" href="#how-to-review-an-airport"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Review an Airport</h2>
<section id="12a.1.2">
<h3><a class="header-anchor" href="#12a.1.2">12A.1.2</a></h3>
<section class="reference">
<p>The following procedure outlines the order in which to follow when reviewing an airport:</p>
<dl>
<dt>Step 1</dt>
<dd>Once the airport has been selected, tap the three dots on the right and then &quot;View on Forum&quot;. This will open the current topic for that airport in a new tab. Reviewers <strong class="red">must</strong> ensure that they look at the history (i.e. if any previous reviews have been undertaken by another reviewer) of the airport before starting their review</dd>
</dl>
<blockquote>
<p>If a Reviewer is unsure about previous feedback, they <strong class="red">should</strong> contact the previous Reviewer to seek clarification to ensure all feedback is consistent</p>
</blockquote>
<dl>
<dt>Step 2</dt>
<dd>Reviewers can then conduct a full review of the airport, taking into account any previous history of the airport to ensure it is compliant with the standards set out within this manual <em>(see <a href="/guide/scenery-editor-manual/12.-review-and-release/12.2-editor-checklist#12.2-editor-checklist" class="documentation-content-link">12.2</a> above)</em></dd>
<dt>Step 3</dt>
<dd>Feedback <strong class="red">must</strong> be given in the IFC airport thread so that there is a record of this</dd>
<dt>Step 4</dt>
<dd>Following the review, return to the <a href="https://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and login using your IFC credentials</dd>
<dt>Step 5</dt>
<dd>From the navigation bar on the left of the screen, select &quot;Airports&quot; under &quot;Scenery Editing&quot;</dd>
<dt>Step 6</dt>
<dd>Select &quot;In Review&quot; from the top navigation bar</dd>
<dt>Step 7</dt>
<dd>Select the airport in review by tapping on the three dots on the right of the airport and then change the status of the airport as required (i.e. &quot;Needs Changes&quot; or &quot;Ready for Release&quot;)</dd>
</dl>
<blockquote>
<p>All airports marked as &quot;Ready for Release&quot; will be included in the next update of the app; therefore, Reviewers <strong class="red">must</strong> ensure that there is no doubt in the airports quality</p>
</blockquote>
</section>
</section>
</section>
<section id="how-to-assign-an-airport-to-an-apprentice">
<h2><a class="header-anchor" href="#how-to-assign-an-airport-to-an-apprentice"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Assign an Airport to an Apprentice</h2>
<section id="12a.1.3">
<h3><a class="header-anchor" href="#12a.1.3">12A.1.3</a></h3>
<section class="reference">
<p>The following procedure outlines how to assign an airport to an Apprentice:</p>
<blockquote>
<p>In some cases, Editors may also require manual assignment to an airport (e.g. if the airport has been previously assigned to another Editor). In these cases (typically collaborations with multiple Editors of the same airport), the below procedure can be followed</p>
</blockquote>
<dl>
<dt>Step 1</dt>
<dd>Go to the <a href="https://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and login using your IFC credentials</dd>
<dt>Step 2</dt>
<dd>From the navigation bar on the left of the screen, select &quot;Editors&quot; under &quot;Scenery Editing&quot;</dd>
<dt>Step 3</dt>
<dd>Select &quot;Apprentices&quot; from the top navigation bar</dd>
<dt>Step 4</dt>
<dd>Use the search function to locate the Editor. Tap the three dots on the right and then &quot;Manage Assignments&quot;</dd>
<dt>Step 5</dt>
<dd>Type the ICAO airport code in the search bar and then &quot;Update&quot;</dd>
</dl>
<blockquote>
<p>Apprentices <strong class="red">must not</strong> be assigned more than one airport at a time, unless the airport has been submitted for an Official Review. Apprentices may be assigned (and begin editing) their next airport whilst awaiting feedback from their airport in review, but <strong class="red">must</strong> prioritize completing this airport once feedback has been given</p>
</blockquote>
</section>
</section>
</section>
<section id="how-to-promote-an-apprentice-to-editor">
<h2><a class="header-anchor" href="#how-to-promote-an-apprentice-to-editor"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Promote an Apprentice to Editor</h2>
<section id="12a.1.4">
<h3><a class="header-anchor" href="#12a.1.4">12A.1.4</a></h3>
<section class="reference">
<p>The following procedure outlines how to promote an Apprentice to the rank of Editor:</p>
<blockquote>
<p>All Apprentices <strong class="red">must</strong> complete a minimum of two airports (i.e. submitted for Official Review and have been marked as Ready for Release) before being promoted to Editor. After this, it is the sole discretion of Reviewers to determine when to promote an Apprentice. It is important to note that once they have been promoted, they will no longer require assignment when choosing new airports to edit. Reviewers <strong class="red">should</strong> take this into account along with previous feedback, Apprentice reception to feedback, and overall judgement before promoting them. Reviewers <strong>must</strong>.{red} consider the opinions of fellow Reviewers before promoting an Apprentice Editor.</p>
</blockquote>
<dl>
<dt>Step 1</dt>
<dd>Go to the <a href="https://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and login using your IFC credentials</dd>
<dt>Step 2</dt>
<dd>From the navigation bar on the left of the screen, select &quot;Editors&quot; under &quot;Scenery Editing&quot;</dd>
<dt>Step 3</dt>
<dd>Select &quot;Apprentices&quot; from the top navigation bar</dd>
<dt>Step 4</dt>
<dd>Use the search function to locate the Editor. Tap the three dots on the right and then &quot;Promote from Apprentice&quot;</dd>
</dl>
</section>
</section>
</section>
</section>


12A.1 Reviewer Admin

<section id="13.1-editing-overview">
<h1><a class="header-anchor" href="#13.1-editing-overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 13.1 Editing Overview</h1>
<section id="13.1.1">
<h3><a class="header-anchor" href="#13.1.1">13.1.1</a></h3>
<section class="reference">
<p>It is recommended that Editors use a &quot;bottom up&quot; mentality for editing (i.e. start with everything at the bottom such as imagery and taxiways and work your way up to 3D objects). A summary of the steps that <strong class="red">should</strong> be followed is below (although these can be completed in any order that the Editor wishes):</p>
<dl>
<dt>Step 1</dt>
<dd>Look at the available imagery quality (within SASPlanet) to check if it is okay (zoom level 19 or higher), if it is blurry then it will not be worth starting <em>(see <a href="/guide/scenery-editor-manual/4.-satellite-imagery/4.1-satellite#4.1.2" class="documentation-content-link">4.1.2</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Compile charts and other sources to assist (some areas do not have free or public charts available)</dd>
<dt>Step 3</dt>
<dd>Adjust airport properties <em>(see <a href="/guide/scenery-editor-manual/3.-getting-started/3.2-airport-properties" class="documentation-content-link">3.2</a> above)</em></dd>
<dt>Step 4</dt>
<dd>Check that the runway is in the correct location using the coordinates, you can then use this as a reference point for the satellite imagery</dd>
</dl>
<blockquote>
<p>Most of the time the runway is already in the correct position</p>
</blockquote>
<dl>
<dt>Step 5</dt>
<dd>Export satellite imagery from SASPlanet and then import into Infinite Flight <em>(see <a href="/guide/scenery-editor-manual/4.-satellite-imagery/4.2-exporting-imagery#4.2.1" class="documentation-content-link">4.2.1</a> and <a href="/guide/scenery-editor-manual/4.-satellite-imagery/4.3-importing-imagery#4.3.1" class="documentation-content-link">4.3.1</a> above)</em></dd>
<dt>Step 6</dt>
<dd>Ensure airport boundary is accurate, and adjust if required <em>(see <a href="/guide/scenery-editor-manual/3.-getting-started/3.3-airport-boundary#3.3.1" class="documentation-content-link">3.3.1</a> above)</em></dd>
<dt>Step 7</dt>
<dd>Add and adjust runways, pavements, taxiways and lines <em>(see <a href="/guide/scenery-editor-manual/5.-runways/5.1-editing-runways" class="documentation-content-link">5.1</a>, <a href="/guide/scenery-editor-manual/6.-pavements/6.1-editing-pavements" class="documentation-content-link">6.1</a>, and <a href="/guide/scenery-editor-manual/7.-taxiways/7.1-editing-taxiways" class="documentation-content-link">7.1</a> above)</em></dd>
<dt>Step 8</dt>
<dd>Add lights, taxiway names, taxiway network and any other properties required <em>(see <a href="/guide/scenery-editor-manual/7.-taxiways/7.2-properties" class="documentation-content-link">7.2</a> and <a href="/guide/scenery-editor-manual/7.-taxiways/7.3-taxiway-network" class="documentation-content-link">7.3</a> above)</em></dd>
<dt>Step 9</dt>
<dd>Add spawns/start locations <em>(see <a href="/guide/scenery-editor-manual/8.-start-locations/8.1-editing-start-locations" class="documentation-content-link">8.1</a> above)</em></dd>
<dt>Step 10</dt>
<dd>Add and edit buildings <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.1-editing-buildings" class="documentation-content-link">9.1</a> above)</em>. You can &quot;Download OSM&quot; if you prefer to use this as a starting point <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.1-editing-buildings#9.1.6" class="documentation-content-link">9.1.6</a> above)</em></dd>
<dt>Step 11</dt>
<dd>Add objects <em>(see <a href="/guide/scenery-editor-manual/10.-objects/10.2-selection-and-placement" class="documentation-content-link">10.2</a> above)</em>, including jet bridges and stand guidance if applicable <em>(see <a href="/guide/scenery-editor-manual/11.-airport-gates/11.2-stand-guidance" class="documentation-content-link">11.2</a> above)</em></dd>
<dt>Step 12</dt>
<dd>Adjust jet bridge properties <em>(see <a href="/guide/scenery-editor-manual/11.-airport-gates/11.3-jet-bridge-properties" class="documentation-content-link">11.3</a> above)</em> and enable jet bridge animations <em>(see <a href="/guide/scenery-editor-manual/11.-airport-gates/11.4-jet-bridge-animations" class="documentation-content-link">11.4</a> above)</em> if applicable</dd>
</dl>
</section>
</section>
</section>


13.1 Editing Overview

<section id="1a.1-discord-communication">
<h1><a class="header-anchor" href="#1a.1-discord-communication"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.1  Discord Communication</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Infinite Flight app related issues can be discussed within the Airport Editing Discord Channels for advice; however, for official support, the <a href="https://community.infiniteflight.com/c/support/17" class="documentation-content-link">IFC Forum</a> <strong class="red">must</strong> be used.</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="general">
<h2><a class="header-anchor" href="#general"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> General</h2>
<section id="1a.1.1">
<h3><a class="header-anchor" href="#1a.1.1">1A.1.1</a></h3>
<section class="reference">
<p>Discord is a messenger app for teams to make work simpler, more pleasant and more productive. More information on how this app works can be found <a href="https://support.discord.com/hc/en-us" class="documentation-content-link">here</a>.</p>
<p>Scenery Editing makes use of a category within the official Infinite Flight Discord, which can be found <a href="https://discord.gg/infiniteflight" class="documentation-content-link">here</a>. A Discord account is required.</p>
</section>
</section>
<section id="1a.1.2">
<h3><a class="header-anchor" href="#1a.1.2">1A.1.2</a></h3>
<section class="reference">
<p>The channels within the Scenery Editing category and their use is outlined in the table below:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Channel</th>
<th style="text-align:left">Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>#announcements</td>
<td style="text-align:left">Official comms channel for Staff &amp; Mods to make broadcast announcements</td>
</tr>
<tr>
<td>#guidelines-&amp;-info</td>
<td style="text-align:left">Highlights the rules of the Scenery Editing category &amp; useful information</td>
</tr>
<tr>
<td>#editors-chat</td>
<td style="text-align:left">A dedicated chat channel for Infinite Flight scenery editors to discuss things related to airport development</td>
</tr>
<tr>
<td>#airport-assignments</td>
<td style="text-align:left">A channel for ASE's (Apprentice Scenery Editors) to request airport assignments. Editors <strong class="red">must</strong> use this format to request an airport: &quot;Requesting ICAO&quot;. A Scenery Editor Moderator or Reviewer will then assign an airport to the Editor</td>
</tr>
<tr>
<td>#sas-requests</td>
<td style="text-align:left">A channel to request satellite imagery. Editors <strong class="red">must</strong> use this format to request imagery: &quot;Requesting SAS for ICAO&quot;.</td>
</tr>
<tr>
<td>#peer-review</td>
<td style="text-align:left">For Editors to be able to review each other's airports before it is submitted for Official Review. Editors must ensure that their airport is nearing completion before requesting a peer review. Editors MUST use this format to request a peer review: &quot;Requesting PR for ICAO - URL to respective IFC topic&quot; <br><em>(see <a href="/guide/scenery-editor-manual/12.-review-and-release/12.1-review-and-release-process#12.1.3" class="documentation-content-link">12.1.3</a> below)</em></td>
</tr>
<tr>
<td>#support</td>
<td style="text-align:left">Ticketing channel to get direct support from Scenery Editor Reviewers or Scenery Editor Moderators</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>
<section id="voice-channels">
<h2><a class="header-anchor" href="#voice-channels"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Voice Channels</h2>
<section id="1a.1.3">
<h3><a class="header-anchor" href="#1a.1.3">1A.1.3</a></h3>
<section class="reference">
<p>Voice Channels (VCs) <strong class="red">must</strong> only be used in accordance with the Discord Rules <em>(see <a href="/guide/scenery-editor-manual/1a.-administration/1a.2-discord-rules#1a.2.1" class="documentation-content-link">1A.2.1</a> below)</em>.</p>
</section>
</section>
<section id="1a.1.4">
<h3><a class="header-anchor" href="#1a.1.4">1A.1.4</a></h3>
<section class="reference">
<p>The use of VCs is <strong class="red">not required</strong> and is at the sole discretion of the Editors.</p>
<p>It is important to note that all pro subscribers have access to the voice channels, so only use these channels if you are comfortable with your airport progress being made public (If non editors join the voice channel)</p>
</section>
</section>
<section id="1a.1.5">
<h3><a class="header-anchor" href="#1a.1.5">1A.1.5</a></h3>
<section class="reference">
<p>To open a VC, the following steps are to be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Open the Official Infinite Flight Discord</dd>
<dt>Step 2</dt>
<dd>Navigate to the Voice Chat category</dd>
<dt>Step 3</dt>
<dd>Create voice chat</dd>
</dl>
<p>*<em>Coordination with other Editors <strong class="red">should</strong> be done in the respective Discord channel (i.e. <em>#editors-chat</em>) before entering a VC</em></p>
</section>
</section>
<section id="1a.1.6">
<h3><a class="header-anchor" href="#1a.1.6">1A.1.6</a></h3>
<section class="reference">
<p>Below are some useful tips for VCs:</p>
<ul>
<li>You can see how many members currently occupy a VC at any time by noting the [00/10] channel count</li>
<li>Selecting &quot;Mute&quot; (microphone symbol) means no one can hear you</li>
<li>Selecting &quot;Deafen&quot; (headphones symbol) means you don't hear anyone else</li>
<li>Always double-check your sound settings (i.e. Input = Mic and Output = Speaker)</li>
<li>Connecting to a VC will act much like a phone call and can run in the background whilst editing</li>
</ul>
</section>
</section>
</section>


1A.1 Discord Communication

<section id="1a.2-discord-rules">
<h1><a class="header-anchor" href="#1a.2-discord-rules"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.2  Discord Rules</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>All Editors <strong class="red">must</strong> ensure that their Discord Nickname is either the same as their IFC Username or real name - this means that Editors can be found easily if required <em>(see <a href="/guide/scenery-editor-manual/1a.-administration/1a.2-discord-rules#1a.2.1" class="documentation-content-link">1A.2.1</a> below)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="general">
<h2><a class="header-anchor" href="#general"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> General</h2>
<section id="1a.2.1">
<h3><a class="header-anchor" href="#1a.2.1">1A.2.1</a></h3>
<section class="reference">
<ul>
<li>Editors <strong class="red">must</strong> have an Infinite Flight account</li>
<li>Editors <strong class="red">must</strong> be 13 years of age or above</li>
<li>Editors <strong class="red">must</strong> <a href="/guide/getting-started-guide/home-user-interface/user-profile#linking-community-forum-account" class="documentation-content-link">link</a> their Community Forum Account <strong>BEFORE</strong> editing</li>
<li>Editors <strong class="red">must</strong> ensure that their Discord Nickname is either the same as their IFC Username or real name</li>
<li>Editors <strong class="red">must not</strong> share any airport editing material or conversations (including audio) contained within the Scenery Editing category externally (unless prior approval has been granted)</li>
<li>Editors <strong class="red">must</strong> be respectful to other users and practice common courtesies</li>
<li>Editors <strong class="red">must not</strong> use any language which, in the exclusive discretion of Infinite Flight, may be deemed offensive (including, but not limited to, language that is unlawful, threatening, vulgar, sexually explicit, or racially, ethnically or otherwise objectionable)</li>
<li>Criticism and feedback will generally be given via DM; however, on occasion, it may be provided publicly if it is deemed to be a wider issue amongst Editors</li>
<li>By uploading airports using the Scenery Editor, you agree to the <a href="https://github.com/infiniteflight/infiniteflight-localization/blob/main/CONTRIBUTING.md" class="documentation-content-link">Contributor License Agreement (CLA)</a></li>
<li>The rules of the Infinite Flight Server also apply and <strong class="red">must</strong> be adhered to. These can be found under the Welcome tab, in the rules-and-info channel</li>
</ul>
</section>
</section>
</section>
<section id="voice-channels">
<h2><a class="header-anchor" href="#voice-channels"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Voice Channels</h2>
<section id="1a.2.2">
<h3><a class="header-anchor" href="#1a.2.2">1A.2.2</a></h3>
<section class="reference">
<ul>
<li>English <strong class="red">must</strong> be used at all times</li>
<li>The voice channels <strong class="red">must</strong> only be used by members who are actively discussing editing with other Editors</li>
<li>Coordination to use voice channels <strong class="red">must</strong> only occur in the <em>#editors-chat</em> Discord channels</li>
<li>Editors <strong class="red">must not</strong> transmit anything that may be interpreted as disruptive</li>
<li>Editors <strong class="red">must not</strong> transmit any private, identifying or sensitive information</li>
<li>Editors <strong class="red">must not</strong> impersonate other users</li>
<li>Further guidance on the use of VCs can be found in Discord Communication <em>(see <a href="/guide/scenery-editor-manual/1a.-administration/1a.1-discord-communication#1a.1.3" class="documentation-content-link">1A.1.3</a> above)</em></li>
</ul>
</section>
</section>
<section id="1a.2.3">
<h3><a class="header-anchor" href="#1a.2.3">1A.2.3</a></h3>
<section class="reference">
<p>Members may contact a Staff Member or IFC Moderator at any time to report a serious violation of VC rules or an unsafe situation. Editor member safety and privacy is a top priority.</p>
<blockquote>
<p>Due to the representation of widely diverse social norms, there may be accidental utterances provoked by excitement which do not warrant moderation (e.g. mild profanity and spontaneous phrases as a result of a startling event)</p>
</blockquote>
</section>
</section>
</section>
<section id="support">
<h2><a class="header-anchor" href="#support"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Support</h2>
<section id="1a.2.4">
<h3><a class="header-anchor" href="#1a.2.4">1A.2.4</a></h3>
<section class="reference">
<ul>
<li>In the first instance, Editors <strong class="red">should</strong> make every effort to use the resources available to them, including this manual and fellow Editors, to seek support</li>
<li>If Editors are unable to find the answer they need, they can ask for help in the <em>#editors-chat</em> Discord Channel</li>
<li>The Rank Structure can be helpful to find out what the different roles in Airport Editing are, and therefore who might be appropriate to ask <em>(see <a href="/guide/scenery-editor-manual/1a.-administration/1a.4-rank-structure#1a.4.1" class="documentation-content-link">1A.4.1</a> below)</em></li>
<li>Should Editors require assistance with server related enquiries, they can contact Infinite Flight Server Moderators by using #server-support under the &quot;Support&quot; Tab</li>
</ul>
</section>
</section>
</section>


1A.2 Discord Rules

<section id="1a.3-editor-rules">
<h1><a class="header-anchor" href="#1a.3-editor-rules"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.3  Editor Rules</h1>
<section id="1a.3.1">
<h3><a class="header-anchor" href="#1a.3.1">1A.3.1</a></h3>
<section class="reference">
<ul>
<li>All Editors <strong class="red">should not</strong> edit airports that are closed IRL</li>
<li>All Editors <strong class="red">should not</strong> delete everything at an airport to start from scratch</li>
<li>Editors conducting Peer Reviews <strong class="red">must not</strong> take more than 2 airports at any time, and <strong class="red">must</strong> ensure that they have the time available to conduct the review in a timely manner (i.e. time frames of when the review will be done <strong class="red">must not</strong> be mentioned as the Editor is expected to only conduct a Peer Review when they are available). If in doubt, the Editor <strong class="red">should</strong> leave the airport available for review <em>(see <a href="/guide/scenery-editor-manual/12.-review-and-release/12.1-review-and-release-process#12.1.3" class="documentation-content-link">12.1.3</a> below)</em></li>
<li>Editors <strong class="red">must not</strong> &quot;leak&quot; any WIP airports that they are not editing themselves without the express permission of the assigned Editor(s). Doing so may result in removal of the editor from the Airport Editing Team <em>(see <a href="/guide/scenery-editor-manual/1a.-administration/1a.6-disciplinary-and-suspension-procedure" class="documentation-content-link">1A.6</a> below)</em></li>
<li>When uploading a new version of a recently edited airport (i.e tapping &quot;Upload as Draft&quot; or &quot;Upload for Review&quot;), Editors will be required to submit a &quot;changelog&quot; which highlights what has been changed in that version. Changelogs <strong class="red">must</strong> be specific to ensure that it is clear what has been changed (e.g. &quot;Adjusted C19 jetbridge. Changed taxiway line type on Taxiway A&quot;). Additional details can be added to the IFC airport thread if required <em>(see <a href="/guide/scenery-editor-manual/12.-review-and-release/12.1-review-and-release-process" class="documentation-content-link">12.1</a> below)</em></li>
</ul>
</section>
</section>
</section>


1A.3 Editor Rules

<section id="1a.4-rank-structure">
<h1><a class="header-anchor" href="#1a.4-rank-structure"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.4  Rank Structure</h1>
<section id="1a.4.1">
<h3><a class="header-anchor" href="#1a.4.1">1A.4.1</a></h3>
<section class="reference">
<p>The table below outlines the rank structure in place. Promotion is based on activity, performance, and feedback:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Rank</th>
<th>Airport Assignment Required</th>
<th>View WIP Airports</th>
<th>Conduct Peer/Official Reviews</th>
</tr>
</thead>
<tbody>
<tr>
<td>Apprentice</td>
<td>Yes*</td>
<td>No**</td>
<td>No</td>
</tr>
<tr>
<td>Senior Editor</td>
<td>No</td>
<td>Yes</td>
<td>Only Peer Reviews</td>
</tr>
<tr>
<td>Reviewer</td>
<td>No</td>
<td>Yes</td>
<td>Yes***</td>
</tr>
</tbody>
</table></div><p>*<em>Apprentices <strong class="red">must not</strong> be assigned more than one airport at a time, unless the airport has been submitted for an Official Review <em>(see <a href="/guide/scenery-editor-manual/12.-review-and-release/12.1-review-and-release-process#12.1.4" class="documentation-content-link">12.1.4</a> below)</em>. Apprentices may be assigned (and begin editing) their next airport whilst awaiting feedback from their airport in review, but <strong class="red">must</strong> prioritize completing this airport once feedback has been given</em></p>
<p>**<em>Apprentices are only able to view airports that are assigned to them, any WIP airports are invisible until they have been released or the Apprentice is promoted to Senior Editor</em></p>
<p>***<em>When conducting Official Reviews, Reviewers will not make any edits to the airport unless it is deemed very small and does not require feedback to the Editor. Any large changes will be sent to the Editor so that they can make the changes required.</em></p>
<blockquote>
<p>All Editors are subject to promotion/demotion at any time based on activity, performance and feedback!</p>
</blockquote>
</section>
</section>
<section id="promotion-to-editor">
<h2><a class="header-anchor" href="#promotion-to-editor"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Promotion to Editor</h2>
<section id="1a.4.2">
<h3><a class="header-anchor" href="#1a.4.2">1A.4.2</a></h3>
<section class="reference">
<p>Promotion to the rank of Editor is dealt with on a case by case basis and not solely on time served. With this in mind, Apprentices <strong class="red">must</strong> avoid asking when they will be promoted; and instead, <strong class="red">should</strong> focus on editing airports to a high standard. Editors will be notified when they have been promoted.</p>
</section>
</section>
</section>
<section id="promotion-to-reviewer">
<h2><a class="header-anchor" href="#promotion-to-reviewer"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Promotion to Reviewer</h2>
<section id="1a.4.3">
<h3><a class="header-anchor" href="#1a.4.3">1A.4.3</a></h3>
<section class="reference">
<p>The rank of Reviewer is only awarded when a need exists and to Editors that have demonstrated a high standard of airport editing and professional conduct within the Airport Editing team.</p>
<p>The purpose of the Reviewer Team is to:</p>
<ul>
<li>Assist in the day-to-day operations of the Scenery Editing Team</li>
<li>Provide leadership and/or mentoring to individual Editors</li>
<li>Assign airports to Editors with the rank of Apprentice</li>
<li>Review editing quality via the &quot;Official Review&quot; process*</li>
<li>and Moderate the Scenery Editing Team Discord channel</li>
</ul>
<p>*<em>Reviewers <strong class="red">should not</strong> upload changes on behalf of the editors during the Official Review process without the editors' explicit consent in the interest of the editors' skill improvement and respect towards the editors' work, unless the issues found during the Official Review process are minor, not consistently present, and a new OR cycle for the airport would not be considered reasonable if they were left for the airport's editor to fix. Examples of minor issues are improperly snapped lines, buildings and/or pavements, and lines with 1 or more inaccurate properties. Reviewers are advised to use their judgement regarding the consistency and severity of the issues found proportionally to the size and complexity of the airport subject to review. For example, 3 improperly snapped lines would not be as big of an issue at KLAX, but they would be at a small GA field. If a Reviewer does decide to upload changes on behalf of the editors during the Official Review process, a summary of the changes made, preferably including screenshots, <strong class="red">should</strong> be provided for the sake of respect towards the editors' work.</em></p>
</section>
</section>
<section id="1a.4.4">
<h3><a class="header-anchor" href="#1a.4.4">1A.4.4</a></h3>
<section class="reference">
<p>The following prerequisites are required for promotion to the rank of Reviewer:</p>
<ul>
<li>Editor rank with demonstrated proficiency in <strong>all</strong> aspects of airport editing</li>
<li>Proficient editor who leads by example and follows all server rules</li>
<li>Positive editing record</li>
<li>Ability to communicate respectfully and professionally</li>
</ul>
</section>
</section>
</section>
<section id="other-airport-editing-roles">
<h2><a class="header-anchor" href="#other-airport-editing-roles"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Other Airport Editing Roles</h2>
<section id="1a.4.5">
<h3><a class="header-anchor" href="#1a.4.5">1A.4.5</a></h3>
<section class="reference">
<p>In addition to the rank structure outlined above, individuals may hold other roles within the Airport Editing team. These are shown below:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Title</th>
<th>Role</th>
<th>Rank</th>
</tr>
</thead>
<tbody>
<tr>
<td>Moderator</td>
<td>Moderates the Airport Editing team, including day to day operations, quality assurance, personnel issues, performance and disciplinary demotions and/or suspensions</td>
<td>N/A</td>
</tr>
</tbody>
</table></div><blockquote>
<p>IFC Moderators are present within the Airport Editing team; however, Airport Moderators will usually deal with most day-to-day tasks</p>
</blockquote>
</section>
</section>
</section>
</section>


1A.4 Rank Structure

<section id="1a.5-airport-assignments">
<h1><a class="header-anchor" href="#1a.5-airport-assignments"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.5  Airport Assignments</h1>
<section id="1a.5.1">
<h3><a class="header-anchor" href="#1a.5.1">1A.5.1</a></h3>
<section class="reference">
<p>All Editors at the rank of Apprentice (initial rank when joining) <strong class="red">must</strong> have all airports assigned to them in order to upload them. This is to ensure that new Editors do not assign themselves an airport too large/complex and so that they can focus on one airport at a time, addressing any issues spotted during Peer and Official Reviews <em>(see <a href="/guide/scenery-editor-manual/12.-review-and-release/12.1-review-and-release-process" class="documentation-content-link">12.1</a> below)</em>.</p>
<blockquote>
<p>Apprentices <strong class="red">must not</strong> be assigned more than one airport at a time, unless the airport has been submitted for an Official Review. Apprentices may be assigned (and begin editing) their next airport whilst awaiting feedback from their airport in review, but <strong class="red">must</strong> prioritize completing this airport once feedback has been given</p>
</blockquote>
</section>
</section>
<section id="1a.5.2">
<h3><a class="header-anchor" href="#1a.5.2">1A.5.2</a></h3>
<section class="reference">
<p>Following successful Official Reviews from airports that have been assigned, Apprentices will be promoted to the rank of Editor and will no longer be required to request airport assignments <em>(see <a href="/guide/scenery-editor-manual/1a.-administration/1a.4-rank-structure#1a.4.2" class="documentation-content-link">1A.4.2</a> above)</em>.</p>
<blockquote>
<p>In some cases, Editors may also require manual intervention by a Reviewer. For example, to get unassigned from an airport, to collaborate and work on an airport with other Editors at the same time, or if the airport has been previously assigned to another Editor. In these cases, it remains the discretion of the Reviewing Team and may not be approved (even if the Editor has already been promoted from the rank of Apprentice)</p>
</blockquote>
</section>
</section>
<section id="1a.5.3">
<h3><a class="header-anchor" href="#1a.5.3">1A.5.3</a></h3>
<section class="reference">
<p>For any request relating to airport assignments the following steps <strong class="red">must</strong> be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Open the Offical Infinite Flight Discord and using the navigation bar on the left side of the screen, find the &quot;Scenery Editing&quot; tab</dd>
<dt>Step 2</dt>
<dd>Click on the <em>#airport-assignments</em> Discord channel</dd>
<dt>Step 3</dt>
<dd>Create a request in the channel for an airport you'd like to edit. The following format must be used to request airports: &quot;Requesting ICAO&quot; and any other information that may be relevant such as &quot;collab with [editors name]&quot;</dd>
<dt>Step 4</dt>
<dd>A Reviewer will look at the request and either approve the airport assignment or suggest an alternative plan (for Apprentices in particular, this may be the case if the airport is considered too large/complex)</dd>
</dl>
<blockquote>
<p>This will be in a thread underneath the request made. All further comments relating to that airport <strong class="red">should</strong> be in the thread to ensure that airport assignments are not lost within the Discord channel</p>
</blockquote>
</section>
</section>
<section id="1a.5.4">
<h3><a class="header-anchor" href="#1a.5.4">1A.5.4</a></h3>
<section class="reference">
<p>When Apprentices select an airport that they want to be assigned, consideration <strong class="red">should</strong> be given to the following criteria:</p>
<ul>
<li>Airport size and complexity</li>
<li>Time available</li>
<li>Ability</li>
<li>and Previous feedback given by Reviewers (if applicable)</li>
</ul>
</section>
</section>
</section>


1A.5 Airport Assignments

<section id="1a.6-disciplinary-and-suspension-procedure">
<h1><a class="header-anchor" href="#1a.6-disciplinary-and-suspension-procedure"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.6  Disciplinary and Suspension Procedure</h1>
<section id="1a.6.1">
<h3><a class="header-anchor" href="#1a.6.1">1A.6.1</a></h3>
<section class="reference">
<p>Editors not following the Scenery Editing Manual can expect the following procedure:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Offense</th>
<th>Action Taken</th>
</tr>
</thead>
<tbody>
<tr>
<td>1st</td>
<td>Warning via DM</td>
</tr>
<tr>
<td>2nd</td>
<td>3 day Scenery Editor &amp; Discord suspension</td>
</tr>
<tr>
<td>3rd</td>
<td>7 day Scenery Editor &amp; Discord suspension</td>
</tr>
<tr>
<td>4th</td>
<td>Removal from the Airport Editing Team</td>
</tr>
</tbody>
</table></div><p>Following any suspension, Editors will return at the rank they previously held. Usually, the date they’re reinstated on will serve as the new start date at that rank; however, this is dealt with on a case by case basis.</p>
</section>
</section>
<section id="1a.6.2">
<h3><a class="header-anchor" href="#1a.6.2">1A.6.2</a></h3>
<section class="reference">
<p>Serious cases, reviewed by Staff or IFC Moderators, are subject to immediate removal or suspension.</p>
</section>
</section>
</section>


1A.6 Disciplinary and Suspension Procedure

2.1 Editor Screen

<section id="3.1-first-steps">
<h1><a class="header-anchor" href="#3.1-first-steps"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.1 First Steps</h1>
<section id="airport-information-resources">
<h2><a class="header-anchor" href="#airport-information-resources"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Airport Information Resources</h2>
<section id="3.1.1">
<h3><a class="header-anchor" href="#3.1.1">3.1.1</a></h3>
<section class="reference">
<p>To find information on airport facts and figures, we recommend the following websites:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Website</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="http://www.aircharts.org" class="documentation-content-link">www.aircharts.org</a></td>
<td></td>
</tr>
<tr>
<td><a href="http://www.airmate.aero" class="documentation-content-link">www.airmate.aero</a></td>
<td></td>
</tr>
<tr>
<td><a href="http://www.airnav.com" class="documentation-content-link">www.airnav.com</a></td>
<td>US and Canada only</td>
</tr>
<tr>
<td><a href="http://www.apxp.info" class="documentation-content-link">www.apxp.info</a></td>
<td></td>
</tr>
<tr>
<td><a href="http://www.ead.eurocontrol.int" class="documentation-content-link">www.ead.eurocontrol.int</a></td>
<td>Charts for European airports</td>
</tr>
<tr>
<td><a href="https://erau.libguides.com/UAS/eAIP" class="documentation-content-link">www.erau.libguides.com</a></td>
<td>List of nation's AIPs</td>
</tr>
<tr>
<td><a href="http://www.faa.gov/air_traffic/flight_info/aeronav/Aero_Data/Airport_Data" class="documentation-content-link">www.faa.gov/air_traffic/flight_info/aeronav/Aero_Data/Airport_Data</a></td>
<td>Charts for US airports</td>
</tr>
<tr>
<td><a href="http://www.flightplandatabase.com/tools" class="documentation-content-link">www.flightplandatabase.com/tools</a></td>
<td></td>
</tr>
<tr>
<td><a href="http://www.gcmap.com" class="documentation-content-link">www.gcmap.com</a></td>
<td></td>
</tr>
<tr>
<td><a href="http://www.opennav.com" class="documentation-content-link">www.opennav.com</a></td>
<td></td>
</tr>
<tr>
<td><a href="http://www.rocketroute.com" class="documentation-content-link">www.rocketroute.com</a></td>
<td></td>
</tr>
<tr>
<td><a href="http://www.worldaerodata.com" class="documentation-content-link">www.worldaerodata.com</a></td>
<td></td>
</tr>
</tbody>
</table></div><blockquote>
<p>Airport editing often requires coordinates which can be provided in a variety of formats. <a href="http://www.earthpoint.us/convert.aspx" class="documentation-content-link">www.earthpoint.us/convert.aspx</a> can be helpful to convert them into the desired format</p>
</blockquote>
</section>
</section>
</section>
<section id="opening-the-scenery-editor">
<h2><a class="header-anchor" href="#opening-the-scenery-editor"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Opening the Scenery Editor</h2>
<section id="3.1.2">
<h3><a class="header-anchor" href="#3.1.2">3.1.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Open the Infinite Flight App and select &quot;Scenery Editor&quot;</dd>
<dt>Step 2</dt>
<dd>Choose the airport that you wish to edit and then select any runway or parking position. Tap &quot;Ok&quot; and then &quot;Open&quot; to begin</dd>
<dt>Step 3</dt>
<dd>If you are editing a new airport (or working on an existing one which does not have a thread on the IFC yet), a topic will automatically be created in the <a href="https://community.infiniteflight.com/c/scenery-editing/editors/52" class="documentation-content-link">Scenery Editor Category</a>. Whenever new versions are uploaded, the changelogs will be added automatically to each thread so it's easy to keep track. All communication about a particular airport <strong class="red">must</strong> remain within it's specific thread</dd>
<dt>Step 4</dt>
<dd>When you first upload an airport, it will automatically assign you to that airport (this prevents others from uploading to the same airport)</dd>
</dl>
</section>
</section>
</section>
</section>


3.1 First Steps

<section id="3.2-airport-properties">
<h1><a class="header-anchor" href="#3.2-airport-properties"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.2 Airport Properties</h1>
<section id="3.2.1">
<h3><a class="header-anchor" href="#3.2.1">3.2.1</a></h3>
<section class="reference">
<p>To edit airport properties the below steps <strong class="red">must</strong> be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Tap &quot;File &gt; Airport Properties&quot; <strong>(1)</strong> from the management buttons on the left of the screen</dd>
<dt>Step 2</dt>
<dd>The airport properties will appear on the right hand side of the screen <strong>(2)</strong></dd>
<dt>Step 3</dt>
<dd>All are adjusted by tapping the property, except for &quot;Frequencies&quot; <em>(see <a href="/guide/scenery-editor-manual/3.-getting-started/3.2-airport-properties#3.2.3" class="documentation-content-link">3.2.3</a> below)</em> and then entering the new value/name and tapping &quot;OK&quot;</dd>
<dt>Step 4</dt>
<dd>Some of the properties may already be populated, Editors <strong class="red">must</strong> ensure that these are correct and fill in any properties that are missing</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/3.3.1.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/3.3.1.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/3.3.1.1@3x.png 3x" alt="Image 3.2.1.1 - Airport Properties" class="documentation-image-lightbox-link" >
          <figcaption>Image 3.2.1.1 - Airport Properties</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="3.2.2">
<h3><a class="header-anchor" href="#3.2.2">3.2.2</a></h3>
<section class="reference">
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Airport Property</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>ICAO</td>
<td>Four letter ICAO code (e.g. KSFO or EGLL) <strong>should not</strong>.{red} be changed, as it can mess with the airport saving system. If this has to be changed (e.g. a real-life airport changes its ICAO code), the airport <strong>must</strong>.{red} be released with the new ICAO code before further drafts can be made.</td>
</tr>
<tr>
<td>Elevation</td>
<td>Elevation of the airport (in meters)</td>
</tr>
<tr>
<td>Name</td>
<td>Name of the airport</td>
</tr>
<tr>
<td>Spoken Name</td>
<td>Name of the airport that will be spoken in-app</td>
</tr>
<tr>
<td>City</td>
<td>City that the airport primarily serves. This may not necessarily be the same as the geographical city location (e.g. for KJFK the city name would be New York, not Queens)</td>
</tr>
<tr>
<td>Country</td>
<td>Country that the airport is located in</td>
</tr>
<tr>
<td>State</td>
<td>State or equivalent (such as county) that the airport is located in</td>
</tr>
<tr>
<td>IATA Code</td>
<td>Three letter IATA code (e.g. SFO or LHR)</td>
</tr>
<tr>
<td>FAA Code</td>
<td>Three to five letter alphanumeric code for airports in the USA only (usually similar to the IATA code)</td>
</tr>
<tr>
<td>Airport Class</td>
<td>Class of airport (from Alpha to Echo)</td>
</tr>
<tr>
<td>Latitude</td>
<td>Latitude of the airport (this <strong class="red">should not</strong> be changed)</td>
</tr>
<tr>
<td>Longitude</td>
<td>Longitude of the airport (this <strong class="red">should not</strong> be changed)</td>
</tr>
<tr>
<td>Frequencies</td>
<td>The frequencies of the airport</td>
</tr>
<tr>
<td>Taxiway Routes Available</td>
<td>When selected, orange tick is displayed (<strong class="red">must</strong> be selected for ATC taxiway network to be available to controllers and pilots)</td>
</tr>
<tr>
<td>Jet Bridges Available</td>
<td>When selected, orange tick is displayed (<strong class="red">must</strong> be selected for animated jet bridges to be available to pilots but only once jet bridges have been added and are usable - <em>see <a href="/guide/scenery-editor-manual/11.-airport-gates/11.4-jet-bridge-animations#11.4.1" class="documentation-content-link">11.4.1</a> below</em>)</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="3.2.3">
<h3><a class="header-anchor" href="#3.2.3">3.2.3</a></h3>
<section class="reference">
<p>To add/delete or edit frequencies, the below steps <strong class="red">must</strong> be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Tap the &quot;+&quot; symbol next to &quot;Frequencies&quot; <strong>(1)</strong></dd>
<dt>Step 2</dt>
<dd>All frequencies currently listed for that airport will appear beneath. Tap the &quot;+&quot; symbol to the left of a frequency to open its properties <strong>(2)</strong></dd>
<dt>Step 3</dt>
<dd>Frequency Type, Name, Frequency and Spoken Name can all be changed in the same way as other airport properties <em>(see <a href="/guide/scenery-editor-manual/3.-getting-started/3.2-airport-properties#3.2.1" class="documentation-content-link">3.2.1</a> above)</em></dd>
<dt>Step 4</dt>
<dd>Tap the &quot;-&quot; symbol to the left of the same frequency to &quot;close&quot; its properties tab <strong>(3)</strong></dd>
<dt>Step 5</dt>
<dd>To delete a frequency, tap the &quot;-&quot; symbol on the right of that frequency <strong>(4)</strong></dd>
<dt>Step 6</dt>
<dd>To add a new frequency, tap the &quot;+&quot; symbol at the bottom right beneath all frequencies <strong>(5)</strong></dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/3.3.3.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/3.3.3.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/3.3.3.1@3x.png 3x" alt="Image 3.2.3.1 - Editing Frequencies" class="documentation-image-lightbox-link" >
          <figcaption>Image 3.2.3.1 - Editing Frequencies</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


3.2 Airport Properties

<section id="3.3-airport-boundary">
<h1><a class="header-anchor" href="#3.3-airport-boundary"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.3 Airport Boundary</h1>
<section id="3.3.1">
<h3><a class="header-anchor" href="#3.3.1">3.3.1</a></h3>
<section class="reference">
<p>The airport boundary is shown in a light green line that surrounds the airport, the elevation within the airport boundary will always be completely flat to allow editing and prevent any buildings/objects from floating or being submerged. All topography outside of the airport boundary will have a varying elevation based on real world topography.</p>
<blockquote>
<p>All objects <strong class="red">must</strong> be within the airport boundary, the only exception to this is airport equipment such as the localizer antenna. In these cases, the Editor <strong class="red">must</strong> ensure that the object is properly aligned with the terrain</p>
</blockquote>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If you find buildings/objects are floating/submerged, it may be because they are too close to the airport boundary. You can either move the airport boundary, or move the buildings/objects slightly in from the boundary</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="3.3.2">
<h3><a class="header-anchor" href="#3.3.2">3.3.2</a></h3>
<section class="reference">
<p>To edit the airport boundary, follow the steps below:</p>
<blockquote>
<p>If changing the airport boundary, a navigation database update will be required before the new boundary is reflected in-app. Therefore, Editors <strong class="red">should not</strong> add any new buildings/objects in the new airport boundary until this has been updated</p>
</blockquote>
<dl>
<dt>Step 1</dt>
<dd>Tap on or near to the light green line and select &quot;airport boundary&quot; <strong>(1)</strong></dd>
</dl>
<blockquote>
<p>You might not be presented with the option to select &quot;airport boundary&quot;, but you will know if it is selected by looking at the bottom left of the screen, where it will indicate what is currently selected</p>
</blockquote>
<dl>
<dt>Step 2</dt>
<dd>Tap &quot;Modify Shape&quot; from the edit buttons on the right <strong>(2)</strong>, it will turn amber to show it has been selected</dd>
<dt>Step 3</dt>
<dd>Nodes will appear <strong>(3)</strong> which can be moved by tapping on them (it will turn magenta to show it has been selected)</dd>
<dt>Step 4</dt>
<dd>Tap, hold and drag on the center circle to move the node <strong>(4)</strong></dd>
<dt>Step 5</dt>
<dd>More nodes can be added by tapping &quot;insert point&quot; <strong>(5)</strong> from the edit buttons on the right</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/3.4.1.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/3.4.1.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/3.4.1.1a@3x.png 3x" alt="Image 3.3.2.1 - Airport Boundary" class="documentation-image-lightbox-link" >
          <figcaption>Image 3.3.2.1 - Airport Boundary</figcaption>
        </figure>
      </p>
</section>
</section>


3.3 Airport Boundary

<section id="4.1-satellite">
<h1><a class="header-anchor" href="#4.1-satellite"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 4.1 Satellite</h1>
<section id="overview">
<h2><a class="header-anchor" href="#overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Overview</h2>
<section id="4.1.1">
<h3><a class="header-anchor" href="#4.1.1">4.1.1</a></h3>
<section class="reference">
<p>Satellite imagery is used to assist Editors in creating accurate airports. SASPlanet is the recommended program, as it is capable of exporting orthophotos from various sources, such as Google, Bing or Yandex maps in varying quality. Files downloaded will be zipped, which can be extracted using Windows Explorer. A link to download this program is below:</p>
<blockquote>
<p>SASPlanet is only available on Windows and Linux. MacOS users will need to request orthophotos from other Editors</p>
</blockquote>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Program</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="https://gisenglish.geojamal.com/2018/06/download-sas-planet-nightly-all.html" class="documentation-content-link">SASPlanet</a></td>
<td>Satellite imagery</td>
</tr>
</tbody>
</table></div><dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Satellite imagery can be distorted, it is important to remember this while editing. Straight lines may appear warped, your best judgement should be used in these cases to avoid unrealistic bends or curves</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
</section>
<section id="installing-sasplanet">
<h2><a class="header-anchor" href="#installing-sasplanet"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Installing SASPlanet</h2>
<section id="4.1.2">
<h3><a class="header-anchor" href="#4.1.2">4.1.2</a></h3>
<section class="reference">
<p>The following steps <strong class="red">should</strong> be followed to extract the file:</p>
<dl>
<dt>Step 1</dt>
<dd>Right click the .zip folder and extract files</dd>
<dt>Step 2</dt>
<dd>Select the location to extract the SAS to</dd>
<dt>Step 3</dt>
<dd>SAS is ready for use and no further installations are required</dd>
</dl>
</section>
</section>
</section>
<section id="zoom-levels">
<h2><a class="header-anchor" href="#zoom-levels"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Zoom Levels</h2>
<section id="4.1.3">
<h3><a class="header-anchor" href="#4.1.3">4.1.3</a></h3>
<section class="reference">
<p>Different zoom levels are available:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Zoom Level (z)</th>
<th>Quality</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>z22</td>
<td>Commercial</td>
<td>For commercial use - not available</td>
</tr>
<tr>
<td>z21</td>
<td>High</td>
<td>Maximum quality that can be found from public sources</td>
</tr>
<tr>
<td>z20</td>
<td>Good</td>
<td>z20 or higher <strong class="red">should</strong> always be used when available</td>
</tr>
<tr>
<td>z19</td>
<td>Marginal</td>
<td>If higher quality not available, can be sufficient</td>
</tr>
<tr>
<td>z18 or lower</td>
<td>Poor</td>
<td>z18 or lower <strong class="red">should not</strong> be used</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="4.1.4">
<h3><a class="header-anchor" href="#4.1.4">4.1.4</a></h3>
<section class="reference">
<p>To work out if the zoom level required is available:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>Click the &quot;Cached tiles map&quot; icon (this is 5 icons in from the left of the screen and represented by a silver/black circle) and then tick the relevant zoom</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>If the tiles are clear, then the zoom level is available. Otherwise, they will be shown in grey</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>You can check different satellite image sources to find the most recent images or images of best quality, however, construction sites, outdated imagery and low image quality can make editing quite hard, especially for a new Editor. If your desired airport has low quality imagery and/or significant construction sites impeding editing in SAS, consider postponing the airport to a later date until more recent or higher quality imagery is available</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>


4.1 Satellite

<section id="4.2-exporting-imagery">
<h1><a class="header-anchor" href="#4.2-exporting-imagery"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 4.2 Exporting Imagery</h1>
<section id="4.2.1">
<h3><a class="header-anchor" href="#4.2.1">4.2.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>After downloading SASPlanet, open the program</dd>
<dt>Step 2</dt>
<dd>Navigate to the area that you want to obtain satellite imagery for by using the zoom in/out function and left click of your mouse</dd>
<dt>Step 3</dt>
<dd>Select &quot;Maps&quot; and then the map that you would like to use</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>It is important to pick the best/most recent source(s) possible. It can be helpful to compare the image with recent charts, so you know what satellite image is more recent (if the layout differs between sources). If you know the airport well, or know an area that is under construction, you can also look for sources that show this detail to help with selection</dd>
</dl>
<dl>
<dt>Step 4</dt>
<dd>Select the &quot;Polygonal Selection&quot; within the &quot;Selection Manager&quot; button (this is the second icon from the left represented by a section of map surrounded by a series of blue lines). You can also do this by going to &quot;Operations &gt; Selection Manager &gt; Polygonal Selection&quot;</dd>
<dt>Step 5</dt>
<dd>You can use the zoom in/out function and right clicks on your mouse to navigate around the screen. Every left click will place a new node (a pop-up would have appeared on the map when the selection manager was selected, this allows you to delete a previous node if required)</dd>
<dt>Step 6</dt>
<dd>Place nodes around the section of map that you want to export. The best way is to follow the airport boundary, but with an additional margin added to this (diagonal lines will cause a zig-zag edge due to the tiles, so working too close too the boundary will cause areas within the airport boundary to not be fully included in the image)</dd>
<dt>Step 7</dt>
<dd>Once you have finished placing all nodes, click the green tick from the pop-up</dd>
<dt>Step 8</dt>
<dd>The &quot;Selection Manager&quot; pop-up will appear, select the zoom level or levels <em>(see <a href="/guide/scenery-editor-manual/4.-satellite-imagery/4.1-satellite#4.1.3" class="documentation-content-link">4.1.3</a> and <a href="/guide/scenery-editor-manual/4.-satellite-imagery/4.1-satellite#4.1.4" class="documentation-content-link">4.1.4</a> above)</em></dd>
<dt>Step 9</dt>
<dd>Click &quot;Start&quot; from the selection manager pop-up, another pop-up will then appear that will show the progress of the download</dd>
<dt>Step 10</dt>
<dd>When this is completed, another pop-up will appear, saying &quot;The task is completed!&quot;. You may now click &quot;Quit&quot;</dd>
<dt>Step 11</dt>
<dd>Go to &quot;Operations &gt; Selection Manager &gt; Last Selection&quot;. The Selection Manager popup will appear again, select the &quot;Stitch&quot; tab at the top</dd>
<dt>Step 12</dt>
<dd>The following inputs <strong class="red">must</strong> be made before clicking &quot;Start&quot;:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Window</th>
<th>Input</th>
</tr>
</thead>
<tbody>
<tr>
<td>Output Format</td>
<td>JPEG*</td>
</tr>
<tr>
<td>Save To</td>
<td>Select your desired output folder</td>
</tr>
<tr>
<td>Map</td>
<td>Same source as source used to download imagery</td>
</tr>
<tr>
<td>Zoom</td>
<td>Same zoom as used to download imagery</td>
</tr>
<tr>
<td>Projection</td>
<td>&quot;Geographic (Latitude/Longitude) / WGS84 / EPSG: 4326&quot; is recommended</td>
</tr>
<tr>
<td>Quality</td>
<td>Select 50% - if the file needs to be smaller, consider using a lower zoom level, such as z20 instead of z21</td>
</tr>
<tr>
<td>Create Georeferencing file</td>
<td>Tick &quot;.kml&quot;</td>
</tr>
<tr>
<td>Split Image</td>
<td>Splitting the image makes the file more manageable when importing it into Infinite Flight and improves performance <em>(see <a href="/guide/scenery-editor-manual/4.-satellite-imagery/4.2-exporting-imagery#4.2.2" class="documentation-content-link">4.2.2</a> below)</em></td>
</tr>
</tbody>
</table></div><p>*<em>There is no difference in quality between JPEG and PNG, however, JPEG uses compression, thus saving file size and improving performance</em></p>
<blockquote>
<p>50% quality is almost identical to 100%, with the advantage of the file size being almost 8 times smaller (e.g. 100% image quality and a size of 450MB would give the same amount of quality as a 50% image that is only 70MB). However, the smaller file size does not mean a larger area can be selected. This is because, while loade0, the files are converted to BMP (bitmap) file format, meaning that the file is translated into the same amount of data when in-app (in the example above, 70MB or 450MB would both translate to 2.6GB of data)</p>
</blockquote>
<dl>
<dt>Step 13</dt>
<dd>Once it is completed, navigate to the folder and delete any images of white tiles, as these take up space and are not required</dd>
</dl>
<blockquote>
<p>It is important to remember that it is not the file size that is being imported that will limit the device, but what this is converted to in-app. While a 213MB file with image quality set to 95% could work, a 80MB file with the image quality setting set to 50% could exceed the maximum file size limit. In addition, it matters how many partially white tiles are in the zip file. As a JPG file, those files are a lot smaller than the other tiles (making the zip file smaller), but as a BMP file, they are exactly the same size as the other tiles. Therefore, it is important to remove empty (white) tiles.</p>
</blockquote>
<dl>
<dt>Step 14</dt>
<dd>Select all remaining files, right click and select the option to compress into a &quot;.zip&quot;. <strong>Ensure you are selecting and compressing the files <em>inside</em> the output folder, and not the output folder itself</strong> - otherwise, the imagery <strong class="red">will not</strong> open in Infinite Flight</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>You need to keep one image set to under 400MB, you may have to split further if this is the case, but it is rare. If z20 is used then this should never happen</dd>
</dl>
<dl>
<dt>Step 15</dt>
<dd>The .zip folder will appear within the folder you have sent it to, you can then send this to you device using email, or a cloud service, such as Google Drive</dd>
</dl>
</section>
</section>
<section id="split-image">
<h2><a class="header-anchor" href="#split-image"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Split Image</h2>
<section id="4.2.2">
<h3><a class="header-anchor" href="#4.2.2">4.2.2</a></h3>
<section class="reference">
<p>When looking at the &quot;Stitch&quot; tab of the &quot;Selection Manager&quot; popup, there are tiles that the satellite imagery are within. By splitting the image, it makes the file more manageable when importing it into Infinite Flight and improves performance. To do this, follow the below steps:</p>
<dl>
<dt>Step 1</dt>
<dd>Look at the number of tiles displayed within the &quot;Stitch&quot; tab by &quot;Number of Tiles&quot;</dd>
<dt>Step 2</dt>
<dd>Take the first number and divide this by 100, then multiply it by 15. Round this number up to the nearest whole number and select this under &quot;Split Image&quot; next to the &quot;Horizontally&quot; window</dd>
<dt>Step 3</dt>
<dd>Apply the same method to the second number (i.e. after the x), but select this next to the &quot;Vertically&quot; window</dd>
</dl>
<p><strong>Example:</strong></p>
<ul>
<li>
<p>Number of tiles shown is 60 x 66</p>
</li>
<li>
<p>60 / 100 x 15 = 9</p>
</li>
<li>
<p>66 / 100 x 15 = 9.9 (10 when rounded up)</p>
</li>
<li>
<p>9 is inputted into the &quot;Horizontally&quot; window, and 10 into the &quot;Vertically&quot; window</p>
</li>
</ul>
</section>
</section>
</section>
</section>


4.2 Exporting Imagery

<section id="4.3-importing-imagery">
<h1><a class="header-anchor" href="#4.3-importing-imagery"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 4.3 Importing Imagery</h1>
<section id="4.3.1">
<h3><a class="header-anchor" href="#4.3.1">4.3.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>
<p>Tap &quot;Satellite&quot; from the Management Buttons on the left of the screen</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Tap &quot;Import Imagery&quot;</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>A window will appear allowing you to navigate around your device to find the files that you want to import</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>It can take a while (even a few minutes) for the imagery to import, this is normal. No other actions are possible whilst importing is in progress</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>


4.3 Importing Imagery

<section id="5.1-editing-runways">
<h1><a class="header-anchor" href="#5.1-editing-runways"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 5.1 Editing Runways</h1>
<section id="creating-a-runway">
<h2><a class="header-anchor" href="#creating-a-runway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Creating a Runway</h2>
<section id="5.1.1">
<h3><a class="header-anchor" href="#5.1.1">5.1.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Tap in the area of the airport that you want to place the new runway <strong>(1)</strong></dd>
<dt>Step 2</dt>
<dd>Tap &quot;Object&quot; and then &quot;Create Runway&quot;. A runway will be placed at the cursor's location, and your editor will enter ShapeEditing mode automatically <strong>(2)</strong></dd>
<dt>Step 3</dt>
<dd>Adjust the nodes of the runway to ensure it lines up with the imagery. Placing and deleting nodes of the runway object is not possible</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways1@3x.png 3x" alt="Image 5.1.1.1 - Creating a Runway" class="documentation-image-lightbox-link" >
          <figcaption>Image 5.1.1.1 - Creating a Runway</figcaption>
        </figure>
      </p>
<blockquote>
<p>If the new runway has ILS in real life, it <strong class="red">must</strong> be added in Infinite Flight as well. In order to do that, open a Reviewer ticket in the IFAET Discord server, and notify them of the new runway with ILS at your airport.</p>
</blockquote>
</section>
</section>
</section>
<section id="editing-an-existing-runway">
<h2><a class="header-anchor" href="#editing-an-existing-runway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Editing an Existing Runway</h2>
<section id="5.1.2">
<h3><a class="header-anchor" href="#5.1.2">5.1.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the runway by tapping on or near the line, you may have to select the runway from a drop down list if there are multiple items in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Tap the &quot;Modify Shape&quot; button on the right side <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>The runway's nodes will appear</dd>
<dt>Step 4</dt>
<dd>By tapping a node it will turn magenta <strong>(2)</strong> to show it has been selected <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 5</dt>
<dd>You can then tap, hold and then drag your finger on the screen to move the node(s) into the desired position</dd>
<dt>Step 6</dt>
<dd>When editing is complete, tap &quot;Modify Shape&quot; to deselect it (you will be unable to edit other objects without doing this)</dd>
</dl>
<blockquote>
<p>If the modified runway has ILS in real life, the ILS properties <strong class="red">must</strong> modified in Infinite Flight as well. In order to do that, open a Reviewer ticket in the IFAET Discord server, and notify them of the modified runway with ILS at your airport.</p>
</blockquote>
</section>
</section>
</section>
<section id="movingchanging-orientation-of-a-runway">
<h2><a class="header-anchor" href="#movingchanging-orientation-of-a-runway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Moving/Changing Orientation of a Runway</h2>
<section id="5.1.3">
<h3><a class="header-anchor" href="#5.1.3">5.1.3</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the runway by tapping on or near the runway <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the runway from a drop down box if there are multiple in close proximity. The runway's name will appear to indicate it has been selected <strong>(1)</strong></dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>If you have only just made the runway then just tap &quot;Modify Shape&quot; to deselect this and the runway will be selected</dd>
</dl>
<dl>
<dt>Step 3</dt>
<dd>Two circles will appear as well as a compass rose. Tap and hold on the circle <strong>(2)</strong> to move the runway or to change orientation:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Circle</th>
<th>Function</th>
</tr>
</thead>
<tbody>
<tr>
<td>Center</td>
<td>Will move the runway endpoints by dragging your finger to the desired location</td>
</tr>
<tr>
<td>Outer</td>
<td>Will change the orientation of the runway endpoints by dragging your finger in the direction you want to orientate it to</td>
</tr>
</tbody>
</table></div><p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways2.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways2@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways2@3x.png 3x" alt="Image 5.1.3.1 - Moving/Changing Orientation of Runway" class="documentation-image-lightbox-link" >
          <figcaption>Image 5.1.3.1 - Moving/Changing Orientation of Runway</figcaption>
        </figure>
      </p>
<blockquote>
<p>If the moved runway has ILS in real life, the ILS will move together with the runway, as long as it has not been otherwise modified.</p>
</blockquote>
</section>
</section>
</section>
<section id="deleting-a-runway">
<h2><a class="header-anchor" href="#deleting-a-runway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Deleting a Runway</h2>
<section id="5.1.4">
<h3><a class="header-anchor" href="#5.1.4">5.1.4</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the runway by tapping on or near the runway <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the runway from a drop down box if there are multiple in close proximity. The runway's name will appear to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap &quot;Delete Selection&quot; from the edit buttons <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways3.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways3@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/editing-runways3@3x.png 3x" alt="Image 5.1.4.1 - Deleting a Runway" class="documentation-image-lightbox-link" >
          <figcaption>Image 5.1.4.1 - Deleting a Runway</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
</section>


5.1 Editing Runways

<section id="5.2-properties">
<h1><a class="header-anchor" href="#5.2-properties"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 5.2 Properties</h1>
<section id="5.2.1">
<h3><a class="header-anchor" href="#5.2.1">5.2.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the runway by tapping on or near the runway <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the runway from a drop down box if there are multiple in close proximity. The runway name will appear to indicate it has been selected</dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Properties&quot; tab on the right side of the screen</dd>
<dt>Step 4</dt>
<dd>You can then adjust the following properties for the runway</dd>
<dt>Step 5</dt>
<dd>Runway property changes don't take effect immediately. To make them reflect, simply place an object, like an Electrical Equipment Building, next to the runway and move it after changing the runway properties. It will make the runway update to the new settings. Don't forget to remove the object when done.</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Runway</td>
<td>Runway properties, such as markings and lights</td>
<td>See <a href="#5.2.2">5.2.2</a> below</td>
</tr>
<tr>
<td>Latitude / Longitude</td>
<td>Coordinates of the runway</td>
<td><strong class="red">Should not</strong> be changed, it does not move the runway itself</td>
</tr>
<tr>
<td>Altitude</td>
<td>This shows the current altitude (in meters) of the start location. <em>(Inherited from the airport's elevation - see <a href="/guide/scenery-editor-manual/3.-getting-started/3.2-airport-properties#3.2.2" class="documentation-content-link">3.2</a>)</em></td>
<td><strong class="red">Should not</strong> be changed</td>
</tr>
<tr>
<td>Name</td>
<td>You can name the runway using this field</td>
<td>Correct format: &quot;<em>(Lower RWY end ID)</em>[L/R/C/T]-<em>(Higher RWY end ID)</em>[L/R/C/T]&quot;. L/R/C/T are optional, they <strong class="red">must only</strong> be added if the runway identifier has one of these IRL. Examples: 09-27, 08R-26L, 18C-36C, 03T-21T</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="5.2.2">
<h3><a class="header-anchor" href="#5.2.2">5.2.2</a></h3>
<section class="reference">
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Width</td>
<td>You can change the width of the runway (in meters)</td>
<td></td>
</tr>
<tr>
<td>Surface</td>
<td>You can change the surface type by tapping this</td>
<td>Surface types <strong class="red">must</strong> be chosen based on airport documentation, rather than what is seen on satellite imagery (i.e. even if a bright asphalt runways looks like concrete color-wise, it <strong class="red">must</strong> still be drawn as asphalt)</td>
</tr>
<tr>
<td>ShoulderSurface</td>
<td>You can change the runway shoulder surface type (concrete or asphalt)</td>
<td>Surface types <strong class="red">must</strong> be chosen based on airport documentation, rather than what is seen on satellite imagery (i.e. even if a bright asphalt runways looks like concrete color-wise, it <strong class="red">must</strong> still be drawn as asphalt)</td>
</tr>
<tr>
<td>HasEdgeLights</td>
<td>You can change whether or not the runway has edge lights</td>
<td><strong class="red">Must</strong> be set in accordance with airport documentation</td>
</tr>
<tr>
<td>HasCenterlineLights</td>
<td>You can change whether or not the runwyay has centerline lights</td>
<td><strong class="red">Must</strong> be set in accordance with airport documentation</td>
</tr>
<tr>
<td>RunwayEnds</td>
<td>Runway end properties</td>
<td>See <a href="#5.2.3">5.2.3</a> below</td>
</tr>
<tr>
<td>Length</td>
<td>Shows the runway length (in meters)</td>
<td>Cannot be changed through the Properties window. Calculated based on the distance between the two nodes</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="5.2.3">
<h3><a class="header-anchor" href="#5.2.3">5.2.3</a></h3>
<section class="reference">
<p>The RunwayEnds property contains two runway end groups. Their structure is identical; properties in these can differ.</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Overrun</td>
<td>You can change the runway overrun area (in meters)</td>
<td>See 5.2.4 below for more details</td>
</tr>
<tr>
<td>DisplacedThreshold</td>
<td>You can change how much the runway threshold is dispalced (in meters)</td>
<td>See 5.2.4 below for more details</td>
</tr>
<tr>
<td>Approach Lights</td>
<td>You can change the approach lights</td>
<td>Approach lights <strong class="red">must</strong> be set in accordance with airport documentation</td>
</tr>
<tr>
<td>Markings</td>
<td>You can change the markings type of the runway</td>
<td></td>
</tr>
<tr>
<td>Touchdown Lighting</td>
<td>You can change whether or not the runway end has touchdown lighting</td>
<td>Currently unavailable in Infinite Flight. Touchdown lighting <strong class="red">must</strong> be set in accordance with airport documentation for futureproofing purposes.</td>
</tr>
<tr>
<td>REILType</td>
<td>You can change the Runway End Identifier Lights type</td>
<td>REIL lights <strong class="red">must</strong> be set in accordance with airport documentation</td>
</tr>
<tr>
<td>Location</td>
<td>Coordinates of the runway end</td>
<td><strong class="red">Should not</strong> be changed</td>
</tr>
<tr>
<td>Identifier</td>
<td>You can change the runway end identifier[^1]</td>
<td>Correct format: &quot;<em>(RWY ID)</em>[L/R/C/T]. L/R/C/T are optional, they <strong class="red">must only</strong> be added if the runway identifier has one of these IRL.</td>
</tr>
<tr>
<td>Glideslope / Localizer</td>
<td><em>N/A</em>[^2]</td>
<td><strong class="red">Must not</strong> be set</td>
</tr>
<tr>
<td>Heading</td>
<td>Changes the runway end heading</td>
<td><strong class="red">Should not</strong> be changed through the Properties window, move the runway nodes instead <em>(see <a href="#5.2.1">5.1.2</a> above)</em></td>
</tr>
</tbody>
</table></div><blockquote>
<p>[^1] In case a runway identifier for an ILS end of a runway has been modified, open a Reviewer ticket in the IFAET Discord server, and notify them of the runway end identifier change. An app restart will be required after changing identifiers (Make sure to save before restarting). Taxiway network checker will not work until the database has been updated (typically just before an app update)</p>
</blockquote>
<blockquote>
<p>[^2] In case a runway has missing ILS, open a Reviewer ticket in the IFAET Discord server, and notify them of the missing ILS for the respective runway.</p>
</blockquote>
</section>
</section>
<section id="5.2.4">
<h3><a class="header-anchor" href="#5.2.4">5.2.4</a></h3>
<section class="reference">
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/runway-end-markings.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/runway-end-markings@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/runway-end-markings@3x.jpg 3x" alt="Image 5.2.4.1 - Runway End Markings" class="documentation-image-lightbox-link" >
          <figcaption>Image 5.2.4.1 - Runway End Markings</figcaption>
        </figure>
      </p>
<p>The red dot shown in the image above is where the runway end point should be located when editing runways</p>
<p>Overrun - The portion of the runway marked with yellow chevons, not meant for use by aircraft (unless in case of an emergency)</p>
<p>Displaced Threshold - This is where the Threshold of the runway is further down the runway due to landing restrictions. The portion in front of it can be used for takeoffs. The runway end point should be located at the beginning of this area, then the threshold displaced with the correct property (as seen above)</p>
</section>
</section>
</section>


5.2 Properties

<section id="5.3-runways-dos-and-donts">
<h1><a class="header-anchor" href="#5.3-runways-dos-and-donts"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 5.3 Runways Dos and Don'ts</h1>
<section class="reference">
<p>Below is a table containing what you do need to edit and what you do not edit, while working with runways</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th><i class="icon check circle"></i> DO</th>
<th><i class="icon times circle"></i> DO NOT</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i> Notify reviewers if you've modified a runway that has ILS</td>
<td><i class="icon times circle"></i> Add runway markings including markings for displaced thresholds and blast pads</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Only add X's to taxiways and runways that are permanently closed</td>
<td><i class="icon times circle"></i> Add X's to taxiways and runways that are temporarily closed</td>
</tr>
<tr>
<td></td>
<td></td>
</tr>
</tbody>
</table></div></section>
</section>


5.3 Dos and Don'ts

<section id="6.1-editing-pavements">
<h1><a class="header-anchor" href="#6.1-editing-pavements"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.1 Editing Pavements</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Whenever you connect buildings/lines/pavements, you <strong class="red">must</strong> use the &quot;Snap&quot; function to avoid gaps and/or overlapping <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.4" class="documentation-content-link">2.1.4</a> above)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="creating-pavements">
<h2><a class="header-anchor" href="#creating-pavements"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Creating Pavements</h2>
<section id="6.1.1">
<h3><a class="header-anchor" href="#6.1.1">6.1.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Tap &quot;Pavement&quot; and then &quot;Create Pavement&quot; <strong>(1)</strong> from the management buttons on the left</dd>
<dt>Step 2</dt>
<dd>Tap in the area of the airport that you want pavement <strong>(2)</strong>, the first node will be placed</dd>
<dt>Step 3</dt>
<dd>Continue to tap to add nodes <strong>(3)</strong>, once three or more are placed, a section of pavement will be created</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.1.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.1.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.1.1@3x.png 3x" alt="Image 6.1.1.1 - Creating Pavements" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.1.1.1 - Creating Pavements</figcaption>
        </figure>
      </p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Use the walls of a shipping container to help make 90 degree corners</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="editing-an-existing-pavements-shape">
<h2><a class="header-anchor" href="#editing-an-existing-pavements-shape"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Editing an Existing Pavements Shape</h2>
<section id="6.1.2">
<h3><a class="header-anchor" href="#6.1.2">6.1.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the pavement by tapping on or near the pavement, you may have to select the pavement from a drop down list if there are multiple items in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Tap the &quot;Modify Shape&quot; button on the right side <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>The outline will turn magenta when selected and nodes will appear</dd>
<dt>Step 4</dt>
<dd>By tapping a node it will turn magenta <strong>(2)</strong> to show it has been selected <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 5</dt>
<dd>You can then tap, hold and then drag your finger on the screen to move the node(s) into the desired position</dd>
<dt>Step 6</dt>
<dd>When editing is complete, tap &quot;Modify Shape&quot; to deselect it (you will be unable to edit other pavements without doing this)</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/6.3.1.1b.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/6.3.1.1b@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/6.3.1.1b@3x.png 3x" alt="Image 6.1.2.1 - Editing Pavements" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.1.2.1 - Editing Pavements</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="movingchanging-orientation-of-pavement">
<h2><a class="header-anchor" href="#movingchanging-orientation-of-pavement"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Moving/Changing Orientation of Pavement</h2>
<section id="6.1.3">
<h3><a class="header-anchor" href="#6.1.3">6.1.3</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the pavement by tapping on or near the pavement <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the pavement from a drop down box if there are multiple in close proximity. The outline of the pavement will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>If you have only just made the pavement then just tap &quot;Modify Shape&quot; to deselect this and the pavement will be selected</dd>
</dl>
<dl>
<dt>Step 3</dt>
<dd>Two circles will appear as well as a compass rose. Tap and hold on the circle <strong>(2)</strong> to move the pavement or to change orientation:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Circle</th>
<th>Function</th>
</tr>
</thead>
<tbody>
<tr>
<td>Center</td>
<td>Will move the pavement by dragging your finger to the desired location</td>
</tr>
<tr>
<td>Outer</td>
<td>Will change the orientation of the pavement by dragging your finger in the direction you want to orientate it to</td>
</tr>
</tbody>
</table></div><p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.3.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.3.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.3.1@3x.png 3x" alt="Image 6.1.3.1 - Moving/Changing Orientation of Pavement" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.1.3.1 - Moving/Changing Orientation of Pavement</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="copy--pasting-a-pavement">
<h2><a class="header-anchor" href="#copy--pasting-a-pavement"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Copy &amp; Pasting a Pavement</h2>
<section id="6.1.4">
<h3><a class="header-anchor" href="#6.1.4">6.1.4</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the pavement by tapping on or near the pavement <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the pavement from a drop down box if there are multiple in close proximity. The outline of the pavement will turn magenta to indicate it has been selected</dd>
<dt>Step 3</dt>
<dd>Tap &quot;Edit&quot; and then &quot;Copy&quot; from the management buttons <strong>(1)</strong> on the left side of the screen</dd>
<dt>Step 4</dt>
<dd>Tap in the area of the airport that you want to add the copied pavement to, this will place a white cursor <strong>(2)</strong>. Adjust this as required and then tap &quot;Paste&quot;</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.4.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.4.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.4.1@3x.png 3x" alt="Image 6.1.4.1 - Copying &amp; Pasting a Pavement" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.1.4.1 - Copying &amp; Pasting a Pavement</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="deleting-a-pavement">
<h2><a class="header-anchor" href="#deleting-a-pavement"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Deleting a Pavement</h2>
<section id="6.1.5">
<h3><a class="header-anchor" href="#6.1.5">6.1.5</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the pavement by tapping on or near the pavement <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the pavement from a drop down box if there are multiple in close proximity. The outline of the pavement will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap &quot;Delete Selection&quot; from the edit buttons <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.5.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.5.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.5.1@3x.png 3x" alt="Image 6.1.5.1 - Deleting a Pavement" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.1.5.1 - Deleting a Pavement</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="creating-a-hole-within-the-pavement">
<h2><a class="header-anchor" href="#creating-a-hole-within-the-pavement"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Creating a Hole within the Pavement</h2>
<section id="6.1.6">
<h3><a class="header-anchor" href="#6.1.6">6.1.6</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the pavement by tapping on or near the pavement <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the pavement from a drop down box if there are multiple in close proximity. The outline of the pavement will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap &quot;Modify Shape&quot; <strong>(2)</strong> and then &quot;Create Hole&quot; from the edit buttons <strong>(3)</strong> on the right side of the screen</dd>
<dt>Step 4</dt>
<dd>Tap in the area of the pavement that you want the hole <strong>(4)</strong>, the first node will be placed</dd>
<dt>Step 5</dt>
<dd>Continue to tap to add nodes <strong>(5)</strong>, once three or more are placed, a hole will be created and you can continue to add more nodes to create the desired shape</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.6.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.6.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.6.1@3x.png 3x" alt="Image 6.1.6.1 - Creating a Hole within the Pavement" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.1.6.1 - Creating a Hole within the Pavement</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


6.1 Editing Pavements

<section id="6.2-properties">
<h1><a class="header-anchor" href="#6.2-properties"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.2 Properties</h1>
<section id="6.2.1">
<h3><a class="header-anchor" href="#6.2.1">6.2.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the pavement by tapping on or near the pavement <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the pavement from a drop down box if there are multiple in close proximity. The outline of the pavement will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Properties&quot; tab <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.2.1.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.2.1.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.2.1.1@3x.png 3x" alt="Image 6.2.1.1 - Pavement Properties" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.2.1.1 - Pavement Properties</figcaption>
        </figure>
      </p>
<dl>
<dt>Step 4</dt>
<dd>You can then adjust the following properties for pavements:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Surface Type</td>
<td>You can change the surface type by tapping this</td>
<td>Surface types that are a close match to the satellite imagery <strong class="red">must</strong> be used (i.e. even if a bright asphalt looks like concrete color-wise, it <strong class="red">must</strong> still be drawn as asphalt)</td>
</tr>
<tr>
<td>Texture Orientation</td>
<td>Add any number between 0 and 360 to change the grain of the textures (orientated around true north)</td>
<td>This is particuarly useful to make the textures align with the direction of taxiways. You can also tap &quot;Building&quot; &gt; &quot;Auto Texture Orientation&quot; from the management buttons on the left to do this <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.2" class="documentation-content-link">2.1.2</a> above)</em></td>
</tr>
<tr>
<td>Latitude / Longitude</td>
<td>Current latitude/longitude of the pavement</td>
<td>This <strong class="red">should not</strong> be changed</td>
</tr>
<tr>
<td>Altitude</td>
<td>This shows the current altitude (in meters) of the pavement. Tap the number and then enter in a new value to adjust this</td>
<td>The altitude is always based on the elevation of the airport (this <strong class="red">should not</strong> be changed)</td>
</tr>
<tr>
<td>Name</td>
<td>You can name the pavement using this field</td>
<td>Pavements do not need to be named but it can help during the editing process to be able to distinguish between different pavements if they are labelled</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>


6.2 Properties

<section id="6.3-pavements-dos-and-donts">
<h1><a class="header-anchor" href="#6.3-pavements-dos-and-donts"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.3 Pavements Dos and Don'ts</h1>
<section class="reference">
<p>Below is a table containing what you do need to edit and what you do not edit, while working with pavements</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th><i class="icon check circle"></i> DO</th>
<th><i class="icon times circle"></i> DO NOT</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i> Add roads and taxiways as shown in charts and satellite imagery</td>
<td><i class="icon times circle"></i> Add public roads which are invisible or irrelevant for pilots using the airport</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add grass pavement where they are used for aircraft movements</td>
<td><i class="icon times circle"></i> Add grass or green pavement to replicate pieces of lawn which are not used as movement areas</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add public roads in areas which are prominently visible from aircraft movement areas</td>
<td><i class="icon times circle"></i> Add concrete or snow pavements to replicate bright asphalt areas</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add concrete pavement below hangar buildings (other materials are allowed if this is present IRL)</td>
<td><i class="icon times circle"></i> Create pavement areas using lots of small segments unnecessarily</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Keep the number of connecting nodes between taxiway pieces to a minimum</td>
<td><i class="icon times circle"></i> Add snow pavements to create texts or symbols on the ground</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add pavement patches on top of the surrounding pavements (i.e. no hole created underneath)*</td>
<td><i class="icon times circle"></i> Add any types of “easter eggs”</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Use too many nodes for edges</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Recreate broken pavements</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Create holes in pavements just for buildings</td>
</tr>
</tbody>
</table></div><p>*<em>If there is a more performance efficient way (i.e. less nodes created) then this is acceptable (at the Reviewers discretion). E.g. snapping a pavement patch to the edge of the pavement rather than placing it on top, or allowing holes to be created underneath</em></p>
</section>
</section>


6.3 Dos and Don'ts

<section id="7.1-editing-taxiways">
<h1><a class="header-anchor" href="#7.1-editing-taxiways"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7.1 Editing Taxiways</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Whenever you connect buildings/lines/pavements, you <strong class="red">must</strong> use the &quot;Snap&quot; function to avoid gaps and/or overlapping <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.4" class="documentation-content-link">2.1.4</a> above)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="creating-a-taxiway">
<h2><a class="header-anchor" href="#creating-a-taxiway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Creating a Taxiway</h2>
<section id="7.1.1">
<h3><a class="header-anchor" href="#7.1.1">7.1.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Tap &quot;Taxiways&quot; and then &quot;Create Taxiway Line&quot; <strong>(1)</strong></dd>
<dt>Step 2</dt>
<dd>Tap in the area of the airport that you want a taxiway line <strong>(2)</strong>, the first node will be placed</dd>
<dt>Step 3</dt>
<dd>Continue to tap to add nodes <strong>(3)</strong>, a taxiway line will continue to be drawn between the nodes</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.2.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.2.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.2.1@3x.png 3x" alt="Image 7.1.1.1 - Creating a Taxiway" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.1.1.1 - Creating a Taxiway</figcaption>
        </figure>
      </p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Avoid creating long sections of straight lines with no nodes near gates, or pilots could suffer issues with the auto pushback feature</p>
</dd>
</dl>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Use the walls of a shipping container to help make 90 degree corners</p>
</dd>
</dl>
</section>
</section>
</dl>
</section>
<section id="editing-an-existing-line">
<h2><a class="header-anchor" href="#editing-an-existing-line"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Editing an Existing Line</h2>
<section id="7.1.2">
<h3><a class="header-anchor" href="#7.1.2">7.1.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the taxiway by tapping on or near the line, you may have to select the taxiway from a drop down list if there are multiple items in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Tap the &quot;Modify Shape&quot; button on the right side <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>The line will turn magenta when selected and nodes will appear</dd>
<dt>Step 4</dt>
<dd>By tapping a node it will turn magenta <strong>(2)</strong> to show it has been selected <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 5</dt>
<dd>You can then tap, hold and then drag your finger on the screen to move the node(s) into the desired position</dd>
<dt>Step 6</dt>
<dd>When editing is complete, tap &quot;Modify Shape&quot; to deselect it (you will be unable to edit other taxiways without doing this)</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/6.3.1.1b.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/6.3.1.1b@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/6.3.1.1b@3x.png 3x" alt="Image 7.1.2.1 - Editing Taxiways" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.1.2.1 - Editing Taxiways</figcaption>
        </figure>
      </p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If a line has too many nodes for, use the Simplify option under Line Options</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="movingchanging-orientation-of-taxiway">
<h2><a class="header-anchor" href="#movingchanging-orientation-of-taxiway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Moving/Changing Orientation of Taxiway</h2>
<section id="7.1.3">
<h3><a class="header-anchor" href="#7.1.3">7.1.3</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the taxiway by tapping on or near the taxiway <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the taxiway from a drop down box if there are multiple in close proximity. The outline of the taxiway will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>If you have only just made the taxiway then just tap &quot;Modify Shape&quot; to deselect this and the taxiway will be selected</dd>
</dl>
<dl>
<dt>Step 3</dt>
<dd>Two circles will appear as well as a compass rose. Tap and hold on the circle <strong>(2)</strong> to move the taxiway or to change orientation:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Circle</th>
<th>Function</th>
</tr>
</thead>
<tbody>
<tr>
<td>Center</td>
<td>Will move the taxiway by dragging your finger to the desired location</td>
</tr>
<tr>
<td>Outer</td>
<td>Will change the orientation of the taxiway by dragging your finger in the direction you want to orientate it to</td>
</tr>
</tbody>
</table></div><p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.3.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.3.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.3.1@3x.png 3x" alt="Image 7.1.3.1 - Moving/Changing Orientation of Taxiway" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.1.3.1 - Moving/Changing Orientation of Taxiway</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="copy--pasting-a-taxiway">
<h2><a class="header-anchor" href="#copy--pasting-a-taxiway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Copy &amp; Pasting a Taxiway</h2>
<section id="7.1.4">
<h3><a class="header-anchor" href="#7.1.4">7.1.4</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the taxiway by tapping on or near the taxiway <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the taxiway from a drop down box if there are multiple in close proximity. The outline of the taxiway will turn magenta to indicate it has been selected</dd>
<dt>Step 3</dt>
<dd>Tap &quot;Edit&quot; and then &quot;Copy&quot; from the management buttons <strong>(1)</strong> on the left side of the screen</dd>
<dt>Step 4</dt>
<dd>Tap in the area of the airport that you want to add the copied taxiway to, this will place a white cursor <strong>(2)</strong>. Adjust this as required and then tap &quot;Paste&quot;</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.4.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.4.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.4.1@3x.png 3x" alt="Image 7.1.4.1 - Copying &amp; Pasting a Taxiway" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.1.4.1 - Copying &amp; Pasting a Taxiway</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="deleting-a-taxiway">
<h2><a class="header-anchor" href="#deleting-a-taxiway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Deleting a Taxiway</h2>
<section id="7.1.5">
<h3><a class="header-anchor" href="#7.1.5">7.1.5</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the taxiway by tapping on or near the taxiway <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the taxiway from a drop down box if there are multiple in close proximity. The outline of the taxiway will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap &quot;Delete Selection&quot; from the edit buttons <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.5.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.1.5.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.1.5.1@3x.png 3x" alt="Image 7.1.5.1 - Deleting a Taxiway" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.1.5.1 - Deleting a Taxiway</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="splitting-lines">
<h2><a class="header-anchor" href="#splitting-lines"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Splitting Lines</h2>
<section id="7.1.6">
<h3><a class="header-anchor" href="#7.1.6">7.1.6</a></h3>
<section class="reference">
<p>Each line can only have one set of properties, therefore whenever the property of a line changes, you will need a new line. It is recommended to always start with one long line drawn, and then use the &quot;split&quot; function to break the line up (to avoid having to create lots of separate lines manually), follow the steps below to do this:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>Tap the line that you want to split and then &quot;Modify Shape&quot; on the right of the screen</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Select the node that you want to split</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Tap &quot;Split Line&quot;</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>When splitting the line for the turn, it must be done at the node just as the line starts to &quot;break off&quot;</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>It is usually easiest to set the properties of the line to what is present at the node numbered &quot;0&quot;. You can then choose where to split the line, this node will become the new &quot;0&quot; and you can then change the properties for the remaining section of line. This process can then be repeated until the entire line properties have been adjusted as required</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="reverse-a-line">
<h2><a class="header-anchor" href="#reverse-a-line"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Reverse a Line</h2>
<section id="7.1.7">
<h3><a class="header-anchor" href="#7.1.7">7.1.7</a></h3>
<section class="reference">
<p>Should the nodes on a line run the wrong way, they can be reversed. (0,1,2) turns into  (2,1,0)</p>
<dl>
<dt>Step 1</dt>
<dd>Tap the line that you want to reverse</dd>
<dt>Step 2</dt>
<dd>Tap on &quot;Line Options&quot;</dd>
<dt>Step 3</dt>
<dd>Tap &quot;Reverse&quot;</dd>
</dl>
</section>
</section>
</section>
<section id="simplify-a-line">
<h2><a class="header-anchor" href="#simplify-a-line"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Simplify a Line</h2>
<section id="7.1.8">
<h3><a class="header-anchor" href="#7.1.8">7.1.8</a></h3>
<section class="reference">
<p>Should there be too many nodes on a line such as a curve, the simplify tool can be used to reduce the number of nodes while maintaining the shape of the curve</p>
<dl>
<dt>Step 1</dt>
<dd>Tap the line that you want to simplify</dd>
<dt>Step 2</dt>
<dd>Tap on &quot;Line Options&quot;</dd>
<dt>Step 3</dt>
<dd>Tap &quot;Simplify&quot;</dd>
</dl>
</section>
</section>
</section>
<section id="straighten-a-line">
<h2><a class="header-anchor" href="#straighten-a-line"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Straighten a Line</h2>
<section id="7.1.7-2">
<h3><a class="header-anchor" href="#7.1.7-2">7.1.7</a></h3>
<section class="reference">
<p>If a section of line has multiple nodes that need to be in a perfectly straight line, you can use the straighten tool to straighten out any line (or section of a line)</p>
<dl>
<dt>Step 1</dt>
<dd>Tap the line that you want to straighten</dd>
<dt>Step 2</dt>
<dd>Select the all the nodes that need to be in a straight line</dd>
<dt>Step 3</dt>
<dd>Tap on &quot;Line Options&quot;</dd>
<dt>Step 4</dt>
<dd>Tap &quot;Straighten&quot;</dd>
</dl>
</section>
</section>
</section>
<section id="change-line-layer-order">
<h2><a class="header-anchor" href="#change-line-layer-order"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Change Line Layer Order</h2>
<section id="7.1.9">
<h3><a class="header-anchor" href="#7.1.9">7.1.9</a></h3>
<section class="reference">
<p>If a section of line needs to &quot;painted&quot; on top of another line, such as runway hold lines on top of taxiway centrelines</p>
<dl>
<dt>Step 1</dt>
<dd>Tap the line that you want to move to the top</dd>
<dt>Step 2</dt>
<dd>Open the &quot;Pavements&quot; tab on the left side of the screen</dd>
<dt>Step 3</dt>
<dd>Tap on &quot;Move to Top&quot; or &quot;Move Up&quot; as necessary</dd>
</dl>
</section>
</section>
</section>


7.1 Editing Taxiways

7.2 Properties

<section id="7.3-taxiway-network">
<h1><a class="header-anchor" href="#7.3-taxiway-network"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7.3 Taxiway Network</h1>
<section id="7.3.1">
<h3><a class="header-anchor" href="#7.3.1">7.3.1</a></h3>
<section class="reference">
<p>The taxiway network allows ATC taxi instructions to be sent to aircraft from controllers in-app using the paths that are generated.</p>
<p>The taxiway network <strong class="red">must</strong> be built prior to uploading an airport for review</p>
</section>
</section>
<section id="taxiway-connections">
<h2><a class="header-anchor" href="#taxiway-connections"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Taxiway Connections</h2>
<section id="7.3.2">
<h3><a class="header-anchor" href="#7.3.2">7.3.2</a></h3>
<section class="reference">
<p>Taxiway connections are required to make a continuous path for guiding aircraft using the taxiway network. They are invisible lines that join taxiways together that are not physically connected. This allows the system to know that it can be used as a path to direct aircraft from the runway to the stand (and vice versa). Taxiway connections are required in the following cases:</p>
<ul>
<li>Start locations that are not physically connected to the taxiway line</li>
<li>Runway crossings where there is not a physical line that directly crosses the runway (not including &quot;line up&quot; lines)</li>
<li>Or self-positioning stand where there is no physical line to direct aircraft back to the taxiway after parking</li>
<li>Pushback points that don't have a physical line connecting them to the stand or main taxiway centreline</li>
</ul>
<p>These connections are allowed to overlap other lines if the node/line count would be reduced by doing so</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>When creating taxiway connections, Editors <strong class="red">should</strong> attempt to create lines that look similar to what physical taxiway lines would actually look like if they were present IRL as these can be seen on the airport maps when flying in-app</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
</section>
<section id="7.3.3">
<h3><a class="header-anchor" href="#7.3.3">7.3.3</a></h3>
<section class="reference">
<p>Below are the steps that <strong class="red">must</strong> be followed to create these:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>Tap &quot;Taxiways &gt; Create Connection&quot;</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Tap in the area of the airport that you want a taxiway connection, the first node will be placed</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Continue to tap to add nodes, a taxiway line will continue to be drawn between the nodes</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Whenever you connect buildings/lines/pavements, you <strong class="red">must</strong> use the &quot;Snap&quot; function to avoid gaps and/or overlapping <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.4" class="documentation-content-link">2.1.4</a> above)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="building-taxiway-network">
<h2><a class="header-anchor" href="#building-taxiway-network"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Building Taxiway Network</h2>
<section id="7.3.4">
<h3><a class="header-anchor" href="#7.3.4">7.3.4</a></h3>
<section class="reference">
<p>After naming all taxiways/hold lines, assigning the taxiway network usage and drawing all taxiway connections, you can build the taxiway network as described below (If you have recently changed runway identifiers, or added new ones, the taxiway network checker will fail, until the main airport database has been updated just before a release):</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>For airports with no runway hold lines, add temporary hold lines to verify the rest of the taxiway network is correct. These can then be removed before uploading for review</dd>
</dl>
<dl>
<dt>Step 1</dt>
<dd>Tap &quot;Taxiways &gt; Build Layout&quot;</dd>
</dl>
<blockquote>
<p>This process can take up to 15 minutes if the airport is large</p>
</blockquote>
<dl>
<dt>Step 2</dt>
<dd>Then tap &quot;Taxiways &gt; Check Layout&quot;. Each start location will show a list of all runways, and these will be color coded to indicate if it has a valid path to that runway:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Color</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>Red</td>
<td>Does not have valid path to the runway edge</td>
</tr>
<tr>
<td>Orange</td>
<td>Valid path to the hold short line but does not reach the runway edge</td>
</tr>
<tr>
<td>Green</td>
<td>Valid path to the runway edge</td>
</tr>
</tbody>
</table></div><dl>
<dt>Step 3</dt>
<dd>If a runway is shown in red, the Editor will need to recheck the routing to troubleshoot</dd>
</dl>
<blockquote>
<p>Editors <strong class="red">must not</strong> fix issues by simply renaming lines to &quot;APRON&quot; or by splitting longer taxiway lines into smaller pieces (Unless taxiway properties require this)</p>
</blockquote>
<dl>
<dt>Step 4</dt>
<dd>Once changes have been made, the layout will need to be rebuilt before the layout can be rechecked (i.e. repeating steps 1 and 2)</dd>
<dt>Step 5</dt>
<dd>Check that Airport Properties <em>(see <a href="/guide/scenery-editor-manual/3.-getting-started/3.2-airport-properties#3.2.2" class="documentation-content-link">3.2.2</a> above)</em> has the &quot;Taxiway Routes Available&quot; tick box selected (orange tick when selected) by tapping &quot;File &gt; Airport Properties &gt; Taxiway Routes Available&quot;</dd>
</dl>
<blockquote>
<p>Taxiway networks will not work in flight mode for controllers/pilots until this tick box is selected</p>
</blockquote>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Your local save of the taxiway network is used when you control. Using the training/IFATC servers can be a great way to troubleshoot taxiway routing issues</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>


7.3 Taxiway Network

<section id="7.1-taxiways-dos-and-donts">
<h1><a class="header-anchor" href="#7.1-taxiways-dos-and-donts"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7.1 Taxiways Dos and Don'ts</h1>
<section class="reference">
<p>Below is a table containing what you do need to edit and what you do not edit, while working with taxiways</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th><i class="icon check circle"></i> DO</th>
<th><i class="icon times circle"></i> DO NOT</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i> Add all visible taxiway lines and gate outlines</td>
<td><i class="icon times circle"></i> Add text with lines</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add roads to aprons</td>
<td><i class="icon times circle"></i> Fill areas (e.g. arrows etc.) with lines</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add stopbars at stands</td>
<td><i class="icon times circle"></i> Add hashed areas</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add hold lines and assign them to the respective runways</td>
<td><i class="icon times circle"></i> Add lines perpendicular to taxiway edge lines</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add lights to taxiway lines where present IRL</td>
<td><i class="icon times circle"></i> Make up markings</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add correct aircraft categories and taxiway names to lines according to official documentation</td>
<td><i class="icon times circle"></i> Add lights to lines that do not have lighting IRL (especially centerline lights to stand lines unless official documentation says otherwise)</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Only add X's to taxiways and runways that are permanently closed</td>
<td><i class="icon times circle"></i> Add X's to taxiways and runways that are temporarily closed</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Add anything drawn with taxiway line paint on taxiways</td>
<td><i class="icon times circle"></i> Add runway markings including markings for displaced thresholds and blast pads</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Layer holding lines ontop of taxiway centrelines</td>
<td><i class="icon times circle"></i> Add any types of “easter eggs”</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Use too many nodes for curves</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Place lines on top of other lines to create new line types</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Draw each individual car parking space (Only the outline of each block is allowed)</td>
</tr>
</tbody>
</table></div></section>
</section>


7.4 Dos and Don'ts

<section id="8.1-editing-start-locations">
<h1><a class="header-anchor" href="#8.1-editing-start-locations"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 8.1 Editing Start Locations</h1>
<section class="reference">
<blockquote>
<p>If adding/moving start locations, a navigation database update will be required before the new start locations are reflected in-app</p>
</blockquote>
</section>
<section id="how-to-see-aircraft-start-locations">
<h2><a class="header-anchor" href="#how-to-see-aircraft-start-locations"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to see Aircraft Start Locations</h2>
<section id="8.1.1">
<h3><a class="header-anchor" href="#8.1.1">8.1.1</a></h3>
<section class="reference">
<p>Before placing objects near aircraft start locations, it is recommended to turn on Aircraft Start Locations following these steps:</p>
<dl>
<dt>Step 1</dt>
<dd>On the left of the screen, tap &quot;View&quot;</dd>
<dt>Step 2</dt>
<dd>Then tap &quot;Start Locations&quot; (it will change to amber to indicate it has been selected)</dd>
<dt>Step 3</dt>
<dd>Each start location will be represented by a blue dot. By zooming in on a start location you will be able to see the start location details including:</dd>
</dl>
<ul>
<li>Identifier (i.e. Terminal and stand number)</li>
<li>Type (i.e. Gate, Tie-down, Misc or Hangar)</li>
<li>Gate Size (i.e. maximum aircraft category)</li>
<li>Ramp Operation Type (i.e. GA, Airline, Cargo or Military)</li>
</ul>
</section>
</section>
</section>
<section id="selecting-and-placing-a-start-location">
<h2><a class="header-anchor" href="#selecting-and-placing-a-start-location"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Selecting and Placing a Start Location</h2>
<section id="8.1.2">
<h3><a class="header-anchor" href="#8.1.2">8.1.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>
<p>Scroll up/down the list on the right of the screen to see the object repository (the &quot;Library&quot; tab <strong class="red">must</strong> be selected)</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Select &quot;Start Location&quot; under &quot;Airport Items&quot; by tapping it <strong>(1)</strong></p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Tap in the area of the airport that you want to add the start location to (you may have to press and hold), this will place a white cursor <strong>(2)</strong>. Adjust this as required and then tap &quot;Add Object&quot; <strong>(3)</strong></p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>You might need to &quot;freeze&quot; lines and pavements to avoid these being selected when tapping on your screen. To do this tap &quot;Edit &gt; Freeze All Lines / Freeze All Pavements&quot;</p>
</dd>
</dl>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.1.2.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.1.2.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.1.2.1a@3x.png 3x" alt="Image 8.1.2.1 - Start Location Placement" class="documentation-image-lightbox-link" >
          <figcaption>Image 8.1.2.1 - Start Location Placement</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
</section>
<section id="changing-positionorientation-of-a-start-location">
<h2><a class="header-anchor" href="#changing-positionorientation-of-a-start-location"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Changing Position/Orientation of a Start Location</h2>
<section id="8.1.3">
<h3><a class="header-anchor" href="#8.1.3">8.1.3</a></h3>
<section class="reference">
<p>The blue circle of the start location is the default position where an aircraft nose wheel will be located when spawning, follow the steps below to adjust the position and orientation of the start location to match its position IRL:</p>
<blockquote>
<p>The orientation of the start location <strong class="red">must</strong> exactly match the orientation of the gate centerline</p>
</blockquote>
<dl>
<dt>Step 1</dt>
<dd>Select the start location by tapping on or near the blue circle <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>The circle will turn magenta to indicate it has been selected. If there are multiple objects in close proximity, a list will appear so you can select the object you want</dd>
<dt>Step 3</dt>
<dd>Two circles will appear as well as a compass rose. Tap and hold on the circle <strong>(1)</strong> to move the start location or to change orientation:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Circle</th>
<th>Function</th>
</tr>
</thead>
<tbody>
<tr>
<td>Center</td>
<td>Will move the start location by dragging your finger to the desired location</td>
</tr>
<tr>
<td>Outer</td>
<td>Will change the orientation of the start location by dragging your finger in the direction you want to orientate it to</td>
</tr>
</tbody>
</table></div><p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.1.3.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.1.3.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.1.3.1a@3x.png 3x" alt="Image 8.1.3.1 - Changing Start Location Orientation" class="documentation-image-lightbox-link" >
          <figcaption>Image 8.1.3.1 - Changing Start Location Orientation</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="copy--pasting-a-start-location">
<h2><a class="header-anchor" href="#copy--pasting-a-start-location"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Copy &amp; Pasting a Start Location</h2>
<section id="8.1.4">
<h3><a class="header-anchor" href="#8.1.4">8.1.4</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>
<p>Select the start location by tapping on or near the blue circle <strong>(1)</strong> <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></p>
</dd>
<dt>Step 2</dt>
<dd>
<p>The circle will turn magenta to indicate it has been selected. If there are multiple objects in close proximity, a list will appear so you can select the start location you want</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Tap the &quot;Edit&quot; button <strong>(2)</strong> on the left of the screen and then Copy&quot; button <strong>(3)</strong></p>
</dd>
<dt>Step 4</dt>
<dd>
<p>Tap in the area of the airport that you want to add the copied start location to (you may have to press and hold), this will place a white cursor <strong>(4)</strong>. Adjust this as required and then tap &quot;Paste&quot; <strong>(5)</strong></p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>You might need to &quot;freeze&quot; lines and pavements to avoid these being selected when tapping on your screen. To do this tap &quot;Edit &gt; Freeze All Lines / Freeze All Pavements&quot;</p>
</dd>
</dl>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.1.4.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.1.4.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.1.4.1a@3x.png 3x" alt="Image 8.1.4.1 - Copy &amp; Pasting a Start Location" class="documentation-image-lightbox-link" >
          <figcaption>Image 8.1.4.1 - Copy &amp; Pasting a Start Location</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="deleting-a-start-location">
<h2><a class="header-anchor" href="#deleting-a-start-location"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Deleting a Start Location</h2>
<section id="8.1.5">
<h3><a class="header-anchor" href="#8.1.5">8.1.5</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the start location by tapping on or near the blue circle <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>The circle will turn magenta to indicate it has been selected. If there are multiple objects in close proximity, a list will appear so you can select the start location you want</dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Delete Selection&quot; button <strong>(1)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.1.5.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.1.5.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.1.5.1a@3x.png 3x" alt="Image 8.1.5.1 - Deleting a Start Location" class="documentation-image-lightbox-link" >
          <figcaption>Image 8.1.5.1 - Deleting a Start Location</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


8.1 Editing Start Locations

<section id="8.2-properties">
<h1><a class="header-anchor" href="#8.2-properties"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 8.2 Properties</h1>
<section id="8.2.1">
<h3><a class="header-anchor" href="#8.2.1">8.2.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the start location by tapping on or near it <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>You may have to select the start location from a drop down box if there are multiple items in close proximity. The outline of the start location will turn magenta to indicate it has been selected <strong>(1)</strong></dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Properties&quot; tab <strong>(2)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.1.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/7.2.1.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/7.2.1.1a@3x.png 3x" alt="Image 8.2.1.1 - Start Location Properties" class="documentation-image-lightbox-link" >
          <figcaption>Image 8.2.1.1 - Start Location Properties</figcaption>
        </figure>
      </p>
<dl>
<dt>Step 4</dt>
<dd>You can then adjust the following properties for start locations:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Terminal</td>
<td>You can name the terminal using this field</td>
<td>This <strong class="red">must</strong> be the name of the general area the spawn is located in (such as Terminal/Concourse/GA/Cargo/Apron/FBO etc.)</td>
</tr>
<tr>
<td>Ramp Size</td>
<td>The maximum size aircraft category that can spawn and park on that stand is determined with this setting</td>
<td>See <a href="/guide/scenery-editor-manual/1.-introduction/1.3-aircraft-categories" class="documentation-content-link">1.3</a> above</td>
</tr>
<tr>
<td>Ramp Start Type</td>
<td>Indicate if this start location is a Gate, Tie-Down, Hangar or Misc</td>
<td>N/A</td>
</tr>
<tr>
<td>Ramp Operation Type</td>
<td>Indicate the primary operational use of the start location</td>
<td>N/A</td>
</tr>
<tr>
<td>Equipment Type</td>
<td>N/A</td>
<td>Not required at this time</td>
</tr>
<tr>
<td>Gate Stops</td>
<td>Gate stops for different aircraft types at the same start location</td>
<td>See <a href="/guide/scenery-editor-manual/8.-start-locations/8.2-properties#8.2.2" class="documentation-content-link">8.2.2</a> below</td>
</tr>
<tr>
<td>Stand Guidance</td>
<td>N/A</td>
<td>This is automatically loaded when the app is launched in flight mode</td>
</tr>
<tr>
<td>Latitude / Longitude</td>
<td>Current latitude/longitude of the start location</td>
<td>Can be changed to precisely place the start location (e.g. using coordinates from charts)</td>
</tr>
<tr>
<td>Altitude</td>
<td>This shows the current altitude (in meters) of the start location</td>
<td><strong class="red">Should not</strong> be changed</td>
</tr>
<tr>
<td>Name</td>
<td>You can name the gate using this field</td>
<td>A format such as &quot;Gate/Stand [alphanumeric/number]&quot; is recommended - Editors <strong>must</strong> ensure that terminal names (e.g. T1) are not included in the &quot;Name&quot; property</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="gate-stops">
<h2><a class="header-anchor" href="#gate-stops"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Gate Stops</h2>
<section id="8.2.2">
<h3><a class="header-anchor" href="#8.2.2">8.2.2</a></h3>
<section class="reference">
<p>To add/delete or edit gate stops, the below steps <strong class="red">must</strong> be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Tap the &quot;+&quot; symbol next to &quot;Gate Stops&quot; <strong>(1)</strong></dd>
<dt>Step 2</dt>
<dd>All gate stops currently listed for that start location will appear beneath, if there are none it will be blank. Tap the &quot;+&quot; symbol underneath this on the right to add more <strong>(2)</strong></dd>
<dt>Step 3</dt>
<dd>A line saying &quot;No Types Specified&quot; will appear. To the left of this will be a &quot;+&quot; symbol <strong>(3)</strong>, tap this to expand the gate stop so aircraft types and the offset can be set</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.3.4.1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.3.4.1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.3.4.1@3x.png 3x" alt="Image 8.2.2.1 - Adding Gate Stops" class="documentation-image-lightbox-link" >
          <figcaption>Image 8.2.2.1 - Adding Gate Stops</figcaption>
        </figure>
      </p>
<dl>
<dt>Step 4</dt>
<dd>
<p>The same symbol will then change to a &quot;-&quot; symbol <strong>(4)</strong>, tap it again to hide this expanded information</p>
</dd>
<dt>Step 5</dt>
<dd>
<p>When the list is expanded for each gate stop, tap &quot;Aircraft Type&quot; <strong>(5)</strong> to add aircraft types, a list will appear that you can add from</p>
</dd>
<dt>Step 6</dt>
<dd>
<p>Tap &quot;Offset&quot; <strong>(6)</strong> to add an offset in meters for the gate stop, this will be the distance from the start location to the point that you want certain aircraft types to stop at</p>
</dd>
<dt>Step 7</dt>
<dd>
<p>You will then see the new gate stop appear with the aircraft types applicable</p>
</dd>
<dt>Step 8</dt>
<dd>
<p>Add another gate stop with no type specified at 0m offset after adding any other gate stop. &quot;Any&quot; should be displayed on the start location (Failure to do so will result in jetbridges not working for that stand)</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If multiple aircraft have the same offset, add all these aircraft types to one stop gate rather than making multiple ones</p>
</dd>
</dl>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/5.3.4.2.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/5.3.4.2@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/5.3.4.2@3x.png 3x" alt="Image 8.2.2.2 - Setting Gate Stop Aircraft Types and Offsets" class="documentation-image-lightbox-link" >
          <figcaption>Image 8.2.2.2 - Setting Gate Stop Aircraft Types and Offsets</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
</section>


8.2 Properties

<section id="9.1-editing-buildings">
<h1><a class="header-anchor" href="#9.1-editing-buildings"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 9.1 Editing Buildings</h1>
<section class="reference">
<p>Buildings in Infinite Flight are created from building parts. Each part is defined by at least 2 nodes and a height in meters
(See below)</p>
<p>A roof can also be added if a building part contains at least 3 nodes forming at least one corner. Other object properties can be edited, such as name, if the part should be enclosed and height
(See <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.2-properties" class="documentation-content-link">9.2</a>)</p>
<p>Each building part can be assigned a texture
(See <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.3-editing-facades" class="documentation-content-link">9.3</a>)</p>
<p>Stacking multiple building parts together is known as &quot;layering&quot; and can be used to create complicated buildings
(See <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.4-layering" class="documentation-content-link">9.4</a>)</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Whenever you connect buildings/lines/pavements, you <strong class="red">must</strong> use the &quot;Snap&quot; function to avoid gaps and/or overlapping <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.4" class="documentation-content-link">2.1.4</a> above)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="selecting-and-placing-a-building">
<h2><a class="header-anchor" href="#selecting-and-placing-a-building"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Selecting and Placing a Building</h2>
<section id="9.1.1">
<h3><a class="header-anchor" href="#9.1.1">9.1.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Tap &quot;Building Parts&quot; and then &quot;Create Building Part&quot; <strong>(1)</strong> from the management buttons on the left</dd>
<dt>Step 2</dt>
<dd>Tap in the area of the airport that you want a building <strong>(2)</strong>, the first node will be placed</dd>
<dt>Step 3</dt>
<dd>Continue to tap to add nodes <strong>(3-5)</strong>, once 2 nodes are placed a wall will be created, add more nodes to add more walls as required</dd>
<dt>Step 4</dt>
<dd>Walls are only visible on one side, If the walls appears &quot;inside out&quot;, you can tap &quot;Line Options&quot; &gt; &quot;Reverse Points&quot; on the right side of the screen which will reverse the numbering of all points</dd>
<dt>Step 5</dt>
<dd>If you need to enclose the building, open the properties tab and tick the &quot;Closed&quot; checkbox. A wall connecting the last node to the first will appear. See <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.2-properties" class="documentation-content-link">9.2</a> for additional properties such as height and roof types</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-creating.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-creating@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-creating@3x.png 3x" alt="Image 9.1.1.1 - Creating a Building" class="documentation-image-lightbox-link" >
          <figcaption>Image 9.1.1.1 - Creating a Building</figcaption>
        </figure>
      </p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Use Angle Snapping to get perfect angles (Right Menu &gt; Snap &gt; Angle Snapping On/Off). Angle snapping will snap at 5 degree increments</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="editing-an-existing-buildings-shape">
<h2><a class="header-anchor" href="#editing-an-existing-buildings-shape"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Editing an Existing Buildings Shape</h2>
<section id="9.1.2">
<h3><a class="header-anchor" href="#9.1.2">9.1.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the building by tapping on or near the building, you may have to select the building from a drop down list if there are multiple items in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>The outlines of the walls will turn red when selected</dd>
<dt>Step 3</dt>
<dd>Tap the &quot;Modify Shape&quot; button on the right side <strong>(1)</strong>. the nodes making up the building part will be displayed</dd>
<dt>Step 4</dt>
<dd>By tapping a node it will turn magenta <strong>(2)</strong> to show it has been selected <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 5</dt>
<dd>You can then tap, hold and then drag your finger on the screen to move the node(s) into the desired position</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>When moving around the airport, you notice rendering issues with the buildings (i.e. a &quot;judder&quot; motion), the building is duplicated and one will need to be selected and deleted to fix this</dd>
</dl>
<dl>
<dt>Step 6</dt>
<dd>When editing is complete, tap &quot;Modify Shape&quot; to deselect it (you will be unable to edit other buildings without doing this)</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-editing.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-editing@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-editing@3x.png 3x" alt="Image 9.1.2.1 - Editing Buildings" class="documentation-image-lightbox-link" >
          <figcaption>Image 9.1.2.1 - Editing Buildings</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="moving-a-building">
<h2><a class="header-anchor" href="#moving-a-building"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Moving a Building</h2>
<section id="9.1.3">
<h3><a class="header-anchor" href="#9.1.3">9.1.3</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the building by tapping on or near the building, you may have to select the building from a drop down list if there are multiple items in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>If you have only just made the building part then just tap &quot;Modify Shape&quot; to deselect this and the building part will be selected</dd>
</dl>
<dl>
<dt>Step 2</dt>
<dd>Three circles will appear as well as a compass rose. Tap and hold on the circle <strong>(1)</strong> to move the building or to change height/orientation:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Circle</th>
<th>Function</th>
</tr>
</thead>
<tbody>
<tr>
<td>Center</td>
<td>Will move the building by dragging your finger to the desired location</td>
</tr>
<tr>
<td>Top (just above center circle)</td>
<td>Will adjust the elevation or altitude of the building</td>
</tr>
<tr>
<td>Outer</td>
<td>Will change the orientation of the building by dragging your finger in the direction you want to orientate it to</td>
</tr>
</tbody>
</table></div><p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-moving.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-moving@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-moving@3x.png 3x" alt="Image 9.1.3.1 - Changing Building Orientation" class="documentation-image-lightbox-link" >
          <figcaption>Image 9.1.3.1 - Changing Building Orientation</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="copy--pasting-a-building">
<h2><a class="header-anchor" href="#copy--pasting-a-building"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Copy &amp; Pasting a Building</h2>
<section id="9.1.4">
<h3><a class="header-anchor" href="#9.1.4">9.1.4</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the building by tapping on or near the building, you may have to select the building from a drop down list if there are multiple items in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Tap &quot;Edit&quot; and then &quot;Copy&quot; <strong>(1)</strong> on the right side of the screen</dd>
<dt>Step 3</dt>
<dd>Tap in the area of the airport that you want to add the copied building to, this will place a white cursor <strong>(2)</strong>. Adjust this as required and then tap &quot;Paste&quot; <strong>(3)</strong></dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-copying.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-copying@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-copying@3x.png 3x" alt="Image 9.1.4.1 - Copy &amp; Pasting a Building" class="documentation-image-lightbox-link" >
          <figcaption>Image 9.1.4.1 - Copy &amp; Pasting a Building</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="deleting-a-building">
<h2><a class="header-anchor" href="#deleting-a-building"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Deleting a Building</h2>
<section id="9.1.5">
<h3><a class="header-anchor" href="#9.1.5">9.1.5</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the building by tapping on or near the building, you may have to select the building from a drop down list if there are multiple items in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Tap the &quot;Delete Selection&quot; button <strong>(1)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-deleting.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-deleting@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-buildings-deleting@3x.png 3x" alt="Image 9.1.5.1 - Deleting a Building" class="documentation-image-lightbox-link" >
          <figcaption>Image 9.1.5.1 - Deleting a Building</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="downloading-osm-for-building-placement">
<h2><a class="header-anchor" href="#downloading-osm-for-building-placement"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Downloading OSM for Building Placement</h2>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If using OSM, it will automatically place the buildings when downloaded <em>(see <a href="/guide/scenery-editor-manual/3.-getting-started/3.1-first-steps#3.1.4" class="documentation-content-link">3.1.4</a> above)</em> however you may find that they do not completely align with pavements and will need to be moved</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="9.1.6">
<h3><a class="header-anchor" href="#9.1.6">9.1.6</a></h3>
<section class="reference">
<p>Open Street Map (OSM) can also be used for importing buildings automatically by following the steps below. Once added, they can be edited in the same way as buildings that have been added manually:</p>
<dl>
<dt>Step 1</dt>
<dd>Download the OSM data by tapping &quot;File&quot; <strong>(1)</strong> and then &quot;Download OSM&quot; <strong>(2)</strong></dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/6.1.5.1a.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/6.1.5.1a@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/6.1.5.1a@3x.png 3x" alt="Image 9.1.6.1 - Downloading OSM" class="documentation-image-lightbox-link" >
          <figcaption>Image 9.1.6.1 - Downloading OSM</figcaption>
        </figure>
      </p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If you have previously downloaded the OSM but subsequently delete some buildings in error (and these changes are saved), it may be more appropriate to use &quot;Download OSM at Cursor&quot;. This option will only download the data within 200m of the cursor on the map, and may help avoid duplicate buildings being downloaded (which could result from using the &quot;Download OSM&quot; button)</p>
</dd>
</dl>
<dl>
<dt>Step 2</dt>
<dd>
<p>Delete all buildings outside of the airport boundary <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.1-editing-buildings#9.1.5" class="documentation-content-link">9.1.5</a> above)</em></p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Remember to regularly save and upload your work. You can do this by tapping &quot;File &gt; Save&quot; and then to upload your work tap &quot;File &gt; File Manager &gt; Upload [as Draft/for Review]&quot; <em>(see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.2" class="documentation-content-link">2.1.2</a> above)</em></p>
</dd>
</dl>
</dl>
</section>
</section>


9.1 Editing Buildings

<section id="9.2-properties">
<h1><a class="header-anchor" href="#9.2-properties"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 9.2 Properties</h1>
<section id="9.2.1">
<h3><a class="header-anchor" href="#9.2.1">9.2.1</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Select the building part by tapping on or near the building, you may have to select the building from a drop down list if there are multiple buildings/objects in the vicinity <em>(or use the rectangle selection tool - see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.6" class="documentation-content-link">2.1.6</a> above)</em></dd>
<dt>Step 2</dt>
<dd>Tap the &quot;Properties&quot; tab <strong>(1)</strong> on the right side of the screen</dd>
</dl>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/building-properties.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/building-properties@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/building-properties@3x.png 3x" alt="Image 9.2.1.1 - Building Properties" class="documentation-image-lightbox-link" >
          <figcaption>Image 9.2.1.1 - Building Properties</figcaption>
        </figure>
      </p>
<dl>
<dt>Step 3</dt>
<dd>You can then adjust the following properties:</dd>
</dl>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Button</th>
<th>Function</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Height</td>
<td>This shows the height (in meters) of the building. Tap the number and then enter in a new value to adjust this</td>
<td>Tools such as &quot;3D Path&quot; in Google Earth are a useful way to get accurate heights. In addition, buildings need to be in proportion (e.g. a hangar that you know can park a 777 inside needs to be given a height that can accommodate this - <em>see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.2-properties#9.2.2" class="documentation-content-link">9.2.2</a> below</em>)</td>
</tr>
<tr>
<td>Roof Orientation</td>
<td>Tap the &quot;+/-&quot; symbols to adjust the orientation of the roof (you can also use the &quot;Auto Roof Texture&quot; button)</td>
<td>Building roofs have a square pattern, use this tool to get the lines to match the building edges for aesthetic purposes. You can also use the &quot;Auto Texture Orientation&quot; button by tapping Building Parts &gt; Auto Texture Orientation (this may still require manual adjustments - <em>see <a href="/guide/scenery-editor-manual/2.-user-interface/2.1-editor-screen#2.1.2" class="documentation-content-link">2.1.2</a> above</em>)</td>
</tr>
<tr>
<td>Roof Depth</td>
<td>This shows the roof depth (in meters) of the building. Tap the number and then enter in a new value between 0 and 1 to adjust this</td>
<td>Adds a section of roof thats height is offset from the rest of the roof. If being used, only add to top level of buildings</td>
</tr>
<tr>
<td>Roof Type</td>
<td>The type of roof can be selected from here</td>
<td>&quot;None&quot; - <strong class="red">must</strong> be used for all buildings when layering unless it is the top layer (or the bottom layer of a floating building such as a bridge). &quot;Flat&quot; - to be selected for a building that does not have a ledge (roof depth <strong class="red">must</strong> be set to 0 when this is used). &quot;Flat with Ledge&quot; - to be selected for a building that has a ledge (roof depth can be adjusted for this)</td>
</tr>
<tr>
<td>Closed</td>
<td>Used to connect the last node with the first with a Wall to enclose a building part</td>
<td>Use this option instead of using an additional node. This should not be used on building parts with only 2 nodes</td>
</tr>
<tr>
<td>Latitude / Longitude</td>
<td>Current latitude/longitude of the building</td>
<td>This <strong class="red">should not</strong> be changed</td>
</tr>
<tr>
<td>Altitude</td>
<td>This shows the current altitude (in meters) of the building. Tap the number and then enter in a new value to adjust this</td>
<td>The altitude is always based on the bottom of the building. You can also use &quot;Auto Altitude&quot; by tapping Object &gt; Auto Altitude <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.1-editing-buildings#9.1.2" class="documentation-content-link">9.1.2</a> below)</em> if the building is positioned on top of the building you want it to go on top of (perfect for layering!)</td>
</tr>
<tr>
<td>Name</td>
<td>You can name the building using this field</td>
<td>To make layering easier, it is recommended to name the different layers appropriately (i.e. &quot;Lvl 1 Terminal 1&quot;)</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="hangar-height">
<h2><a class="header-anchor" href="#hangar-height"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Hangar Height</h2>
<section id="9.2.2">
<h3><a class="header-anchor" href="#9.2.2">9.2.2</a></h3>
<section class="reference">
<p>The following table outlines the minimum hangar height for aircraft within Infinite Flight:</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th>Aircraft Category</th>
<th>Current Aircraft in Infinite Flight</th>
<th>Minimum Height Required (meters)</th>
</tr>
</thead>
<tbody>
<tr>
<td>A</td>
<td>CC19, C172, F16, F18S, F22, SPIT, SR22, TBM9</td>
<td>4.5</td>
</tr>
<tr>
<td>B</td>
<td>A10, CL35, CRJ2/7, C208, F14, P38</td>
<td>6.5</td>
</tr>
<tr>
<td>C</td>
<td>A318/319/320/321, BCS3, B712, B737/738/739, CRJ9/X, DH8D, E175/190</td>
<td>18</td>
</tr>
<tr>
<td>D</td>
<td>B752, B763, C130, C17, DC10, MD11</td>
<td>19</td>
</tr>
<tr>
<td>E</td>
<td>A332F/333/339, A346, A359, B742/744, B77L/77W/772, B788/789/78X</td>
<td>25</td>
</tr>
<tr>
<td>F</td>
<td>A388, B748</td>
<td>27</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>
</section>


9.2 Properties

<section id="9.3-editing-facades">
<h1><a class="header-anchor" href="#9.3-editing-facades"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 9.3 Editing Facades</h1>
<section id="9.3.1">
<h3><a class="header-anchor" href="#9.3.1">9.3.1</a></h3>
<section class="reference">
<p>Currently you can only set 1 facade or &quot;face&quot; per building part. To create buildings with different faces layering should be used see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.4-layering" class="documentation-content-link">9.4</a> for more information</p>
</section>
</section>
<section id="9.3.2">
<h3><a class="header-anchor" href="#9.3.2">9.3.2</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>
<p>Select the building by tapping on or near the building (you may have to select the building from a drop down list if there are multiple items in the vicinity)</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Tap the &quot;Building Texturing&quot; button <strong>(1)</strong> on the right side panel</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Tap the bottom left hand button <strong>(2)</strong> to select a different building style. Scroll as necessary, tap to view the different faces in that building style</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>Scroll up/down the list on the right of the screen <strong>(3)</strong> to see the different faces available for that style</p>
</dd>
<dt>Step 5</dt>
<dd>
<p>Select the desired face and then tap &quot;Assign&quot; <strong>(4)</strong>. All walls of the selected building part(s) will be changed</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>You can see and select previous faces used in your current editing session on the left side <strong>(5)</strong> of the panel. Just tap and hit assign</p>
</dd>
</dl>
</dl>

<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-facades.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-facades@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/editing-facades@3x.png 3x" alt="Image 9.3.2.1 - Editing Facades" class="documentation-image-lightbox-link" >
          <figcaption>Image 9.3.2.1 - Editing Facades</figcaption>
        </figure>
      </p>
</section>
</section>
</section>

9.3 Editing Facades

<section id="9.4-layering">
<h1><a class="header-anchor" href="#9.4-layering"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 9.4 Layering</h1>
<section class="reference">

<p>Layering is the process of using multiple building parts to create one building, this is necessary due to each building part only being able to support one texture.</p>
</section>
<section id="9.4.1">
<h3><a class="header-anchor" href="#9.4.1">9.4.1</a></h3>
<section class="reference">
<p>The below steps highlight a good method for adding detail to buildings (layering) however you may find different methods that you prefer:</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/layering-diagram.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/layering-diagram@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/layering-diagram@3x.jpg 3x" alt="Example of how to add a window to a wall with layering" class="documentation-image-lightbox-link" >
          <figcaption>Example of how to add a window to a wall with layering</figcaption>
        </figure>
      </p>
<p>The example above shows how you could add a window to a wall using building parts. Each coloured block represents one building part</p>
<dl>
<dt>Step 1</dt>
<dd>Set the building height <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.2-properties#9.2.1" class="documentation-content-link">9.2.1</a> above)</em>. If it is a hangar you can use the minimum hangar heights for guidance <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.2-properties#9.2.2" class="documentation-content-link">9.2.2</a> above)</em>. For terminals or other complicated buildings, it is better to create multiple levels. Any level that is not the top floor should have the roof type set to &quot;none&quot; <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.2-properties#9.2.1" class="documentation-content-link">9.2.1</a> above)</em></dd>
</dl>
<blockquote>
<p>If the lowest layer of a building is floating (i.e. not touching the ground level) such as a bridge, this layer will require a new building part. Height should be zero with roof type set to &quot;flat&quot;. Then reverse the line points to show the roof from below</p>
</blockquote>
<dl>
<dt>Step 2</dt>
<dd>If making multiple floors, first copy &amp; paste the first layer of the building <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.1-editing-buildings#9.1.4" class="documentation-content-link">9.1.4</a> above)</em></dd>
<dt>Step 3</dt>
<dd>Using the management buttons on the left of the screen, tap &quot;Object&quot; and then &quot;Auto Altitude&quot;. This will raise the newly copied building to make it the second layer (roof height of the first layer). You can also set the height of the building manually if needed for the same effect <em>(see <a href="/guide/scenery-editor-manual/9.-buildings-and-facades/9.2-properties#9.2.1" class="documentation-content-link">9.2.1</a> above)</em></dd>
</dl>
<blockquote>
<p>When you layer buildings, you <strong class="red">must</strong> ensure that the lower layer ends at the same point as the next layer starts to prevent any overlapping of facades. This also applies for pillars under floating buildings</p>
</blockquote>
<dl>
<dt>Step 4</dt>
<dd>Using external sources, continue to adjust the size and shapes of the layers to replicate the overall look of the building. For passenger terminals a minimum of three layers is recommended</dd>
<dt>Step 5</dt>
<dd>With every new layer added, don't forget to check the corners of the building have been snapped correctly to ensure that the layers are aligned</dd>
</dl>
</section>
</section>
<section id="z-fighting">
<h2><a class="header-anchor" href="#z-fighting"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Z-Fighting</h2>
<section id="9.4.2">
<h3><a class="header-anchor" href="#9.4.2">9.4.2</a></h3>
<section class="reference">
<p>When you layer buildings, you <strong class="red">must</strong> ensure that the lower layer ends at the same point as the next layer starts to prevent any overlapping of facades. This also applies for pillars under floating buildings</p>
<p>The below image is an example of how overlapping building parts are displayed in app. This <strong class="red">must</strong> be avoided</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/layering1.png" srcset="https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/layering1@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/scenery-editor/buildings-and-facades/layering1@3x.png 3x" alt="Example of Overlapping Building Parts" class="documentation-image-lightbox-link" >
          <figcaption>Example of Overlapping Building Parts</figcaption>
        </figure>
      </p>
<p>To avoid the above, no building parts should overlap. The same also applies to roofs set to the same height</p>
</section>
</section>
</section>
</section>

9.4 Layering

<section id="9.5-buildings-dos-and-donts">
<h1><a class="header-anchor" href="#9.5-buildings-dos-and-donts"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 9.5 Buildings Dos and Don'ts</h1>
<section class="reference">
<p>Below is a table containing what you do need to edit and what you do not edit, while working with buildings</p>
<div class="table-wrapper overflow-x-auto overflow-y-hidden w-full max-w-full mb-5"><table class="documentation-table">
<thead>
<tr>
<th><i class="icon check circle"></i> DO</th>
<th><i class="icon times circle"></i> DO NOT</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i> Add buildings within the airport boundary, including prominent buildings outside the airport fence which are visible for the pilots and contribute to the character of the airport</td>
<td><i class="icon times circle"></i> Create sloped or vertical round shapes (roofs, walls, arches, ramps, or anything else) using layered buildings or building parts</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Use layering to create custom facades</td>
<td><i class="icon times circle"></i> Add irrelevant buildings outside the airport boundary and buildings which are not visible to pilots</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Remove roofs for layers of which the roof and floors are invisible to the user</td>
<td><i class="icon times circle"></i> Create multi-story car parks from multiple individual buildings (for each floor). Use the available car park texture instead</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Snap Buildings to avoid gaps or overlapping</td>
<td><i class="icon times circle"></i> Add any types of “easter eggs”</td>
</tr>
<tr>
<td><i class="icon check circle"></i> Keep the amount of building parts used as small as possible</td>
<td><i class="icon times circle"></i> Make numbers/letters out of buildings</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Use building parts to create open doors/windows</td>
</tr>
<tr>
<td>-</td>
<td><i class="icon times circle"></i> Used the &quot;Closed&quot; checkbox on 2 node building parts (As this adds an additional wall)</td>
</tr>
</tbody>
</table></div></section>
</section>


9.5 Dos and Don'ts

If you're new to Infinite Flight, this is the place to start. We'll get you up and running quickly with our comprehensive Getting Started Guide!

Getting Started Guide

Now that you know your way around the user interface, it's time to take to the skies. Our Flying Guide will help you on your journey to the Expert Server!

Flying Guide

Want to control the aircraft of Infinite Flight? Learn about the user interface with our ATC Guide before moving onto our ATC Manual to learn the rules of controlling!

ATC Guide

Whether you're a qualified controller or just beginning your journey, the ATC Manual will be your rulebook to controlling the skies of Infinite Flight.

ATC Manual

Still having trouble? Our expert support team will get you back up and running in no time.

Get Help

Explore our developer documentation and find out how to extend Infinite Flight with our APIs.

Developer Reference

Help the airports of Infinite Flight come to life with both 2D and 3D editing. This manual is the rulebook on how to use our Scenery Editor within Infinite Flight.

Scenery Editor Manual

Help the airports of Infinite Flight come to life with both 2D and 3D editing. This manual is the rulebook on how to use our Scenario Editor within Infinite Flight.

Infinite Flight User Guide

1a. Administration