{ "id": 238658, "title": "Noisy data filtering examples by the data provider", "url": "/competitions/google-smartphone-decimeter-challenge/discussion/238658", "author_name": "jeong", "post_date": "2021-05-13T01:24:28.074000", "votes": 8, "comment_count": 0, "views": 0, "content": "

In addition to the filtering rules shared by @sohier here, we can find additional filtering rules from the slides shared by the data provider (new ones are highlighted):

\n
\n

Measurements from GNSS chipsets of mobile phones are often noisier and more erroneous. Example of filters your can apply (to exclude) are:

\n
    \n
  1. Full bias nanoseconds is zero or invalid
    2. \n
  2. BiasUncertaintyNanos too large
    3. \n
  3. Arrival time is negative or unrealistically large
    4. \n
  4. Unknown constellation
    5. \n
  5. TimeNanos is empty
    6. \n
  6. State is not STATE_TOW_DECODED
    7. \n
  7. ReceivedSvTimeUncertaintyNanos is high
    8. \n
  8. AdrState violating this condition: ADR_STATE_VALID == 1 & ADR_STATE_RESET == 0 & ADR_STATE_CYCLE_SLIP == 0
    9. \n
  9. AdrUncertaintyMeters is high
    10. \n
\n
\n

Hope it helps.

", "messages": [ { "id": 1304903, "postDate": "2021-05-13T01:24:28.073Z", "content": "

In addition to the filtering rules shared by @sohier here, we can find additional filtering rules from the slides shared by the data provider (new ones are highlighted):

\n
\n

Measurements from GNSS chipsets of mobile phones are often noisier and more erroneous. Example of filters your can apply (to exclude) are:

\n
    \n
  1. Full bias nanoseconds is zero or invalid
    2. \n
  2. BiasUncertaintyNanos too large
    3. \n
  3. Arrival time is negative or unrealistically large
    4. \n
  4. Unknown constellation
    5. \n
  5. TimeNanos is empty
    6. \n
  6. State is not STATE_TOW_DECODED
    7. \n
  7. ReceivedSvTimeUncertaintyNanos is high
    8. \n
  8. AdrState violating this condition: ADR_STATE_VALID == 1 & ADR_STATE_RESET == 0 & ADR_STATE_CYCLE_SLIP == 0
    9. \n
  9. AdrUncertaintyMeters is high
    10. \n
\n
\n

Hope it helps.

", "rawMarkdown": "In addition to the filtering rules shared by @sohier [here](https://www.kaggle.com/c/google-smartphone-decimeter-challenge/discussion/238583), we can find additional filtering rules from the [slides](https://www.kaggle.com/google/android-smartphones-high-accuracy-datasets?select=ION+GNSS+2020+Slides+Android+Raw+GNSS+Measurement+Datasets+for+Precise+Positioning.pdf) shared by the data provider (new ones are highlighted):\n\n> Measurements from GNSS chipsets of mobile phones are often noisier and more erroneous. Example of filters your can apply (to exclude) are:\n1. Full bias nanoseconds is zero or invalid\n2. `BiasUncertaintyNanos` too large\n3. Arrival time is negative or unrealistically large\n4. **Unknown constellation**\n5. `TimeNanos` is empty\n6. `State` is not `STATE_TOW_DECODED`\n7. `ReceivedSvTimeUncertaintyNanos` is high\n8. **`AdrState` violating this condition: `ADR_STATE_VALID == 1 & ADR_STATE_RESET == 0 & ADR_STATE_CYCLE_SLIP == 0`**\n9. **`AdrUncertaintyMeters` is high**\n\nHope it helps.", "votes": 7 } ], "comments": [], "raw_markdown_by_id": { "1304903": "In addition to the filtering rules shared by @sohier [here](https://www.kaggle.com/c/google-smartphone-decimeter-challenge/discussion/238583), we can find additional filtering rules from the [slides](https://www.kaggle.com/google/android-smartphones-high-accuracy-datasets?select=ION+GNSS+2020+Slides+Android+Raw+GNSS+Measurement+Datasets+for+Precise+Positioning.pdf) shared by the data provider (new ones are highlighted):\n\n> Measurements from GNSS chipsets of mobile phones are often noisier and more erroneous. Example of filters your can apply (to exclude) are:\n1. Full bias nanoseconds is zero or invalid\n2. `BiasUncertaintyNanos` too large\n3. Arrival time is negative or unrealistically large\n4. **Unknown constellation**\n5. `TimeNanos` is empty\n6. `State` is not `STATE_TOW_DECODED`\n7. `ReceivedSvTimeUncertaintyNanos` is high\n8. **`AdrState` violating this condition: `ADR_STATE_VALID == 1 & ADR_STATE_RESET == 0 & ADR_STATE_CYCLE_SLIP == 0`**\n9. **`AdrUncertaintyMeters` is high**\n\nHope it helps." } }