How big is a MODIS 250m pixel in reality?How to mosaic multiple MODIS images of Multiple months using MRT tool?How to reproject MODIS L2 data with lat/lonHow to remove cloudy pixel from MODIS NDVI (MOD13Q1)How can I create a polygon(filled polygon) from a single pixel stored in a hdf file(MODIS)?Issue with mapping MODIS SIN grid to EASE 2.0 with gdalwarpHow to mosaic multiple modis tiles of several dates using mrt tool?MODIS Landsat overlappingMODIS R Connection errorChange pixel size of MODIS in GEEMODIS 04_L2 projection transformation

Did Ender ever learn that he killed Stilson and/or Bonzo?

How to terminate ping <dest> &

How to create the Curved texte?

Look at your watch and tell me what time is it. vs Look at your watch and tell me what time it is

Python if-else code style for reduced code for rounding floats

What options are left, if Britain cannot decide?

How to use deus ex machina safely?

Why did it take so long to abandon sail after steamships were demonstrated?

Professor being mistaken for a grad student

How to deal with taxi scam when on vacation?

Gantt Chart like rectangles with log scale

Life insurance that covers only simultaneous/dual deaths

How difficult is it to simply disable/disengage the MCAS on Boeing 737 Max 8 & 9 Aircraft?

how to draw discrete time diagram in tikz

Define, (actually define) the "stability" and "energy" of a compound

How to explain that I do not want to visit a country due to personal safety concern?

Instead of Universal Basic Income, why not Universal Basic NEEDS?

Use void Apex method in Lightning Web Component

Why doesn't the EU now just force the UK to choose between referendum and no-deal?

How to simplify this time periods definition interface?

Do I need to be arrogant to get ahead?

Why do Australian milk farmers need to protest supermarkets' milk price?

How can I track script which gives me "command not found" right after the login?

My adviser wants to be the first author



How big is a MODIS 250m pixel in reality?


How to mosaic multiple MODIS images of Multiple months using MRT tool?How to reproject MODIS L2 data with lat/lonHow to remove cloudy pixel from MODIS NDVI (MOD13Q1)How can I create a polygon(filled polygon) from a single pixel stored in a hdf file(MODIS)?Issue with mapping MODIS SIN grid to EASE 2.0 with gdalwarpHow to mosaic multiple modis tiles of several dates using mrt tool?MODIS Landsat overlappingMODIS R Connection errorChange pixel size of MODIS in GEEMODIS 04_L2 projection transformation













1















How big is a MODIS 250m pixel in reality?



This appears to be a question that contains its own answer, but I have several reasons to doubt that the pixel size is actually 250m x 250m:



  1. I downloaded MODIS 250m NDVI data from the USGS site, transformed it from Sin to Geographic (SRID 4326) using the MODIS Reprojection Tool (which has since been replaced, but at the time was the official tool).

  2. Using gdalinfo on the resulting file gives the pixel size as (0.002884053983564 X 0.002884053983564). I assume that this measurement is in decimal degrees.

  3. This online calculator gives the length of one degree of latitude at the latitude of my study area as 111,092.7 m, and of longitude as 81,540.9 m. That would make the pixel dimensions 320m in the N-S direction and 235m in the E-W direction.

  4. I've overlaid the NDVI image onto other data, and the two correspond; for example you can clearly see greener vegetation along rivers. This wouldn't happen if they were misaligned or mis-projected.

  5. I can also measure the size of a pixel using QGIS's measurement tool, and the length comes out to about 320 x 235 m, i.e., it agrees with the file metadata.

I have read the documentation and found a few suspicious references in published papers to things like "nominal" pixel size of 250 m, or pixel size of 250 m "at nadir", and this paper makes it look to me as if the physical camera/mirror apparatus would result in pixels that aren't 250m x 250m square, but the authors don't describe in detail the projection and/or transformation used to create the data products so I'm not sure.










share|improve this question




























    1















    How big is a MODIS 250m pixel in reality?



    This appears to be a question that contains its own answer, but I have several reasons to doubt that the pixel size is actually 250m x 250m:



    1. I downloaded MODIS 250m NDVI data from the USGS site, transformed it from Sin to Geographic (SRID 4326) using the MODIS Reprojection Tool (which has since been replaced, but at the time was the official tool).

    2. Using gdalinfo on the resulting file gives the pixel size as (0.002884053983564 X 0.002884053983564). I assume that this measurement is in decimal degrees.

    3. This online calculator gives the length of one degree of latitude at the latitude of my study area as 111,092.7 m, and of longitude as 81,540.9 m. That would make the pixel dimensions 320m in the N-S direction and 235m in the E-W direction.

    4. I've overlaid the NDVI image onto other data, and the two correspond; for example you can clearly see greener vegetation along rivers. This wouldn't happen if they were misaligned or mis-projected.

    5. I can also measure the size of a pixel using QGIS's measurement tool, and the length comes out to about 320 x 235 m, i.e., it agrees with the file metadata.

    I have read the documentation and found a few suspicious references in published papers to things like "nominal" pixel size of 250 m, or pixel size of 250 m "at nadir", and this paper makes it look to me as if the physical camera/mirror apparatus would result in pixels that aren't 250m x 250m square, but the authors don't describe in detail the projection and/or transformation used to create the data products so I'm not sure.










    share|improve this question


























      1












      1








      1


      1






      How big is a MODIS 250m pixel in reality?



      This appears to be a question that contains its own answer, but I have several reasons to doubt that the pixel size is actually 250m x 250m:



      1. I downloaded MODIS 250m NDVI data from the USGS site, transformed it from Sin to Geographic (SRID 4326) using the MODIS Reprojection Tool (which has since been replaced, but at the time was the official tool).

      2. Using gdalinfo on the resulting file gives the pixel size as (0.002884053983564 X 0.002884053983564). I assume that this measurement is in decimal degrees.

      3. This online calculator gives the length of one degree of latitude at the latitude of my study area as 111,092.7 m, and of longitude as 81,540.9 m. That would make the pixel dimensions 320m in the N-S direction and 235m in the E-W direction.

      4. I've overlaid the NDVI image onto other data, and the two correspond; for example you can clearly see greener vegetation along rivers. This wouldn't happen if they were misaligned or mis-projected.

      5. I can also measure the size of a pixel using QGIS's measurement tool, and the length comes out to about 320 x 235 m, i.e., it agrees with the file metadata.

      I have read the documentation and found a few suspicious references in published papers to things like "nominal" pixel size of 250 m, or pixel size of 250 m "at nadir", and this paper makes it look to me as if the physical camera/mirror apparatus would result in pixels that aren't 250m x 250m square, but the authors don't describe in detail the projection and/or transformation used to create the data products so I'm not sure.










      share|improve this question
















      How big is a MODIS 250m pixel in reality?



      This appears to be a question that contains its own answer, but I have several reasons to doubt that the pixel size is actually 250m x 250m:



      1. I downloaded MODIS 250m NDVI data from the USGS site, transformed it from Sin to Geographic (SRID 4326) using the MODIS Reprojection Tool (which has since been replaced, but at the time was the official tool).

      2. Using gdalinfo on the resulting file gives the pixel size as (0.002884053983564 X 0.002884053983564). I assume that this measurement is in decimal degrees.

      3. This online calculator gives the length of one degree of latitude at the latitude of my study area as 111,092.7 m, and of longitude as 81,540.9 m. That would make the pixel dimensions 320m in the N-S direction and 235m in the E-W direction.

      4. I've overlaid the NDVI image onto other data, and the two correspond; for example you can clearly see greener vegetation along rivers. This wouldn't happen if they were misaligned or mis-projected.

      5. I can also measure the size of a pixel using QGIS's measurement tool, and the length comes out to about 320 x 235 m, i.e., it agrees with the file metadata.

      I have read the documentation and found a few suspicious references in published papers to things like "nominal" pixel size of 250 m, or pixel size of 250 m "at nadir", and this paper makes it look to me as if the physical camera/mirror apparatus would result in pixels that aren't 250m x 250m square, but the authors don't describe in detail the projection and/or transformation used to create the data products so I'm not sure.







      remote-sensing modis pixel modis-reprojection-tool cell-size






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 40 mins ago









      Aaron

      38.2k20109254




      38.2k20109254










      asked 4 hours ago









      JohnJohn

      887




      887




















          1 Answer
          1






          active

          oldest

          votes


















          4














          Per https://lpdaac.usgs.gov/dataset_discovery/modis, the viewing swath width of MODIS is 2,330 km, thus a large portion of the image is off-nadir in some way. https://modis.gsfc.nasa.gov/about/specifications.php



          The following forum post gives an explanation of how to calculate pixel size based on viewing position. (Note: still an estimate due to factors outlined in the post)
          https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=2018




          Compute the scan angle, S (in radians), given pixel number:



          S = (I-hp)/H


          where:



           I is the zero-based pixel index
          hp is 1/2 the total number of pixels (zero-based) (for MODIS each scan is 1354 "1km" pixels, 1353 zero-based, so hp = 676.5)
          H is the sensor altitude divided by the pixel size (for MODIS altitude is approximately 700km, so for "1km" pixels, H = 700/1)

          For 500m pixels, hp = 1353, H = 1400 (700/0.5)
          For 250m pixels, hp = 2706, H = 2800 (700/0.25)


          Compute the zenith angle:



          Z = asin(1.111*sin(S)) 


          where Z is the zenith angle.



          Compute the Along-track pixel size:



          Pt = Pn*9*sin(Z-S)/sin(S)


          where Pn is the nadir pixel size (e.g. 1km, 0.5km, 0.25km)



          Compute the Along-scan pixel size:



          Ps = Pt/cos(Z)


          Thus, area is ~ Pt * Ps




          Additional information can be found at https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=277






          share|improve this answer

























          • Excellent answer; these equations are very useful.

            – John
            2 hours ago











          • The equations show that the pixel size varies with pixel position relative to the center of the satellite path, but they do not show size varying with latitude. Am I right to assume that these equations hold everywhere, e.g., even over the poles? If I'm envisioning it correctly, there must be much more overlap between successive passes at the poles than at the equator, meaning that a given location on earth might have different pixel widths in successive passes (i.e., up near the pole it might be close to the center of the path on one pass, further on another).

            – John
            2 hours ago










          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "79"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f315691%2fhow-big-is-a-modis-250m-pixel-in-reality%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          4














          Per https://lpdaac.usgs.gov/dataset_discovery/modis, the viewing swath width of MODIS is 2,330 km, thus a large portion of the image is off-nadir in some way. https://modis.gsfc.nasa.gov/about/specifications.php



          The following forum post gives an explanation of how to calculate pixel size based on viewing position. (Note: still an estimate due to factors outlined in the post)
          https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=2018




          Compute the scan angle, S (in radians), given pixel number:



          S = (I-hp)/H


          where:



           I is the zero-based pixel index
          hp is 1/2 the total number of pixels (zero-based) (for MODIS each scan is 1354 "1km" pixels, 1353 zero-based, so hp = 676.5)
          H is the sensor altitude divided by the pixel size (for MODIS altitude is approximately 700km, so for "1km" pixels, H = 700/1)

          For 500m pixels, hp = 1353, H = 1400 (700/0.5)
          For 250m pixels, hp = 2706, H = 2800 (700/0.25)


          Compute the zenith angle:



          Z = asin(1.111*sin(S)) 


          where Z is the zenith angle.



          Compute the Along-track pixel size:



          Pt = Pn*9*sin(Z-S)/sin(S)


          where Pn is the nadir pixel size (e.g. 1km, 0.5km, 0.25km)



          Compute the Along-scan pixel size:



          Ps = Pt/cos(Z)


          Thus, area is ~ Pt * Ps




          Additional information can be found at https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=277






          share|improve this answer

























          • Excellent answer; these equations are very useful.

            – John
            2 hours ago











          • The equations show that the pixel size varies with pixel position relative to the center of the satellite path, but they do not show size varying with latitude. Am I right to assume that these equations hold everywhere, e.g., even over the poles? If I'm envisioning it correctly, there must be much more overlap between successive passes at the poles than at the equator, meaning that a given location on earth might have different pixel widths in successive passes (i.e., up near the pole it might be close to the center of the path on one pass, further on another).

            – John
            2 hours ago















          4














          Per https://lpdaac.usgs.gov/dataset_discovery/modis, the viewing swath width of MODIS is 2,330 km, thus a large portion of the image is off-nadir in some way. https://modis.gsfc.nasa.gov/about/specifications.php



          The following forum post gives an explanation of how to calculate pixel size based on viewing position. (Note: still an estimate due to factors outlined in the post)
          https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=2018




          Compute the scan angle, S (in radians), given pixel number:



          S = (I-hp)/H


          where:



           I is the zero-based pixel index
          hp is 1/2 the total number of pixels (zero-based) (for MODIS each scan is 1354 "1km" pixels, 1353 zero-based, so hp = 676.5)
          H is the sensor altitude divided by the pixel size (for MODIS altitude is approximately 700km, so for "1km" pixels, H = 700/1)

          For 500m pixels, hp = 1353, H = 1400 (700/0.5)
          For 250m pixels, hp = 2706, H = 2800 (700/0.25)


          Compute the zenith angle:



          Z = asin(1.111*sin(S)) 


          where Z is the zenith angle.



          Compute the Along-track pixel size:



          Pt = Pn*9*sin(Z-S)/sin(S)


          where Pn is the nadir pixel size (e.g. 1km, 0.5km, 0.25km)



          Compute the Along-scan pixel size:



          Ps = Pt/cos(Z)


          Thus, area is ~ Pt * Ps




          Additional information can be found at https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=277






          share|improve this answer

























          • Excellent answer; these equations are very useful.

            – John
            2 hours ago











          • The equations show that the pixel size varies with pixel position relative to the center of the satellite path, but they do not show size varying with latitude. Am I right to assume that these equations hold everywhere, e.g., even over the poles? If I'm envisioning it correctly, there must be much more overlap between successive passes at the poles than at the equator, meaning that a given location on earth might have different pixel widths in successive passes (i.e., up near the pole it might be close to the center of the path on one pass, further on another).

            – John
            2 hours ago













          4












          4








          4







          Per https://lpdaac.usgs.gov/dataset_discovery/modis, the viewing swath width of MODIS is 2,330 km, thus a large portion of the image is off-nadir in some way. https://modis.gsfc.nasa.gov/about/specifications.php



          The following forum post gives an explanation of how to calculate pixel size based on viewing position. (Note: still an estimate due to factors outlined in the post)
          https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=2018




          Compute the scan angle, S (in radians), given pixel number:



          S = (I-hp)/H


          where:



           I is the zero-based pixel index
          hp is 1/2 the total number of pixels (zero-based) (for MODIS each scan is 1354 "1km" pixels, 1353 zero-based, so hp = 676.5)
          H is the sensor altitude divided by the pixel size (for MODIS altitude is approximately 700km, so for "1km" pixels, H = 700/1)

          For 500m pixels, hp = 1353, H = 1400 (700/0.5)
          For 250m pixels, hp = 2706, H = 2800 (700/0.25)


          Compute the zenith angle:



          Z = asin(1.111*sin(S)) 


          where Z is the zenith angle.



          Compute the Along-track pixel size:



          Pt = Pn*9*sin(Z-S)/sin(S)


          where Pn is the nadir pixel size (e.g. 1km, 0.5km, 0.25km)



          Compute the Along-scan pixel size:



          Ps = Pt/cos(Z)


          Thus, area is ~ Pt * Ps




          Additional information can be found at https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=277






          share|improve this answer















          Per https://lpdaac.usgs.gov/dataset_discovery/modis, the viewing swath width of MODIS is 2,330 km, thus a large portion of the image is off-nadir in some way. https://modis.gsfc.nasa.gov/about/specifications.php



          The following forum post gives an explanation of how to calculate pixel size based on viewing position. (Note: still an estimate due to factors outlined in the post)
          https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=2018




          Compute the scan angle, S (in radians), given pixel number:



          S = (I-hp)/H


          where:



           I is the zero-based pixel index
          hp is 1/2 the total number of pixels (zero-based) (for MODIS each scan is 1354 "1km" pixels, 1353 zero-based, so hp = 676.5)
          H is the sensor altitude divided by the pixel size (for MODIS altitude is approximately 700km, so for "1km" pixels, H = 700/1)

          For 500m pixels, hp = 1353, H = 1400 (700/0.5)
          For 250m pixels, hp = 2706, H = 2800 (700/0.25)


          Compute the zenith angle:



          Z = asin(1.111*sin(S)) 


          where Z is the zenith angle.



          Compute the Along-track pixel size:



          Pt = Pn*9*sin(Z-S)/sin(S)


          where Pn is the nadir pixel size (e.g. 1km, 0.5km, 0.25km)



          Compute the Along-scan pixel size:



          Ps = Pt/cos(Z)


          Thus, area is ~ Pt * Ps




          Additional information can be found at https://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=277







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 3 hours ago

























          answered 3 hours ago









          smillersmiller

          2,134217




          2,134217












          • Excellent answer; these equations are very useful.

            – John
            2 hours ago











          • The equations show that the pixel size varies with pixel position relative to the center of the satellite path, but they do not show size varying with latitude. Am I right to assume that these equations hold everywhere, e.g., even over the poles? If I'm envisioning it correctly, there must be much more overlap between successive passes at the poles than at the equator, meaning that a given location on earth might have different pixel widths in successive passes (i.e., up near the pole it might be close to the center of the path on one pass, further on another).

            – John
            2 hours ago

















          • Excellent answer; these equations are very useful.

            – John
            2 hours ago











          • The equations show that the pixel size varies with pixel position relative to the center of the satellite path, but they do not show size varying with latitude. Am I right to assume that these equations hold everywhere, e.g., even over the poles? If I'm envisioning it correctly, there must be much more overlap between successive passes at the poles than at the equator, meaning that a given location on earth might have different pixel widths in successive passes (i.e., up near the pole it might be close to the center of the path on one pass, further on another).

            – John
            2 hours ago
















          Excellent answer; these equations are very useful.

          – John
          2 hours ago





          Excellent answer; these equations are very useful.

          – John
          2 hours ago













          The equations show that the pixel size varies with pixel position relative to the center of the satellite path, but they do not show size varying with latitude. Am I right to assume that these equations hold everywhere, e.g., even over the poles? If I'm envisioning it correctly, there must be much more overlap between successive passes at the poles than at the equator, meaning that a given location on earth might have different pixel widths in successive passes (i.e., up near the pole it might be close to the center of the path on one pass, further on another).

          – John
          2 hours ago





          The equations show that the pixel size varies with pixel position relative to the center of the satellite path, but they do not show size varying with latitude. Am I right to assume that these equations hold everywhere, e.g., even over the poles? If I'm envisioning it correctly, there must be much more overlap between successive passes at the poles than at the equator, meaning that a given location on earth might have different pixel widths in successive passes (i.e., up near the pole it might be close to the center of the path on one pass, further on another).

          – John
          2 hours ago

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Geographic Information Systems Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f315691%2fhow-big-is-a-modis-250m-pixel-in-reality%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Are there any AGPL-style licences that require source code modifications to be public? Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Force derivative works to be publicAre there any GPL like licenses for Apple App Store?Do you violate the GPL if you provide source code that cannot be compiled?GPL - is it distribution to use libraries in an appliance loaned to customers?Distributing App for free which uses GPL'ed codeModifications of server software under GPL, with web/CLI interfaceDoes using an AGPLv3-licensed library prevent me from dual-licensing my own source code?Can I publish only select code under GPLv3 from a private project?Is there published precedent regarding the scope of covered work that uses AGPL software?If MIT licensed code links to GPL licensed code what should be the license of the resulting binary program?If I use a public API endpoint that has its source code licensed under AGPL in my app, do I need to disclose my source?

          2013 GY136 Descoberta | Órbita | Referências Menu de navegação«List Of Centaurs and Scattered-Disk Objects»«List of Known Trans-Neptunian Objects»

          Button changing it's text & action. Good or terrible? The 2019 Stack Overflow Developer Survey Results Are Inchanging text on user mouseoverShould certain functions be “hard to find” for powerusers to discover?Custom liking function - do I need user login?Using different checkbox style for different checkbox behaviorBest Practices: Save and Exit in Software UIInteraction with remote validated formMore efficient UI to progress the user through a complicated process?Designing a popup notice for a gameShould bulk-editing functions be hidden until a table row is selected, or is there a better solution?Is it bad practice to disable (replace) the context menu?