Support

Getting started

1. Choose Import source and examine the new file’s diagnostic report. Nothing is assimilated until you accept the review.
2. For a comma- or tab-delimited file whose headings or units need explanation, choose Map Columns. Declare the delimiter and whether a header row exists, preview the data, assign time, latitude, longitude and depth, and declare depth and time units. Magnitude, magnitude type and identifier are optional. Confirming a mapping produces another review: it does not automatically accept the import.
3. Accept the usable records after review, or reject the import. Inspect candidate duplicates using identifiers, time and location. Choose Keep or Exclude deliberately: similarity is not proof that two records describe the same event.
4. Use Save Session to preserve the original source bytes, accepted mappings and keep/exclude decisions in a .QuakeMLer document. Choose a new filename: the current save operation does not overwrite an existing document.
5. Use Export generated QuakeML to write retained records as .QuakeML and save a matching .QuakeMLer review document beside it. The original imported files are never altered.

Opening and revising saved work

Choose Open saved .QuakeMLer document to restore original source bytes, accepted mappings and keep/exclude decisions. The app verifies stored sources before replacing the current catalogue. Save unsaved work first.

Select a record and use File → Edit selected source mapping to inspect or revise that source’s explicit mapping. A source imported without an explicit mapping must be imported again and mapped before these choices can be edited. Accepting a revised mapping replaces that source’s records, not other sources. Exclusions are retained only where public identifiers match unambiguously: new or ambiguous identifiers require review.

Paired export: names, access and recovery

Choose an export name, then approve the same destination folder when asked. Folder permission allows the app to create both files. If either name already exists, both outputs receive the same unused numbered suffix, such as Catalogue (1).QuakeML and Catalogue (1).QuakeMLer. Existing files are not silently replaced.

The current paired-export implementation requires a destination that supports hard links. If the destination is unsupported, choose a suitable local folder. The two-file operation cannot guarantee recovery from a sudden app or computer interruption between file creations. If export reports failure or an interruption occurs, inspect the reported output paths and confirm that both files exist before treating the pair as complete. Ordinary failures attempt to remove only incomplete files created by that export.

Supported data and important limits

The current source supports QuakeML 1.2 Basic Event Description (BED), USGS GeoJSON earthquake FeatureCollections, supported UTF-8 header-based CSV, and explicitly mapped comma- or tab-delimited text with or without headers. Time mapping supports ISO 8601 with a timezone, Unix seconds or Unix milliseconds. Coordinates must be decimal degrees, and depth units must be declared as metres or kilometres.

The supplied extended 48-column CSV layout is recognised for origin data. Additional centroid and CMT fields are retained as source provenance, not converted into native QuakeML moment-tensor solutions. This is not a lossless converter for every QuakeML or earthquake-data object. Native NDK catalogue import is not currently supported.

Saved sessions include original source bytes, even for records excluded from export. Non-mapped fields are not necessarily represented in the exported catalogue. Inspect the QuakeML output before sharing or using it with another program.

The source limits each imported file to 64 MiB and a catalogue to 100,000 records. Saved-session input and the paired companion document are limited to 512 MiB. Candidate matching can stop at 100,000 pairs or 5,000,000 proximity comparisons. An incomplete-search message must not be read as proof that there are no more duplicates.

Troubleshooting

• Unknown headings or no headings: use Map Columns for delimited text. It does not apply to XML, JSON or NDK.
• Conflicting public identifiers: review the implicated events, not only their filenames.
• Missing magnitude: QuakeML permits an absent magnitude, but the current export warns that eQuakes may not accept those records. Review or exclude them if the destination requires magnitude. Never invent zero.
• Session restore blocked: keep the source and session. A changed parser result or mismatching source hash or record identifiers must not be ignored.
• Export folder prompt: select the same folder chosen in the export dialog. Cancelling folder access writes neither output.
• Finder opens another app: use Open With to choose QuakeMLer for a QuakeML file. Use the app’s saved-document command for a review session.

Reporting a problem

Include the app version, macOS version, source format, exact message and steps to reproduce. A small synthetic example is preferable to a private catalogue. Do not include passwords or payment details.

Publisher: The Virtual Explorer.
Support and privacy contact: director@thevirtualexplorer.com.au.

Gordon Lister handles support correspondence and attachments personally and decides how each is dealt with after receipt. No fixed retention period or automatic deletion schedule is stated. The privacy information remains a draft pending final release verification. Do not send confidential catalogue material or credentials.