Every scientific source must have a stable identity, access basis, licensing or reuse note and provenance trail. Sources that do not permit the intended production use are rejected or kept reference-only instead of being scraped silently.
Record identity and provenance
Every scientific record should be traceable to source_id, station_id or another stable source identity, observation time and processing information. Derived values and authored indices additionally preserve algorithm version, parameter hash and exact input-record identities so the transformation can be audited.
Reuse rights before automation
A source does not become an automated dependency merely because it is visible in a browser. Production ingestion requires an access basis and reuse terms compatible with the intended GeoLira function. When rights are unclear the source can remain a bibliographic or validation reference rather than being silently scraped.
Canonical history and user-facing attribution
Canonical storage may retain successive revisions of one event for audit. User-facing views select the newest accepted revision of the logical event so, for example, repeated USGS corrections do not appear as separate earthquakes. Source links help users verify provenance, but an institutional name or DOI does not replace freshness and quality metadata for the specific record. GeoLira does not present external material as its own measurement.
4. Scientific providers and their independence
GeoLira can present data from sources such as NOAA, NASA, GFZ and USGS alongside locally derived results. Every dataset has its own method, update cadence, format and limitations. Naming an organisation does not imply that it approved all interpretations or entered into a formal partnership with GeoLira. Users should inspect the specific source identifier and observation time. A forecast should not be treated as a measurement, and an authored index must not be represented as an official warning. Reuse rights depend on the provider's actual terms. Public visibility does not automatically grant an unlimited right to copy or sell information. Source licences and technical documentation should be checked before reuse.
5. Revision history and event identification
A scientific event may receive revised observations, such as an updated location, time or earthquake magnitude. Canonical storage can retain revisions for audit while public views choose the latest accepted record of the logical event. This helps prevent a provider's correction from appearing as a second independent earthquake. Users should distinguish observation time from update or retrieval time. Differences between an archive and a current chart can reflect quality-control procedures. A historical correction does not imply intentional falsification. Reproducible research should preserve source identifiers, the timeframe and relevant algorithm versions.
6. Derived values, algorithms and authored indices
Some values are calculated locally from other observations, while custom indices can use their own parameters, versions and normalisation. A derived result is not an instrument measurement merely because it uses scientific input. GeoLira should preserve relevant algorithm and input provenance to make the displayed meaning traceable. Users must not advertise an authored index as a universally recognised medical scale or international physical standard without adequate evidence. Decisions requiring precision should rely on original measurements and professional assessment. Different algorithms can produce different results and require different interpretation.
7. Copyright and reuse permissions
Photographs, text, maps, graphics and datasets can be protected regardless of whether the originating organisation is public or private. GeoLira should establish the access basis and required attribution before automated ingestion. Material with unclear reuse rights may remain a bibliographic reference rather than being copied into the catalogue. Anyone reusing information from GeoLira must consider the original provider's licence, attribution requirements, version and modification notices where applicable. Author credits must not be removed, and external measurements must not be passed off as original observations. Statutory exceptions, such as lawful quotation, remain subject to their own conditions.
8. Data quality, delays and provider faults
Data can become stale, incomplete or temporarily unavailable because of an upstream outage, connection problem or quality review. Retrieval time differs from observation time. The Service can display the last valid reading with an indication of staleness but should not suggest that it is a measurement taken at the current moment. Conflicting values should be compared using their units, geographic scope and calculation method. GeoLira cannot guarantee continuous availability of every external station. Safety-related uses require parallel consultation of appropriate official warnings rather than reliance on one widget or chart.
9. Evidence categories and symbolic interpretation
Scientific measurements, derived values, authored indices, voluntary self-reports and symbolic interpretations are distinct evidence categories. Showing them together does not establish causation. A text about a belief system can document a tradition without proving its claims about health effects or physical changes in the body. Provider marks must not be used to imply that organisations endorse every GeoLira interpretation. Users may report inaccurate attribution or contradictory explanations. Scientific assessment depends on real data, methods and limitations, not merely visual similarity between charts.
10. Reporting errors and corrections
A useful discrepancy report identifies the page, provider, record reference, observation time and the apparent difference. Passwords or private journal contents are not needed for an ordinary scientific-data correction. The team can inspect original provider documentation and, where justified, correct the presentation or withdraw an invalid data layer. A support response does not automatically change a scientific provider's source database or validate every claim made by the reporter. A correction that depends on a provider update should be distinguished from a local rendering error. Independent rights under data-protection and electronic-service rules remain available.