Account Settings

Settings is the one page in GeoLens about your own account rather than the catalog. Open it from the avatar menu at the right of the top navigation bar, or go straight to /settings. You have to be signed in; there is nothing here for anonymous visitors.

The page has two tabs: Preferences and API Keys.

Preferences

Profile

Your username and the role you hold, shown as a badge: viewer, editor, or admin. Those three are the whole role set. An administrator can change what each role is allowed to do, but cannot define new roles.

Nothing on this card is editable. Your username is fixed at account creation; your email address and your roles are changed by an administrator from the user-management page. There is no password-change form in the web UI either; the API exposes POST /api/auth/change-password/ for that.

Storage usage

Two meters, both reading your own account only.

File storage sums the bytes of the dataset files GeoLens holds for datasets you created: the raster file itself, plus any pre-conversion original kept when a lossy COG conversion replaced it. Vector and tabular datasets live as PostGIS tables and a virtual raster is a definition over sources it does not copy, so none of them adds anything to this number.

Datasets counts the records you created that are datasets: vector, raster, virtual raster, and non-spatial tables. Maps, collections, and registered services are not counted.

Each meter reads used / cap with a progress bar when your administrator has set a cap, and just the used figure with the word Unlimited when they haven’t. Both caps default to unlimited, so on an instance nobody has tuned, both meters read Unlimited and no bar is drawn. The caps are the Max Storage per User and Max Datasets per User settings under Settings -> Storage.

Over limit. Both caps are checked when you create something, not continuously, so lowering a cap below what an account already holds takes nothing away. On the dataset meter that state is labelled: it reads e.g. 18 / 10 with a red Over limit underneath. You keep every dataset you have and can still open, edit, and export them; you cannot add another until you are back under the cap. The import page does the same arithmetic before you start: it shrinks the per-batch file allowance as you approach the cap and refuses an upload that would cross it. See Importing Data.

If the usage query itself fails, the file-storage figure reads Unavailable rather than a plausible-looking zero.

Language

The GeoLens interface ships in English, Español, Français, Deutsch, and 简体中文. Picking one from the select applies it immediately, with no page reload.

The choice is stored in your browser, not on your account: it follows the browser profile you set it in, does not travel to another machine, and resets to your browser’s own language preference if you clear site data.

Before you pick one, GeoLens reads the browser’s own language tag. A Simplified Chinese tag selects 简体中文: zh, zh-CN, zh-SG, zh-MY, and any other tag whose script resolves to Han Simplified. Traditional Chinese tags such as zh-TW and zh-HK are a different written form, not this bundle, so they fall back to English.

API Keys

Every signed-in user can mint their own API keys here. No administrator has to be involved and no special permission is required. A key belongs to exactly one account and can do what that account can do, narrowed by the key’s scope.

Creating one. Click Create Key, give it a name, pick a Scope, and submit. The scope select offers Full access (the default) and Read only; the two options and their meaning are the same ones an admin sees, and are described under API keys -> Key scope. Scope is fixed at creation.

The raw key appears once, in a dialog with a copy button, under the warning “This key will not be shown again.” That is literal. GeoLens keeps only a SHA-256 hash of the key, so one you lose cannot be recovered and has to be replaced. Copy it into your secret store before you dismiss the dialog.

The list. Each key shows its name, a fingerprint (the first eight and last four characters of the key, enough to tell two keys apart in an audit log), an Active or Revoked badge, a Read only badge when that is its scope, the date it was created, and when it was last used. A key that has never authenticated a request reads Never used.

Revoking. The trash icon next to an active key opens a confirmation, and the key stops working the moment you confirm. Revoked keys stay in the list, in their revoked state, as a record. There is no un-revoke.

Expiry. The form here has no expiry field, so keys minted in the UI do not expire on their own. To set one, create the key through the API instead:

# One year out, RFC 3339.
# GNU date equivalent: date -u -d '+1 year' +%Y-%m-%dT%H:%M:%SZ
EXPIRES=$(python3 - <<'EOF'
import datetime as d
print((d.datetime.now(d.timezone.utc) + d.timedelta(days=365)).isoformat(
    timespec='seconds').replace('+00:00', 'Z'))
EOF
)

curl -X POST https://geolens.example.com/api/auth/api-keys/ \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"name\":\"sync\",\"scope\":\"read_only\",\"expires_at\":\"$EXPIRES\"}"

Security events on your own account also invalidate your keys: a password change or a role change stops every key you hold from resolving, and you will need to mint replacements. Signing out of the web UI deliberately does not.