api.radiantdrift.com
  • Radiant Drift API
    • Subscription Plans
    • Educational Use and Research
    • API End Points
  • Getting Started
    • About your account
    • Request Authentication
    • Managing API Keys
    • OpenAPI Specification
    • Date/Time Format
    • Validity, Accuracy, and Precision
  • Usage Guidelines
    • Acceptable Use Policy
    • Usage Credits and Call Costs
    • Attribution
    • Rate Limits
  • Julian Day
  • Delta-T
  • Rise, Transit, Set Times
  • Body Position
    • Request Parameters
    • Position at a given time
    • Positions for a time range
    • Observer location
  • Solar Eclipses
    • Embeddable Web Widgets
      • Eclipse Map
      • Eclipse Simulator
    • Besselian Elements
    • Local Circumstances
    • Eclipse Paths
    • Five Millennium Canon of Solar Eclipses
  • The Moon
    • Lunar Libration
    • Lunar Limb Profile
  • Geospatial
    • Geodesic
    • Elevation
  • Reference
    • Definitions
    • Errors
Powered by GitBook
On this page
  1. Getting Started

Validity, Accuracy, and Precision

Under construction 🚧

We plan to add information regarding validity of end points, particularly with respect to date ranges, and also expected accuracy.

Generally, calculated astronomical values are presented to 8 decimal places, which may exceed the expected accuracy in some cases. Calculated coordinates (e.g. latitude, longitudes in eclipse paths) are normally given to 6 decimal places.

It's been our experience that having precision match or exceed expected accuracy is often advantageous - not in a scientific context but in that of day-to-day software development, where comparability of results is usually most helpful and the ability to detect changes in outputs can often signify an unintended or unexpected change in inputs, assumptions, algorithms or behaviors, even if the digits that changed are not in themselves practically significant.

PreviousDate/Time FormatNextUsage Guidelines

Last updated 12 months ago