igs-slm 0.1.5b1__tar.gz → 0.1.5b3__tar.gz

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: igs-slm
-Version: 0.1.5b1
+Version: 0.1.5b3
 Summary: IGS Site Log Manager
 Project-URL: Homepage, https://igs-slm.readthedocs.io
 Project-URL: Documentation, https://igs-slm.readthedocs.io
@@ -64,6 +64,10 @@ Requires-Dist: python-dateutil<3.0.0,>=2.8.2
 Requires-Dist: requests<3.0.0,>=2.32.4
 Requires-Dist: rich<14.0.0,>=13.7.1
 Requires-Dist: tqdm<5.0.0,>=4.64.1
+Provides-Extra: debug
+Requires-Dist: django-debug-toolbar<5.0.0,>=4.1.0; extra == 'debug'
+Requires-Dist: django-extensions<4.0.0,>=3.1.5; extra == 'debug'
+Requires-Dist: ipdb<1.0.0,>=0.13.13; extra == 'debug'
 Provides-Extra: gunicorn
 Requires-Dist: gunicorn>=22.0.0; extra == 'gunicorn'
 Description-Content-Type: text/markdown

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/doc/source/changelog.rst

@@ -6,13 +6,27 @@
 Change Log
 ==========
 
-v0.1.5b1 (2024-07-15)
+v0.1.5b3 (2025-07-25)
+=====================
+
+* Fixed `Provide SLM IGS station naming validation toggle. <https://github.com/International-GNSS-Service/SLM/issues/153>`_
+* Fixed `Sometimes the javascript diffing/site log error renderer inserts extra newlines. <https://github.com/International-GNSS-Service/SLM/issues/151>`_
+
+
+v0.1.5b2 (2025-07-15)
+=====================
+
+* Beta Bug Fix
+* Added `Add debug dependency group <https://github.com/International-GNSS-Service/SLM/issues/155>`_
+* Fixed `WSGI_APPLICATION default is wrong <https://github.com/International-GNSS-Service/SLM/issues/154>`_
+
+v0.1.5b1 (2025-07-15)
 =====================
 
 * Beta Bug Fix
 * Fixed `SLM_INCLUDE url inclusion is not working to spec <https://github.com/International-GNSS-Service/SLM/issues/152>`_
 
-v0.1.5b0 (2024-07-15)
+v0.1.5b0 (2025-07-15)
 =====================
 
 * Beta Increment

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/doc/source/conf.py

@@ -13,6 +13,7 @@ from sphinx.ext.autodoc import between
 import warnings
 import os
 import django
+from django.utils.version import get_docs_version
 import re
 
 sys.path.append(str(Path(__file__).parent.parent.parent / "src"))
@@ -20,6 +21,7 @@ sys.path.append(str(Path(__file__).parent.parent.parent))
 os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'tests.settings')
 django.setup()
 
+
 # -- Path setup --------------------------------------------------------------
 
 # If extensions (or modules to document with autodoc) are in another directory,
@@ -106,13 +108,22 @@ django_show_db_tables = True                # Boolean, default: False
 # Add abstract database tables names (only takes effect if django_show_db_tables is True)
 django_show_db_tables_abstract = True       # Boolean, default: False
 
+autodoc_default_options = {
+    'show-inheritance': True,
+    # Add other autodoc options here if desired, e.g.:
+    # 'members': True,
+    # 'inherited-members': True,
+}
+# In your Sphinx conf.py
+autodoc_typehints = "description"
+autodoc_typehints_format = "short"
+autodoc_class_signature = "separated"
 autodoc_member_order = 'bysource'
 
-# TODO - ALWAYS POINT THE DJANGO DOCS AT OUR CURRENT DJANGO VERSION, NOT STABLE
 intersphinx_mapping = {
     "django": (
-        "https://docs.djangoproject.com/en/4.2",
-        "https://docs.djangoproject.com/en/4.2/_objects/",
+        f"https://docs.djangoproject.com/en/{get_docs_version()}/",
+        f"https://docs.djangoproject.com/en/{get_docs_version()}/_objects/",
     ),
     "click": ("https://click.palletsprojects.com/en/stable", None),
     "rich": ("https://rich.readthedocs.io/en/stable", None),
@@ -139,6 +150,7 @@ html_css_files = [
     'https://cdnjs.cloudflare.com/ajax/libs/bootstrap-icons/1.11.3/font/bootstrap-icons.min.css',
 ]
 
+
 def color_role(name, rawtext, text, lineno, inliner, options={}, content=[]):
     """Role that creates a color box with the hex color."""
     from docutils import nodes
@@ -156,6 +168,7 @@ def color_role(name, rawtext, text, lineno, inliner, options={}, content=[]):
     node = nodes.raw('', html, format='html')
     return [node], []
 
+
 def css_icon(name, rawtext, text, lineno, inliner, options={}, content=[]):
     """Role that creates a color box with the hex color."""
     from docutils import nodes
@@ -168,6 +181,7 @@ def css_icon(name, rawtext, text, lineno, inliner, options={}, content=[]):
     node = nodes.raw('', html, format='html')
     return [node], []
 
+
 def setup(app):
     # Register a sphinx.ext.autodoc.between listener to ignore everything
     # between lines that contain the word IGNORE

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/doc/source/configuration.rst

@@ -1,5 +1,6 @@
 .. include:: refs.rst
 
+.. _configuration:
 
 =============
 Configuration
@@ -220,6 +221,9 @@ The following settings may be overridden by environment variables:
    * - :setting:`SLM_DEBUG_TOOLBAR`
      - :ref:`env_types_bool`
      - ``on|off``
+   * - :setting:`SLM_IGS_STATION_NAMING`
+     - :ref:`env_types_bool`
+     - ``on|off``
    * - :setting:`SLM_SITE_NAME`
      - :ref:`env_types_bool`
      - ``slm.yourdomain.org``
@@ -444,6 +448,26 @@ Enable or disable the MapBox_ admin map in the SLM. Must be set in the environme
 or prior to the inclusion of ``slm.settings.root``. You may also enable or disable
 the admin map by adding or removing ``slm.map`` from :setting:`INSTALLED_APPS`.
 
+``SLM_IGS_STATION_NAMING`` ⚙️
+------------------------------
+.. setting:: SLM_IGS_STATION_NAMING
+
+Default: ``False``
+
+Enable or disable the use of IGS naming rules for station names. If enabled, the defaults for
+:setting:`SLM_STATION_NAME_REGEX` and :setting:`SLM_STATION_NAME_HELP` will be set to:
+
+.. code-block:: python
+
+    SLM_STATION_NAME_REGEX = r"[\w]{4}[\d]{2}[\w]{3}"
+    SLM_STATION_NAME_HELP = _(
+         "This is the 9 Character station name (XXXXMRCCC) used in RINEX 3 "
+         "filenames Format: (XXXX - existing four character IGS station "
+         "name, M - Monument or marker number (0-9), R - Receiver number "
+         "(0-9), CCC - Three digit ISO 3166-1 country code)"
+    )
+
+
 ``SLM_STATION_NAME_REGEX``
 --------------------------
 .. setting:: SLM_STATION_NAME_REGEX
@@ -518,7 +542,7 @@ We provide a more reasonable default than Django_'s :setting:`django:DEFAULT_FRO
 -----------------------
 .. setting:: WSGI_APPLICATION
 
-Default: ``slm.wsgi``
+Default: ``slm.wsgi.application``
 
 We set a default for :setting:`django:WSGI_APPLICATION` that works if *either*:
 

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/doc/source/index.rst

@@ -30,7 +30,8 @@ This documentation speaks to multiple audiences:
 
 * **Developers** will want to refer to the :ref:`installation`, :ref:`architecture`,
   :ref:`commands` and :ref:`reference` sections.
-* **System administrators** may be interested in :ref:`operations` and :ref:`commands`.
+* **System administrators** may be interested in :ref:`configuration`, :ref:`upgrading` and
+  :ref:`commands`.
 * **Users** and **network coordinators** will be interested in the :ref:`user_manual`.
 * **Developers** wishing to work with SLM managed data will be interested in the :ref:`api`.
 * **Everyone**, but particularly **program managers** will want to take a look at the
@@ -47,9 +48,7 @@ map is on the projects_ page.
 
 Contributions_ from the community are encouraged!
 
-.. APIs
-.. manual/index
-.. operations/index
+
 
 .. toctree::
    :maxdepth: 2
@@ -60,8 +59,10 @@ Contributions_ from the community are encouraged!
    upgrading
    configuration
    architecture/index
+   manual/index
    commands
    dependencies
+   APIs
    reference/index
    changelog
 

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/doc/source/installation.rst

@@ -35,12 +35,19 @@ Hereafter, we will use the following terminology to describe these deployments:
 Manual Installation
 ===================
 
-The SLM is both a :doc:`Django app <django:ref/applications>` and a fully deployable website. Most
-users of the SLM will want to customize certain aspects of it (things like adding
-:pypi:`django-ldap` or :doc:`two-factor authentication <django-allauth:mfa/index>`). To facilitate
-that we will use the bundled command slm-startproject_ to generate a scaffold to build off of (not
-unlike Django's :django-admin:`startproject`). But first we must install some dependencies.
-
+The SLM is both a :doc:`Django app <django:ref/applications>` and a fully deployable website. Many
+users of the SLM will want to customize it significantly (things like adding
+:pypi:`django-ldap` or :doc:`two-factor authentication <django-allauth:mfa/index>`). It can also
+be deployed out of the box with a :ref:`minimal configuration <configuration>`. We recommend trying
+a minimal development set up first to familiarize yourself with the software and identify any data
+importing pain points. The following guide includes instructions for running the SLM out of the
+box and for generating a scaffold to customize it. We will first work through a
+:ref:`local develop <slm-startproject>` installation and then we cover
+:ref:`deployment to a production server <deploy>`.
+
+To facilitate customization we provide a bundled command slm-startproject_ to generate a scaffold to
+build off of (not unlike Django's :django-admin:`startproject`). But first we must install some
+dependencies.
 
 Dependencies
 ############
@@ -132,6 +139,8 @@ Platform specific Installation guidance.
 Start Project
 #############
 
+**If you are not customizing the SLM, skip ahead to step 2.**
+
 To get up and running quickly with your customized SLM deployment we bundle a command called
 slm-startproject_ that will scaffold out a directory structure and settings files for you to start
 working with. Before running slm-startproject_ you will need to have installed all of GeoDjango_'s
@@ -162,8 +171,8 @@ itself yet though.
 
   .. tab:: github
 
-    You also have the option of working with our development version from github, but unless you have
-    a compelling reason to do so you should use the release on pypi.
+    You also have the option of working with our development version from github, but unless you
+    have a compelling reason to do so you should use the release on pypi.
 
     .. code:: bash
 
@@ -256,16 +265,57 @@ the first question you can just hit enter to accept the defaults:
 (2) Create environment & database
 ---------------------------------
 
-* Use either psql_ or pgAdmin_ to create the database that slm-startproject_ instructs you to.
-  In our example this database would be named ``network``.
+.. tabs::
+
+  .. tab:: Basic Install
+
+    * Use either psql_ or pgAdmin_ to create a database called ``slm``.
+
+    * We recommend creating a local development :mod:`python virtual environment <venv>`, but you
+      may also use any python on your system that meets the :pypi:`igs-slm` minimum python
+      requirement.
+
+    * You will need to set a few environment variables and create an environment variable file so
+      the SLM knows some basic things about itself.
+
+    In your local development directory:
+
+    .. code-block:: bash
+
+      ?> python -m venv .venv
+      ?> source .venv/bin/activate
+      (.venv) ?> export SLM_ENV=`pwd`/.env
+      (.venv) ?> touch .env
+      (.venv) ?> pip install "igs-slm[debug]"
 
-* Use uv to install the virtual environment then activate it.
+    Add a minimal configuration to the .env file. It may look something like this. You may also
+    refer to the :ref:`configuration` page for all of the available settings. The most important
+    settings are :setting:`SLM_ENV`, :setting:`BASE_DIR`:
 
     .. code-block:: bash
 
-      ?> uv sync --all-extras
+      DEBUG=True
+      BASE_DIR=./
+      SLM_ORG_NAME="ORG"
+      SLM_SITE_NAME="localhost"
+      # you may have to set these paths if your postgis libraries
+      # are in non-standard locations
+      # GEOS_LIBRARY_PATH=/path/to/libgeos_c.dylib
+      # GDAL_LIBRARY_PATH=/path/to/libgdal.dylib
 
 
+  .. tab:: Custom Install
+
+    * Use either psql_ or pgAdmin_ to create the database that slm-startproject_ instructs you to.
+      In our example this database would be named ``network``.
+
+    * Use uv to install the virtual environment then activate it.
+
+        .. code-block:: bash
+
+          ?> cd ./network
+          ?> uv sync --all-extras
+
 .. _import_sitelogs:
 
 (3) Import Existing Logs and Deploy
@@ -276,11 +326,23 @@ existing logs to import you'll probably just want to run :django-admin:`routine
 Otherwise gather your logs into a single directory or tar file and run the
 :django-admin:`routine install` routine:
 
-  .. code-block:: bash
+.. tabs::
+
+  .. tab:: Basic Install
+
+    .. code-block:: bash
+
+      (.venv) ?> slm routine install
 
-    ?> <slm> routine install
+  .. tab:: Custom Install
 
-**<slm> is the name of your management script. In our example it would be called 'network'.**
+    .. code-block:: bash
+
+      ?> uv run network routine install
+
+You will be prompted to create a superuser account and also for a file path or directory containing
+site logs you wish to import. After the import is finished an html log of the import process will
+open.
 
 The data import will both generate logs and record import errors and warnings as alerts and
 validation flags in the database so you can manually go through the web interface and correct any
@@ -291,24 +353,39 @@ errors.
 
 You should now be able to start up the development server and see data in your SLM instance.
 
-  .. code-block:: bash
+.. tabs::
+
+  .. tab:: Basic Install
+
+    .. code-block:: bash
+
+      (.venv) ?> <slm> runserver
+      Performing system checks...
+
+      System check identified no issues (1 silenced).
+      Django version 4.2.23, using settings 'slm.settings.root'
+      Starting development server at http://127.0.0.1:8000/
+      Quit the server with CONTROL-C.
+
+  .. tab:: Custom Install
 
-    ?> <slm> runserver
-    Performing system checks...
+    .. code-block:: bash
+
+      ?> uv run network runserver
+      Performing system checks...
 
-    System check identified no issues (1 silenced).
-    Django version 4.2.14, using settings 'sites.<slm>.develop'
-    Starting development server at http://127.0.0.1:8000/
-    Quit the server with CONTROL-C.
+      System check identified no issues (1 silenced).
+      Django version 4.2.23, using settings 'sites.network.develop'
+      Starting development server at http://127.0.0.1:8000/
+      Quit the server with CONTROL-C.
 
 In addition to the front end interface where site logs are edited, moderated and published. We use
 the `Django admin for a more direct access to system data <http://127.0.0.1:8000/admin>`_. This is
 where we control permissions and make site adjustments. You may also add users and agencies and set
 their permissions through the admin.
 
-.. tip::
 
-  Refer to :ref:`operations` for advice on production deployments.
+.. _deploy:
 
 Deploy
 ######
@@ -318,10 +395,10 @@ Deploy
   We offer a notional deployment strategy here. There are myriad operational concerns that will vary
   based on your organization's so the following examples are merely suggestions.
 
-The scaffold we generated should be checked into version control. You can manage it just like you
-would a normal python package. It can be built and installed using uv_ or pip_ or any other python
-package management tooling that supports wheels. When you install it it will pull in all of its
-required python dependencies.
+If you are customizing the SLM, the scaffold we generated should be checked into version control.
+You can manage it just like you would a normal python package. It can be built and installed using
+uv_ or pip_ or any other python package management tooling that supports wheels. When you install it
+it will pull in all of its required python dependencies.
 
 First you need to make sure your host server has all the dependencies installed, PostGIS_, etc.
 Then you should use ``psql`` to create the database. It is usually sufficient to configure PostGIS_
@@ -373,31 +450,69 @@ environment somewhere you think is appropriate. For example:
 Build and Install
 -----------------
 
-.. code-block:: bash
+.. tabs::
+
+  .. tab:: Basic Install
 
-  # in your git repository holding your slm-startproject
-  ?> uv build
-  # get the wheel to your server somehow
-  ?> scp dist/network-x.x.x-py3-none-any.whl yourserver:./
-  ?> ssh yourserver
-  ?> source /opt/slm_venv/bin/activate
-  # install with gunicorn if using nginx or mod_wsgi if using Apache
-  (slm_venv) ?> pip install network-x.x.x-py3-none-any.whl
-  # if using nginx:
-  (slm_venv) ?> pip install gunicorn
-  # if using apache:
-  (slm_venv) ?> pip install mod_wsgi
+    .. code-block:: bash
+
+      ?> source /opt/slm_venv/bin/activate
+      # install with gunicorn if using nginx or mod_wsgi if using Apache
+      (slm_venv) ?> pip install igs-slm
+      # if using nginx:
+      (slm_venv) ?> pip install gunicorn
+      # if using apache:
+      (slm_venv) ?> pip install mod_wsgi
+
+  .. tab:: Custom Install
+
+    .. code-block:: bash
+
+      # in your git repository holding your slm-startproject
+      ?> uv build
+      # get the wheel to your server somehow
+      ?> scp dist/network-x.x.x-py3-none-any.whl yourserver:./
+      ?> ssh yourserver
+      ?> source /opt/slm_venv/bin/activate
+      # install with gunicorn if using nginx or mod_wsgi if using Apache
+      (slm_venv) ?> pip install network-x.x.x-py3-none-any.whl
+      # if using nginx:
+      (slm_venv) ?> pip install gunicorn
+      # if using apache:
+      (slm_venv) ?> pip install mod_wsgi
 
 Filesystem
 ----------
 
 We recommend setting up your site's working directory somewhere under /var/www:
 
-.. code-block:: bash
+.. tabs::
+
+  .. tab:: Basic Install
+
+    .. code-block:: bash
+
+      ?> mkdir -p /var/www/network.example.com/production
+      ?> cd /var/www/network.example.com/production
+      ?> mkdir static media logs secrets
+
+    You will need to create an environment file to tell the SLM about itself:
+
+    .. code-block:: bash
+      :caption: /var/www/network.example.com/production/.env
+
+      DEBUG=False
+      BASE_DIR=/var/www/network.example.com/production
+      SLM_ORG_NAME="Example"
+      SLM_SITE_NAME="network.example.com"
 
-  ?> mkdir -p /var/www/network.example.com/production
-  ?> cd /var/www/network.example.com/production
-  ?> mkdir static media logs secrets
+  .. tab:: Custom Install
+
+  .. code-block:: bash
+
+    ?> mkdir -p /var/www/network.example.com/production
+    ?> cd /var/www/network.example.com/production
+    ?> mkdir static media logs secrets
 
 web servers
 -----------
@@ -472,6 +587,7 @@ web servers
       User=www-data
       Group=www-data
       WorkingDirectory=/var/www/network.example.com/production
+      Environment="SLM_ENV=/var/www/network.example.com/production/.env"
       ExecStart=/opt/slm_venv/bin/gunicorn --workers 4 --bind unix:/var/www/network.example.com/production/slm.sock sites.network.production.wsgi:application
 
       [Install]
@@ -507,6 +623,13 @@ web servers
           # WSGI configuration
           WSGIDaemonProcess network python-home=/opt/slm_venv python-path=/var/www/network.example.com/production
           WSGIProcessGroup network
+
+          WSGIEnvVar SLM_ENV /var/www/network.example.com/production/.env
+
+          # TODO - For Basic Install:
+          WSGIScriptAlias / /opt/slm_venv/lib/python3.x/site-packages/slm/wsgi.py
+
+          # TODO - For Custom Install:
           WSGIScriptAlias / /opt/slm_venv/lib/python3.x/site-packages/sites/network/production/wsgi.py
 
           # Static & media files
@@ -533,15 +656,47 @@ routine deploy
 Anytime you install a new version of your SLM you need to run :django-admin:`routine deploy`. This
 will migrate the database and bundle all static files:
 
-.. code-block:: bash
 
-  (slm_venv) ?> network routine deploy
+.. tabs::
+
+  .. tab:: Basic Install
+
+    .. code-block:: bash
+
+      (slm_venv) ?> slm routine deploy
+
+    If it is the first installation you can run the :django-admin:`routine install` routine instead:
+
+    .. code-block:: bash
+
+      (slm_venv) ?> slm routine install
+
+  .. tab:: Custom Install
+
+    .. code-block:: bash
+
+      (slm_venv) ?> network routine deploy
+
+    If it is the first installation you can run the :django-admin:`routine install` routine instead:
+
+    .. code-block:: bash
+
+      (slm_venv) ?> network routine install
+
+
+.. tip::
+
+  Refer to :ref:`upgrading` for advice on updating the SLM.
 
 .. _containerization:
 
 Containerization
 ================
 
+.. todo::
+
+    Instructions for running our containers..
+
 
 .. _fast_hosting:
 
@@ -549,4 +704,5 @@ Fast Hosting
 ============
 
 .. todo::
-       Instructions for quickly deploying to a hosting service..
+
+    Instructions for quickly deploying to a hosting service..

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/doc/source/upgrading.rst

@@ -1,5 +1,6 @@
 .. include:: refs.rst
 
+.. _upgrading:
 
 =========
 Upgrading

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "igs-slm"
-version = "0.1.5b1"
+version = "0.1.5b3"
 description = "IGS Site Log Manager"
 requires-python = ">=3.8,<4.0"
 authors = [
@@ -85,6 +85,11 @@ dependencies = [
 
 [project.optional-dependencies]
 gunicorn = ["gunicorn>=22.0.0"]
+debug = [
+    "ipdb>=0.13.13,<1.0.0",
+    "django-debug-toolbar>=4.1.0,<5.0.0",
+    "django-extensions>=3.1.5,<4.0.0",
+]
 
 
 [build-system]

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/src/slm/__init__.py

@@ -15,7 +15,7 @@ r"""
 
 """
 
-VERSION = (0, 1, "5b1")
+VERSION = (0, 1, "5b3")
 
 __title__ = "IGS/Site Log Manager"
 __version__ = ".".join(str(i) for i in VERSION)

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/src/slm/settings/root.py

@@ -242,5 +242,5 @@ set_default(
 )
 
 WSGI_APPLICATION = env(
-    "WSGI_APPLICATION", default=get_setting("WSGI_APPLICATION", "slm.wsgi")
+    "WSGI_APPLICATION", default=get_setting("WSGI_APPLICATION", "slm.wsgi.application")
 )

{igs_slm-0.1.5b1 → igs_slm-0.1.5b3}/src/slm/settings/slm.py

@@ -186,15 +186,18 @@ set_default(
 # instance than the instance that generates serialized artifacts
 SLM_FILE_DOMAIN = None
 
-
-set_default("SLM_STATION_NAME_REGEX", None)
-set_default("SLM_STATION_NAME_HELP", _("The name of the station."))
-
-# IGS Settings:
-# SLM_STATION_NAME_REGEX = r"[\w]{4}[\d]{2}[\w]{3}"
-# SLM_STATION_NAME_HELP = _(
-#     "This is the 9 Character station name (XXXXMRCCC) used in RINEX 3 "
-#     "filenames Format: (XXXX - existing four character IGS station "
-#     "name, M - Monument or marker number (0-9), R - Receiver number "
-#     "(0-9), CCC - Three digit ISO 3166-1 country code)"
-# )
+SLM_IGS_STATION_NAMING = env(
+    "SLM_IGS_STATION_NAMING", default=get_setting("SLM_IGS_STATION_NAMING", False)
+)
+if SLM_IGS_STATION_NAMING:
+    # Use IGS naming rules for station names:
+    SLM_STATION_NAME_REGEX = r"[\w]{4}[\d]{2}[\w]{3}"
+    SLM_STATION_NAME_HELP = _(
+        "This is the 9 Character station name (XXXXMRCCC) used in RINEX 3 "
+        "filenames Format: (XXXX - existing four character IGS station "
+        "name, M - Monument or marker number (0-9), R - Receiver number "
+        "(0-9), CCC - Three digit ISO 3166-1 country code)"
+    )
+else:
+    set_default("SLM_STATION_NAME_REGEX", None)
+    set_default("SLM_STATION_NAME_HELP", _("The name of the station."))