FlightGear wiki - User contributions [en]

OpenRadar

2018-03-29T16:54:31Z

Wagnerw:

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease = Nov, 18th 2012
| latestrelease = Mar, 29th 2018
| writtenin = Java
| os = Linux, Windows, Mac
| platform = Java
| developmentstatus = active
| type =
| license =
| website = https://sourceforge.net/projects/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadar_FGFS_ORCAM|ORCAM: Your window to the the airport]]

* [[OpenRadarDownload|'''Download'''! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadarKnownIssues|'''FAQ''' / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:OpenRadar| ]]
[[Category:ATC clients]]
[[Category:Air Traffic Control]]

OpenRadar Change Log

2018-03-29T16:19:19Z

Wagnerw:

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update ==

== Published updates ==

=== OpenRadar updates 2018-03-29 ===

* Compatibility updates
:* Support for new MP protocol, supports display and chat in both protocols simultaneously
:* New flightplan download interface is now supported
:* Metar server changed to the server that is used by FGFS

* There is a new data mode FUTURISTIC that changes the contact color in screen with their altitude.

* Radar reception range
:* MP protocol allows to tell the server how far you can see / how for the contacts could be away until you don't receive their information anymore. IMPORTANT: You can see them and read their chats, but the contacts have their own setting that defaults to 100NM. You cannot chat with contacts far away for that reason.
:* Using a wide range, means you can see many contacts. The flightstrip bay may overflow. OR has a small input, right side, below the radar screen, to define the range that you want to manage in your flightstrip bay.
:* The reception range is calculated out of your visible range (zoom situation). The minimum is your flightstrip range setting, the maximum is defined by the MP server with 2000NM.
:* As your chat would overflow with messages from contacts far away, the chat filter RNG (range) is back and shows only chat messages from within you flightstrip range setting. Remember again, that contacts can read you only, as long as you are within their reception range (100NM).
:* To manage wider ranges, you need to use FGCOM or mumble.

* the METAR URL has been removed from settings, as there is no common data format, some send coma separated, some space separated information with different header lines.
* Fix for missing correction of magnetic declination in route design and mouse attached heading adviser (a test modification made it into production, sorry)
* Added "Delete Airport" button to startup dialog => Simple cleanup
* Improvements in situations without shapefile download server (if it should be down again)
:* Download error is displayed in a popup dialog (choose between "run without scenery" / "delete partially download")
:* OpenRadar runs without any shapefiles, the runways are constructed out of the internal xplane data, no taxiways and no scenery available, but all navpoints etc.

== Published updates ==

=== OpenRadar updates 2015-03-16 ===

* chat input foreground color is not fixed to black anymore, adapts to your system settings
* better formula to calculate initial heading to remote airports. Matches now to skyvector results (small error caused by magnetic model of fgfs)

=== OpenRadar updates 2015-03-14 ===

* Transition is more flexible now
:* Transition altitude must be defined (usually fix for airport)
:* Default: Calculated Transition Level depending on air pressure: Transition Layer minimum width can be defined
:* Fix TL Mode: Less airports have a fix TL: It can be defined now. Usually you are wrong, if you use this on any other airport. Manual TL calculation on normal airports requires frequent re-calculation to ensure separation.
* Fixes to ORCAM
:* better control of FGFS to avoid weird things when you adapt the height of the camera via CTRL+A, CTRL+Z
:* Fix for missing MP properties (rotors did not turn, livery missing, retracted gear movement), OR forwarded wrong type for a multiplayer property.
:* Fix for small bugs that can build a MP packet loop, making usage impossible

=== OpenRadar updates 2015-03-02 ===

* deselect a contact with a double ESC
* volume control for FGCOM (use your mouse wheel above the number in radio line)
* Possibility to use flightgear as window to the airport (ORCAM)
:* Presets
:* different camera locations possible
:* initial auto zoom
:* follow mode (camera follows contact)
:* multiplayer port forwarding makes camera invisible on MP server
* remove need for AirportIndex data file, OR finds all airports now

=== OpenRadar updates 2015-01-31 ===

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
* small weather icon displays the flight conditions around the airport (start and landing): VFR,MVFR,IFR,LIFR

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadarKnownIssues

2018-03-29T05:25:07Z

Wagnerw:

[[OpenRadar| Back to mainpage]]

This is more or less the help page of [[OpenRadar]]. If you don't find answers here, at the install page or in the guide, please ask in the [http://forum.flightgear.org/viewtopic.php?f=68&t=18263 Forum]!

== FAQ ==
* '''FGCom setup''': [[OpenRadarDownload|See installation page]]!
* '''How can I contact the developer?''': Send me mails from the fg forum.
* '''ATIS wind direction differs from METAR''': Yes, spoken is MAGNETIC, written is TRUE. ATIS information always respects the magnetic declination.

== Known Issues ==
* '''I can't see all 24 runways on my netbook, there is no scrollbar''' Sorry guys. but we need space. There is so much to display and tell that you should really consider to use a wider screen! Our target platform is a modern wide screen monitor. If you have two, the better: You can run a flightgear instance with a "camera aircraft" on the other and you add a nice view for ground operations...

* '''Unsupported major.minor version x.y''': Your installed Java is too old. Please install at least Java 7

* '''METAR support for small airports''' METAR is available only for big airports. => rightclick on Metar to define an alternative

* '''FONTS are bad using OpenJDK''' there license issues with the fonts I have read. Open OpenRadar.sh or OpenRadar.bat and add <code>-Dswing.aatext=true -Dawt.useSystemAAFontSettings=on</code> in front of <code>--jar OpenRadar.jar</code>

[[Category:OpenRadar|KnownIssues]]

OpenRadar Change Log

2018-03-29T05:19:53Z

Wagnerw: /* Next update */

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update ==

* Compatibility updates
:* Support for new MP protocol, supports display and chat in both protocols simultaneously
:* New flightplan download interface is not supported
:* Metar server changed to the server that is used by FGFS

* There is a new data mode FUTURISTIC that changes the contact color in screen with their altitude.

* Radar reception range
:* MP protocol allows to tell the server how far you can see / how for the contacts could be away until you don't receive their information anymore. IMPORTANT: You can see them and read their chats, but the contacts have their own setting that defaults to 100NM. You cannot chat with contacts far away for that reason.
:* Using a wide range, means you can see many contacts. The flightstrip bay may overflow. OR has a small input, right side, below the radar screen, to define the range that you want to manage in your flightstrip bay.
:* The reception range is calculated out of your visible range (zoom situation). The minimum is your flightstrip range setting, the maximum is defined by the MP server with 2000NM.
:* As your chat would overflow with messages from contacts far away, the chat filter RNG (range) is back and shows only chat messages from within you flightstrip range setting. Remember again, that contacts can read you only, as long as you are within their reception range (100NM).
:* To manage wider ranges, you need to use FGCOM or mumble.

* the METAR URL has been removed from settings, as there is no common data format, some send coma separated, some space separated information with different header lines.
* Fix for missing correction of magnetic declination in route design and mouse attached heading adviser (a test modification made it into production, sorry)
* Added "Delete Airport" button to startup dialog => Simple cleanup
* Improvements in situations without shapefile download server (if it should be down again)
:* Download error is displayed in a popup dialog (choose between "run without scenery" / "delete partially download")
:* OpenRadar runs without any shapefiles, the runways are constructed out of the internal xplane data, no taxiways and no scenery available, but all navpoints etc.

== Published updates ==

=== OpenRadar updates 2015-03-16 ===

* chat input foreground color is not fixed to black anymore, adapts to your system settings
* better formula to calculate initial heading to remote airports. Matches now to skyvector results (small error caused by magnetic model of fgfs)

=== OpenRadar updates 2015-03-14 ===

* Transition is more flexible now
:* Transition altitude must be defined (usually fix for airport)
:* Default: Calculated Transition Level depending on air pressure: Transition Layer minimum width can be defined
:* Fix TL Mode: Less airports have a fix TL: It can be defined now. Usually you are wrong, if you use this on any other airport. Manual TL calculation on normal airports requires frequent re-calculation to ensure separation.
* Fixes to ORCAM
:* better control of FGFS to avoid weird things when you adapt the height of the camera via CTRL+A, CTRL+Z
:* Fix for missing MP properties (rotors did not turn, livery missing, retracted gear movement), OR forwarded wrong type for a multiplayer property.
:* Fix for small bugs that can build a MP packet loop, making usage impossible

=== OpenRadar updates 2015-03-02 ===

* deselect a contact with a double ESC
* volume control for FGCOM (use your mouse wheel above the number in radio line)
* Possibility to use flightgear as window to the airport (ORCAM)
:* Presets
:* different camera locations possible
:* initial auto zoom
:* follow mode (camera follows contact)
:* multiplayer port forwarding makes camera invisible on MP server
* remove need for AirportIndex data file, OR finds all airports now

=== OpenRadar updates 2015-01-31 ===

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
* small weather icon displays the flight conditions around the airport (start and landing): VFR,MVFR,IFR,LIFR

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadar: Editing routes

2016-01-26T10:32:40Z

Wagnerw: Added clickable attribute to screentext

[[File:EDDF-Triangle-OpenRadar.png|right|300px|thumb|EDDF with procedures, routes and additional information.]]
[[OpenRadar| Back to mainpage]]

== About ==
You can define standard routes to OpenRadar. This can be done by converting a NavaidDB file and improve the result or define it from scratch by adding lines, curves and bows to the radar screen.
So you can define waiting loops, STARs and SIDs if you want to and if you need them.

Please send your finished work in to include it into the next OpenRadar update for everybody.

To have an example, check out airport LFSB. It is our showcase in this matter.

Please be warned: Defining all approaches and procedures for a more complex airport may produce too much details to work with. Concentrate on the important things, like additional vectors or waiting rooms.

A collection of possibilities:
* Highlight only the navaids that you need to see
* Create only the holding areas
* Create the Approaches to appear on a higher viewpoint and the STAR/SID routes on lower viewpoints
* Use texts to have the taxiways names in the map at the best spot (hide them on higher viewlevels)
* Use texts to have the maximum speed in the map
* Create only the most important routes, or
* Create all standard STAR and SID routes

== Guidelines ==
To avoid that everyone develops his own standards, we need to agree to common standards.

=== Display Modes ===
The route attribute displayMode can have different values:
{| class="wikitable"
|-
! displaymode !! Description
|-
| always ||These routes are always displayed. You cannot switch them off using the STAR/SID switch.
That means that you can use them to enrich the map itself: For forbidden areas or areas that require a minimum height... or for instance to add the names for taxiways to the map.
|-
| optional || This route will be hidden when you switch off START/SID.
You can use it for any route specific elements, that are not related to a specific runway.
|-
| sid / star || These values mark a route as sid/star. In future we might want to select a sid/star from a list. To be able to do that, we need to know which routes we need to display.
|}
So please follow these simple guidelines:
# Define one route per SID/STAR and design it, that it can be displayed individually, everything else switched off
# Mark these routes with the correct ''displayMode''
# Use the official STAR/NAME as route name, we will use it for display

=== Content ===
==== Airport local data ====
-- to be added--

==== Data shared between airports ====
Should be in a directory with a name describing the region. The airport xml files can incorporate these definitions via include xml element.
-- to be added--

=== Coloring ===
-- to be added--

== Generating the OpenRadar definitions from existing ProceduresDB file ==

WARNING: Known issues: There is an major issue when reading the procedure file, in the current version. I will fix it soon, but it requires to implement more functionality to define standard routes... I will need some time to do that.
'''Until this feature works, it is disabled in the published versions of OR.'''

There is already an XML format that contains the STARs and SIDs. Converting it can save you some work.

We do not use it directly because:
* These data are not free
* It purpose it to provide input for the autopilot/flight manager, not for an ATC screen
* Our format is made to display the important information which an ATC needs:
:*adaptive detail (you can define the lower and upper zoom level values between the route is being displayed)
:*display of STARs and SIDs can depend on the runway usage mode
:*colors (each route, each element can have its own color), strokes and line width
:*more graphical elements curves, bows and text
:*NAVAID hightlighting

The SID/STAR xml files can be bought and downloaded for a few bucks from [http://navigraph.com Navigraph]. Generally FlightGear looks for them in a Airports/I/C/A/ICAO.procedures.xml (where ICAO is an airport). For example, the procedures file for ELLX, if it exists, is under Airports/E/L/L/ELLX.procedures.xml.

OpenRadar can also read these XML files. For that:
* create the directory OpenRadar/data/routes/ICAO (where ICAO is the code of the airport you want to use)
* put your procedure XML (named ICAO.procedures.xml) into it
* start OpenRadar at your airport (ICAO), you now have a converted file ICAO.procedures.or.xml in the OpenRadar/data/routes/ICAO directory
* exit OpenRadar : the original file is not needed anymore after this step (move it somewhere else if you want)
* rename your ICAO.procedures.or.xml file to ICAO.procedures.xml

Now when restarting OpenRadar, the converted routes are available. You can and should modify the new file following the explanations below.

== Manual creation / refinement ==
The '''most important''' first:
*'''SHIFT+F12''' reloads the standard routes of your current airport. So you can see changes quickly...
*'''F12''' determines the geo position of your mouse tip and copies it to your clipboard. So you can easily place points: Place mouse pointer in OR map at the spot that you need, hit F12, change to your XML file, place the cursor, at the right spot and paste the clipboard. SHIFT+F12 will reload your work for verification...
*'''CTRL+F12''' determines the current zoom level and copies it to your clipboard. So you can easily set the zoom levels for your routes: Set the desired zoom level in OR map, hit CTRL+F12, change to your XML file, place the cursor, at the right spot and paste the clipboard. SHIFT+F12 will reload your work for verification...

The files must be located in directory data/routes/[airport name].

The files must end with ".xml", so they must be xml documents. Here is a simple example of everything around your route definitions:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
--- here are your definitions ---
</routes>
</syntaxhighlight>

=== A Route ===
A route is a collection of definitions that belong together. The values zoomMin and zoomMax allow you to define adaptive details or layers of information that appear within those constraints. Omitting them means there is no constraint at this side...

A route can have the following attributes:
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| name || {{no}} || A meaningful name for this route
|-
| zoomMin || {{yes}} || The minimum zoom level at which this route is being displayed. If you zoom in more, it disappears. (default values: Ground: 14, Tower: 26, App: 100)
|-
| zoomMax || {{yes}} || The maximum zoom level at which this route is being displayed. If you zoom out more, it disappears. (default values: Ground: 14, Tower: 26, App: 100)
|-
| displayMode || {{no|(No)}} || Controls how the different switches work for this route:
*"always": route is displayed always
*"optional": routes is displayed independently from the runways, but STAR/SID switch turns it off
*"sid": This route is a SID, its name is the official id, enabling the SID checkbox in runway panel displays it, and the STAR/SID main switch toggles it
*"star": This route is a STAR, its name is the official id, enabling the STAR checkbox in runway panel displays it, and the STAR/SID main switch toggles it
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| color || {{yes}} || Defines the color of the elements of this route. Use it carefully and rarely. You still want to be able to read the most important information on the radar: The contacs position info....
|}

Supported are the following xml tags:
{| class="wikitable"
|-
! Tag !! Opt. !! Description
|-
| activeStartRunways || {{yes}} || A comma separated list of runways. If one of them is active for '''starts''' the route will be displayed.
|-
| activeLandingRunways || {{yes}} || A comma separated list of runways. If one of them is active for '''landings''' the route will be displayed. If neither activeStartRunways nor activeLandingRunways is defined, the route will always be displayed. Use this for parking rooms...
|-
| navaids || {{yes}} || A comma separated list of navaid ids (FIX, NDB, VOR, Airportcodes) that will be highlighted if this route is being displayed, regardless if the main switches for FIX/NDB etc. are enabled or not.
This tag can have an attribute <code>color</code> that defines the color for the navaids in RGB values. Example: color="120,140,120"
There can be multiple instances of this element having different colors assigned.
|-
| (other elements) || {{yes}} || The graphical tags explained below
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>
--- more to be explained ---
</route>
</routes>
</syntaxhighlight>

=== Route features ===
==== Zoomlevel ====
Use the Attributes <code>zoomMin</code> and <code>zoomMax</code> to define a range in which a route is being displayed. So you can separate routes interesting for APP zoom level from details on tower level.

==== Navaid coloring ====
Both routes and navaids can have a <code>color</code> attribute defined. The rules which one is displayed are:
# If navaids block has no color defined, the route's color is being used.
# If route's block has no color defined, a default color will be used.
# Navaids are highlighted only, if the route is being displayed (zoom level, active start/landing runway)
# If a navaid is used in more than one visible route:
:# The color of a static route (no runway conditions) has highest priority (zoomLevel is respected only, to check if it is displayed at all)
:# Then follows the color attribute of the current navaids block, if defined.
:# Then follows the color attribute of the current route block, if defined, its default color otherwise.

Navaids used in many routes are of somewhat importance and should get their own static route and a separate color as hotspots.
In conflict case, the color, that is found first, wins.

=== Points and Angles ===
All elements of your route base on points and angles. '''Angles''' are magnetic and defined in degrees.

'''Points''' on your radar can be defined:
{| class="wikitable"
! Point !! Description
|-
| Navaid || You can use the navaid ID, e.g begin="BLM"
|-
| Runway end || You can use any runway end of the current airport. e.g. Runway 15 at Basel: begin="'''LFSB'''-RW'''15'''"
|-
| Geographic Location || You can use the geographic location separated by a comma. e.g. <pre>begin="47.599450,7.531936", begin="N47°57'51'',E7°54'58''" or begin="N47°57.2',E7°54.10'"</pre>
|-
| Relative Location || You can define a point relative to a navaid in the format: dddNMaaa@iii (where ddd is the decimal distance in NM, aaa is the magnetic bearing from iii, which is a navaid id. Distance and heading have the decimal separator 'dot'.
e.g. "2.5NM165@BLM"
|}
'''Length'''' are also given in decimal NM.

'''Missing Navaids:'''

If you notice that some navaids are not available in OpenRadar's data, you can use their geographic positions, or better define them in your route file.
These additional definitions can be used like navaids defined in the AptNav files...
A useful misuse of this feature is to produce highlighting-enabled route texts: Define the text as addPoint and reference it in a routes navaid block.
Please remember, very likely your clients will not have them visible in their inflight map...

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| code || {{yes}} || The ID under that your want to find it. Try to use non existing to avoid conflicts
|-
| point || {{yes}} || The geographic coordinates of the point.
|}

Examples:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<addPoint code="AGOLO" point="50.200000,9.676111"/>
<addPoint code="BIBTI" point="50.966667,7.108611"/>
<addPoint code="ESUPI" point="50.058333,8.121111"/>
<addPoint code="FRD" point="50.030556,8.566944"/>
<addPoint code="IBVIL" point="50.434444,7.369167"/>
<addPoint code="KERAX" point="50.475000,9.581944"/>

...
</routes>
</syntaxhighlight>

=== File Includes ===
It is possible to share xml route definitions between airports to avoid duplicating them.
This is done quite straight forward, but including a file with relative path to the current file. The included file needs to have the same structure as the main file and will be imported after all files in the current directory are imported.

{{note|This xml element is on the same level as the routes.}}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
<include file="../uk.xml"/>
<route...
...
</routes>
</syntaxhighlight>

== Elements ==
A route can be constructed out of the following Elements:

==== line ====
A line is a line is a line.
It can be defined ''(1) either via two points'' or ''(2) via one point, direction and length''.

'''two point definition'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the line
|-
| end || {{no}} || The end point of the line
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should start
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin", "end", "both". Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the line. The line is broken at this spot.
|}

'''via one point, direction and length'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the line
|-
| angle || {{no}} || The magnetic angle of this line
|-
| length || {{no}} || The length of the line including the offsets
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should start
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed at the middle of the line. The line is broken at this spot.
|}

Examples:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<line start="BLM" end="ELBEG" text="069" />
<line start="HOC" end="HOMBO" startOffset="3" text="341" />
<line start="5.4NM226@BLM" end="LUMEL" text="226" />

<line start="BLM" startOffset="1.2" angle="003" length="10" text="003" arrows="end"/>

<line start="BLM" angle="202" length="4.5" stroke="dashed,1" text="202" />

</route>
</routes>
</syntaxhighlight>

==== multi-point-line / polygon ====
This element can be used to draw polygons, both open and closed.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| close || {{yes}} || "true" is the default, "false" does not connect the last with the first point
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

In difference to the other XML elements, this element contains children named <code>points</code>. Their content is a normal point definition as explained above.

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="Polygon example">
...
<multiPointLine close="false">
<point>ALTIK</point>
<point>6NM226@BLM</point>
<point>50.454722,7.227222</point>
</multiPointLine>
...
</route>
</routes>
</syntaxhighlight>

==== intercept ====
An intercept is currently implemented as a line from a startpoint in a startheading, a bow and a second line to a endPoint in a specific heading. The bow is defined in a way, that both lines are tangents to a circle with the same radius as the bow.
You can define it in two ways:

'''General Case'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the first line
|-
| startHeading || {{no}} || The initial heading of the plane at startPoint
|-
| radius || {{no}} || The radius in NM that the plane has to fly. You can also use ''speed'' to define it.
|-
| (speed) || {{no}} || Alternative to radius. Assuming a standard turn (360 degrees in 2 minutes, we can calculate the radius for you...)
|-
| direction || {{no}} || Is the turn to be made left or right
|-
| endHeading || {{no}} || The heading that the plane will fly after the turn in direction '''to''' the endPoint. This is the opposite of ''radial''. Use either ''endHeading'' or ''radial''
|-
| (radial) || {{no}} || Alternative to ''endHeading'': The radial you want to intercept. The radial is the direction '''from''' the endPoint, so it is the opposite of ''endHeading''.
|-
| end || {{no}} || The end point of the line (in real live most likely a VOR or NDB)
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should end
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the second line. The line is broken at this spot.
|}

'''Known-start-of-turn Case'''
In this case there is no first line. The drawing starts directly with the bow.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| startTurn || {{no}} || The start point of the '''bow'''
|-
| startHeading || {{no}} || The initial heading of the plane at startTurn
|-
| radius || {{no}} || The radius in NM that the plane has to fly. You can also use ''speed'' to define it.
|-
| (speed) || {{no}} || Alternative to radius. Assuming a standard turn (360 degrees in 2 minutes, we can calculate the radius for you...)
|-
| direction || {{no}} || Is the turn to be made left or right
|-
| endHeading || {{no}} || The heading that the plane will fly after the turn in direction '''to''' the endPoint. This is the opposite of ''radial''. Use either ''endHeading'' or ''radial''
|-
| (radial) || {{no}} || Alternative to ''endHeading'': The radial you want to intercept. The radial is the direction '''from''' the endPoint, so it is the opposite of ''endHeading''.
|-
| end || {{no}} || The end point of the line (in real live most likely a VOR or NDB)
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should end
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the second line. The line is broken at this spot.
|}

'''''Undesired results'''''
Constructing an intercept is easy with ruler and triangle, but more difficult when you are facing numerics and different coordinate systems. I have performed a lot of tests and are pretty sure that it works now, but there still can be issues.

*'''Parallel headings''' cause the problem, that I have to ignore the radius definition to connect them with one bow. I use the distance between the lines as bow diameter.
*'''Long lines''' In the ''general case'' most problems I saw arose from a radius, that was too small. If the lines are getting closer with growing distance from start, a small radius will cause the lines to be too long. In that case consider to use a larger radius or split the intercept into two.
*'''Bow behind startPoint:''' This is often caused by the fact that the plane needs to fly a wider radius to intercept the endHeading. In that case consider to use a larger radius or split the intercept into two.
*'''Other cases''' If construction is not possible, the result freaks out and paints something else. Verify your parameters! I help if I can, as this also might be a bug. Please send in your route!

'''''Constraints'''''
* Currently it is not possible to draw S-shape like intercepts automatically. I plan to add it, but need time and a free head for that. Use two intercepts until then!

==== curve ====
Curves are an easy and comfortable way to connect lines if there is not radius defined and if the angle is small.
A curve is implemented as quad curve, so it has a ''startPoint'', an ''endPoint'' and an ''controlPoint'' which controls the curving. A good start point for the control point is the interception between the lines that should be connected.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the curve
|-
| end || {{no}} || The end point of the curve
|-
| controlPoint || {{no}} || The location of the control point of this curve.
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<curve start="6NM226@BLM" end="13.5NM315@BASUD" controlPoint="7.5NM226@BLM"/>
</route>
</routes>
</syntaxhighlight>

==== bow ====
A bow is a part of a circle around a specified point. It can be used to define circling approaches or wider curves.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| center || {{no}} || The center of the bow
|-
| radius || {{no}} || The radius of the bow
|-
| startAngle || {{no}} || The magnetic start angle of the bow
|-
| extentAngle || {{no}} || The extend of the bow in degress. Positive direction is the direction of the compass
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed at the center angle of the bow. The line is broken at this spot.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<bow center="BLM" radius="9" startAngle="277" extentAngle="50" text="D9"/>

<bow center="BLM" radius="15" startAngle="274" extentAngle="-36" stroke="dashed" arrows="start" text="D15"/>
</route>
</routes>
</syntaxhighlight>

==== loop ====
This element displays a parking area. It has predefined text locations for min, max and misap height...

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| navpoint || {{no}} || The hook of the parking. The target of the inbound direction, where the pilots turn into the loop.
|-
| inboundHeading || {{no}} || As magnetic direction.
|-
| length || {{yes}} || the length of a leg in NM (the straight part of the loop)
|-
| width || {{yes}} || the distance between the legs in NM
|-
| right || {{yes}} || '''"true"''' or "false", does the pilot turn to right or left at navpoint? Default: right
|-
| minHeight || {{yes}} || The minimum height for planes in this loop (painted bold)
|-
| maxHeight || {{yes}} || The maximum height for planes in this loop
|-
| misapHeight || {{yes}} || The default height for missed approaches.
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="LFSB Wait loops">
<navaids>BLM,ALTIK,SEDOR</navaids>
<loop navpoint="SEDOR" inboundHeading="192" width="5" arrows="both" minHeight="7000" maxHeight="MAX 12000"/>>
<loop navpoint="ALTIK" inboundHeading="94" width="5" arrows="both" minHeight="5500" maxHeight="MAX 11000" misapHeight="MISAP4000"/>
<loop navpoint="BALIR" inboundHeading="319" width="5" arrows="both" minHeight="7000" maxHeight="MAX 12000"/>
</route>
</routes>
</syntaxhighlight>

==== text ====
This element draws a text at the specified spot. If marked as clickable, it can be used to assign a route to the selected contact with a single click.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| position || {{no}} || The geographic position of the text's center
|-
| angle || {{yes}} || The text can be rotated, if you need to. Default is horizontal, angle grows clockwise
|-
| alignHeading || {{yes}} || Alternative to ''angle''. The text will be displayed aligned to a heading. Useful if you want to write along a route leg.
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| clickable || {{yes}} || If set to "true", the route can be assigned to the selected contact with a single click onto this text.
|-
| text || {{no}} || This text will be displayed. Single line only!
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="text example">
<text position="5NM327@BLM" font="Arial" fontSize="22" angle="-90" text="Example text"/>
<text position="6NM327@BLM" font="Arial" fontSize="22" alignHeading="110" text="Example text"/>

<text position="47.546992,7.664459" fontSize="11" clickable="true" text="ELBEG 6T"/>
</route>
</routes>
</syntaxhighlight>

==== screenText ====
This element draws a text at the specified spot on your radar display. It will not pan, nor zoom with the rest of the map.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| screenPos || {{no}} || The position of the text's center in pixels in x,y format, e.g. "50,50". x,y start in the upper left corner. Negative values count from the other side of the screen. "center" works on per x/y base too.
|-
| angle || {{yes}} || The text can be rotated, if you need to. Default is horizontal, angle grows clockwise
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| clickable || {{yes}} || If set to "true", the route can be assigned to the selected contact with a single click onto this text.
|-
| text || {{no}} || This text will be displayed. Single line only!
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="screenText example">
<screenText screenPos="50,50" text="top left"/>
<screenText screenPos="-50,50" text="top right"/>
<screenText screenPos="50,-50" text="bottom left"/>
<screenText screenPos="-50,-50" text="bottom right"/>
<screenText screenPos="center,center" text="center"/>
</route>
</routes>
</syntaxhighlight>

==== VFR minimum altitudes ====
This element draws the known minimum altitude symbol.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| position || {{no}} || The position of the text's center
|-
| value || {{no}} || The altitude in thousands of feet ("3.4" means 3400 ft)
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="LFSB minimum altitudes">

<minAlt position="47.705141,7.911530" value="5.7"/>
<minAlt position="47.861,8.01315" value="5.9"/>

<minAlt position="47.81546,6.847916" value="5.3"/>
<minAlt position="48.084501,7.236557" value="5.4"/>

<minAlt position="47.406250,7.706909" value="5.7"/>
<minAlt position="47.208841,7.245483" value="6.2"/>
</route>
</routes>
</syntaxhighlight>
==== restriction ====
This element draws speed and/or altitude restrictions.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| position || {{no}} || The position of the centre if the restriction element.
|-
| maxspeed || {{yes}} || The maximum permitted speed in knots.
|-
| notabove || {{yes}} || The altitude above which aircraft should not proceed, see below for how this can be represented.
|-
| notbelow || {{yes}} || The altitude below which aircraft should not proceed, see below for how this can be represented.
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave out to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the colour of lines and text in this element. Overrides the colour inherited from the <code><route></code>.
|}

Example:
<syntaxhighlight lang="xml">
<routes>
<route name="Restrictions test" displayMode="always" color="255,255,255" zoomMax="300">

<restriction position="53,-7.0" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-6.6" maxspeed="240" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-6.2" notabove="3000ft" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-5.8" notbelow="FL120" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-5.4" maxspeed="240" notabove="3000ft" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-5.0" maxspeed="240" notbelow="FL120" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-4.6" notabove="3000ft" notbelow="FL120" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-4.2" notabove="FL120" notbelow="3000ft" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-3.8" notabove="FL120" notbelow="FL120" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-3.4" maxspeed="240" notabove="FL120" notbelow="FL120" stroke="line,2" font="Courier" fontSize="10"/>
<restriction position="53,-2.8" maxspeed="240" notabove="3000ft" notbelow="FL120" stroke="line,2" font="Courier" fontSize="10"/>

</route>
</routes>

</syntaxhighlight>
The type of restriction displayed is controlled by the combination and relationship between the three options <code> maxspeed, notabove</code> and <code> notbelow </code>. Not all the combinations are useful; specify none of the three and you'll get a blank restriction you can't even see. Specify all 3 options and where <code>notabove</code> and <code> notbelow </code> are not equal you'll get this helpful error message displayed.

[[File:stdRteRestriction-error.png]]

The remaining 9 combinations are useful.

[[File:stdRteRestriction.png]]
from left to right:
#maxspeed only
#notabove only
#notbelow only
#notabove and maxspeed
#notbelow and maxspeed
#notabove and notbelow where notabove < notbelow
#notabove and notbelow where notabove > notbelow
#notabove and notbelow where notabove = notbelow
#notabove, notbelow and maxspeed where notabove = notbelow

Altitudes for <code>notabove</code> and <code>notbelow</code> are represented as feet or Flight Level. Any text provided would be displayed, but to determine the correct symbol and positioning of the text for a particular restriction a calculation has to be performed to determine which of the 2 altitudes provided is higher than the other, or if they are both the same. For this purpose an attempt is made to approximate what is provided in feet. This table shows the currently available formats and the result in feet

{| class="wikitable"
|-
! provided text !! Approximation method !! Approximation in feet
|-
| 3000 || parse number || 3000
|-
| 3000ft || remove ft & parse number || 3000
|-
| 3,500 || remove commas & parse number || 3000
|-
| 3000 AMSL || remove AMSL & parse number || 3000
|-
| MAX 3000 || remove MAX & parse number || 3000
|-
| FL120 || remove FL, parse number & multiply by 100 || 12000
|-
| SFC || assume 0 (surface) || 0
|-
| GND || assume 0 (ground) || 0
|-
|}

It is obviously incorrect to assume that GND will be 0, but it is sufficient in most cases in order to determine which of the 2 levels would be greater than the other, there are cases where this could be a problem (where the ground is below sea level perhaps), in the unlikely event that you encounter one of these rare situations, please use the actual altitude in feet as a workaround.

==== Include a route / shared route parts ====
This element can be used to include all elements of another, already defined, route into the current route. You shall use it, to avoid duplicate route definitions for the part, that is shared by multiple routes.

{{note|The include tag does not inherit route definitions like route attributes, active runways or navaids to highlight. These definitions must be done for each real route (the one that includes the shared route). Only the route elements like lines, intercepts etc. are included.}}

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| routeName || {{no}} || The name of the route that will be included.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="sharedRouteName">
<line start="BLM" end="ELBEG" text="069" />
</route>

<route name="ELBEG 6T" displayMode="sid" zoomMin="10" zoomMax="100" color="120,140,120">
<activestartRunways>15</activestartRunways>
<navaids color="255,255,0">ELBEG,HOC</navaids>

<include routeName="sharedRouteName" />
</route>
</routes>
</syntaxhighlight>

[[Category:OpenRadar|Editing routes]]

OpenRadar Change Log

2015-11-16T07:39:23Z

Wagnerw: Added improvements for next update

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update ==
* Fix for missing correction of magnetic declination in route design and mouse attached heading adviser (a test modification made it into production, sorry)
* Added "Delete Airport" button to startup dialog => Simple cleanup
* Improvements in situations without shapefile download server (if it should be down again)
:* Download error is displayed in a popup dialog (choose between "run without scenery" / "delete partially download")
:* OpenRadar runs without any shapefiles, the runways are constructed out of the internal xplane data, no taxiways and no scenery available, but all navpoints etc.

== Published updates ==

=== OpenRadar updates 2015-03-16 ===

* chat input foreground color is not fixed to black anymore, adapts to your system settings
* better formula to calculate initial heading to remote airports. Matches now to skyvector results (small error caused by magnetic model of fgfs)

=== OpenRadar updates 2015-03-14 ===

* Transition is more flexible now
:* Transition altitude must be defined (usually fix for airport)
:* Default: Calculated Transition Level depending on air pressure: Transition Layer minimum width can be defined
:* Fix TL Mode: Less airports have a fix TL: It can be defined now. Usually you are wrong, if you use this on any other airport. Manual TL calculation on normal airports requires frequent re-calculation to ensure separation.
* Fixes to ORCAM
:* better control of FGFS to avoid weird things when you adapt the height of the camera via CTRL+A, CTRL+Z
:* Fix for missing MP properties (rotors did not turn, livery missing, retracted gear movement), OR forwarded wrong type for a multiplayer property.
:* Fix for small bugs that can build a MP packet loop, making usage impossible

=== OpenRadar updates 2015-03-02 ===

* deselect a contact with a double ESC
* volume control for FGCOM (use your mouse wheel above the number in radio line)
* Possibility to use flightgear as window to the airport (ORCAM)
:* Presets
:* different camera locations possible
:* initial auto zoom
:* follow mode (camera follows contact)
:* multiplayer port forwarding makes camera invisible on MP server
* remove need for AirportIndex data file, OR finds all airports now

=== OpenRadar updates 2015-01-31 ===

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
* small weather icon displays the flight conditions around the airport (start and landing): VFR,MVFR,IFR,LIFR

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadarDownload

2015-03-21T07:05:38Z

Wagnerw: Changed link for download to SF files page

[[OpenRadar|< Back to the main OpenRadar page]]

This article will guide you through the download, installation and setup of OpenRadar.

At first the most important: We publish early to give you influence on the final application.

== Installation of OpenRadar ==
=== Download ===
# Download the zip file from [https://sourceforge.net/projects/openradar/files/Latest%20release/ here] ([[OpenRadar_Change_Log|Change Log]])
# Extract the content to a place where it is easy to find
# If your former version had a 'settings' folder, please copy the 'xml' and 'properties' files into the new extracted settings folder (all but the defaults.properties: user.properties contains your inputs in settings dialogue, atcComments.xml contains the text on the flight strips, the airport property files your centerline/radio frequency settings of the airport, the content of sub folder ATCmsg contains the templates for the automatic ATC messages, copy it only, if you have adapted it!)

=== Dependencies ===
# You need a recent Java installed (at least Java Runtime Environment 1.7)

== The Guide ==
Please read our [[OpenRadarGuide| Guide]] ! It shows all the features in detail!

== Questions/Help/Issues ==
I try to collect known issues tips and tricks on this page and [[OpenRadarKnownIssues|here]].
Please check if I have provided a new version of the binary release in meantime. Maybe your issue is gone.

Last but not least: Please be positive and give constructive feedback. Which features are useful, which should be changed, what is really missing. Target should be to have a reliable, handy tool, not an potentially really useful, but overloaded and buggy everlasting prototype.

== Developers ==
If you are a developer, please contact us (Wolfram) before you start to help us.

[[Category:OpenRadar|Download]]

OpenRadar

2015-03-21T07:01:13Z

Wagnerw: Changed gitourious to SF

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease = Nov, 18th 2012
| latestrelease = March, 16th 2015
| writtenin = Java
| os = Linux, Windows, Mac
| platform = Java
| developmentstatus = active
| type =
| license =
| website = https://sourceforge.net/projects/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadar_FGFS_ORCAM|ORCAM: Your window to the the airport]]

* [[OpenRadarDownload|'''Download'''! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadarKnownIssues|'''FAQ''' / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:OpenRadar| ]]

OpenRadarGuide

2015-03-16T20:12:31Z

Wagnerw: Functional Keys added ESC ESC and F1-F4

[[OpenRadar|Back to mainpage]]

=='''''Preface'''''==
[[OpenRadar]] supports [[FlightGear]]-[[ATC#Air_Traffic_Control|ATCs]] when guiding/controlling [[Howto:Multiplayer|Multiplayer]]-traffic within FlighGear.

Some words to our project targets:
* '''Realism:''' That means we show all the data a Real-Live ATC would need for his job. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises to a Real-Life operation.
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application.

We hope that we met your needs and are happy to get feedback!

'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have been forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...
 
----

=='''''Prerequisites'''''==
===Internet===
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!

===Communication===
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).
You will soon discover, that using a Radio-application makes it much easier to communicate
*as well for you ''(who hopefully will control many pilots at the same time)''
*as also for the pilots ''(who need both hands to control their plane)''.

Typically available ways of communication are:
*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots. You always should offer this option ''(and try to convince pilots to use a Radio-Option!)''.
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directly from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone".
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.
:::To activate it see http://mumble.sourceforge.net/Mumbleguide
:::The most used Mumble-server is "mumble.allfex.org"

=== Java V7 ===
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp

=== OpenRadar ===
For the latest stable version of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.
 
If you did already work with an OpenRadar installation you may want to
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!

== '''''Startup''''' ==
Inside the downloaded OpenRadar base-directory you will find start-scripts. See
* for Windows: OpenRadar.bat
* for Linux: OpenRadar.sh
* for OSX: OpenRadar.jar
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 4 TABs to define your preferences:
{|
|-
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome - Select Airport]]
|| [[File:OpenRadar- Settings-linux.png|thumb|Settings - Communication]]
|| [[File:OpenRadar-Flightplans-Linux.png|thumb|Flightplans]]
|| [[File:OpenRadar - Tweaks.png|thumb|Tweaks]]
|}
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.
 
=== OpenRadar-Welcome - Select Airport ===
OpenRadar will always start with the most left Window in which you define the airport on which you want to operate:
* '''If this is the first time you work with OpenRadar you first must check/set your options in all the other tabs!'''
* If the wanted airport is not yet listed:
:* type the wanted airport ICAO (e.g. KSFO or EDDF or ...) into the inputline left of "search" and click onto "search"
::* if that ICAO code is available, then OpenRadar will list add it to the list
::* a single mouseclick onto the listed airport will activate that selection
:::* and will set a default into the "CallSign" field at the lower right corner. You may overwrite that here or later on during the session (ref. chapter [[#Status_Informations]])
:::* then you can review all settings prior you click onto Start
* If the wanted airport is already in the list of airports then you may directly start with a mouse-double-click onto that ICAO-code ''(or single click and then "Start" at the bottom)''
::* a double-click on it will order OpenRadar to search and load all the required data (into your local file "OpenRadar/Data/ICAO")
::* that may take some time → wait till the "Ready" appears in the lower Textfield → then click onto "Start"
* To delete an airport form your PC delete its ICAO code out of your local directory "OpenRadar/Data/"

=== Settings (Communication) ===
This window lets you define your communication settings:

==== ''FGCom (Radio/Voice Communication)'' ====
:OpenRadar can support up to 4 instances of FGcom in 2 ways:
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)
:#or just control manually started FgCom-sessions.

:You select these modes of operation by the “'''FgComMode'''” selection:
 
:'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:
::'''Path:''' Here you define where your FGcom is installed.
:::In the following some examples:

:::{| class="wikitable" style="text-align:center"
!type
!Windows
!Linux
!OSX
|-
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)
|-
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)
|-
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)
|}
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b'''

::'''Executable:''' Here you define the program-name that shall be started
:::*For Windows: "fgcom.exe" or "anyName.bat"
:::*for Linux: "fgcom" or "anyName.sh"
:::*OSX: ''again for OSX this does not apply, see 1b''
:::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0)
::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org
:::''You still may be using fgcom01.flightgear.org in a group in that all users use this server''
::'''Client:''' must always be “localhost”
::'''FGcom Ports:''' The here defined values are crucial for the operation because:
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar
:::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!
:::::e.g. 16661,16662
 
:'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:
::*'''Client:''' localhost
::::If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,
:::::e.g. "fgcom -Sfgcom.flightgear.org/ -p16662 -i1 -o1 -s192.168.178.23" 
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''
 
:'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar)
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields.

==== ''Alternative Radios (e.g. '''Mumble''')'' ====
:Mark this option if you want to use e.g. Mumble - that has no functional implications, but will add an information to that effect onto your OpenRadar Operating-Panel.
:If you want to use mumble see http://wiki.mumble.info/wiki/Main_Page and/or http://www.emmerich-j.de/Mumble/mumble.html for installation and operation

==== ''FG Multiplayer'' ====
:Here you find the server and connection port for the "FlightGear multiplayer server". It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals".
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.

==== ''Multiplayer Chat'' ====
:In addition to the standard List of ATC-commands selected out of of the drop-down-select-list (right click onto a target) there is a list of codes that you can type into the MPchat. See the list in "../OpenRadar/data/atcMessages/alias.txt". This list you may extend for any (standard) messages you want to sent to pilots via MPchat.
::Define as "Prefix" any character that you will use to indicate that the following is a command (default is a dot ".").
:::e.g. if you type ".rs" → MPchat will replace that with "Reduce speed to ".

==== ''METAR'' ====
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!

=== Flightplans ===
You must define the Server for the distribution of FlightPlan data between all OpenRadar-ATCs. So activate "enable flightplan exchange" and insert the server address:
 http://h2281805.stratoserver.net/FgFpServer/
 Under this address you can also check where ATC's are offering services right now.

Please click on the "Check Settings" button to have your settings checked prior to continue:

=== Tweaks ===
Select/enable according to the descriptions.
 Be aware that these option may influence the responstimes of your PC drastically!

== '''''Operating''''' ==
[[File:OpenRadar Prototype.png|right|270px]]
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''

The OpenRadar main screen is divided into four regions:
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids, and the radar targets.
#At the bottom of that Radar Map there is a line for '''Radar Options'''
#Bottom left you see the '''MPchat Area''' for the FlightGear MultiPlayer chat feature
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are
##'''Status Information'''
##'''Radios for Communication''' ''(only if you have defined one or more in chapter [[#Settings]] )''
##'''Runway Manager''' to set up runways used
##the '''Flight Strip Manager''', where you can manage your radar targets.
To see examples of actual ATC-events with OpenRadar you may visit http://www.emmerich-j.de/EDDF/Films/Films.html.
==== Radar Map ====
The radar map is the most complex part of OpenRadar, thus you have many options to zoom into any detailed area you are interested in. To do that you can:
* zoom in and out using your mouse wheel ''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''
* adjust the map-center by dragging it with your mouse (click-hold left and drag)
* a double mouse-click onto the scope will move that point into the center of the scope
* a double right mouse-click will center the scope back to your location
* a double mouse-click onto a Flightstrip will center the "Target and Airport" into the center of the map and resize accordingly
* set the four functional zoom levels '''''GROUND, TOWER, APP and SECTOR''''' by zooming the radar map to your taste and then do a "right mouse-click" onto the zoom level wanted for it. Then you can always resize the map to that zoom again by just clicking onto the wanted zoom-level.

 
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]
The standard '''''Radar-targets'''''
*do have a label attached with the following informations:
::''(See also the chapter [[#Flight-management]])''
:{| class="wikitable" style="text-align:center"
|-
|UID||heading direction
|-
|Airplane type||Flightplan||controlling ATC (if not you)
|-
|Flight Level||Airspeed
|}
*and are displayed in 6 different colors:
:{| class="wikitable"
|-
|align="middle"|blue||That are all targets that you controll
see e.g. "KL-666" on approach and "B777-20" ready for TakeOff
 their Flightstrips are placed to the left
|-
|align="center"|white||That is always the currently selected target for ATC messages. It's UID is also placed into the MPchat inputline for immediate messages
see e.g. "G-MNKY" who just gets his taxi-instructions from you
 his Flightstrip may be in any position - it's control-status does not matter because you can talk to any target on the screen (but please do not interfere with the operation of other ATC's in the area!) 
|-
|align="center"|yellow||may be used for targets that are not under your controll - but may ask for your attation soon or may become hazardous for your operations!
their Flightstripes are placed into the middle
|-
|align="center"|green||targets who are not controlled by you
see e.g. "CEMI198" just crossing in high altitude - outside your control
 their Flightstrips are placed to the right - that is also the position in which all new targets are placed initially
|-
|align="center"|gray||is a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.
|}

==== ''Radar-Options'' ====
[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can show/noShow types of data by the following buttons at the lower botton of the radar-scope:
 
[[File:OpenRadar-Radar-Options.png|250px]]
 
'''''a) map:'''''
{| class="wikitable"
|-
| style="text-align:center;" | STP || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', an attachment to the mousepointer, showing
*the direction from the "active target" to the mouse-position (and reverse)
*and the distance and the calculated time for the target to get there|
|-
| style="text-align:center;" | PPN || Show/NoShow Parking/Gate names (those will automatically be set "NoShow" above distinct scale-settings!)
|-
| style="text-align:center;" | FIX || Show/NoShow FIX's (those will automatically be set "NoShow" above distinct scale-settings!)
|-
| style="text-align:center;" | RW-FIX || Special Waypoints for automatic approaches/departures (those will automatically be set "NoShow" above distinct scale-settings!)
|-
| style="text-align:center;" | NDB || Show/NoShow NDB's
|-
| style="text-align:center;" | VOR || Show/NoShow VOR's
|-
| style="text-align:center;" | Airports || Show/NoShow Airports, inclusive their groundlayout (You may double-click onto a wanted airport and zoom in to see the layout)
|-
| style="text-align:center;" | Circles || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!
|-
| style="text-align:center;" | GS Heights || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. (They will automatically be set "NoShow" above distinct scale-settings!)
|-
| style="text-align:center;" | data mode || Defines different modes of Transponder-operations. Try it and notice the differences in the Target-tags and Flightstrips.
|-
| style="text-align:center;" | update frequencies || allows you to vary the timespan between refreshing the radar-picture
|-
| style="text-align:center;" | contact tail || adds a tail of points to the targets - thus indicating the past way of the target
|-
| style="text-align:center;" | layers || lets you select to add overlays to the radar:
*landmass = costlines and similar
*taramacs = the GND-shape of airports
|}
 
'''''b) sounds:'''''
 Here you can select which "happenings" will produce an additional sound (This list may change in further releases)
 
'''''c) STP:'''''
 
Show/NoShow the "Selected (target) To Pointer" ''(doggy)'' (Same as in table above - just for faster access)
 
'''''d) STAR/SID:'''''
 
Show/NoShow the unique Waypoints defined in the STAR/SID's
 
'''''e) PPN:'''''
 
Show/NoShow Parking/Gate names (Same as in table above)

 
==== MPchat area ====
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]
This area allows you to enter chat messages, view the chat history and filter it.
 
In the '''''entry-line''''' atop you define your messages to any radar-target by:
*Manually typing a message:
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line
**Then you may type or copy/past anything behind that - and send it out by ENTER
*** The font-color will change to red if the message becomes too long for the multiplayer distribution - shortly bevor that the font-color changes to blue as an early warning.
*Generate a standard message:
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER
*Repeat a message:
**With the '''cursor-keys "up" and "down"''' you can scroll thru the list of messages and place them into the '''''entry-line''''' - then you may edit it and send it out by ENTER.

*OpenRadar will always set the ATC-name (as it appears on the very top of the service area - see the following chapter) in front of the message.

Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".

You may enlarge that MPchat-area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!

==== Service Area ====
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.

=====Status Informations=====
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations (the here 3rd line will be removed soon!)]]

This area shows in 4 lines the status-informations of your session ''(compare the picture)'':
* The first line contains several informations:
::* "19:46 '''UTC'''" is the actual "Coordinated Universal Time" ''(replacing nowadays the formerly used "Greenwich Mean Time" (GMT))''
::* "5000/TL055" is the so called '''Transition Altitude''' for that airport/area, in which:
:::* 5000 gives the "Transition Altitude" in feet when climbing
:::* TL055 gives the "Transition Level" when descending into that area ''(in FlightLevels: 1 FL = 100 feet))''
:::: Above that level the altimeter must be set to the standard pressure setting of '''1013''' hectopascals (millibars) or '''29.92''' inches of mercury
::* At the very right is a text box that allows you to see and change your current '''MP-callsign'''. So you can quickly change it, if e.g. a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). You may change that ID also when starting the OpenRadar. (ref. chapter [[#Startup]])
* The second line displays the '''[[http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO]]''' and the long name of your airport.
* The last 2 lines show the current '''[[Weather_reports]]''' (also called ATIS or METAR):
::* At the begining there will be placed a short summary of the flight-conditions:
::::{| class="wikitable" style="text-align:center"
!Code
!Meaning
!Cloud Ceiling
!Visibility
|-
|LIFR||Limited IFR||<500 ft|| visibility <1 nm
|-
|IFR||Instrument Flight Rules||<1000 ft || visibility <3 nm
|-
|MVFR||Marginal VFR||<3000 ft|| visibility <5 nm
|-
|VFR||Visual Flight Rules||>3000 ft||>5 nm
|}
::* With a mouse-click on the upper line only that line will be sent to the target
::* A mouse-click to the lower line will send both lines to the target

====='''COM-Radios'''=====
'''''if FGCOM'''''
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]
:According to the amount of FGcom-Ports you defined during [[#FGCom_.28Radio.2FVoice_Communication.29|setup]] you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may
:*choose a frequency out of the list by clicking onto the arrow at the right of the input-field
:*or empty the field by a right mouseclick and enter any other frequency wanted.
:At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.
::{| class="wikitable" style="text-align:center"
!COMx
!left on keyboard
!right on keyboard
|-
|COM0||Ctrl||NumOff+Num0
|-
|COM1||SHIFT||NumOff+Num1
|-
|COM2|| ||NumOff+Num2
|-
|COM3|| ||NumOff+Num7
|}
:Please watch the color change of the PTT buttons to know, when you can speak.

:In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode (compare the [[#FGCom_.28Radio.2FVoice_Communication.29|Setup]]), then
:*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)
:*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.
 
'''''if e.g. MUMBLE'''''
:In case you use mumble there will be just a blank input-field. Into that field you may insert any text that will then show up in your advises to pilots. We suggest e.g. the to use the mumble-server:
::: '''mumble.allfex.org'''

====='''Runway Settings'''=====
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right:
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values ''(see the picture "The Runway Manager Settings" below)''. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'':
**In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)''. These settings will then be saved separately for each unique runway and airport in you private settings.
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may
:::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear
:::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.
:*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways.
 
Finally your picture will look similar to the right/above shown "The Runway Manager"!
*In that one you see from left to right the following informations for each runway:
:*The runway-name
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)
:*A second check-box to display SID/STAR graphics for that runway (if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml).
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! (Remember: You find the normal wind values in the METAR-data further up in the [[#Status_Informations]])
:*To the right follows
::*in the upper line the exact runway heading (as needed for older type autopilots)
::*in the lower line the length and width of the runway in feet!
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.

After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. (You may move the mouse very fast - then all runways remain visible). Click into that remaining "Runway Manager" to show again all runways.

====='''Flight Strip Manager'''=====
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:
:{| class="wikitable" style="text-align:center"
|-
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC
|-
|distance to it||IAS+GND speed||Altitude (FL)||current heading
|}
In addition You may add some more unique informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list may become that long, that you must scroll constantly! These additional lines will be saved as target-data ''(see ../OpenRadar/Settings/atcComments.xml)'' and inserted each time a new stripe is created for that target! See as a suggestion a typical last line for a unique target name:
:"ILS VOR FGC NRW || and personal remark"
:This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || and personal remark

You are absolutely free to define your own codes and whatever. To do so:
* enter/edit those data by opening the "'''''Note Editor'''''" with a '''center mouse-click''' ''(Mac: Alt + right mouse-click)'' onto the stripe. There you have several areas to add unique informations:
:* At the top of this editor you can
::* select in which '''''native language''''' the "standard commands" shall be transmitted (in addition) to that target
::* mark if that target uses Radio ''(the label now says "FgCom", but you may use that for any Radio-usage)''
:* the upper, larger input-block at the bottom is planed to be used for additonal FligtPlan-data or extended lists of waypoints.
:''The above data may be distributed to all ATC's.''
:* the lower, smaller input-block you may use for your personal requirements, they will not be distributed, but they will be retrieved automatically each time that target reappears on your screen.
:* all other (Flight-Plan) data will be explained in the next chapter: [[#Flight-Plan & Flight-Management]]
* exit the Flight-Stripe-Editor clicking into any area outside of it.
 
You can '''''manipulate the listing''''' regarding the vertical and horizontal position of the flight strips:
* New radar-targets will always appear at the end of the list on the right side and will be colored in lightgreen (that green will disappear when you touch that lable first time - thus you always know which ones you have already actively noticed!)
* You can move the stripes in vertical order by drag and drop
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!
* The radar-targets will change their color according to the horizontal position of their stripe:
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized - i.e. they are not under your controll - any ATC in the area can take control of them
** the radar-targets for stripes in the center will be '''yellow'''
** the radar-targets for stripes at the left side will be '''cyan'''
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!

You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, or he may become a danger to the traffic controlled by me if he continues uncontrolled! etc.
:'''''cyan''''' = left = under my control.
Again: That is a proposal - you can define your on meanings!

You can '''apply the following mouse-actions''' onto the stripes as well as onto the radar-targets:
* a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition
**its listed messages in the MPchat-list become colored cyan
**and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.

=='''''Flight-Plan & Flight-Management'''''==
There is now a Flight-Plan feature inside OpenRadar. With this you can define OpenRadar-internal Flight-Plans ("OR-FP") that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. Due to time-restraints/workload ATC's will only input the most required data (see in the following the "Mandatory fields") - thus that will never substitute a thorough flightplanning by the pilot - nor will ATC take the time to type ALL flightdata as dictated by the pilot!
 
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define all data for his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. As of Feb.2015 this is already functional with the Flighplanning on "http://flightgear-atc.alwaysdata.net".

==='''Define/Edit a Flight-Plan:'''===
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]

You open the Flight-Plan for a target by clicking with the “center mouse-button”
*onto the Flight-Strip of the target
*or the target on the radar-screen
*You can also open the "active" target by the '''^'''-key

'''Before''' you start defining a new plan
# click onto the button "Retrieve FP" - that will load any Flightplan that may be available on a compatable FP-system
# otherwise you should make sure all data become "newly intialized" click onto the button "Reset FP"

'''After''' the Pilot "Landed" and "closes" his FP you should use the "Close FP" so that plan will also be closed in the OpebRadar server

'''Controlling the ownership:''' 
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field
“Controlled/Uncontrolled" must state “controlled by me”!

* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change

*If it is “'''Controlled by …..'''”
**you must wait till the ATC controlling it now will
***either remove his “ownership” by
****clicking onto “Handover to” and selecting
*****another ATC for takeover
*****or the “blank” for just removing his control.
****or clicking onto the button “Control” (besides the lable "Uncontrolled...")
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically
**or you send the controlling ATC a mail asking him to release the target

*If it shows “'''Controlled by me'''” you can release the target
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)
**or you move the Flight-Strip all the way to the right – that will just remove your ownership

'''Mandatory fields of the OR-Flight-Plan:'''
*'''Contact''' is the FGFS-UID of the target (will be set automatically)
*'''Radio''' needs to indicate that the target can use Radio (FGCom or Mumble or ..)
*'''Aircraft''' is the model-code of the target (will be set automatically)
*'''Assgnd RWY''' needs the planned runway for departure or landing. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”
*'''SID/STAR''' needs the name of the SID/STAR, if requested by the pilot
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)
*'''Destination''' needs the ICAO-code of the destination (e.g. EDDF for Frankfurt)
*'''Crsg Alt''' needs the planned (initial) cruising altitude for that flight (usually in FL)
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)

'''Optional fields of the OR-Flight-Plan:'''
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”
*'''Squawk''' shows the Squawk-Code you assigned to the target (for details see [[Transponder]])
*'''Waypoints''' keeps predefined waypoints (if required or sent by other flightplanning systems)
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))
*'''Code''' will be used in future when given by a more professional Flight-Planning system
*'''IFR/VFR''' may be defined by the PullDown
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned destination airport
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). These will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.

==='''Flight-management:'''===
Open the wanted Flight-Plan
* by a center-mouse-click onto the radar-target or the FlightStrip
* you can also use the '''^'''-key to open the FlightPlan of the active target.
Then continue as described in the following scenarios:
''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''

'''''1. A target appears on your airport'''''
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]
:There are no data yet filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus
:*the text in the tag-color is “green” - i.e. you did not yet take control
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it
:*a simple mouse-click or any other action will remove the green background (and activate that target as usual - i.e. showing the lable-text and the MPchat messages for this target in cyan).

'''''2. You define a new Flight Plan'''''
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''
*'''Generate the Flight-Plan:'''
:Compare the Informations given in the target-label and the stripe:
::''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]
::{| class="wikitable"
|-
|jomo
|the pilot FGFS-UID
|-
|160°
|the current heading (now on ramp!)
|-
|HeadSet-sign
|that pilot uses radio (FGCom or Mumble)
|-
|CONC
|the FGFS-model is the Concorde
|-
|KJFK
|is the planned destination
|-
|260°
|is the straight heading EDDF (departure) to KJFK (destination)
|-
|BIBTI
|is the SID planned for departure (on arrival here would be the STAR)
|-
|RW25C
|is the runway assigned for departure (or for arrival)
|-
|0400*
|is the current altitude (on GND in EDDF!)
|-
|00
|is the speed (still parking!)
|}
 
*'''Departing:'''
**GND will use the data as shown above, to bring the plane to the HoldingPoint
**TWR will take over
**The runway-assignment will be removed automatically after Take-Off
 
*'''Transfer Control to next ATC (or blank) '''
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]
*grab-move the FlightStrip to the left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.
*if there is no “next ATC” available select the blank entry – the target is then free to be picked up by another ATC en-route.
*the FlightStrip will indicate the pending transfer by showing
:::“current ATC” => “next ATC”
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!

'''''3. A target appears in your airspace:'''''
*take over the control (i.e. move the Flight-Strip all the way to the left)'' if
:* there is no ATC assigned yet
:* or the FlightStrip indicates that the current ATC wants you to take over the control '' ''(see above “current ATC” => “next ATC” indication)''
* if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.
* If the target lands on your airport:
** assign a RW and optional a STAR
** the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''

'''''4. A ATC forgets to “reassign” or “free” a target:'''''
* The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.
* or you contact that ATC and require to release that target out of his control
 
==='''Summery of Flight-Strips and Target-Tags'''===
Depending on what you selected in "map" -> "data mode" ''(see the menu above the MPchat entry-line, at the very left)'' the Radar labels may look different. See the summary in the following table:
{| class="wikitable"
|+
!width="30%"|Status
!width="30%"|FlightStrip
!width="20%"|Traditional
(no transponder interaction)
!width="20%"|Simulation
(Transponder enabled)
!width="20%"|Pure Simulation
(Transponder enforced)
|-
|'''''Target appears on EDDF airport:'''''
no ATC and no Flight-Data are assigned yet
|align="center"|[[File:OpenRadar-target-lables-10.png]]
|align="center"|[[File:OpenRadar-target-lables-11.png]]
|align="center"|[[File:OpenRadar-target-lables-12.png]]
|align="center"|[[File:OpenRadar-target-lables-13.png]]
|-
|'''''jomoATC inputs a Flightplan:'''''
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250
Rw for TakeOff 25C
|align="center"|[[File:OpenRadar-target-lables-20.png]]
|align="center"|[[File:OpenRadar-target-lables-21.png]]
|align="center"|[[File:OpenRadar-target-lables-22.png]]
|align="center"|[[File:OpenRadar-target-lables-23.png]]
|-
|'''''After TakeOff:'''''
notice that RW25C has been canceled
|align="center"|[[File:OpenRadar-target-lables-30.png]]
|align="center"|[[File:OpenRadar-target-lables-31.png]]
|align="center"|[[File:OpenRadar-target-lables-32.png]]
|align="center"|[[File:OpenRadar-target-lables-33.png]]
|}
'''''EDDF forwards the target to EDDK:'''''
{| class="wikitable"
|-
|'''in EDDK''' it appears with a yellow background to enforce attantion
after ATC-EDDK has taken over, that yellow will disappear
and the "lastATC ==> "newATC" will be replaced by "currentATC"
and the "private Notes" will be replaced with those of the newATC (if he has some)
|align="center"|[[File:OpenRadar-target-lables-41.png]]
|-
|'''in EDDF''' that private notes remain,
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”
|align="center"|[[File:OpenRadar-target-lables-42.png]]
|align="center"|[[File:OpenRadar-target-lables-43.png]]
|}

== '''''Functional Keys''''' ==
'''Radar Map'''
* On contact
:* '''left''' click '''selects''' and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box

* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...

'''Flight Strip Area'''
* On flight strip
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box 

:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)
:* '''CTRL+left''' click sets the contact to be '''neglected'''

* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)

'''Runway area'''
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)

'''Radios'''
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself

''' Shortcuts '''
{| class="wikitable"
|-
! Shortcut !! Action
|-
| {{key press|ESC}} || Close all open dialogs and cancel the text input (reset chat input field)

|-
| {{key press|ESC}},{{key press|ESC}} || Deselects the current contact

|-
| {{key press|ALT}} + {{key press|L}} || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left {{key press|CTRL}}''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left {{key press|SHIFT}}''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|-
| {{key press|F1}} || Zoom Level GROUND
|-
| {{key press|F2}} || Zoom Level TOWER
|-
| {{key press|F3}} || Zoom Level APP
|-
| {{key press|F4}} || Zoom Level SECTOR
|-
| {{key press|F11}} || play new Chat, new Contact and new METAR sound (for sound testing)
|-
| {{key press|F12}} || Copy mouse location (geo coordinates) to clipboard (for route design)
|-
| {{key press|Shift|F12}} || Reload and update standard route
definitions and texts (for development)
|}

== Related content ==
* [[OpenRadar|The Design-Rules for OpenRadar]]
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadarKnownIssues|FAQ / Known Issues]]

[[Category:OpenRadar|Guide]]

OpenRadar Change Log

2015-03-16T19:59:09Z

Wagnerw: OR update

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update ==
n/a

== Published updates ==

=== OpenRadar updates 2015-03-16 ===

* chat input foreground color is not fixed to black anymore, adapts to your system settings
* better formula to calculate initial heading to remote airports. Matches now to skyvector results (small error caused by magnetic model of fgfs)

=== OpenRadar updates 2015-03-14 ===

* Transition is more flexible now
:* Transition altitude must be defined (usually fix for airport)
:* Default: Calculated Transition Level depending on air pressure: Transition Layer minimum width can be defined
:* Fix TL Mode: Less airports have a fix TL: It can be defined now. Usually you are wrong, if you use this on any other airport. Manual TL calculation on normal airports requires frequent re-calculation to ensure separation.
* Fixes to ORCAM
:* better control of FGFS to avoid weird things when you adapt the height of the camera via CTRL+A, CTRL+Z
:* Fix for missing MP properties (rotors did not turn, livery missing, retracted gear movement), OR forwarded wrong type for a multiplayer property.
:* Fix for small bugs that can build a MP packet loop, making usage impossible

=== OpenRadar updates 2015-03-02 ===

* deselect a contact with a double ESC
* volume control for FGCOM (use your mouse wheel above the number in radio line)
* Possibility to use flightgear as window to the airport (ORCAM)
:* Presets
:* different camera locations possible
:* initial auto zoom
:* follow mode (camera follows contact)
:* multiplayer port forwarding makes camera invisible on MP server
* remove need for AirportIndex data file, OR finds all airports now

=== OpenRadar updates 2015-01-31 ===

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
* small weather icon displays the flight conditions around the airport (start and landing): VFR,MVFR,IFR,LIFR

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadar

2015-03-16T19:56:47Z

Wagnerw: OR update

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease = Nov, 18th 2012
| latestrelease = March, 16th 2015
| writtenin = Java
| os = Linux, Windows, Mac
| platform = Java
| developmentstatus = active
| type =
| license =
| website = http://www.gitorious.org/fg/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadar_FGFS_ORCAM|ORCAM: Your window to the the airport]]

* [[OpenRadarDownload|'''Download'''! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadarKnownIssues|'''FAQ''' / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:OpenRadar| ]]

OpenRadar Change Log

2015-03-15T08:35:24Z

Wagnerw: /* Next update */

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update ==
* chat input foreground color is not fixed to black anymore, adapts to your system settings (hopefully, cannot test it)
* better formula to calculate initial heading to remote airports. Matches now to skyvectors results (small error caused by magnetic model of fgfs)

== Published updates ==

=== OpenRadar updates 2015-03-14 ===

* Transition is more flexible now
:* Transition altitude must be defined (usually fix for airport)
:* Default: Calculated Transition Level depending on air pressure: Transition Layer minimum width can be defined
:* Fix TL Mode: Less airports have a fix TL: It can be defined now. Usually you are wrong, if you use this on any other airport. Manual TL calculation on normal airports requires frequent re-calculation to ensure separation.
* Fixes to ORCAM
:* better control of FGFS to avoid weird things when you adapt the height of the camera via CTRL+A, CTRL+Z
:* Fix for missing MP properties (rotors did not turn, livery missing, retracted gear movement), OR forwarded wrong type for a multiplayer property.
:* Fix for small bugs that can build a MP packet loop, making usage impossible

=== OpenRadar updates 2015-03-02 ===

* deselect a contact with a double ESC
* volume control for FGCOM (use your mouse wheel above the number in radio line)
* Possibility to use flightgear as window to the airport (ORCAM)
:* Presets
:* different camera locations possible
:* initial auto zoom
:* follow mode (camera follows contact)
:* multiplayer port forwarding makes camera invisible on MP server
* remove need for AirportIndex data file, OR finds all airports now

=== OpenRadar updates 2015-01-31 ===

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
* small weather icon displays the flight conditions around the airport (start and landing): VFR,MVFR,IFR,LIFR

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadarDownload

2015-03-14T09:56:38Z

Wagnerw: Stripped the page down

[[OpenRadar|< Back to the main OpenRadar page]]

This article will guide you through the download, installation and setup of OpenRadar.

At first the most important: We publish early to give you influence on the final application.

== Installation of OpenRadar ==
=== Download ===
# Download the zip file from [http://wagnerw.de/OpenRadar.zip here] ([[OpenRadar_Change_Log|Change Log]])
# Extract the content to a place where it is easy to find
# If your former version had a 'settings' folder, please copy the 'xml' and 'properties' files into the new extracted settings folder (all but the defaults.properties: user.properties contains your inputs in settings dialogue, atcComments.xml contains the text on the flight strips, the airport property files your centerline/radio frequency settings of the airport, the content of sub folder ATCmsg contains the templates for the automatic ATC messages, copy it only, if you have adapted it!)

=== Dependencies ===
# You need a recent Java installed (at least Java Runtime Environment 1.7)

== The Guide ==
Please read our [[OpenRadarGuide| Guide]] ! It shows all the features in detail!

== Questions/Help/Issues ==
I try to collect known issues tips and tricks on this page and [[OpenRadarKnownIssues|here]].
Please check if I have provided a new version of the binary release in meantime. Maybe your issue is gone.

Last but not least: Please be positive and give constructive feedback. Which features are useful, which should be changed, what is really missing. Target should be to have a reliable, handy tool, not an potentially really useful, but overloaded and buggy everlasting prototype.

== Developers ==
If you are a developer, please contact us (Wolfram) before you start to help us.

[[Category:OpenRadar|Download]]

OpenRadar

2015-03-14T07:55:47Z

Wagnerw: Update

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease = Nov, 18th 2012
| latestrelease = Feb, 14nd 2015
| writtenin = Java
| os = Linux, Windows, Mac
| platform =
| developmentstatus = active
| type =
| license =
| website = http://www.gitorious.org/fg/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadar_FGFS_ORCAM|ORCAM: Your window to the the airport]]

* [[OpenRadarDownload|'''Download'''! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadarKnownIssues|'''FAQ''' / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:OpenRadar| ]]

OpenRadar Change Log

2015-03-14T07:41:33Z

Wagnerw: Update

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update ==
-n/a-

== Published updates ==

=== OpenRadar updates 2015-03-14 ===

* Transition is more flexible now
:* Transition altitude must be defined (usually fix for airport)
:* Default: Calculated Transition Level depending on air pressure: Transition Layer minimum width can be defined
:* Fix TL Mode: Less airports have a fix TL: It can be defined now. Usually you are wrong, if you use this on any other airport. Manual TL calculation on normal airports requires frequent re-calculation to ensure separation.
* Fixes to ORCAM
:* better control of FGFS to avoid weird things when you adapt the height of the camera via CTRL+A, CTRL+Z
:* Fix for missing MP properties (rotors did not turn, livery missing, retracted gear movement), OR forwarded wrong type for a multiplayer property.
:* Fix for small bugs that can build a MP packet loop, making usage impossible

=== OpenRadar updates 2015-03-02 ===

* deselect a contact with a double ESC
* volume control for FGCOM (use your mouse wheel above the number in radio line)
* Possibility to use flightgear as window to the airport (ORCAM)
:* Presets
:* different camera locations possible
:* initial auto zoom
:* follow mode (camera follows contact)
:* multiplayer port forwarding makes camera invisible on MP server
* remove need for AirportIndex data file, OR finds all airports now

=== OpenRadar updates 2015-01-31 ===

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
* small weather icon displays the flight conditions around the airport (start and landing): VFR,MVFR,IFR,LIFR

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadarDownload

2015-03-02T06:44:58Z

Wagnerw: /* Shortcuts */

[[OpenRadar| Back to mainpage]]

At first the most important: We publish early to give you influence on the final application.

== Installation of [[OpenRadar]] ==

=== Download ===
# Download the zip file from [http://wagnerw.de/OpenRadar.zip here] ([[OpenRadar_Change_Log|Change Log]])
# Extract the content to a place where it is easy to find
# If your former version had a 'settings' folder, please copy the 'xml' and 'properties' files into the new extracted settings folder (all but the defaults.properties: user.properties contains your inputs in settings dialogue, atcComments.xml contains the text on the flight strips, the airport property files your centerline/radio frequency settings of the airport, the content of sub folder ATCmsg contains the templates for the automatic ATC messages, copy it only, if you have adapted it!)

=== Dependencies ===
# You need a recent Java installed (at least Java Runtime Environment 1.7)

== First start ==
Depending on how good your Java is integrated into your OS, you can make a double click onto OpenRadar.jar, start one of the provided helper batch files or you have to start it manually.
In worst case: Open a console, change to the OpenRadar directory and type '''java -jar OpenRadar.jar'''.

At first start you have to define the settings. The settings are pre-set, but please check them!

===Notes to FGCom===

FGCom is a very useful part of software. Who has time to write chat message while flying? Speaking is easier and much more realistic.

You have four choices to define how much FgCom should be used by OpenRadar:

=====First: AUTO use the OR internal setup=====
If you choose this mode, you only have to provide the name of your fgcom server and one or several local ports. Each port will produce one radio in OR. You can have up to four radios, but more than 2 is not advised.
Use this mode if possible!

=====Second: Internal integrated=====
This is a possibility, if the first does not work for you:
Download the fgcom zip for your platform from here: [http://fgcom.flightgear.org/download/] and extract it to a place where you find it later.

After download and extraction set the path to the FGCom executable on settings tab to something like
{| class="wikitable"
|-
| Path || /home/USERNAME/fgcom/bin
|-
| Executable Windows: || fgcom.exe
|-
| Executable Linux: ||fgcom or fgcom.exe (uses wine)
|}
OpenRadar will use these settings to start fgcom.

You also need the following fields:
{| class="wikitable"
|-
| Server || the fgcom voip server to be contacted, e.g. fgcom.flightgear.org
|-
| Portlist || define one UDP port per fgcom instance you want to use (comma separated), e.g. 16661,16662
|}

=====Third: Control an external FgCom instance:=====
You can also start FGCom externaly and let OpenRadar control it. This can be used to separate OpenRadar and FgCom running on different computers. FgCom must be installed and extracted first:
Download the fgcom zip for your platform from here: [http://fgcom.flightgear.org/download/] and extract it to a place where you find it later.

To run FgCom externally, open one console per Radio, you want to use, change into the fgcom directory and start fgcom with someting like:
{| class="wikitable"
|-
| fgcom.exe --port=16661 -Sfgcom.flightgear.org
|}
Use different port numbers, one per instance and maintain them on settings tab as coma separated list!

In this scenario you also have to define the computer (client) running the fgcom instance. This enables you, to separate fgcom to run on a separate machine.
{| class="wikitable"
|-
| Client || the machine running the fgcom instance, most of the times 'localhost'
|}

OpenRadar will try to contact this instance using the port numbers you have defined here and on the settings tab.
You can also use FgComGui instead: You will have to set the ports in its Settings dialog.

=====Fourth: Off=====
You can decide, not to use FgCom. If so, some predefined ATC messages need manual correction because they refer to FgCom frequencies.

===Airport download===
Next step is the download of the surroundings around the airport you want to control. Please follow the instructions in A guide to OpenRadar!

== Shortcuts ==
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)
|-
| '''ESC, ESC''' || Double ESC deselects a contact.
|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|-
| '''F1''' || Zoom Level GROUND
|-
| '''F2''' || Zoom Level TOWER
|-
| '''F3''' || Zoom Level APP
|-
| '''F4''' || Zoom Level SECTOR
|-
| '''SHIFT+F12''': || Reload and update standard route definitions (for development)
|}

== Questions/Help/Issues ==
I try to collect known issues tips and tricks on this page and [[OpenRadarKnownIssues|here]].
Please check if I have provided a new version of the binary release in meantime. Maybe your issue is gone.

Last but not least: Please be positive and give constructive feedback. Which features are useful, which should be changed, what is really missing. Target should be to have a reliable, handy tool, not an potentially really useful, but overloaded and buggy everlasting prototype.

== Developers ==
If you are a developer, please contact us (Ralf and Wolfram) before you start to help us. Currently the code is still changing heavily and there are some places that are not stable.
Maybe single needed files may miss in GIT, please tell us, if you miss something!

[[Category:OpenRadar|Download]]

OpenRadar

2015-03-02T06:43:51Z

Wagnerw: OR update

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease = Nov, 18th 2012
| latestrelease = Feb, 2nd 2015
| writtenin = Java
| os = Linux, Windows, Mac
| platform =
| developmentstatus = active
| type =
| license =
| website = http://www.gitorious.org/fg/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadar_FGFS_ORCAM|ORCAM: Your window to the the airport]]

* [[OpenRadarDownload|'''Download'''! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadarKnownIssues|'''FAQ''' / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:OpenRadar| ]]

OpenRadar FGFS ORCAM

2015-03-02T06:41:39Z

Wagnerw:

[[OpenRadar|Back to mainpage]]

OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running FlightGear to make it act like a tower window, or a airport surveillance camera.

== Introduction ==
With only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== Install the aircraft orcam ===
At first you need to install the flightgear aircraft ''ORCAM''. It is a slightly modified ATC aircraft.

All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable. Help is appreciated anyway!

The aircraft is delivered with OpenRadar. You find it in OpenRadar's subdirectory "orcam". Please extract it into your aircraft directory!

(If it is not there, please update your OpenRadar first!)

=== Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=ORCAM \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Cameras, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''start follow mode''', click on Follow, while the contact is selected. The text follow changes, to display whom OR follows.

To '''end the follow mode''', click on Follow again, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

[[Category:OpenRadar]]

OpenRadar

2015-02-28T14:10:06Z

Wagnerw: /* Related content */

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease = Nov, 18th 2012
| latestrelease = Jan, 31st 2015
| writtenin = Java
| os = Linux, Windows, Mac
| platform =
| developmentstatus = active
| type =
| license =
| website = http://www.gitorious.org/fg/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadar_FGFS_ORCAM|ORCAM: Your window to the the airport]]

* [[OpenRadarDownload|'''Download'''! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadarKnownIssues|'''FAQ''' / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:OpenRadar| ]]

OpenRadar FGFS ORCAM

2015-02-28T14:09:23Z

Wagnerw:

[[OpenRadar|Back to mainpage]]
{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== Install the aircraft orcam ===
At first you need to install the flightgear aircraft ''ORCAM''. It is a slightly modified ATC aircraft.

All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable. Help is appreciated anyway!

The aircraft is delivered with OpenRadar. You find it in OpenRadar's subdirectory "orcam". Please extract it into your aircraft directory!

(If it is not there, please update your OpenRadar first!)

=== Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=ORCAM \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Cameras, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''start follow mode''', click on Follow, while the contact is selected. The text follow changes, to display whom OR follows.

To '''end the follow mode''', click on Follow again, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T14:06:36Z

Wagnerw: /* Write a fgfs startup script */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== Install the aircraft orcam ===
At first you need to install the flightgear aircraft ''ORCAM''. It is a slightly modified ATC aircraft.

All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable. Help is appreciated anyway!

The aircraft is delivered with OpenRadar. You find it in OpenRadar's subdirectory "orcam". Please extract it into your aircraft directory!

(If it is not there, please update your OpenRadar first!)

=== Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=ORCAM \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Cameras, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''start follow mode''', click on Follow, while the contact is selected. The text follow changes, to display whom OR follows.

To '''end the follow mode''', click on Follow again, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T14:05:58Z

Wagnerw: /* Install the aircraft orcam */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== Install the aircraft orcam ===
At first you need to install the flightgear aircraft ''ORCAM''. It is a slightly modified ATC aircraft.

All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable. Help is appreciated anyway!

The aircraft is delivered with OpenRadar. You find it in OpenRadar's subdirectory "orcam". Please extract it into your aircraft directory!

(If it is not there, please update your OpenRadar first!)

=== Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Cameras, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''start follow mode''', click on Follow, while the contact is selected. The text follow changes, to display whom OR follows.

To '''end the follow mode''', click on Follow again, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T14:05:17Z

Wagnerw: /* Download the aircraft orcam */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== Install the aircraft orcam ===
At first you need to install the flightgear aircraft ''ORCAM''. It is a slightly modified ATC aircraft. #

All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable. Help is appreciated anyway!

The aircraft is delivered with OpenRadar. You find it in OpenRadar's subdirectory "orcam". Please extract it into your aircraft directory!

(If it is not there, please update your OpenRadar first!)

=== Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Cameras, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''start follow mode''', click on Follow, while the contact is selected. The text follow changes, to display whom OR follows.

To '''end the follow mode''', click on Follow again, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T12:18:44Z

Wagnerw: /* Follow a contact */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== Download the aircraft orcam ===
At first you need the flightgear aircraft ''orcam''. That is a modified ATC aircraft. All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable.

Download the file from '''''Todo: URL to ORCAM''''' and extract it to your flightgear Aircraft directory. The same directory that contains all your downloaded aircrafts.

=== Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Cameras, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''start follow mode''', click on Follow, while the contact is selected. The text follow changes, to display whom OR follows.

To '''end the follow mode''', click on Follow again, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T10:23:36Z

Wagnerw: /* Two Camera, second camera shows same picture like first */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== Download the aircraft orcam ===
At first you need the flightgear aircraft ''orcam''. That is a modified ATC aircraft. All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable.

Download the file from '''''Todo: URL to ORCAM''''' and extract it to your flightgear Aircraft directory. The same directory that contains all your downloaded aircrafts.

=== Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Cameras, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''end the follow mode''', click on Follow, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T10:22:49Z

Wagnerw: /* Configuration */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== Download the aircraft orcam ===
At first you need the flightgear aircraft ''orcam''. That is a modified ATC aircraft. All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable.

Download the file from '''''Todo: URL to ORCAM''''' and extract it to your flightgear Aircraft directory. The same directory that contains all your downloaded aircrafts.

=== Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Camera, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''end the follow mode''', click on Follow, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T10:21:37Z

Wagnerw: /* Modifying the view */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== (1) Download the aircraft orcam ===
At first you need the flightgear aircraft ''orcam''. That is a modified ATC aircraft. All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable.

Download the file from '''''Todo: URL to ORCAM''''' and extract it to your flightgear Aircraft directory. The same directory that contains all your downloaded aircrafts.

=== (2) Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== (3) Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Camera, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via CTRL + A (up) and CTRL + Z (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''end the follow mode''', click on Follow, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T10:19:04Z

Wagnerw: /* Usage */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== (1) Download the aircraft orcam ===
At first you need the flightgear aircraft ''orcam''. That is a modified ATC aircraft. All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable.

Download the file from '''''Todo: URL to ORCAM''''' and extract it to your flightgear Aircraft directory. The same directory that contains all your downloaded aircrafts.

=== (2) Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== (3) Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Camera, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

[[File:OR CamControl.png|OpenRadars Camera control panel, controlling one FGFS ORCAM instance]]

This is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via STRG + A (up) and (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''end the follow mode''', click on Follow, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

File:OR Settings FGFS.png

2015-02-28T10:17:08Z

Wagnerw: Wagnerw uploaded a new version of File:OR Settings FGFS.png

=={{int:filedesc}}==
{{Information
|description={{en|1=OpenRadars ORCAM settings page}}
|date=2015-02-28 11:11:24
|source={{own}}
|author=[[User:Wagnerw|Wagnerw]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:OpenRadar screenshots]]

OpenRadar FGFS ORCAM

2015-02-28T10:15:59Z

Wagnerw: /* (3) Configure OpenRadar */

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== (1) Download the aircraft orcam ===
At first you need the flightgear aircraft ''orcam''. That is a modified ATC aircraft. All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable.

Download the file from '''''Todo: URL to ORCAM''''' and extract it to your flightgear Aircraft directory. The same directory that contains all your downloaded aircrafts.

=== (2) Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== (3) Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab for ORCAM.

[[File:OR Settings FGFS.png|thumb|OpenRadars ORCAM settings page]]

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Camera, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

Here is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via STRG + A (up) and (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''end the follow mode''', click on Follow, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

File:OR Settings FGFS.png

2015-02-28T10:12:54Z

Wagnerw: User created page with UploadWizard

File:OR CamControl.png

2015-02-28T10:12:43Z

Wagnerw: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=OpenRadars Camera control panel, controlling one FGFS ORCAM instance}}
|date=2015-02-28 11:11:24
|source={{own}}
|author=[[User:Wagnerw|Wagnerw]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:OpenRadar screenshots]]

OpenRadar FGFS ORCAM

2015-02-28T09:47:42Z

Wagnerw: Added more text

{{WIP}}

== Introduction ==
OpenRadar has got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your view instance of flightgear really invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== (1) Download the aircraft orcam ===
At first you need the flightgear aircraft ''orcam''. That is a modified ATC aircraft. All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable.

Download the file from '''''Todo: URL to ORCAM''''' and extract it to your flightgear Aircraft directory. The same directory that contains all your downloaded aircrafts.

=== (2) Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== (3) Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab:

todo: picture

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
==== One computer ====
This setup uses one flightgear ORCAM instance running (for instance) on the same computer, but on a second monitor (to have it always visible).

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|}
==== Two Computers ====
This setup uses one flightgear ORCAM instance running (for instance) on a separate computer. This helps, if your computers show signs of overload.

{| class="wikitable"
|-
! Computer !! OR Parameter !! FGFS Setting
|-
| computer1 == localhost || <pre>Enable Cam 1: checked
Client host: computer2
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
|| no ORCAM ||
|-
| computer 2 || no OpenRadar ||
<pre>
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,computer1,5010 \
</pre>
|}

=== Two Cameras ===
Running two flightgear instance plus OpenRadar to the same time will be close to too much for your computer. Consider to utilize a second computer running the second flightgear ORCAM instance.

==== Two Computers ====

I assume you have two computers named computer1 (localhost, running the OR instance) and computer2. Replace the symbolic names with your computer names or IP addresses!

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer2 || <pre>Enable Cam 2: checked
Client host: computer2
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,computer1,5020 \
</pre>
|}

==== One, very powerful computer ====

{| class="wikitable"
|-
! Instance !! Computer !! OR Parameter !! FGFS Setting
|-
| ORCAM 1 || computer1 == localhost || <pre>Enable Cam 1: checked
Client host: localhost
FGFS telnet Port: 5010
Enable MP forwarding: checked
FGFS MP Port: 5010
</pre>
||
<pre>

--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
</pre>
|-
| ORCAM 2 || computer1 || <pre>Enable Cam 2: checked
Client host: localhost
FGFS telnet Port: 5020
Enable MP forwarding: checked
FGFS MP Port: 5020
</pre>
||
<pre>

--telnet=,,100,,5020, \
--multiplay=in,100,,5020 \
--multiplay=out,100,localhost,5020 \
</pre>
|}
=== Two Camera, second camera shows same picture like first ===
This example can be used, if you want a second camera that shows the same as the first camera. For instance if you want to record your session.

Configure your OpenRadar like in the example ''Two Computers'' above and check '''Slave to Cam1'''!

This will remove the second cam control line in OR and control CAM2 just like CAM1.

== Usage ==
Once all this is done, you have one or two startup scripts for FGFS ORCAM, can start them easily and you are ready to go.

Here is the camera control line: You see the presets P1 - P5, a possibility to enable and disable the follow mode and on the right side, the link to enable the mode, in which you can define the camera position at your airport.

=== Activate a preset ===
At first startup, the camera will be at the default tower position pointing north. All Presets will be initialized to do so.

To activate a preset, simply click on it. It will restore the saved values: position, angles and zoom.

=== Modifying the view ===
Modifying the camera view is done in flightgear. You can change the '''view angle''' by dragging with the right mouse button pressed.
Try it: Click the right mouse button in flightgear window and move your mouse.

You can '''change the zoom (field of view)''' like you know it from flying via the keys X and SHIFT+X.

And you can move the tower altitude via STRG + A (up) and (down)

=== Save a preset ===
You can save the current setting to a preset by a simple '''right''' click onto it. Left click activates it, right click saves the current view in FGFS ORCAM.

=== Move camera location ===
You also can move the camera location of the current preset, to be able to monitor remote runways or dangerous crossings.

# Enable the preset you want to move
# Move the OR map (zoom), to be able to click, where your camera should be
# Enable the move camera position mode by clicking on '''MoveCam'''. It turns blue to indicate that modus.
# Click on the map, where the camera should be. MoveCam change its color to normal and the FGFS display will move to the new position.
# In FGFS modify your camera view and save it via right click onto the current preset.

=== Follow a contact ===
If there is a contact you want to keep in eye while working with all other contacts, you can tell OR to use FGFS to follow him.

As long as he is in view (6000m), OR will tell FGFS to follow this contact.

OR adapts the zoom factor when you activate the follow mode, later you have to change the Zoom mode via X and SHIFT+X on your own. This was implemented by purpose.

You can change the camera by clicking on the presets in follow mode. The new camera will follow the contact from the new position.

To '''end the follow mode''', click on Follow, while the followed contact is selected.

To '''follow somebody else''', select the new contact and follow him.

== FAQ ==
# ORCAM makes my computer so slow! => FGFS needs big amounts of memory, especially, if you have several contacts in range and if you tuned it to be nice (e.g. if you display many trees). OR needs also some resources especially displaying thousands of dots and the necessary geometric projections take their time. All this might be too much for your computer. FGFS 3.4 brings improvements to FGFS speed and memory consumption, but after all you need a recent computer. Running OR and the single FGFS ORCAM instance on different computers will bring help.

OpenRadar FGFS ORCAM

2015-02-28T08:01:29Z

Wagnerw: First draft

'''WORK IN PROGRESS NOT LIVE YET'''

== Introduction ==
OpenRadar got a new feature lately, that will be published in next update: It can interact with a running Flightgear to make it act like a tower window, or a airport surveillance camera.
That means, with only some minutes of setup, you see the aircrafts moving on the ground, starting and landing. You can define a couple of camera view presets (location, angles and zoom factor) and you can follow a contact as long as he is close to your airport.
For that you should have a second monitor. It should display the Flightgear window, the view out of your tower, while you have OR as your radar view on the main monitor.

'''Forwarding of multiplayer data'''
To avoid that flightgears multiplayer server get plenty of new ATC view only clients, OR got the ability to forward all received MP packets to the view only flightgear instance. It acts like a half MP server, by transmitting what it gets from the server. The packets that the view only flightgear instance sends to OR will not be forwarded to the MP server.
This reduces the load on the MP servers and reduces the bandwidth usage of your internet access, and removes the need for confusing additional pilots in flightgears pilot list. On the other hand, it makes your vieew instance of flightgear realy invisible and makes it impossible to send any data from there to other multiplayers, even while you see them.
This is wanted, as flightgear is reduced to a window to the airport. All actions are done from and in OpenRadar.

== Configuration ==
=== (1) Download the aircraft orcam ===
At first you need the flightgear aircraft ''orcam''. That is a modified ATC aircraft. All that has been added are less lines of code, to be able to disable the aircraft tracking via the interface.
It is not perfect yet, there could still be a pilot list in it and a display, which contact it is following and some controls to move the camera up and down, but it is already pretty usable.

Download the file from '''''Todo: URL to ORCAM''''' and extract it to your flightgear Aircraft directory. The same directory that contains all your downloaded aircrafts.

=== (2) Write a fgfs startup script ===
We suggest that you write a small script file that starts your orcam instance quickly and without effort. You can also couple it into your OpenRadar startup script, if you like to.
The script can look like this:
<pre>
#!/bin/bash --
fgfs
--aircraft=OR-Cam \
--callsign=_ \
--airport=LFSB \
--telnet=,,100,,5010, \
--multiplay=in,100,,5010 \
--multiplay=out,100,localhost,5010 \
--fg-aircraft=/data/fgdata/Aircraft
</pre>

'''The parameters'''
{| class="wikitable"
|-
! parameter !! Note
|-
| --aircraft || This tells fgfs which aircraft to load
|-
| --callsign || The callsign of your view instance. Unimportant for other multiplayers, as you are invisible.
|-
| --telnet || Configures the connection between OpenRadar and Flightgear to exchange data, like setting the camera location and angle, set the contact for follow mode or read the current camera orientation etc.
|-
| --multiplay || flightgears interface to the multiplayer servers, this example is set to send the outgoing data to the computer that runs this flightgear instance. This is, what makes ORCAM invisible.
|-
| --fg-aircraft || An optional parameter to define the location where you store your aircraft, if they are outside of your flightgear installation directory. You can omit it.
|}
Note: You may add all other flightgear parameters too. This is an example only.

It is a good practice to start this flightgear instance before you start OpenRadar, because flightgear initializes the view position based on its tower data, often starting inside buildings.
OpenRadar will restore the first camera preset at start, healing this.

=== (3) Configure OpenRadar ===
The known startup dialog of OpenRadar has got a new tab:

todo: picture

These settings define the other, controlling side of the setup.
{| class="wikitable"
|-
! Field !! Example !! Content
|-
| Checkbox Enable FGFS Cam Control || checked || Main switch, turns camera control line in OpenRadar on or off
|-
| Client host || localhost || Computername or IP address of the computer running FGFS OR Cam
|-
| FGFS telnet port || 5010 || the TCP port, defined by the <code>--telnet</code> parameter in the FGFS startup script above
|-
| Checkbox Enable MP forwarding || checked || Turns forwarding of multiplayer packets to the view only FGFS instance on.
|-
| FGFS MP Port || 5010 || The UDP Port of flightgear that will receive the forwarded multiplayer packets.
|}

These settings exist two times, prepared to enable a second window to the airport. (WARNING: You might need a strong computer!)

== Setups ==
=== One Camera ===
=== Two Cameras ===
=== Two Camera, second camera shows same picture like first ===
== Usage ==
=== Save and enable a preset ===
=== Move camera location ===
=== Follow a contact ===
== FAQ ==

OpenRadar

2015-02-28T06:49:54Z

Wagnerw: /* Related content */

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease = Nov, 18th 2012
| latestrelease = Jan, 31st 2015
| writtenin = Java
| os = Linux, Windows, Mac
| platform =
| developmentstatus = active
| type =
| license =
| website = http://www.gitorious.org/fg/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadar_FGFS_ORCAM|OR-CAM: Your window to the the airport]]

* [[OpenRadarDownload|'''Download'''! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadarKnownIssues|'''FAQ''' / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:OpenRadar| ]]

OpenRadarFeatureWishlist

2015-01-31T08:15:53Z

Wagnerw: Removed implemented or outdated text

[[OpenRadar| Back to mainpage]]

This page collects the feature proposals for [[OpenRadar]].

== General ==
* (by design) Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10
:(comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]])
::Well this should be fixed. What if multiple controllers control with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST)
* Wider radar range for CTR controllers (FGCom radio & visibility range)
:ww:I need to validate, but to my current knowledge, FGCOM is restricted on server side and the contact visibility by the MP server. I thought already about a special mode for CTR, that registers OR as MP server (proxy). Then it would get all contacts worldwide. For FGCOM we could add these special frequencies to the list of frequencies that are available everywhere at the FGCOM server.
* Controlling multiple airports (CTR controller)
:ww: To be able switch some features from airport to airport (METAR, runways, FGCOM, StdRoutes) I need to rework some parts of the application (relocation of OR multiplayer client to new airport, loading of different METAR, runways, routes etc). It would work like an hopping from airport to airport. Something for future releases, I think.
* ATIS recording feature
:ww: Recording and then replay over the ATIS frequency? This might be possible.
::mc: Yes. compare with VRC (VatSim Virtual Radar Client), which has a recording option and EuroScope which does generate if from recorded fragments. - Text to speech (Espeak/Festival) integration would be the "tripple-A" feature!1!! ;)
* Give the fullname of a VOR when going over it with the cursor (MLN = Melun, LGL = L'Aigle) as ATC and pilot use also VOR names in real life. (Do the same for Airports and NDB?)
:ww: technically possible, but tooltips disturb usability very much. Please open a thread in forum and discuss is with the users!
* Traffic counter

== Aircraft/Pilot Flag ==
* See assigned flightlevel (according to flightplan)

== METAR ==
* METAR of nearby airports => right click on the METAR lines and define them.

== Messages ==

== Radar Map ==
* separation rings (1000ft in vertical and 500ft in horizontal distance)
* alerts for collision and speed violations
* additional deselect button below the map
* (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas

== Route Editing ==
* Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?)

== FGCom Integration ==
* Add "set PTT shortcut key" feature
* Change volume of fgcom channel

== ATC Coordination ==
* coordinate multiple instances of OpenRadar using a protocol a la VatSim (ww: this will work only for OpenRadar instances, not to ATC-ML, ATC-TOWER etc...)
* (mp data) see what frequencies other ATC's are using
:ww: I transmit the first frequency via FGCOM protocol, but do not display it yet, because the FG frequencies are set to a fix value.
* Hand-off feature
:* (mp data) See to which frequency the Pilot is connected to (com1 & com2)
::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background)
:* See on the map what regions are "controlled" by who (dark grey if an area is controlled, so the ATC knows to whom he can do the handoff)

== Missing/incomplete FG MP protocol data ==
* '''Active''', tuned in '''frequency''' (COM1/COM2): the '''tuned-in COM frequencies''', there is one for COM1, but it is not implemented, it delivers no data
* MP Chat Unicode support
* MP Chat private message support

[[Category:OpenRadar|FeatureWishlist]]

OpenRadarKnownIssues

2015-01-31T08:06:54Z

Wagnerw: /* Known Issues */

OpenRadarDownload

2015-01-31T08:05:20Z

Wagnerw: /* First start */

[[OpenRadar| Back to mainpage]]

At first the most important: We publish early to give you influence on the final application.

== Installation of [[OpenRadar]] ==

=== Download ===
# Download the zip file from [http://wagnerw.de/OpenRadar.zip here] ([[OpenRadar_Change_Log|Change Log]])
# Extract the content to a place where it is easy to find
# If your former version had a 'settings' folder, please copy the 'xml' and 'properties' files into the new extracted settings folder (all but the defaults.properties: user.properties contains your inputs in settings dialogue, atcComments.xml contains the text on the flight strips, the airport property files your centerline/radio frequency settings of the airport, the content of sub folder ATCmsg contains the templates for the automatic ATC messages, copy it only, if you have adapted it!)

=== Dependencies ===
# You need a recent Java installed (at least Java Runtime Environment 1.7)

== First start ==
Depending on how good your Java is integrated into your OS, you can make a double click onto OpenRadar.jar, start one of the provided helper batch files or you have to start it manually.
In worst case: Open a console, change to the OpenRadar directory and type '''java -jar OpenRadar.jar'''.

At first start you have to define the settings. The settings are pre-set, but please check them!

===Notes to FGCom===

FGCom is a very useful part of software. Who has time to write chat message while flying? Speaking is easier and much more realistic.

You have four choices to define how much FgCom should be used by OpenRadar:

=====First: AUTO use the OR internal setup=====
If you choose this mode, you only have to provide the name of your fgcom server and one or several local ports. Each port will produce one radio in OR. You can have up to four radios, but more than 2 is not advised.
Use this mode if possible!

=====Second: Internal integrated=====
This is a possibility, if the first does not work for you:
Download the fgcom zip for your platform from here: [http://fgcom.flightgear.org/download/] and extract it to a place where you find it later.

After download and extraction set the path to the FGCom executable on settings tab to something like
{| class="wikitable"
|-
| Path || /home/USERNAME/fgcom/bin
|-
| Executable Windows: || fgcom.exe
|-
| Executable Linux: ||fgcom or fgcom.exe (uses wine)
|}
OpenRadar will use these settings to start fgcom.

You also need the following fields:
{| class="wikitable"
|-
| Server || the fgcom voip server to be contacted, e.g. fgcom.flightgear.org
|-
| Portlist || define one UDP port per fgcom instance you want to use (comma separated), e.g. 16661,16662
|}

=====Third: Control an external FgCom instance:=====
You can also start FGCom externaly and let OpenRadar control it. This can be used to separate OpenRadar and FgCom running on different computers. FgCom must be installed and extracted first:
Download the fgcom zip for your platform from here: [http://fgcom.flightgear.org/download/] and extract it to a place where you find it later.

To run FgCom externally, open one console per Radio, you want to use, change into the fgcom directory and start fgcom with someting like:
{| class="wikitable"
|-
| fgcom.exe --port=16661 -Sfgcom.flightgear.org
|}
Use different port numbers, one per instance and maintain them on settings tab as coma separated list!

In this scenario you also have to define the computer (client) running the fgcom instance. This enables you, to separate fgcom to run on a separate machine.
{| class="wikitable"
|-
| Client || the machine running the fgcom instance, most of the times 'localhost'
|}

OpenRadar will try to contact this instance using the port numbers you have defined here and on the settings tab.
You can also use FgComGui instead: You will have to set the ports in its Settings dialog.

=====Fourth: Off=====
You can decide, not to use FgCom. If so, some predefined ATC messages need manual correction because they refer to FgCom frequencies.

===Airport download===
Next step is the download of the surroundings around the airport you want to control. Please follow the instructions in A guide to OpenRadar!

== Shortcuts ==
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|-
| '''F1''' || Zoom Level GROUND
|-
| '''F2''' || Zoom Level TOWER
|-
| '''F3''' || Zoom Level APP
|-
| '''F4''' || Zoom Level SECTOR
|-
| '''SHIFT+F12''': || Reload and update standard route definitions (for development)
|}

== Questions/Help/Issues ==
I try to collect known issues tips and tricks on this page and [[OpenRadarKnownIssues|here]].
Please check if I have provided a new version of the binary release in meantime. Maybe your issue is gone.

Last but not least: Please be positive and give constructive feedback. Which features are useful, which should be changed, what is really missing. Target should be to have a reliable, handy tool, not an potentially really useful, but overloaded and buggy everlasting prototype.

== Developers ==
If you are a developer, please contact us (Ralf and Wolfram) before you start to help us. Currently the code is still changing heavily and there are some places that are not stable.
Maybe single needed files may miss in GIT, please tell us, if you miss something!

[[Category:OpenRadar|Download]]

OpenRadarDownload

2015-01-31T07:51:28Z

Wagnerw: Removed reference to improved older version. FGCom is delivered with OR now...

[[OpenRadar| Back to mainpage]]

At first the most important: We publish early to give you influence on the final application.

== Installation of [[OpenRadar]] ==

=== Download ===
# Download the zip file from [http://wagnerw.de/OpenRadar.zip here] ([[OpenRadar_Change_Log|Change Log]])
# Extract the content to a place where it is easy to find
# If your former version had a 'settings' folder, please copy the 'xml' and 'properties' files into the new extracted settings folder (all but the defaults.properties: user.properties contains your inputs in settings dialogue, atcComments.xml contains the text on the flight strips, the airport property files your centerline/radio frequency settings of the airport, the content of sub folder ATCmsg contains the templates for the automatic ATC messages, copy it only, if you have adapted it!)

=== Dependencies ===
# You need a recent Java installed (at least Java Runtime Environment 1.7)

== First start ==
Depending on how good your Java is integrated into your OS, you can make a double click onto OpenRadar.jar or you have to start it manually.
Open a console, change to the OpenRadar directory and type '''java -jar OpenRadar.jar'''.

At first start you have to define the settings. The settings are pre-set, but please check them!

===Notes to FGCom===

FGCom is a very useful part of software. Who has time to write chat message while flying? Speaking is easier and much more realistic.

But the installation on Linux systems can be a bit tricky. At least for me. Maybe someone volunteers to clean this up a bit.

You have three choices to define how much FgCom should be used by OpenRadar:
=====First: Full integrated=====
If you use Linux and have troubles to install FGCom, please download the pre-compiled zipped Windows package [http://code.google.com/p/fgcomgui/downloads/list], extract it and simply use wine to run FGCom.
This is simple and it works for me.

After download and extraction set the path to the FGCom executable on settings tab to something like
{| class="wikitable"
|-
| Path || /home/USERNAME/bin/fgcomgui-win32-bundle-01192010/
|-
| Executable Windows: || fgcom.exe
|-
| Executable Linux: ||fgcom or fgcom.exe (uses wine)
|}
OpenRadar will use these settings to start fgcom.

You also need the following fields:
{| class="wikitable"
|-
| Server || the fgcom voip server to be contacted, e.g. delta384.server4you.de
|-
| Portlist || define one UDP port per fgcom instance you want to use (comma separated), e.g. 16661,16662
|}

=====Second: Control an external FgCom instance:=====
You can also start FGCom externaly and let OpenRadar control it.

To run FgCom externally, open one console per Radio, you want to use, change into the fgcom directory and start fgcom with someting like:
{| class="wikitable"
|-
| fgcom.exe --port=16661 -Sdelta384.server4you.de
|}
Use different port numbers, one per instance and maintain them on settings tab as coma separated list!

In this scenario you also have to define the client running the fgcom instance. This enables you, to separate fgcom to run on a separate machine.
{| class="wikitable"
|-
| Client || the machine running the fgcom instance, localhost
|}

OpenRadar will try to contact this instance using the port numbers you have defined here and on the settings tab.
You can also use FgComGui instead: You will have to set the ports in its Settings dialog.

=====Third: Off=====
You can decide, not to use FgCom. If so, some predefined ATC messages need manual correction because they refer to FgCom frequencies.

===Airport download===
Next step is the download of the surroundings around the airport you want to control. Please follow the instructions in A guide to OpenRadar!

== Shortcuts ==
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|-
| '''F1''' || Zoom Level GROUND
|-
| '''F2''' || Zoom Level TOWER
|-
| '''F3''' || Zoom Level APP
|-
| '''F4''' || Zoom Level SECTOR
|-
| '''SHIFT+F12''': || Reload and update standard route definitions (for development)
|}

== Questions/Help/Issues ==
I try to collect known issues tips and tricks on this page and [[OpenRadarKnownIssues|here]].
Please check if I have provided a new version of the binary release in meantime. Maybe your issue is gone.

Last but not least: Please be positive and give constructive feedback. Which features are useful, which should be changed, what is really missing. Target should be to have a reliable, handy tool, not an potentially really useful, but overloaded and buggy everlasting prototype.

== Developers ==
If you are a developer, please contact us (Ralf and Wolfram) before you start to help us. Currently the code is still changing heavily and there are some places that are not stable.
Maybe single needed files may miss in GIT, please tell us, if you miss something!

[[Category:OpenRadar|Download]]

OpenRadarDownload

2015-01-31T07:50:24Z

Wagnerw: /* Installation of OpenRadar */

[[OpenRadar| Back to mainpage]]

At first the most important: We publish early to give you influence on the final application.

== Installation of [[OpenRadar]] ==

=== Download ===
# Download the zip file from [http://wagnerw.de/OpenRadar.zip here] ([[OpenRadar_Change_Log|Change Log]])
* (Former version, FGCOM is already integrated into OR now. : Pre-configured integration with FGCom for Windows: [http://www.abyssfusion.tk/openradar/ OpenRadar.zip] (No need to configure for FGCom, it will run together automatically. View "readme.txt" for more information.)
# Extract the content to a place where it is easy to find
# If your former version had a 'settings' folder, please copy the 'xml' and 'properties' files into the new extracted settings folder (all but the defaults.properties: user.properties contains your inputs in settings dialogue, atcComments.xml contains the text on the flight strips, the airport property files your centerline/radio frequency settings of the airport, the content of sub folder ATCmsg contains the templates for the automatic ATC messages, copy it only, if you have adapted it!)

=== Dependencies ===
# You need a recent Java installed (at least Java Runtime Environment 1.7)

== First start ==
Depending on how good your Java is integrated into your OS, you can make a double click onto OpenRadar.jar or you have to start it manually.
Open a console, change to the OpenRadar directory and type '''java -jar OpenRadar.jar'''.

At first start you have to define the settings. The settings are pre-set, but please check them!

===Notes to FGCom===

FGCom is a very useful part of software. Who has time to write chat message while flying? Speaking is easier and much more realistic.

But the installation on Linux systems can be a bit tricky. At least for me. Maybe someone volunteers to clean this up a bit.

You have three choices to define how much FgCom should be used by OpenRadar:
=====First: Full integrated=====
If you use Linux and have troubles to install FGCom, please download the pre-compiled zipped Windows package [http://code.google.com/p/fgcomgui/downloads/list], extract it and simply use wine to run FGCom.
This is simple and it works for me.

After download and extraction set the path to the FGCom executable on settings tab to something like
{| class="wikitable"
|-
| Path || /home/USERNAME/bin/fgcomgui-win32-bundle-01192010/
|-
| Executable Windows: || fgcom.exe
|-
| Executable Linux: ||fgcom or fgcom.exe (uses wine)
|}
OpenRadar will use these settings to start fgcom.

You also need the following fields:
{| class="wikitable"
|-
| Server || the fgcom voip server to be contacted, e.g. delta384.server4you.de
|-
| Portlist || define one UDP port per fgcom instance you want to use (comma separated), e.g. 16661,16662
|}

=====Second: Control an external FgCom instance:=====
You can also start FGCom externaly and let OpenRadar control it.

To run FgCom externally, open one console per Radio, you want to use, change into the fgcom directory and start fgcom with someting like:
{| class="wikitable"
|-
| fgcom.exe --port=16661 -Sdelta384.server4you.de
|}
Use different port numbers, one per instance and maintain them on settings tab as coma separated list!

In this scenario you also have to define the client running the fgcom instance. This enables you, to separate fgcom to run on a separate machine.
{| class="wikitable"
|-
| Client || the machine running the fgcom instance, localhost
|}

OpenRadar will try to contact this instance using the port numbers you have defined here and on the settings tab.
You can also use FgComGui instead: You will have to set the ports in its Settings dialog.

=====Third: Off=====
You can decide, not to use FgCom. If so, some predefined ATC messages need manual correction because they refer to FgCom frequencies.

===Airport download===
Next step is the download of the surroundings around the airport you want to control. Please follow the instructions in A guide to OpenRadar!

== Shortcuts ==
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|-
| '''F1''' || Zoom Level GROUND
|-
| '''F2''' || Zoom Level TOWER
|-
| '''F3''' || Zoom Level APP
|-
| '''F4''' || Zoom Level SECTOR
|-
| '''SHIFT+F12''': || Reload and update standard route definitions (for development)
|}

== Questions/Help/Issues ==
I try to collect known issues tips and tricks on this page and [[OpenRadarKnownIssues|here]].
Please check if I have provided a new version of the binary release in meantime. Maybe your issue is gone.

Last but not least: Please be positive and give constructive feedback. Which features are useful, which should be changed, what is really missing. Target should be to have a reliable, handy tool, not an potentially really useful, but overloaded and buggy everlasting prototype.

== Developers ==
If you are a developer, please contact us (Ralf and Wolfram) before you start to help us. Currently the code is still changing heavily and there are some places that are not stable.
Maybe single needed files may miss in GIT, please tell us, if you miss something!

[[Category:OpenRadar|Download]]

OpenRadar

2015-01-31T07:46:04Z

Wagnerw: Changed release date

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease = Nov, 18th 2012
| latestrelease = Jan, 31st 2015
| writtenin = Java
| os = Linux, Windows, Mac
| platform =
| developmentstatus = active
| type =
| license =
| website = http://www.gitorious.org/fg/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadarDownload|Download! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadarKnownIssues|FAQ / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:OpenRadar| ]]

OpenRadar Change Log

2015-01-31T07:41:56Z

Wagnerw: Updated headings for release

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update ==
-n/a-

== Published updates ==

=== OpenRadar updates 2015-01-31 ===

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
* small weather icon displays the flight conditions around the airport (start and landing): VFR,MVFR,IFR,LIFR

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadar Change Log

2015-01-31T07:02:25Z

Wagnerw: Added weather symbols as change

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update COMMING SOON ==

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
* small weather icon displays the flight conditions around the airport (start and landing): VFR,MVFR,IFR,LIFR

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

== Published updates ==

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadar Change Log

2015-01-02T10:49:40Z

Wagnerw: Added new features for next release

[[OpenRadar| Back to mainpage]]

{{TOC limit|2}}

== Next update COMMING SOON ==

* call sign can be set before OR is launched
* chat history can be re-used via up and down keys
* contact tails are back (flight history marks)
* better handling of map data issues
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)

* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan

* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.

* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements

== Published updates ==

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]

OpenRadarDownload

2015-01-02T10:28:57Z

Wagnerw: /* Download */

[[OpenRadar| Back to mainpage]]

At first the most important: We publish early to give you influence on the final application.

== Installation of [[OpenRadar]] ==

=== Download ===
# Download the zip file from [http://wagnerw.de/OpenRadar.zip here] (Version from 2014-05-18, [[OpenRadar_Change_Log|Change Log]])
## Pre-configured integration with FGCom for Windows: [http://www.abyssfusion.tk/openradar/ OpenRadar.zip] (No need to configure for FGCom, it will run together automatically. View "readme.txt" for more information.)
# Extract the content to a place where it is easy to find
# If your former version had a 'settings' folder, please copy the 'xml' and 'properties' files into the new extracted settings folder (all but the defaults.properties: user.properties contains your inputs in settings dialogue, atcComments.xml contains the text on the flight strips, the airport property files your centerline/radio frequency settings of the airport, the content of sub folder ATCmsg contains the templates for the automatic ATC messages, copy it only, if you have adapted it!)

=== Dependencies ===
# You need a recent Java installed (Java Runtime Environment 1.7)
# We recommend to install [[FGCom]]

== First start ==
Depending on how good your Java is integrated into your OS, you can make a double click onto OpenRadar.jar or you have to start it manually.
Open a console, change to the OpenRadar directory and type '''java -jar OpenRadar.jar'''.

At first start you have to define the settings. The settings are pre-set, but please check them!

===Notes to FGCom===

FGCom is a very useful part of software. Who has time to write chat message while flying? Speaking is easier and much more realistic.

But the installation on Linux systems can be a bit tricky. At least for me. Maybe someone volunteers to clean this up a bit.

You have three choices to define how much FgCom should be used by OpenRadar:
=====First: Full integrated=====
If you use Linux and have troubles to install FGCom, please download the pre-compiled zipped Windows package [http://code.google.com/p/fgcomgui/downloads/list], extract it and simply use wine to run FGCom.
This is simple and it works for me.

After download and extraction set the path to the FGCom executable on settings tab to something like
{| class="wikitable"
|-
| Path || /home/USERNAME/bin/fgcomgui-win32-bundle-01192010/
|-
| Executable Windows: || fgcom.exe
|-
| Executable Linux: ||fgcom or fgcom.exe (uses wine)
|}
OpenRadar will use these settings to start fgcom.

You also need the following fields:
{| class="wikitable"
|-
| Server || the fgcom voip server to be contacted, e.g. delta384.server4you.de
|-
| Portlist || define one UDP port per fgcom instance you want to use (comma separated), e.g. 16661,16662
|}

=====Second: Control an external FgCom instance:=====
You can also start FGCom externaly and let OpenRadar control it.

To run FgCom externally, open one console per Radio, you want to use, change into the fgcom directory and start fgcom with someting like:
{| class="wikitable"
|-
| fgcom.exe --port=16661 -Sdelta384.server4you.de
|}
Use different port numbers, one per instance and maintain them on settings tab as coma separated list!

In this scenario you also have to define the client running the fgcom instance. This enables you, to separate fgcom to run on a separate machine.
{| class="wikitable"
|-
| Client || the machine running the fgcom instance, localhost
|}

OpenRadar will try to contact this instance using the port numbers you have defined here and on the settings tab.
You can also use FgComGui instead: You will have to set the ports in its Settings dialog.

=====Third: Off=====
You can decide, not to use FgCom. If so, some predefined ATC messages need manual correction because they refer to FgCom frequencies.

===Airport download===
Next step is the download of the surroundings around the airport you want to control. Please follow the instructions in A guide to OpenRadar!

== Shortcuts ==
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|-
| '''F1''' || Zoom Level GROUND
|-
| '''F2''' || Zoom Level TOWER
|-
| '''F3''' || Zoom Level APP
|-
| '''F4''' || Zoom Level SECTOR
|-
| '''SHIFT+F12''': || Reload and update standard route definitions (for development)
|}

== Questions/Help/Issues ==
I try to collect known issues tips and tricks on this page and [[OpenRadarKnownIssues|here]].
Please check if I have provided a new version of the binary release in meantime. Maybe your issue is gone.

Last but not least: Please be positive and give constructive feedback. Which features are useful, which should be changed, what is really missing. Target should be to have a reliable, handy tool, not an potentially really useful, but overloaded and buggy everlasting prototype.

== Developers ==
If you are a developer, please contact us (Ralf and Wolfram) before you start to help us. Currently the code is still changing heavily and there are some places that are not stable.
Maybe single needed files may miss in GIT, please tell us, if you miss something!

[[Category:OpenRadar|Download]]

OpenRadar

2015-01-02T10:28:12Z

Wagnerw:

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar Prototype.png
| alt = Frankfurt Airport (EDDF)
| developedby = Wolfram Wagner (Ralf Gerlich)
| initialrelease =
| latestrelease = May, 18th 2014
| writtenin = Java
| os =
| platform =
| developmentstatus = active
| type =
| license =
| website = http://www.gitorious.org/fg/openradar/
}}
[[File:OpenRadar_KSFO_large.png|thumb|270px|San Francisco bay area(historical)]]
[[File:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]](historical)]]

'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.
It supports Multiplayer Chat and multiple FGCom frequencies.

Please read the [[OpenRadarGuide| Guide to OpenRadar]]!

== Main Features ==
* ''Radar:''
:* Display of radar contacts
:* Highlighting of the selected contact, controlled and interesting contacts
:* Contacts can be neglected
:* Display of radar contact base data on screen
:* Airports including runway numbers, alignment lines, extended center lines, vectoring help and baselines
:* Navaids (FIX, NDB, VOR) toggle
:* Navaid search
:* Possibility to convert/define STARs and SIDs
:* Distance circles around airport
:* Ground net including parking positions
:* Free definable zoom levels (Ground, Tower, App, Sector), mouse wheel works additional (zoom level and centers is saved)
:* Zoom depending detail visibility (runway numbers close to ground, airways visible from further away)
* ''Multiplayer Chat''
:* Filter on selection and visibility
:* ''Automated multilanguage text handling like ATC-ML'' (The same texts are available, Live data is included into messages): Click on flight strip, choose message, add details and send the message in English and in one additional language, defined on per contact base
* ''FGCom'' Integration (multiple radios in parallel), PTT Button, FGCom started by OpenRadar in background
* ''Weather'' (Metar) Download and display (wind, air pressure, visibility)
* ''Runway display'' is using Metar information (magn. heading,length, width, cross wind stength, ILS frequency)
* Compensation of wind and magnetic declination
* Radar contacts displayed on ''Flight Strips''
:* Flight Strips can be ordered manual in sequence and arranged in list (3 columns)
:* Automatic ordering available
:* Comment editor to make notes on Flight Strips
* ''Transponder/Squawking''
:* Compatible to FGFS Git implementation (generic transponder in radio dialog)
:* Optional usable
:* Define a squawk code range
:* Assign a squawk code to a contact
:* Revoke a squawk code from a contact to release the contact out of control
* ''SetupDialog''
:* Search airports
:* Download new airport shape files from scenery database
:* Edit settings
:* Main switches to tweak OR (available inside OR via map menu

== Current state ==
[[OpenRadarDownload| Latest binary release download]]

== System requirements ==
OpenRadar is no application for a small, a weak computer without graphic acceleration. We need to handle a lot of data, perform permanent Geo to Map projections and display them on the screen, while you
are shifting the map.
And believe me, a small screen is bad for the eyes and your neck muscles :-)

* a screen wide enough to display everything (22'' can show about 20 radar contacts, with two radios and two runways active, if you control a small airport with less runways, 18'' should be minimum)
* a Java Runtime Environment 1.7.0 e.g. OpenJDK
* [[FGCom]] really recommended
* a rather good network connection (FGCom is a VoIP application and FG transmits data as UDP packages, they can get lost over a weak connection)

== Related content ==
* [[OpenRadarGuide|A guide to OpenRadar]]
* [[OpenRadar: Transponder|Transponder support]] How to use squawk codes (requires contacts with a recent fgfs)
* [[OpenRadar: Chat aliases|Chat Aliases]] Use aliases instead of the chat menu...
* [[OpenRadarDownload|Download! I want to try it!]], [[OpenRadar Change Log|Change Log]]
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadarKnownIssues|FAQ / Known Issues]]
* Please add your feature proposals to [[OpenRadarFeatureWishlist|this page]]!

[[Category:Air Traffic Control]]
[[Category:Java]]
[[Category:OpenRadar| ]]

OpenRadar: Editing routes

2014-12-27T09:09:52Z

Wagnerw: /* Elements: Added include tag to include route elements into another route */

[[File:EDDF-Triangle-OpenRadar.png|right|300px|thumb|EDDF with procedures, routes and additional information.]]
[[OpenRadar| Back to mainpage]]

== About ==
You can define standard routes to OpenRadar. This can be done by converting a NavaidDB file and improve the result or define it from scratch by adding lines, curves and bows to the radar screen.
So you can define waiting loops, STARs and SIDs if you want to and if you need them.

Please send your finished work in to include it into the next OpenRadar update for everybody.

To have an example, check out airport LFSB. It is our showcase in this matter.

Please be warned: Defining all approaches and procedures for a more complex airport may produce too much details to work with. Concentrate on the important things, like additional vectors or waiting rooms.

A collection of possibilities:
* Highlight only the navaids that you need to see
* Create only the holding areas
* Create the Approaches to appear on a higher viewpoint and the STAR/SID routes on lower viewpoints
* Use texts to have the taxiways names in the map at the best spot (hide them on higher viewlevels)
* Use texts to have the maximum speed in the map
* Create only the most important routes, or
* Create all standard STAR and SID routes

== Guidelines ==
To avoid that everyone develops his own standards, we need to agree to common standards.

=== Display Modes ===
The route attribute displayMode can have different values:
{| class="wikitable"
|-
! displaymode !! Description
|-
| always ||These routes are always displayed. You cannot switch them off using the STAR/SID switch.
That means that you can use them to enrich the map itself: For forbidden areas or areas that require a minimum height... or for instance to add the names for taxiways to the map.
|-
| optional || This route will be hidden when you switch off START/SID.
You can use it for any route specific elements, that are not related to a specific runway.
|-
| sid / star || These values mark a route as sid/star. In future we might want to select a sid/star from a list. To be able to do that, we need to know which routes we need to display.
|}
So please follow these simple guidelines:
# Define one route per SID/STAR and design it, that it can be displayed individually, everything else switched off
# Mark these routes with the correct ''displayMode''
# Use the official STAR/NAME as route name, we will use it for display

=== Content ===
==== Airport local data ====
-- to be added--

==== Data shared between airports ====
Should be in a directory with a name describing the region. The airport xml files can incorporate these definitions via include xml element.
-- to be added--

=== Coloring ===
-- to be added--

== Generating the OpenRadar definitions from existing ProceduresDB file ==

WARNING: Known issues: There is an major issue when reading the procedure file, in the current version. I will fix it soon, but it requires to implement more functionality to define standard routes... I will need some time to do that.
'''Until this feature works, it is disabled in the published versions of OR.'''

There is already an XML format that contains the STARs and SIDs. Converting it can save you some work.

We do not use it directly because:
* These data are not free
* It purpose it to provide input for the autopilot/flight manager, not for an ATC screen
* Our format is made to display the important information which an ATC needs:
:*adaptive detail (you can define the lower and upper zoom level values between the route is being displayed)
:*display of STARs and SIDs can depend on the runway usage mode
:*colors (each route, each element can have its own color), strokes and line width
:*more graphical elements curves, bows and text
:*NAVAID hightlighting

The SID/STAR xml files can be bought and downloaded for a few bucks from [http://navigraph.com Navigraph]. Generally FlightGear looks for them in a Airports/I/C/A/ICAO.procedures.xml (where ICAO is an airport). For example, the procedures file for ELLX, if it exists, is under Airports/E/L/L/ELLX.procedures.xml.

OpenRadar can also read these XML files. For that:
* create the directory OpenRadar/data/routes/ICAO (where ICAO is the code of the airport you want to use)
* put your procedure XML (named ICAO.procedures.xml) into it
* start OpenRadar at your airport (ICAO), you now have a converted file ICAO.procedures.or.xml in the OpenRadar/data/routes/ICAO directory
* exit OpenRadar : the original file is not needed anymore after this step (move it somewhere else if you want)
* rename your ICAO.procedures.or.xml file to ICAO.procedures.xml

Now when restarting OpenRadar, the converted routes are available. You can and should modify the new file following the explanations below.

== Manual creation / refinement ==
The '''most important''' first:
*'''SHIFT+F12''' reloads the standard routes of your current airport. So you can see changes quickly...
*'''F12''' determines the geo position of your mouse tip and copies it to your clipboard. So you can easily place points: Place mouse pointer in OR map at the spot that you need, hit F12, change to your XML file, place the cursor, at the right spot and paste the clipboard. SHIFT+F12 will reload your work for verification...
*'''CTRL+F12''' determines the current zoom level and copies it to your clipboard. So you can easily set the zoom levels for your routes: Set the desired zoom level in OR map, hit CTRL+F12, change to your XML file, place the cursor, at the right spot and paste the clipboard. SHIFT+F12 will reload your work for verification...

The files must be located in directory data/routes/[airport name].

The files must end with ".xml", so they must be xml documents. Here is a simple example of everything around your route definitions:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
--- here are your definitions ---
</routes>
</syntaxhighlight>

=== A Route ===
A route is a collection of definitions that belong together. The values zoomMin and zoomMax allow you to define adaptive details or layers of information that appear within those constraints. Omitting them means there is no constraint at this side...

A route can have the following attributes:
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| name || {{no}} || A meaningful name for this route
|-
| zoomMin || {{yes}} || The minimum zoom level at which this route is being displayed. If you zoom in more, it disappears. (default values: Ground: 14, Tower: 26, App: 100)
|-
| zoomMax || {{yes}} || The maximum zoom level at which this route is being displayed. If you zoom out more, it disappears. (default values: Ground: 14, Tower: 26, App: 100)
|-
| displayMode || {{no|(No)}} || Controls how the different switches work for this route:
*"always": route is displayed always
*"optional": routes is displayed independently from the runways, but STAR/SID switch turns it off
*"sid": This route is a SID, its name is the official id, enabling the SID checkbox in runway panel displays it, and the STAR/SID main switch toggles it
*"star": This route is a STAR, its name is the official id, enabling the STAR checkbox in runway panel displays it, and the STAR/SID main switch toggles it
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| color || {{yes}} || Defines the color of the elements of this route. Use it carefully and rarely. You still want to be able to read the most important information on the radar: The contacs position info....
|}

Supported are the following xml tags:
{| class="wikitable"
|-
! Tag !! Opt. !! Description
|-
| activeStartRunways || {{yes}} || A comma separated list of runways. If one of them is active for '''starts''' the route will be displayed.
|-
| activeLandingRunways || {{yes}} || A comma separated list of runways. If one of them is active for '''landings''' the route will be displayed. If neither activeStartRunways nor activeLandingRunways is defined, the route will always be displayed. Use this for parking rooms...
|-
| navaids || {{yes}} || A comma separated list of navaid ids (FIX, NDB, VOR, Airportcodes) that will be highlighted if this route is being displayed, regardless if the main switches for FIX/NDB etc. are enabled or not.
This tag can have an attribute <code>color</code> that defines the color for the navaids in RGB values. Example: color="120,140,120"
There can be multiple instances of this element having different colors assigned.
|-
| (other elements) || {{yes}} || The graphical tags explained below
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>
--- more to be explained ---
</route>
</routes>
</syntaxhighlight>

=== Route features ===
==== Zoomlevel ====
Use the Attributes <code>zoomMin</code> and <code>zoomMax</code> to define a range in which a route is being displayed. So you can separate routes interesting for APP zoom level from details on tower level.

==== Navaid coloring ====
Both routes and navaids can have a <code>color</code> attribute defined. The rules which one is displayed are:
# If navaids block has no color defined, the route's color is being used.
# If route's block has no color defined, a default color will be used.
# Navaids are highlighted only, if the route is being displayed (zoom level, active start/landing runway)
# If a navaid is used in more than one visible route:
:# The color of a static route (no runway conditions) has highest priority (zoomLevel is respected only, to check if it is displayed at all)
:# Then follows the color attribute of the current navaids block, if defined.
:# Then follows the color attribute of the current route block, if defined, its default color otherwise.

Navaids used in many routes are of somewhat importance and should get their own static route and a separate color as hotspots.
In conflict case, the color, that is found first, wins.

=== Points and Angles ===
All elements of your route base on points and angles. '''Angles''' are magnetic and defined in degrees.

'''Points''' on your radar can be defined:
{| class="wikitable"
! Point !! Description
|-
| Navaid || You can use the navaid ID, e.g begin="BLM"
|-
| Runway end || You can use any runway end of the current airport. e.g. Runway 15 at Basel: begin="'''LFSB'''-RW'''15'''"
|-
| Geographic Location || You can use the geographic location separated by a comma. e.g. <pre>begin="47.599450,7.531936", begin="N47°57'51'',E7°54'58''" or begin="N47°57.2',E7°54.10'"</pre>
|-
| Relative Location || You can define a point relative to a navaid in the format: dddNMaaa@iii (where ddd is the decimal distance in NM, aaa is the magnetic bearing from iii, which is a navaid id. Distance and heading have the decimal separator 'dot'.
e.g. "2.5NM165@BLM"
|}
'''Length'''' are also given in decimal NM.

'''Missing Navaids:'''

If you notice that some navaids are not available in OpenRadar's data, you can use their geographic positions, or better define them in your route file.
These additional definitions can be used like navaids defined in the AptNav files...
A useful misuse of this feature is to produce highlighting-enabled route texts: Define the text as addPoint and reference it in a routes navaid block.
Please remember, very likely your clients will not have them visible in their inflight map...

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| code || {{yes}} || The ID under that your want to find it. Try to use non existing to avoid conflicts
|-
| point || {{yes}} || The geographic coordinates of the point.
|}

Examples:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<addPoint code="AGOLO" point="50.200000,9.676111"/>
<addPoint code="BIBTI" point="50.966667,7.108611"/>
<addPoint code="ESUPI" point="50.058333,8.121111"/>
<addPoint code="FRD" point="50.030556,8.566944"/>
<addPoint code="IBVIL" point="50.434444,7.369167"/>
<addPoint code="KERAX" point="50.475000,9.581944"/>

...
</routes>
</syntaxhighlight>

=== File Includes ===
It is possible to share xml route definitions between airports to avoid duplicating them.
This is done quite straight forward, but including a file with relative path to the current file. The included file needs to have the same structure as the main file and will be imported after all files in the current directory are imported.

'''Please note:'''This xml element is on the same level as the routes.

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
<include file="../uk.xml"/>
<route...
...
</routes>
</syntaxhighlight>

== Elements ==
A route can be constructed out of the following Elements:

==== line ====
A line is a line is a line.
It can be defined ''(1) either via two points'' or ''(2) via one point, direction and length''.

'''two point definition'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the line
|-
| end || {{no}} || The end point of the line
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should start
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin", "end", "both". Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the line. The line is broken at this spot.
|}

'''via one point, direction and length'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the line
|-
| angle || {{no}} || The magnetic angle of this line
|-
| length || {{no}} || The length of the line including the offsets
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should start
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed at the middle of the line. The line is broken at this spot.
|}

Examples:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<line start="BLM" end="ELBEG" text="069" />
<line start="HOC" end="HOMBO" startOffset="3" text="341" />
<line start="5.4NM226@BLM" end="LUMEL" text="226" />

<line start="BLM" startOffset="1.2" angle="003" length="10" text="003" arrows="end"/>

<line start="BLM" angle="202" length="4.5" stroke="dashed,1" text="202" />

</route>
</routes>
</syntaxhighlight>

==== multi-point-line / polygon ====
This element can be used to draw polygons, both open and closed.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| close || {{yes}} || "true" is the default, "false" does not connect the last with the first point
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

In difference to the other XML elements, this element contains children named <code>points</code>. Their content is a normal point definition as explained above.

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="Polygon example">
...
<multiPointLine close="false">
<point>ALTIK</point>
<point>6NM226@BLM</point>
<point>50.454722,7.227222</point>
</multiPointLine>
...
</route>
</routes>
</syntaxhighlight>

==== intercept ====
An intercept is currently implemented as a line from a startpoint in a startheading, a bow and a second line to a endPoint in a specific heading. The bow is defined in a way, that both lines are tangents to a circle with the same radius as the bow.
You can define it in two ways:

'''General Case'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the first line
|-
| startHeading || {{no}} || The initial heading of the plane at startPoint
|-
| radius || {{no}} || The radius in NM that the plane has to fly. You can also use ''speed'' to define it.
|-
| (speed) || {{no}} || Alternative to radius. Assuming a standard turn (360 degrees in 2 minutes, we can calculate the radius for you...)
|-
| direction || {{no}} || Is the turn to be made left or right
|-
| endHeading || {{no}} || The heading that the plane will fly after the turn in direction '''to''' the endPoint. This is the opposite of ''radial''. Use either ''endHeading'' or ''radial''
|-
| (radial) || {{no}} || Alternative to ''endHeading'': The radial you want to intercept. The radial is the direction '''from''' the endPoint, so it is the opposite of ''endHeading''.
|-
| end || {{no}} || The end point of the line (in real live most likely a VOR or NDB)
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should end
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the second line. The line is broken at this spot.
|}

'''Known-start-of-turn Case'''
In this case there is no first line. The drawing starts directly with the bow.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| startTurn || {{no}} || The start point of the '''bow'''
|-
| startHeading || {{no}} || The initial heading of the plane at startTurn
|-
| radius || {{no}} || The radius in NM that the plane has to fly. You can also use ''speed'' to define it.
|-
| (speed) || {{no}} || Alternative to radius. Assuming a standard turn (360 degrees in 2 minutes, we can calculate the radius for you...)
|-
| direction || {{no}} || Is the turn to be made left or right
|-
| endHeading || {{no}} || The heading that the plane will fly after the turn in direction '''to''' the endPoint. This is the opposite of ''radial''. Use either ''endHeading'' or ''radial''
|-
| (radial) || {{no}} || Alternative to ''endHeading'': The radial you want to intercept. The radial is the direction '''from''' the endPoint, so it is the opposite of ''endHeading''.
|-
| end || {{no}} || The end point of the line (in real live most likely a VOR or NDB)
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should end
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the second line. The line is broken at this spot.
|}

'''''Undesired results'''''
Constructing an intercept is easy with ruler and triangle, but more difficult when you are facing numerics and different coordinate systems. I have performed a lot of tests and are pretty sure that it works now, but there still can be issues.

*'''Parallel headings''' cause the problem, that I have to ignore the radius definition to connect them with one bow. I use the distance between the lines as bow diameter.
*'''Long lines''' In the ''general case'' most problems I saw arose from a radius, that was too small. If the lines are getting closer with growing distance from start, a small radius will cause the lines to be too long. In that case consider to use a larger radius or split the intercept into two.
*'''Bow behind startPoint:''' This is often caused by the fact that the plane needs to fly a wider radius to intercept the endHeading. In that case consider to use a larger radius or split the intercept into two.
*'''Other cases''' If construction is not possible, the result freaks out and paints something else. Verify your parameters! I help if I can, as this also might be a bug. Please send in your route!

'''''Constraints'''''
* Currently it is not possible to draw S-shape like intercepts automatically. I plan to add it, but need time and a free head for that. Use two intercepts until then!

==== curve ====
Curves are an easy and comfortable way to connect lines if there is not radius defined and if the angle is small.
A curve is implemented as quad curve, so it has a ''startPoint'', an ''endPoint'' and an ''controlPoint'' which controls the curving. A good start point for the control point is the interception between the lines that should be connected.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the curve
|-
| end || {{no}} || The end point of the curve
|-
| controlPoint || {{no}} || The location of the control point of this curve.
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<curve start="6NM226@BLM" end="13.5NM315@BASUD" controlPoint="7.5NM226@BLM"/>
</route>
</routes>
</syntaxhighlight>

==== bow ====
A bow is a part of a circle around a specified point. It can be used to define circling approaches or wider curves.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| center || {{no}} || The center of the bow
|-
| radius || {{no}} || The radius of the bow
|-
| startAngle || {{no}} || The magnetic start angle of the bow
|-
| extentAngle || {{no}} || The extend of the bow in degress. Positive direction is the direction of the compass
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed at the center angle of the bow. The line is broken at this spot.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<bow center="BLM" radius="9" startAngle="277" extentAngle="50" text="D9"/>

<bow center="BLM" radius="15" startAngle="274" extentAngle="-36" stroke="dashed" arrows="start" text="D15"/>
</route>
</routes>
</syntaxhighlight>

==== loop ====
This element displays a parking area. It has predefined text locations for min, max and misap height...

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| navpoint || {{no}} || The hook of the parking. The target of the inbound direction, where the pilots turn into the loop.
|-
| inboundHeading || {{no}} || As magnetic direction.
|-
| length || {{yes}} || the length of a leg in NM (the straight part of the loop)
|-
| width || {{yes}} || the distance between the legs in NM
|-
| right || {{yes}} || '''"true"''' or "false", does the pilot turn to right or left at navpoint? Default: right
|-
| minHeight || {{yes}} || The minimum height for planes in this loop (painted bold)
|-
| maxHeight || {{yes}} || The maximum height for planes in this loop
|-
| misapHeight || {{yes}} || The default height for missed approaches.
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="LFSB Wait loops">
<navaids>BLM,ALTIK,SEDOR</navaids>
<loop navpoint="SEDOR" inboundHeading="192" width="5" arrows="both" minHeight="7000" maxHeight="MAX 12000"/>>
<loop navpoint="ALTIK" inboundHeading="94" width="5" arrows="both" minHeight="5500" maxHeight="MAX 11000" misapHeight="MISAP4000"/>
<loop navpoint="BALIR" inboundHeading="319" width="5" arrows="both" minHeight="7000" maxHeight="MAX 12000"/>
</route>
</routes>
</syntaxhighlight>

==== text ====
This element draws a text at the specified spot. If marked as clickable, it can be used to assign a route to the selected contact with a single click.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| position || {{no}} || The geographic position of the text's center
|-
| angle || {{yes}} || The text can be rotated, if you need to. Default is horizontal, angle grows clockwise
|-
| alignHeading || {{yes}} || Alternative to ''angle''. The text will be displayed aligned to a heading. Useful if you want to write along a route leg.
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| clickable || {{yes}} || If set to "true", the route can be assigned to the selected contact with a single click onto this text.
|-
| text || {{no}} || This text will be displayed. Single line only!
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="text example">
<text position="5NM327@BLM" font="Arial" fontSize="22" angle="-90" text="Example text"/>
<text position="6NM327@BLM" font="Arial" fontSize="22" alignHeading="110" text="Example text"/>

<text position="47.546992,7.664459" fontSize="11" clickable="true" text="ELBEG 6T"/>
</route>
</routes>
</syntaxhighlight>

==== screenText ====
This element draws a text at the specified spot on your radar display. It will not pan, nor zoom with the rest of the map.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| screenPos || {{no}} || The position of the text's center in pixels in x,y format, e.g. "50,50". x,y start in the upper left corner. Negative values count from the other side of the screen. "center" works on per x/y base too.
|-
| angle || {{yes}} || The text can be rotated, if you need to. Default is horizontal, angle grows clockwise
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{no}} || This text will be displayed. Single line only!
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="screenText example">
<screenText screenPos="50,50" text="top left"/>
<screenText screenPos="-50,50" text="top right"/>
<screenText screenPos="50,-50" text="bottom left"/>
<screenText screenPos="-50,-50" text="bottom right"/>
<screenText screenPos="center,center" text="center"/>
</route>
</routes>
</syntaxhighlight>

==== VFR minimum altitudes ====
This element draws the known minimum altitude symbol.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| position || {{no}} || The position of the text's center
|-
| value || {{no}} || The altitude in thousands of feet ("3.4" means 3400 ft)
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="LFSB minimum altitudes">

<minAlt position="47.705141,7.911530" value="5.7"/>
<minAlt position="47.861,8.01315" value="5.9"/>

<minAlt position="47.81546,6.847916" value="5.3"/>
<minAlt position="48.084501,7.236557" value="5.4"/>

<minAlt position="47.406250,7.706909" value="5.7"/>
<minAlt position="47.208841,7.245483" value="6.2"/>
</route>
</routes>
</syntaxhighlight>

==== include a route / shared route parts ====
This element can be used to include all elements of another, already defined, route into the current route. You shall use it, to avoid duplicate route definitions for the part, that is shared by multiple routes.
'''Please note:''' The include tag does not inherit route definitions like route attributes, active runways or navaids to highlight. These definitions must be done for each real route (the one that includes the shared route). Only the route elements like lines, intercepts etc. are included.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| routeName || {{no}} || The name of the route that will be included.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="sharedRouteName">
<line start="BLM" end="ELBEG" text="069" />
</route>

<route name="ELBEG 6T" displayMode="sid" zoomMin="10" zoomMax="100" color="120,140,120">
<activestartRunways>15</activestartRunways>
<navaids color="255,255,0">ELBEG,HOC</navaids>

<include routeName="sharedRouteName" />
</route>
</routes>
</syntaxhighlight>

[[Category:OpenRadar|Editing routes]]

OpenRadar: Editing routes

2014-12-27T08:54:17Z

Wagnerw: /* Includes */

[[File:EDDF-Triangle-OpenRadar.png|right|300px|thumb|EDDF with procedures, routes and additional information.]]
[[OpenRadar| Back to mainpage]]

== About ==
You can define standard routes to OpenRadar. This can be done by converting a NavaidDB file and improve the result or define it from scratch by adding lines, curves and bows to the radar screen.
So you can define waiting loops, STARs and SIDs if you want to and if you need them.

Please send your finished work in to include it into the next OpenRadar update for everybody.

To have an example, check out airport LFSB. It is our showcase in this matter.

Please be warned: Defining all approaches and procedures for a more complex airport may produce too much details to work with. Concentrate on the important things, like additional vectors or waiting rooms.

A collection of possibilities:
* Highlight only the navaids that you need to see
* Create only the holding areas
* Create the Approaches to appear on a higher viewpoint and the STAR/SID routes on lower viewpoints
* Use texts to have the taxiways names in the map at the best spot (hide them on higher viewlevels)
* Use texts to have the maximum speed in the map
* Create only the most important routes, or
* Create all standard STAR and SID routes

== Guidelines ==
To avoid that everyone develops his own standards, we need to agree to common standards.

=== Display Modes ===
The route attribute displayMode can have different values:
{| class="wikitable"
|-
! displaymode !! Description
|-
| always ||These routes are always displayed. You cannot switch them off using the STAR/SID switch.
That means that you can use them to enrich the map itself: For forbidden areas or areas that require a minimum height... or for instance to add the names for taxiways to the map.
|-
| optional || This route will be hidden when you switch off START/SID.
You can use it for any route specific elements, that are not related to a specific runway.
|-
| sid / star || These values mark a route as sid/star. In future we might want to select a sid/star from a list. To be able to do that, we need to know which routes we need to display.
|}
So please follow these simple guidelines:
# Define one route per SID/STAR and design it, that it can be displayed individually, everything else switched off
# Mark these routes with the correct ''displayMode''
# Use the official STAR/NAME as route name, we will use it for display

=== Content ===
==== Airport local data ====
-- to be added--

==== Data shared between airports ====
Should be in a directory with a name describing the region. The airport xml files can incorporate these definitions via include xml element.
-- to be added--

=== Coloring ===
-- to be added--

== Generating the OpenRadar definitions from existing ProceduresDB file ==

WARNING: Known issues: There is an major issue when reading the procedure file, in the current version. I will fix it soon, but it requires to implement more functionality to define standard routes... I will need some time to do that.
'''Until this feature works, it is disabled in the published versions of OR.'''

There is already an XML format that contains the STARs and SIDs. Converting it can save you some work.

We do not use it directly because:
* These data are not free
* It purpose it to provide input for the autopilot/flight manager, not for an ATC screen
* Our format is made to display the important information which an ATC needs:
:*adaptive detail (you can define the lower and upper zoom level values between the route is being displayed)
:*display of STARs and SIDs can depend on the runway usage mode
:*colors (each route, each element can have its own color), strokes and line width
:*more graphical elements curves, bows and text
:*NAVAID hightlighting

The SID/STAR xml files can be bought and downloaded for a few bucks from [http://navigraph.com Navigraph]. Generally FlightGear looks for them in a Airports/I/C/A/ICAO.procedures.xml (where ICAO is an airport). For example, the procedures file for ELLX, if it exists, is under Airports/E/L/L/ELLX.procedures.xml.

OpenRadar can also read these XML files. For that:
* create the directory OpenRadar/data/routes/ICAO (where ICAO is the code of the airport you want to use)
* put your procedure XML (named ICAO.procedures.xml) into it
* start OpenRadar at your airport (ICAO), you now have a converted file ICAO.procedures.or.xml in the OpenRadar/data/routes/ICAO directory
* exit OpenRadar : the original file is not needed anymore after this step (move it somewhere else if you want)
* rename your ICAO.procedures.or.xml file to ICAO.procedures.xml

Now when restarting OpenRadar, the converted routes are available. You can and should modify the new file following the explanations below.

== Manual creation / refinement ==
The '''most important''' first:
*'''SHIFT+F12''' reloads the standard routes of your current airport. So you can see changes quickly...
*'''F12''' determines the geo position of your mouse tip and copies it to your clipboard. So you can easily place points: Place mouse pointer in OR map at the spot that you need, hit F12, change to your XML file, place the cursor, at the right spot and paste the clipboard. SHIFT+F12 will reload your work for verification...
*'''CTRL+F12''' determines the current zoom level and copies it to your clipboard. So you can easily set the zoom levels for your routes: Set the desired zoom level in OR map, hit CTRL+F12, change to your XML file, place the cursor, at the right spot and paste the clipboard. SHIFT+F12 will reload your work for verification...

The files must be located in directory data/routes/[airport name].

The files must end with ".xml", so they must be xml documents. Here is a simple example of everything around your route definitions:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
--- here are your definitions ---
</routes>
</syntaxhighlight>

=== A Route ===
A route is a collection of definitions that belong together. The values zoomMin and zoomMax allow you to define adaptive details or layers of information that appear within those constraints. Omitting them means there is no constraint at this side...

A route can have the following attributes:
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| name || {{no}} || A meaningful name for this route
|-
| zoomMin || {{yes}} || The minimum zoom level at which this route is being displayed. If you zoom in more, it disappears. (default values: Ground: 14, Tower: 26, App: 100)
|-
| zoomMax || {{yes}} || The maximum zoom level at which this route is being displayed. If you zoom out more, it disappears. (default values: Ground: 14, Tower: 26, App: 100)
|-
| displayMode || {{no|(No)}} || Controls how the different switches work for this route:
*"always": route is displayed always
*"optional": routes is displayed independently from the runways, but STAR/SID switch turns it off
*"sid": This route is a SID, its name is the official id, enabling the SID checkbox in runway panel displays it, and the STAR/SID main switch toggles it
*"star": This route is a STAR, its name is the official id, enabling the STAR checkbox in runway panel displays it, and the STAR/SID main switch toggles it
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| color || {{yes}} || Defines the color of the elements of this route. Use it carefully and rarely. You still want to be able to read the most important information on the radar: The contacs position info....
|}

Supported are the following xml tags:
{| class="wikitable"
|-
! Tag !! Opt. !! Description
|-
| activeStartRunways || {{yes}} || A comma separated list of runways. If one of them is active for '''starts''' the route will be displayed.
|-
| activeLandingRunways || {{yes}} || A comma separated list of runways. If one of them is active for '''landings''' the route will be displayed. If neither activeStartRunways nor activeLandingRunways is defined, the route will always be displayed. Use this for parking rooms...
|-
| navaids || {{yes}} || A comma separated list of navaid ids (FIX, NDB, VOR, Airportcodes) that will be highlighted if this route is being displayed, regardless if the main switches for FIX/NDB etc. are enabled or not.
This tag can have an attribute <code>color</code> that defines the color for the navaids in RGB values. Example: color="120,140,120"
There can be multiple instances of this element having different colors assigned.
|-
| (other elements) || {{yes}} || The graphical tags explained below
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>
--- more to be explained ---
</route>
</routes>
</syntaxhighlight>

=== Route features ===
==== Zoomlevel ====
Use the Attributes <code>zoomMin</code> and <code>zoomMax</code> to define a range in which a route is being displayed. So you can separate routes interesting for APP zoom level from details on tower level.

==== Navaid coloring ====
Both routes and navaids can have a <code>color</code> attribute defined. The rules which one is displayed are:
# If navaids block has no color defined, the route's color is being used.
# If route's block has no color defined, a default color will be used.
# Navaids are highlighted only, if the route is being displayed (zoom level, active start/landing runway)
# If a navaid is used in more than one visible route:
:# The color of a static route (no runway conditions) has highest priority (zoomLevel is respected only, to check if it is displayed at all)
:# Then follows the color attribute of the current navaids block, if defined.
:# Then follows the color attribute of the current route block, if defined, its default color otherwise.

Navaids used in many routes are of somewhat importance and should get their own static route and a separate color as hotspots.
In conflict case, the color, that is found first, wins.

=== Points and Angles ===
All elements of your route base on points and angles. '''Angles''' are magnetic and defined in degrees.

'''Points''' on your radar can be defined:
{| class="wikitable"
! Point !! Description
|-
| Navaid || You can use the navaid ID, e.g begin="BLM"
|-
| Runway end || You can use any runway end of the current airport. e.g. Runway 15 at Basel: begin="'''LFSB'''-RW'''15'''"
|-
| Geographic Location || You can use the geographic location separated by a comma. e.g. <pre>begin="47.599450,7.531936", begin="N47°57'51'',E7°54'58''" or begin="N47°57.2',E7°54.10'"</pre>
|-
| Relative Location || You can define a point relative to a navaid in the format: dddNMaaa@iii (where ddd is the decimal distance in NM, aaa is the magnetic bearing from iii, which is a navaid id. Distance and heading have the decimal separator 'dot'.
e.g. "2.5NM165@BLM"
|}
'''Length'''' are also given in decimal NM.

'''Missing Navaids:'''

If you notice that some navaids are not available in OpenRadar's data, you can use their geographic positions, or better define them in your route file.
These additional definitions can be used like navaids defined in the AptNav files...
A useful misuse of this feature is to produce highlighting-enabled route texts: Define the text as addPoint and reference it in a routes navaid block.
Please remember, very likely your clients will not have them visible in their inflight map...

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| code || {{yes}} || The ID under that your want to find it. Try to use non existing to avoid conflicts
|-
| point || {{yes}} || The geographic coordinates of the point.
|}

Examples:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<addPoint code="AGOLO" point="50.200000,9.676111"/>
<addPoint code="BIBTI" point="50.966667,7.108611"/>
<addPoint code="ESUPI" point="50.058333,8.121111"/>
<addPoint code="FRD" point="50.030556,8.566944"/>
<addPoint code="IBVIL" point="50.434444,7.369167"/>
<addPoint code="KERAX" point="50.475000,9.581944"/>

...
</routes>
</syntaxhighlight>

=== File Includes ===
It is possible to share xml route definitions between airports to avoid duplicating them.
This is done quite straight forward, but including a file with relative path to the current file. The included file needs to have the same structure as the main file and will be imported after all files in the current directory are imported.

'''Please note:'''This xml element is on the same level as the routes.

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>

<routes>
<include file="../uk.xml"/>
<route...
...
</routes>
</syntaxhighlight>

== Elements ==
A route can be constructed out of the following Elements:

==== line ====
A line is a line is a line.
It can be defined ''(1) either via two points'' or ''(2) via one point, direction and length''.

'''two point definition'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the line
|-
| end || {{no}} || The end point of the line
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should start
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin", "end", "both". Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the line. The line is broken at this spot.
|}

'''via one point, direction and length'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the line
|-
| angle || {{no}} || The magnetic angle of this line
|-
| length || {{no}} || The length of the line including the offsets
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should start
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed at the middle of the line. The line is broken at this spot.
|}

Examples:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<line start="BLM" end="ELBEG" text="069" />
<line start="HOC" end="HOMBO" startOffset="3" text="341" />
<line start="5.4NM226@BLM" end="LUMEL" text="226" />

<line start="BLM" startOffset="1.2" angle="003" length="10" text="003" arrows="end"/>

<line start="BLM" angle="202" length="4.5" stroke="dashed,1" text="202" />

</route>
</routes>
</syntaxhighlight>

==== multi-point-line / polygon ====
This element can be used to draw polygons, both open and closed.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| close || {{yes}} || "true" is the default, "false" does not connect the last with the first point
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

In difference to the other XML elements, this element contains children named <code>points</code>. Their content is a normal point definition as explained above.

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="Polygon example">
...
<multiPointLine close="false">
<point>ALTIK</point>
<point>6NM226@BLM</point>
<point>50.454722,7.227222</point>
</multiPointLine>
...
</route>
</routes>
</syntaxhighlight>

==== intercept ====
An intercept is currently implemented as a line from a startpoint in a startheading, a bow and a second line to a endPoint in a specific heading. The bow is defined in a way, that both lines are tangents to a circle with the same radius as the bow.
You can define it in two ways:

'''General Case'''
{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the first line
|-
| startHeading || {{no}} || The initial heading of the plane at startPoint
|-
| radius || {{no}} || The radius in NM that the plane has to fly. You can also use ''speed'' to define it.
|-
| (speed) || {{no}} || Alternative to radius. Assuming a standard turn (360 degrees in 2 minutes, we can calculate the radius for you...)
|-
| direction || {{no}} || Is the turn to be made left or right
|-
| endHeading || {{no}} || The heading that the plane will fly after the turn in direction '''to''' the endPoint. This is the opposite of ''radial''. Use either ''endHeading'' or ''radial''
|-
| (radial) || {{no}} || Alternative to ''endHeading'': The radial you want to intercept. The radial is the direction '''from''' the endPoint, so it is the opposite of ''endHeading''.
|-
| end || {{no}} || The end point of the line (in real live most likely a VOR or NDB)
|-
| startOffset || {{yes}} || The distance from start point in miles from which the painting should start
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should end
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the second line. The line is broken at this spot.
|}

'''Known-start-of-turn Case'''
In this case there is no first line. The drawing starts directly with the bow.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| startTurn || {{no}} || The start point of the '''bow'''
|-
| startHeading || {{no}} || The initial heading of the plane at startTurn
|-
| radius || {{no}} || The radius in NM that the plane has to fly. You can also use ''speed'' to define it.
|-
| (speed) || {{no}} || Alternative to radius. Assuming a standard turn (360 degrees in 2 minutes, we can calculate the radius for you...)
|-
| direction || {{no}} || Is the turn to be made left or right
|-
| endHeading || {{no}} || The heading that the plane will fly after the turn in direction '''to''' the endPoint. This is the opposite of ''radial''. Use either ''endHeading'' or ''radial''
|-
| (radial) || {{no}} || Alternative to ''endHeading'': The radial you want to intercept. The radial is the direction '''from''' the endPoint, so it is the opposite of ''endHeading''.
|-
| end || {{no}} || The end point of the line (in real live most likely a VOR or NDB)
|-
| endOffset || {{yes}} || The distance from end point in miles from which the painting should end
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed in the middle of the second line. The line is broken at this spot.
|}

'''''Undesired results'''''
Constructing an intercept is easy with ruler and triangle, but more difficult when you are facing numerics and different coordinate systems. I have performed a lot of tests and are pretty sure that it works now, but there still can be issues.

*'''Parallel headings''' cause the problem, that I have to ignore the radius definition to connect them with one bow. I use the distance between the lines as bow diameter.
*'''Long lines''' In the ''general case'' most problems I saw arose from a radius, that was too small. If the lines are getting closer with growing distance from start, a small radius will cause the lines to be too long. In that case consider to use a larger radius or split the intercept into two.
*'''Bow behind startPoint:''' This is often caused by the fact that the plane needs to fly a wider radius to intercept the endHeading. In that case consider to use a larger radius or split the intercept into two.
*'''Other cases''' If construction is not possible, the result freaks out and paints something else. Verify your parameters! I help if I can, as this also might be a bug. Please send in your route!

'''''Constraints'''''
* Currently it is not possible to draw S-shape like intercepts automatically. I plan to add it, but need time and a free head for that. Use two intercepts until then!

==== curve ====
Curves are an easy and comfortable way to connect lines if there is not radius defined and if the angle is small.
A curve is implemented as quad curve, so it has a ''startPoint'', an ''endPoint'' and an ''controlPoint'' which controls the curving. A good start point for the control point is the interception between the lines that should be connected.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| start || {{no}} || The start point of the curve
|-
| end || {{no}} || The end point of the curve
|-
| controlPoint || {{no}} || The location of the control point of this curve.
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<curve start="6NM226@BLM" end="13.5NM315@BASUD" controlPoint="7.5NM226@BLM"/>
</route>
</routes>
</syntaxhighlight>

==== bow ====
A bow is a part of a circle around a specified point. It can be used to define circling approaches or wider curves.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| center || {{no}} || The center of the bow
|-
| radius || {{no}} || The radius of the bow
|-
| startAngle || {{no}} || The magnetic start angle of the bow
|-
| extentAngle || {{no}} || The extend of the bow in degress. Positive direction is the direction of the compass
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{yes}} || Whatever you define, will be displayed at the center angle of the bow. The line is broken at this spot.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="RW 26 SID" zoomMin="10" zoomMax="100" color="120,140,120">
<activeStartRunways>26</activeStartRunways>
<navaids>BASUD,BLM,BS,ELBEG,HOC,HOMBO,LUMEL,WIL</navaids>

<bow center="BLM" radius="9" startAngle="277" extentAngle="50" text="D9"/>

<bow center="BLM" radius="15" startAngle="274" extentAngle="-36" stroke="dashed" arrows="start" text="D15"/>
</route>
</routes>
</syntaxhighlight>

==== loop ====
This element displays a parking area. It has predefined text locations for min, max and misap height...

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| navpoint || {{no}} || The hook of the parking. The target of the inbound direction, where the pilots turn into the loop.
|-
| inboundHeading || {{no}} || As magnetic direction.
|-
| length || {{yes}} || the length of a leg in NM (the straight part of the loop)
|-
| width || {{yes}} || the distance between the legs in NM
|-
| right || {{yes}} || '''"true"''' or "false", does the pilot turn to right or left at navpoint? Default: right
|-
| minHeight || {{yes}} || The minimum height for planes in this loop (painted bold)
|-
| maxHeight || {{yes}} || The maximum height for planes in this loop
|-
| misapHeight || {{yes}} || The default height for missed approaches.
|-
| stroke || {{yes}} || Can be "line","dashed","dots" or a pattern definition followed optionally by a comma and the line width as decimal, if omitted it is a plain line, 2 dots in width. A pattern definition is a dash separated list of decimals defining the length of the visible and invisible sub-lines of the pattern. e.g. "1-1" (dots), "5-1" (dashes), "10-3-5-3" a long dash, 3 dots space a shorter dash, 3 dots space...
|-
| <s>lineWidth</s> || {{n/a|<s>Yes</s>}} || <s>The width of the lines to be painted. Default is 2px. Use 1px for vectoring helper lines (dashed/dotted)...</s> '''Deprecated, define it in stroke!'''
|-
| arrows || {{yes}} || Paints arrows at the lines end, pointing in direction from start to end: Possible is "begin","end",both", Optionally you can define the arrow size by appending a comma and the size of the arrow. Default is 10, big would be 20. Example: "end,20"
|-
| color || {{yes}} || Defines the color of this line. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="LFSB Wait loops">
<navaids>BLM,ALTIK,SEDOR</navaids>
<loop navpoint="SEDOR" inboundHeading="192" width="5" arrows="both" minHeight="7000" maxHeight="MAX 12000"/>>
<loop navpoint="ALTIK" inboundHeading="94" width="5" arrows="both" minHeight="5500" maxHeight="MAX 11000" misapHeight="MISAP4000"/>
<loop navpoint="BALIR" inboundHeading="319" width="5" arrows="both" minHeight="7000" maxHeight="MAX 12000"/>
</route>
</routes>
</syntaxhighlight>

==== text ====
This element draws a text at the specified spot

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| position || {{no}} || The geographic position of the text's center
|-
| angle || {{yes}} || The text can be rotated, if you need to. Default is horizontal, angle grows clockwise
|-
| alignHeading || {{yes}} || Alternative to ''angle''. The text will be displayed aligned to a heading. Useful if you want to write along a route leg.
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{no}} || This text will be displayed. Single line only!
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="text example">
<text position="5NM327@BLM" font="Arial" fontSize="22" angle="-90" text="Example text"/>
<text position="6NM327@BLM" font="Arial" fontSize="22" alignHeading="110" text="Example text"/>
</route>
</routes>
</syntaxhighlight>

==== screenText ====
This element draws a text at the specified spot on your radar display. It will not pan, nor zoom with the rest of the map.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| screenPos || {{no}} || The position of the text's center in pixels in x,y format, e.g. "50,50". x,y start in the upper left corner. Negative values count from the other side of the screen. "center" works on per x/y base too.
|-
| angle || {{yes}} || The text can be rotated, if you need to. Default is horizontal, angle grows clockwise
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|-
| text || {{no}} || This text will be displayed. Single line only!
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="screenText example">
<screenText screenPos="50,50" text="top left"/>
<screenText screenPos="-50,50" text="top right"/>
<screenText screenPos="50,-50" text="bottom left"/>
<screenText screenPos="-50,-50" text="bottom right"/>
<screenText screenPos="center,center" text="center"/>
</route>
</routes>
</syntaxhighlight>

==== VFR minimum altitudes ====
This element draws the known minimum altitude symbol.

{| class="wikitable"
|-
! Attribute !! Opt. !! Description
|-
| position || {{no}} || The position of the text's center
|-
| value || {{no}} || The altitude in thousands of feet ("3.4" means 3400 ft)
|-
| font || {{yes}} || The font name, please consider using a font everybody has available, or leave it away to take the default
|-
| fontSize || {{yes}} || The font size in points. Default is 10pt
|-
| color || {{yes}} || Defines the color of this text. Overwrites the definition in <code><route></code>. Define it there if possible.
|}

Example:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<routes>
<route name="LFSB minimum altitudes">

<minAlt position="47.705141,7.911530" value="5.7"/>
<minAlt position="47.861,8.01315" value="5.9"/>

<minAlt position="47.81546,6.847916" value="5.3"/>
<minAlt position="48.084501,7.236557" value="5.4"/>

<minAlt position="47.406250,7.706909" value="5.7"/>
<minAlt position="47.208841,7.245483" value="6.2"/>
</route>
</routes>
</syntaxhighlight>

[[Category:OpenRadar|Editing routes]]

Talk:OpenRadar: Editing routes

2014-10-21T19:56:47Z

Wagnerw:

I understand using ''addPoint'' to add missing navigation points. But how can a existing, misplaced waypoint be changed to the correct position? [[User:Mcantsin|Mcantsin]] ([[User talk:Mcantsin|talk]]) 17:32, 20 October 2014 (UTC)

Right addPoint exists to add missing ones. The only way to correct existing ones is to edit the data files downloaded from xplane site. The problem is, that your contacts will still use the wrong files within fgfs... This issue was Jomos daily business in the last years until frankfurt airport has been updated in the data files.
I have checked http://data.x-plane.com/get_data.html for an update, but there is nothing new. I wonder, how I can help...
--[[User:Wagnerw|WagnerW]] ([[User talk:Wagnerw|talk]]) 19:56, 21 October 2014 (UTC)

OpenRadar Change Log

2014-05-31T09:12:50Z

Wagnerw: /* Next update */

[[OpenRadar| Back to mainpage]]

* I am working on (on a slower pace, not contained in next update)
:* Flightplan exchange server
::* Prototype for a common backend for FlightGear (I need someone to add it to FG), ATC apps like OR and Website like lennys FP landing page
::* First stage: Implement and test with OR without full persistence to a database
::* Second stage: Implement database interface
::* Thirst stage: Permanent availability by running on a public server

:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

{{TOC limit|2}}

== Next update ==
* new possibility to download flightplans from server http://flightgear-atc.alwaysdata.net/ using a button in flightplan dialog
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits

== Published updates ==

=== OpenRadar updates 2014-05-18 ===
* fix for minor screen refresh issue (when new METAR requires a screen change)

=== OpenRadar updates 2014-05-10 ===
* fix for course display issue
* fix for FGCOM bug, when OR path contained spaces

=== OpenRadar updates March 2014 ===
:* Flightplan integration into OR
::* Destination airport is displayed in data block
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.

=== OpenRadar 2013-10-12 ===
* Model for magnetic field (variation/declination) has been ported from FGFS to OR (same base data, avoid download from server victim to US government shutdown)
* Assign a runway to a contact via double click on runway (select contact, double click runway) => Runway appears in data block (remove assignement, by another double click on rwy number)
* Improvement to METAR parsing
* Fix for auto assigned squawk codes xxx8 and xxx9, that do not exist
* Chat aliases (see forum),
:*Examples:
::* .tr 010 => Turn right heading 010
::* .sqa => Squawk 2004 (next free squawk code)
::* .hs 15 => Hold short runway 15
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages

=== OpenRadar 2013-05-30 ===
* Standard routes:
:* Separate switches for SID and STARs in runway section
:* New Attribute for Routes displayMode {always, optional, sid, star}
:* New element screenText sets text to a fixed position on map screen
:* New element intercept eases the drawing of intercept bows a lot
:* New element include to include other xml files in separate directories (for airspace data in shared directories)
:* Correction to highlight coloring and documentation
:* Navaid elements can appear multiple times in a route, each with its own color.
* FGCom support is now indicated on the flight strips too
* '''Disabled:''' Chat messages became too long to be received by flightgear
:* Transmitting all FGCom frequencies made text too long => only first frequency is being transmitted
:* ATIS details compressed
* Minor fixes for METAR parsing
* Single map switches moved into a small menu at the same place
* '''Sound support'''
:* Sound for NEW ARRIVING CONTACT (Cessna fly over)
:* Sound for new chat message for current ATC (plop sound)
:* Sound for new metar received (wind blowing)
:* Mute-able one by one and all together
* Fix for NullPointer when trying to load an airport without given tower position (OMDB, LSZN)
* Display of data block in radar is completely dynamic now (lines are build dynamically, symbol drawn dynamically, support for different sets of settings to switch between)
* '''Transponder support''' prototype
:* Read transponder data from MP protocol
:* Display of ident
:* Display of tranfered data
:* Support of simple squawk management (define range, assign squawk, revoke assigned squawk)
* Extended centerline: If there is no ILS, it is displayed in another color.

== OpenRadar beta updates (Jan 2013-Apr 2013) ==
=== Beta update 2013-04-07 ===
* Support for runways, where starting and landing is done at the same end (via rw settings dialog "bi-directional")
* METAR: Improvements to parser
* METAR: wind directions < 100 degrees are displayed with leading zeros
* '''StatusPanel Weather''': Second line showing clouds and phenomena
:* Tool tip text of second line shows a more human readable version of the screen display
:* Double click on first line sends out ATIS as before
:* Double click on first line sends out ATIS and clouds as seconds line
* The chat text selection dialogue uses separators and supports html to modify the text display properties
* Possibility to '''switch off background layers''' to accelerate the application and to get more reality, if you prefer to have less information
* '''Radio frequencies are taken from fgcom phonebook'''. So all frequencies should be recognized by the server
* NDB/VOR symbols are a bit smaller now
* Parking position display, if both, name and number are defined and short, I display them both. Consider to rework groundnetwork xml file, if you have 'General Aviation' or 'Gate' in it! Almost all airports I saw up to now, have only the number defined, e.g. as 'A10', EHAM has name='A' and number='24'. The later is displayed now as 'A24'
* StandardRoutes:
:* New tag to define minimum altitudes for VFR easily
:* New Support for geo formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10' to define points
:* Bugfix for Line: angle 180 and 360 degrees did not work.
:* In xml defined addPoints are now real FIX. They can be highlighted and are displayed as a FIX
* ContactDialog: Checkbox for indicating/remembering FGCOM support in radar (little headset symbol) (forum feedback call http://forum.flightgear.org/viewtopic.php?f=75&t=19648)
* Reworked of AtcMessages:
:* Angles are given in 3 digit format e.g. 005,
:* ILS angle is now in brackets,
:* ATIS: all active FGCOM frequencies are transmitted,
:* QNH is given in both units
:* Correction in russian file

=== Beta update 2013-03-10 ===
* Neglect feature: Replaced CTRL+Click by text button above flight strips to toggle selected contact
* Fix for: Sometimes heading line points into wrong direction
* Standard Routes: Added easy possibility to reference Runway Ends in route definitions
* Standard Routes: Added possibility to use own fixes (for fixes that are not in the navaid database yet)
* SHIFT+F12 is reloading the route definitions, to avoid multiple restarts

=== Beta update 2013-03-10 ===
* Optionally you can show the most important data like direction, distance and ETA beside the mouse pointer (the little dog)
* Possibility to convert/define STAR + SID routes
* Minor improvements

=== Beta update 2013-01-29 ===
* Fix for chat problem with some airplanes (e.g. A380)
* Repositioning of values on flight strips for better readability

=== Beta update 2013-01-26 ===
* Added toggle for display of glide slope heights
* Added shortcuts for zoom level
* Added radar zoom per right mouse button drag
* Improved mouse compatibility for Mac mouses (no middle button)
* Added feature to restart internal managed FGCOM if sound is distorted (FGCom issue)
* Last callsign is now persisted to be used when ATC comes back to airport
* Fix for slightly misplaced baseline heading text (extended center line display)
* Added possibility to copy runway extended centerline settings to all other runways of an airport
* Groundspeed is not calculated (out of position and time at client machine), because the values we get are sometimes incorrect
* moved flightstrip help tooltip to question mark label above
* Found tow other reasons to avoid contacts on radar which have no flight strip
* Change: Double click on flightstrip shows radar contact and airport now by setting center and zoom scale (before it centered the map on contact). So you see their relative location to the airport...
* The selected contact (double click) is highlighted to be easier to find
* There is a navaid search box that finds Fixes, NDB, VOR and airports in range, you can search for a comma separated list, the results are highlighted, even, if they are switched off
* Dragging the map is now faster now

=== Beta update 2013-01-12 ===
* Added heights to the centerline display, they show the height an airplane should have to intercept the glideslope, detail adapts on zoom level (every 500ft, 1000ft, 1500ft)
* Improved status area readability
* Changing of aircraft model now really updated on flight strips
* Changed to current XPlane file format 10.00, runway length must be calculated now, rounded to 100 ft (before it was given)
* METAR parser handles CAVOK now

== OpenRadar prototype updates (Nov 2012-Jan 2013) ==
=== Prototype update 2013-01-08 ===
* Chat filter VIS: hidden, because not needed
* Tower location is now saved in sector.properties, can be adjusted manually
* Hello messages are back, have been filtered out
* Neglected contacts are painted above ghosts (inactive), but below all other contacts, because they must not hide important information
* ''Runway''s have a ''master switch'' now: It can be used to define, that a runway is never used for start/landing or both. => Runway Settings Dialogue
* Fix for sending MP messages before position was set
* Flightstrips of inactive contacts show seconds since last update
* Fix for problem with re-appearing contacts (flight strips where sometimes not displayed)

=== Prototype update 2013-01-04 ===
* Chat filter SEL: Shows only the history of the communication between selected (active) contact and the ATC.
* This filter disables itself, if another contact is selected (Back to Show all)
* Fix for ATC notes saved to a wrong flight strip

=== Prototype update 2012-12-27 ===
* Data/(airportCode)sector.properties contains a new field metarSource now, if no METAR is available for a small airport, set it to an airport nearby (=> MP map, check if there is METAR available)
* OpenRadar starts now, if METAR is missing, issuing a warning on command line...
* Fine tuning of colors
* Runway display reworked (more logical, display of magnetic runway heading)
* Fix for non workinig PTT key for COM3, COM4

=== Prototype update 2012-12-25 ===
* fix for bug 'Chat field not cleared after sending' (only if FGCom control was OFF, because there was no radio frequency to transmit over MP protocol => NumberFormatException)
* wider call sign column in chat history (some clients truncated output)

=== Prototype update 2012-12-23 ===
* Settings: More understandable control over FGCom control modes
* Fixed bug in MP protocol (different MP protocol versions exist, OpenRadar could not talk with other OpenRadars)
* Fixed vectoring/baseline number display of enabled/disabled centerlines
* Added ILS Frequency ATC messages

=== Prototype update 2012-12-18 ===
* Extended center lines have got a configuration dialogue, they can be displayed on one side only and can be asymmetric, have vectoring and baseleg display and show the headings as numbers
* Extended center line settings are saved now
* Zoom level center and zoom value are persisted on per Airport base
* Flight strips have been streamlined to use less space (only two lines without ATC comment)
* Flight strips use more lines, if an ATC comment is maintained
* Distance circles: Depending on zoom level there are distance circles around the airport now
* ATC comments are persisted to stay between sessions
* Frequencies are persisted too
* Added selectable pre-defined ATC messages a la ATC-ML
* Fine tuning of data display and detail level
* Toggles for Display of FIX, NDB, VOR, Distance circles, Airport code and parking position numbers
* Contacts can be set to neglected with CTRL+CLICK on flight strip (grays them out)
* FGCOM/FGCOMGUI is killed when application terminates to avoid ghost instances continue to run
* ATC comments editor has been moved to dialog (right click on contact or flight strip)
* Same dialog allows to set native language, if set, messages of ATC are repeated in this language after English transmission but only for this contact
* Selection clicks work also on radar map now
* Internal redesign to avoid multi-threading dead locks

=== Prototype update 2012-11-18 ===
* Fixed units, now we display knots and feet not km/h and meter
* Filter for heading when airplane stops on ground: Values seem to come from simulation engine and start to turn wildly when radar contact is not moving. The filter steps heading changes if speed is below than 0.5 knots. So a plane can hold without starting to turn
* In radar display shows feet instead of FL
* If at least one runway is selected for landing and starting, the runway panel can be collapsed with a double click (toggle)
* Foreground in status area is set to white now => better readable
* More space on flight strip for notes and smaller font gives space for 3 lines of some words length
* Chat messages can be drag and dropped to the flight strip note editor to simplify copying of flight plans etc.
* Chat messages: own chat messages are sent for 3 secs. at least 10 times, to avoid that a message does not reach its recipient (udp can loose messages)
* Fixes: removed all fixes ending with numbers from display, so we have more space to display important fixes, changed max. zoom level for their display, so you see them from high above
* Fixes: Sector download retrieves magnetic derivation and saves it in sector property file. All old existing sectors must be downloaded again. Derivation is applied to true coarses, to displayed wind and runway analysis
* Longer timeouts to avoid loosing data of people, who pause flightgear, and continue later (inactive become "ghosts" for 1 minute before they are hidden as expired, a new contact will reuse the existing data)
* Possibility to deselect a contact again
* Sending of chat messages on focus lost fixed
* Added vertical speed in hundrets of fpm to be able to guess what a pilot wants to do
* Added distance and bearing from airport to find radar contacts more easily
* Changed size of area drastically to get all necessary shapes and navaids
* Changed Zoom levels GROUND, CLOSE SECTOR to GROUND, TOWER, APP and SECTOR
* Fixed a bug when dragging map after using the ZOOM Levels
* Flight strips extend their length if you enter more lines to display all. Width is restricted to about 26 chars.
* Elevation display has been adapted to usual way of displaying it: FL has been removed, in Radar the feet display has been adapted too. Now 12345 ft are displayed as 123
* The lines showing the future place in 60 seconds same direction same speed, are shorter now, they point to 30 sec. in future
* The selection to pointer compensates the average wind influence now => it is magnetic and shows the direction to fly to reach the pointer
* Radio frequencies can be set manually by doing a middle click on the selection box
* ATC notes to contacts are stored in a file and stay forever
* New ILS symbol
* Better usability of flightstrips: left click: toggle selection, left double click: select and focus on chat, middle click: selection and focus on details editor, middle double click: center map on contact, right click: select exclusively (show chat messages of this contact only)
* Changed from miles to nautical miles
* Inactive contacts are grayed out to ghosts for a minute and hidden after that.

[[Category:OpenRadar]]