오른쪽 상단에는 GNSS 하드웨어 (HW) 비연속 개수 (GnssClock.getHardwareClockDiscontinuityCount)가 표시되며, 이 값은 듀티 사이클링의 사용 여부를 확인하는 데 도움이 됩니다. 이 카운터가 증가하면 GNSS 신호의 연속 관찰에 중단이 발생했음을 나타냅니다 (예: 듀티 사이클링 사용).
카드 아래에는 모든 측정의 집계 정보가 표시됩니다.
코드 유형 열에는 RINEX 4.01에 정의된 코드 유형을 사용하여 GNSS 신호의 정확한 유형이 표시됩니다. 예를 들어 코드 유형이 'C'인 GPS L1 신호는 RINEX 표의 3자리 코드에서 마지막 문자로 표시된 대로 L1 C/A를 나타냅니다. 마찬가지로 GPS L5 Q에는 'Q' 코드 유형이 있습니다. 참고로 이 문서 끝에 있는 다른 GNSS 컨스텔레이션의 표를 확인하세요.
Pseudo Range 열의 RINEX 관측 코드에서 마지막 세 글자는 GnssLogger의 측정값 화면에 표시되는 코드 유형 값입니다.
다음은 편의를 위해 RINEX 4.01 사양의 표입니다.
자세한 내용은 전체 사양을 참고하세요.
그림 4. 표 10: RINEX 버전 4.01 GPS 관측 코드그림 5. 표 11: RINEX 버전 4.01 GLONASS 관측 코드그림 6. 표 12: RINEX 버전 4.01 Galileo 관측 코드그림 7. 표 13: RINEX 버전 4.01 SBAS 관측 코드그림 8. 표 14: RINEX 버전 4.01 QZSS 관측 코드그림 9. 표 15: RINEX 버전 4.01 BDS 관측 코드그림 10. RINEX 버전 4.01 NavIC 관측 코드
이 페이지에 나와 있는 콘텐츠와 코드 샘플에는 콘텐츠 라이선스에서 설명하는 라이선스가 적용됩니다. 자바 및 OpenJDK는 Oracle 및 Oracle 계열사의 상표 또는 등록 상표입니다.
최종 업데이트: 2025-07-27(UTC)
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-27(UTC)"],[],[],null,["# Analyze raw measurements with GnssLogger\n\nWith GnssLogger v3.1, users can view and analyze raw GNSS data on the\n**Measurements** screen.\n\nHere is the **Measurements** screen, followed by a few tips\nand tricks to make the most out of this data:\n**Figure 1.** Measurements screen\n\nIn the top card:\n\n- The top left shows the GNSS clock data (corresponding to [`GnssClock`](/reference/android/location/GnssClock)).\n- The top right shows the count of GNSS hardware (HW) discontinuities (from [`GnssClock.getHardwareClockDiscontinuityCount`](/reference/android/location/GnssClock#getHardwareClockDiscontinuityCount%28%29)), which helps determine if duty-cycling is on or off. When this counter increments, it indicates that there was a disruption in the continuous observation of GNSS signals (e.g., [duty-cycling](https://barbeau.medium.com/gnss-interrupted-the-hidden-android-setting-you-need-to-know-d812d28a3821) is on). Further down, the card displays aggregate information for all measurements:\n - **# valid measurements** --- For a measurement to be considered valid, the [`STATE_CODE_LOCK`](/reference/android/location/GnssMeasurement#STATE_CODE_LOCK) and [`STATE_TOW_KNOWN`](/reference/android/location/GnssMeasurement#STATE_TOW_KNOWN) or [`STATE_TOW_DECODED`](/reference/android/location/GnssMeasurement#STATE_TOW_DECODED)) flags must be set in [`GnssMeasurement.getState`](/reference/android/location/GnssMeasurement#getState%28%29)().\n - **# usable accumulated delta range (ADR) --- For** ADR, or carrier phase, to be considered usable for positioning, the [`ADR_STATE_VALID`](/reference/android/location/GnssMeasurement#ADR_STATE_VALID) flag must be set and neither the [`ADR_STATE_RESET`](/reference/android/location/GnssMeasurement#ADR_STATE_RESET) nor the [`ADR_STATE_CYCLE_SLIP`](/reference/android/location/GnssMeasurement#ADR_STATE_CYCLE_SLIP) flags can be set in [`GnssMeasurement.getAccumulatedDeltaRangeState`](/reference/android/location/GnssMeasurement#getAccumulatedDeltaRangeState%28%29)().\n\nIf your device always reports 0 usable ADR, even when in open sky with\nduty-cycling disabled, that's a good indication that your\ndevice doesn't support carrier phase measurements that can be used for\nhigh-accuracy GNSS.\n\nIn the bottom card, each row represents an individual [`GnssMeasurement`](/reference/android/location/GnssMeasurement).\n\n- The **Code type** column shows the exact type of GNSS signal using the code types defined in [RINEX 4.01](https://www.igs.org/wg/rinex/). For example, the GPS L1 signals with code type \"C\", represent L1 C/A, as indicated by the last letter in the three character code in the RINEX tables. GPS L5 Q would similarly have a \"Q\" code type. See the tables for other GNSS constellations at the end of this document for reference.\n- In the **Rx SV Time (ns)** column, the text is green if the measurement is valid.\n- In the **State column** , the state is also green if the measurement is valid. State shows a human-readable version of the bitwise flags that are set in the [GnssMeasurement.getState()](/reference/android/location/GnssMeasurement#getState%28%29) field.\n\nProvide feedback on new features using our\n[public issue tracker](https://issuetracker.google.com/issues/new?component=313183&template=0).\n\n**Table 10 : RINEX Version 4.01 GPS Observation Codes**\n\nFor each measurement, the \"Code Type\" shown is the last letter of the \"Pseudo\nRange\" value defined in the RINEX 4.01 specification for the relevant GNSS\nsystem and carrier frequency. For example, \"C\" is used for GPS L1\n\\[C/A\\] while \"Q\" is used for GPS L5 Q.\n**Figure 2.** Table 10: RINEX Version 4.01 GPS Observation Codes\n\nUsers can scroll to the right to see additional columns for each measurement:\n**Figure 3.** Additional columns on the Measurements screen in Table 10.\n\n- **PRR** is the Pseudo Range Rate in meters per second from [GnssMeasurement.getPseudorangeRateMetersPerSecond()](/reference/android/location/GnssMeasurement#getPseudorangeRateMetersPerSecond())\n- The **ADR State** column shows the human-readable version of the bitwise flags set in the [GnssMeasurement.getAccumulatedDeltaRangeState()](/reference/android/location/GnssMeasurement#getAccumulatedDeltaRangeState%28%29) column. If the ADR is usable for positioning, the text in the **ADR (m)** and **ADR State** fields is green.\n\nRINEX 4.01 observation codes\n----------------------------\n\nThe last of the three letters in the RINEX observation codes in the Pseudo Range\ncolumn is the **Code type** value shown on the **Measurements** screen in\nGnssLogger.\n\nFollowing are tables from the [RINEX 4.01 spec](https://www.igs.org/wg/rinex/) for convenience.\nSee the full specification for details.\n**Figure 4.** Table 10: RINEX Version 4.01 GPS Observation Codes **Figure 5.** Table 11: RINEX Version 4.01 GLONASS Observation Codes **Figure 6.** Table 12: RINEX Version 4.01 Galileo Observation Codes **Figure 7.** Table 13: RINEX Version 4.01 SBAS Observation Codes **Figure 8.** Table 14: RINEX Version 4.01 QZSS Observation Codes **Figure 9.** Table 15: RINEX Version 4.01 BDS Observation Codes **Figure 10.** RINEX Version 4.01 NavIC Observation Codes"]]
