Moon Data

Navigation:  ScriptLine Properties >

Moon Data

Previous pageReturn to chapter overviewNext page

Property of the ScriptLine: International.

 

The Moon Data property is used to specify the origin of the data used to convert Moon Tokens, and any specific calculation options that should be used.

 

Selecting Moon Data Source(s)

 

The Moon Data property is used to specify the origin of the data used to convert Moon tokens. On the left of the Moon Data property editor is a list of Available Moon Data Sources. Use the Add and Remove buttons to fill the list of Selected Moon Data Sources to the right. Usually you will only select one Moon Data Source per diary, if any.

 

If you often use the same Moon Data source and options, you can set a default to use for any new script, using the Preferences.

 

If you need to select more than one Moon Data Source, then make sure that the selected sources are listed in the order that you will refer to them in Moon tokens. For example, if you are building a table of Moonrise/Moonset for many cities, then the [SR1] and [SS1] tokens will use data from the first source listed in the list, the [SR2] and [SS2] tokens will use data from the second source, etc...

 

This property should not be confused with Moon and Sun Options, which is used to defined how moon events are displayed for each individual DiaryGridLine. The Moon Data property deals with obtaining the moon information, while the Moon and Sun Options property deals with displaying this information.

 

Calculation Options

 

The Calculation Options available to be used in the calculation of Moon Events are:

 

Ignore Summer Times, even if source uses them

(not recommended)

If you select this option, then all moon-related dates and times will be calculated and displayed as if the location used to calculate them did not follow summer time rules. This will produce times that are an hour off from readers' experiences for half of the year.

 

Turning this option on is not recommended, and the only reason to use this option is to match customer data which may have neglected summer time effects by error.

Ignore atmospheric refraction
(not recommended)

If you select this option, then the calculation of the times of moonrise and moonset tokens will be performed without taking into account atmospheric refraction (the bending of light around the Earth due to the atmosphere).

 

Turning this option will produce moonrise times that are later than the observed times, and moonset times that are earlier than those observed.

 

Turning this option on is not recommended, and the only reason to use this option is to match customer data.

Use fixed disk sizes
(not recommended)

If you select this option, then the calculation of the times of moonrise and moonset tokens will be performed without taking into account the fact that the Moon is not always at the same distance from the Earth. When the Moon is at the closest and therefore appear rises sooner and sets later than if one assumes a fixed disk size.

 

Turning this option on is not recommended, and the only reason to use this option is to match customer data.

Reference point for rise/set calculations

Normally the time of moonrise is defined as the moment when the top of the Moon becomes visible, and moonset as the moment when the top of the Moon disappears below the horizon.

 

This corresponds to the value Top of lunar disk which is the default setting and should only be changed if you are sure of the consequences of that change, usually to match existing customer data.

 

The only exception that we are aware of is in Denmark, where rising and setting times of the Sun and the Moon, are calculated based on the Center of lunar disk.

 

You can, and should, set a default value for these properties and rarely change them (see International Preferences).

 

See also: Jewish Data, Muslim Data, Sun Data.


Topic 75000 updated on 25-Jan-2019.
Topic URL: https://www.qppstudio.net/webhelp_xe3/index.html?moondata.htm