![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1314380%2F4de51f246065113b9aa3c0a83d01dfc6%2FScreen%20Shot%202020-03-04%20at%2011.00.19%20AM.png?generation=1583345166597971&alt=media\")
Hi all,
\n\nI was wondering what the timestamps in the Sentinel-5P file names represent.
\n\nFor example: s5p_no2_20180701T161259_20180707T175356
Is that the time span of the sampling, i.e. measurements were taken between 2018-07-01 and 2018-07-07? And if so, are the values in such a file averaged for that time span?
", "messages": [ { "id": 747670, "postDate": "2020-02-16T17:57:27.983Z", "content": "I think that the first date is when the data was acquired and the second date is when the image was processed. I'll come back and edit this comment if it turns out that is incorrect.
\n\nYou can read more about the Sentinel-5p naming conventions here and here.
", "rawMarkdown": "I think that the first date is when the data was acquired and the second date is when the image was processed. I'll come back and edit this comment if it turns out that is incorrect. \n\n\nYou can read more about the Sentinel-5p naming conventions [here](https://sentinel.esa.int/documents/247904/2474726/Sentinel-5P-Level-2-Product-User-Manual-Nitrogen-Dioxide) and [here](https://developers.google.com/earth-engine/datasets/catalog/COPERNICUS_S5P_OFFL_L3_NO2).", "votes": 2, "replies": [ { "id": 747703, "postDate": "2020-02-16T18:30:11.017Z", "content": "Thanks for the clarification!
", "rawMarkdown": "Thanks for the clarification!", "votes": 1 }, { "id": 751953, "postDate": "2020-02-20T17:03:56.977Z", "content": "Just looping back to confirm that, yes, the first date is the actual capture time of the satellite in UTC, whereas the second date is the date that the raw satellite data was turned into a product that you could place on a map. Most users can ignore everything but the capture time -- the data is captured essentially instantly at the timestamp indicated by the first date in the filename.
\n\nHere are some additional details about the naming conventions that are used by the satellite operator https://sentinel.esa.int/documents/247904/685211/Sentinel-2-Product-Specifications-Document
", "rawMarkdown": "Just looping back to confirm that, yes, the first date is the actual capture time of the satellite in UTC, whereas the second date is the date that the raw satellite data was turned into a product that you could place on a map. Most users can ignore everything but the capture time -- the data is captured essentially instantly at the timestamp indicated by the first date in the filename.\n\nHere are some additional details about the naming conventions that are used by the satellite operator https://sentinel.esa.int/documents/247904/685211/Sentinel-2-Product-Specifications-Document" } ] }, { "id": 747158, "postDate": "2020-02-16T03:35:31.580Z", "content": "I believe it is the two satellite passes that generated the data. Polar orbits require two passes and are about 90 minutes apart.
\n\nBut did find info on the Sentinel 2 where the naming convention was time of image capture and time the data was processed.
\n\nSo not real sure but ….
", "rawMarkdown": "I believe it is the two satellite passes that generated the data. Polar orbits require two passes and are about 90 minutes apart. \n\nBut did find info on the Sentinel 2 where the naming convention was time of image capture and time the data was processed.\n\nSo not real sure but ….", "votes": 2 }, { "id": 763639, "postDate": "2020-03-04T17:25:04.293Z", "content": "Hey guys,\nI saw that Puerto Rico is UTC -4h. According to this page https://sentinel.esa.int/web/sentinel/missions/sentinel-5p/orbit and this one https://sentinel.esa.int/web/sentinel/missions/sentinel-5p/geographical-coverage, the satellite should get image near 13:30. However, time in the most of data is between 16 and 17. It means that it passes between 12 and 13. Did you get why?
", "rawMarkdown": "Hey guys,\nI saw that Puerto Rico is UTC -4h. According to this page https://sentinel.esa.int/web/sentinel/missions/sentinel-5p/orbit and this one https://sentinel.esa.int/web/sentinel/missions/sentinel-5p/geographical-coverage, the satellite should get image near 13:30. However, time in the most of data is between 16 and 17. It means that it passes between 12 and 13. Did you get why?", "replies": [ { "id": 763671, "postDate": "2020-03-04T18:07:43.913Z", "content": "Timestamps are in UTC.
\n\nThe Sentinel-5p satellite operates in a Sun-synchronous orbit with a Local Time of Ascending Node of 13:30 local time (Source: Wikipedia.org). For Puerto Rico this would mean that images are acquired on average at approximately 17:30 UTC -- which is not too far off from the actual average of 17:00 UTC.
\n\n
Hopefully that helps!
", "rawMarkdown": "Timestamps are in UTC.\n\nThe Sentinel-5p satellite operates in a Sun-synchronous orbit with a Local Time of Ascending Node of 13:30 local time (Source: [Wikipedia.org](https://en.wikipedia.org/wiki/Sentinel-5_Precursor)). For Puerto Rico this would mean that images are acquired on average at approximately 17:30 UTC -- which is not too far off from the actual average of 17:00 UTC. \n\n\n\nHopefully that helps!\n" } ] }, { "id": 747137, "postDate": "2020-02-16T02:28:00.243Z", "content": "Hi all,
\n\nI was wondering what the timestamps in the Sentinel-5P file names represent.
\n\nFor example: s5p_no2_20180701T161259_20180707T175356
Is that the time span of the sampling, i.e. measurements were taken between 2018-07-01 and 2018-07-07? And if so, are the values in such a file averaged for that time span?
", "rawMarkdown": "Hi all,\n\nI was wondering what the timestamps in the Sentinel-5P file names represent.\n\nFor example: `s5p_no2_20180701T161259_20180707T175356`\n\nIs that the time span of the sampling, i.e. measurements were taken between 2018-07-01 and 2018-07-07? And if so, are the values in such a file averaged for that time span?" }, { "id": 747168, "postDate": "2020-02-16T04:04:03.497Z", "rawMarkdown": "", "isDeleted": true } ], "comments": [ { "id": 747670, "author_name": "Paul Mooney", "author_url": "", "post_date": "2020-02-16T17:57:27.983000", "content": "I think that the first date is when the data was acquired and the second date is when the image was processed. I'll come back and edit this comment if it turns out that is incorrect.
\n\nYou can read more about the Sentinel-5p naming conventions here and here.
", "votes": 2, "replies": [ { "id": 747703, "author_name": "Markus", "author_url": "", "post_date": "2020-02-16T18:30:11.017000", "content": "Thanks for the clarification!
", "votes": 1, "replies": [] }, { "id": 751953, "author_name": "Paul Mooney", "author_url": "", "post_date": "2020-02-20T17:03:56.977000", "content": "Just looping back to confirm that, yes, the first date is the actual capture time of the satellite in UTC, whereas the second date is the date that the raw satellite data was turned into a product that you could place on a map. Most users can ignore everything but the capture time -- the data is captured essentially instantly at the timestamp indicated by the first date in the filename.
\n\nHere are some additional details about the naming conventions that are used by the satellite operator https://sentinel.esa.int/documents/247904/685211/Sentinel-2-Product-Specifications-Document
", "votes": 0, "replies": [] } ] }, { "id": 747158, "author_name": "PC Jimmmy", "author_url": "", "post_date": "2020-02-16T03:35:31.580000", "content": "I believe it is the two satellite passes that generated the data. Polar orbits require two passes and are about 90 minutes apart.
\n\nBut did find info on the Sentinel 2 where the naming convention was time of image capture and time the data was processed.
\n\nSo not real sure but ….
", "votes": 2, "replies": [] }, { "id": 763639, "author_name": "Viktoriia Kobenko", "author_url": "", "post_date": "2020-03-04T17:25:04.293000", "content": "Hey guys,\nI saw that Puerto Rico is UTC -4h. According to this page https://sentinel.esa.int/web/sentinel/missions/sentinel-5p/orbit and this one https://sentinel.esa.int/web/sentinel/missions/sentinel-5p/geographical-coverage, the satellite should get image near 13:30. However, time in the most of data is between 16 and 17. It means that it passes between 12 and 13. Did you get why?
", "votes": 0, "replies": [ { "id": 763671, "author_name": "Paul Mooney", "author_url": "", "post_date": "2020-03-04T18:07:43.913000", "content": "Timestamps are in UTC.
\n\nThe Sentinel-5p satellite operates in a Sun-synchronous orbit with a Local Time of Ascending Node of 13:30 local time (Source: Wikipedia.org). For Puerto Rico this would mean that images are acquired on average at approximately 17:30 UTC -- which is not too far off from the actual average of 17:00 UTC.
\n\n
Hopefully that helps!
", "votes": 0, "replies": [] } ] }, { "id": 747168, "author_name": "", "author_url": "", "post_date": "2020-02-16T04:04:03.497000", "content": "", "votes": 0, "replies": [] } ], "raw_markdown_by_id": { "747670": "I think that the first date is when the data was acquired and the second date is when the image was processed. I'll come back and edit this comment if it turns out that is incorrect. \n\n\nYou can read more about the Sentinel-5p naming conventions [here](https://sentinel.esa.int/documents/247904/2474726/Sentinel-5P-Level-2-Product-User-Manual-Nitrogen-Dioxide) and [here](https://developers.google.com/earth-engine/datasets/catalog/COPERNICUS_S5P_OFFL_L3_NO2).", "747158": "I believe it is the two satellite passes that generated the data. Polar orbits require two passes and are about 90 minutes apart. \n\nBut did find info on the Sentinel 2 where the naming convention was time of image capture and time the data was processed.\n\nSo not real sure but ….", "763639": "Hey guys,\nI saw that Puerto Rico is UTC -4h. According to this page https://sentinel.esa.int/web/sentinel/missions/sentinel-5p/orbit and this one https://sentinel.esa.int/web/sentinel/missions/sentinel-5p/geographical-coverage, the satellite should get image near 13:30. However, time in the most of data is between 16 and 17. It means that it passes between 12 and 13. Did you get why?", "747137": "Hi all,\n\nI was wondering what the timestamps in the Sentinel-5P file names represent.\n\nFor example: `s5p_no2_20180701T161259_20180707T175356`\n\nIs that the time span of the sampling, i.e. measurements were taken between 2018-07-01 and 2018-07-07? And if so, are the values in such a file averaged for that time span?", "747168": "" } }