Configuration

Preliminary remarks

There are a lot if individual configuration options. The basic configuration was already done during the installation within the file config.php . The further configuration is also done in this file.

To get an overview of all settings, have a look on the page link below, where all standard settings are displayed. To change the settings, copy and paste the desired line(s) to config.php and change the values to your ones.

General information about constants

The options shown here are defined by constants. Define a constant with:

define('CONSTANT', Value);

The constant has to be quoted (double or single quotes, no apostrophe)! Whether to quote the value, it depends on its content:

  • A lot of things can be switched on or off. The value can only be true or false. No quotation marks may be used for true/false. Example: define("BO_PURGE_ENABLE", false);
  • Value can also be a number. That means, no quotations marks. Example: define("BO_LAT", 49.393279);
  • Only if value is to a text string, it has to be put in quotes. Example: define("BO_STATION_NAME", "Ro�tal");

Settings

Below are just a few configuration options described.

Data import

Constants: BO_UP_INTVL_STRIKES, BO_UP_INTVL_STATIONS and BO_UP_INTVL_RAW . The value is a number that represents the refresh interval in minutes. Example:

define("BO_UP_INTVL_STATIONS", 15);

The default settings should be sufficient in most cases.

Purging data

The database can grow very quickly. With the constants in the form of BO_PURGE_… , you can define data purging in individual ways. BO_PURGE_ENABLE switches purging completely on or off. BO_PURGE_MAIN_INTVL specifies the time interval in hours, after which the deletion is triggered.

The other constants control the deletion of individual datasets: All strikes, strikes where your station did not participate, signals, statistics etc. A very important setting is BO_PURGE_STRSTA_ALL which is responsible for deleting the strike to participants data (your own station data is stored separately). These data is growing extremely quickly and is not so important, so can be deleted after 24 hours. The lightning data itself can be stored for a much longer time (as desired), the space consumption is not as extreme – for this, you then have an own archive.

All the constants at a glance:

  • BO_PURGE_SIG_NS: signals, where no lightning could be assigned
  • BO_PURGE_SIG_ALL: All signals
  • BO_PURGE_STR_NP: strikes where your station did not participate
  • BO_PURGE_STR_ALL: All strikes
  • BO_PURGE_STR_DIST: Strikes outside the radius BO_PURGE_STR_DIST_KM
  • BO_PURGE_STRSTA_ALL: Strike to other station assignments
  • BO_PURGE_STA_OTHER: Statistics from other stations
  • BO_PURGE_STA_ALL: All statistics

Red = Requires a lot of memory, orange = memory consumption is not quite as big.

The “Radius”

With the constant BO_RADIUS you can set a maximum radius to your own station, where visitors can see detailed lightning data. The default value is set to 50 km. Please do not increase this value if MyBlitzortung is accessible by everyone.

GoogleMaps strike map

The zoom levels are set as follows:

  • BO_DEFAULT_ZOOM: Default zoom level (When you are vistiting the webseite, the actual zoom level will also be stored in a cookie; for testing purposes you should delete the cookies or use a "fresh" browser)
  • BO_MAX_ZOOM_LIMIT: Maximum zoom at which the display of strikes is limited to the radius.
  • BO_MAX_ZOOM_IN / BO_MIN_ZOOM_OUT: Overall maximum and minimum zoom levels.

There is also the constant BO_DEFAULT_MAP for the standard map. All other settings for the maps have to be made by variables.