GNSS Simulator
Talk to an engineer
GNSS Simulator

Our publishing standards

Editorial Policy

Technical information should help you understand a method, plan a test or make a better equipment decision.

This policy sets out the standards for technical guides, product-selection resources and engineering tools published by GNSS Simulator, operated by STARSPACE INTERNATIONAL LIMITED.

Start with the reader’s question

Our resources are written for engineers, researchers, educators and purchasing teams working with GNSS and related test equipment.

Each guide should address a clear question: how a technology works, how to prepare a test, which configuration details matter, or how to interpret a measurement. Definitions, diagrams, examples and comparison tables should make that question easier to resolve.

Use sources that support the explanation

Technical explanations should draw on sources appropriate to the subject, including:

  • Official satellite-system documentation, interface specifications and service information.
  • Product manuals, current specifications and software documentation for the equipment being discussed.
  • Relevant standards, original research and established engineering references.
  • Clearly described calculations, demonstrations and application examples.

References should be linked near the relevant explanation or collected in a source section. Where a document version, software release or test condition affects the conclusion, that context should be stated.

Make product information useful for selection

GNSS Simulator supplies equipment and solutions discussed on this website. Our product-related resources connect technical requirements with equipment selection.

Product information should identify the relevant model, supported configuration and available options. Comparisons should explain practical differences such as signal coverage, expansion, RF outputs, interfaces and integration needs.

A useful recommendation explains why a configuration fits the application and what information is needed to prepare a quotation.

Explain examples and calculations clearly

Worked examples should identify their inputs, units, assumptions and calculation method. Diagrams should make signal paths, data flows and equipment roles easy to follow.

Illustrative scenarios should be labelled as examples. Measured results should describe the equipment, configuration and conditions used to obtain them.

Engineering tools should explain the supported inputs, output quantities and how to interpret the result.

Connect publishing with customer questions

The GNSS Simulator Editorial Team is the publishing identity for our technical resources.

Mike Ren manages website communications and international customer enquiries. He coordinates product and application questions with the technical team, helping connect published information with the requirements customers bring to us.

Meet the people behind the resources on our editorial team page .

Keep updates meaningful

Updates should address changes that matter to the reader: revised documentation, product information, calculation methods, broken references or an explanation that needs clarification.

Publication dates identify when an article first appeared. A modified date should reflect a substantive content update. Significant corrections should be explained on the affected page so readers can understand what changed.

Scroll to Top