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

Are ETF trackers fundamentally better than individual stocks?

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

Is it true that good novels will automatically sell themselves on Amazon (and so on) and there is no need for one to waste time promoting?

A link redirect to http instead of https: how critical is it?

If curse and magic is two sides of the same coin, why the former is forbidden?

How could a scammer know the apps on my phone / iTunes account?

Could the Saturn V actually have launched astronauts around Venus?

Most cost effective thermostat setting: consistent temperature vs. lowest temperature possible

Is it possible to upcast ritual spells?

Unexpected result from ArcLength

Professor being mistaken for a grad student

Is a party consisting of only a bard, a cleric, and a warlock functional long-term?

Can a druid choose the size of its wild shape beast?

how to write formula in word in latex

How big is a MODIS 250m pixel in reality?

Is there a data structure that only stores hash codes and not the actual objects?

Why is the President allowed to veto a cancellation of emergency powers?

In a future war, an old lady is trying to raise a boy but one of the weapons has made everyone deaf

Who is flying the vertibirds?

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

What is the significance behind "40 days" that often appears in the Bible?

Property of summation

What should tie a collection of short-stories together?

Gantt Chart like rectangles with log scale



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 37 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

          Magento 2 duplicate PHPSESSID cookie when using session_start() in custom php scriptMagento 2: User cant logged in into to account page, no error showing!Magento duplicate on subdomainGrabbing storeview from cookie (after using language selector)How do I run php custom script on magento2Magento 2: Include PHP script in headerSession lock after using Cm_RedisSessionscript php to update stockMagento set cookie popupMagento 2 session id cookie - where to find it?How to import Configurable product from csv with custom attributes using php scriptMagento 2 run custom PHP script

          Can not update quote_id field of “quote_item” table magento 2Magento 2.1 - We can't remove the item. (Shopping Cart doesnt allow us to remove items before becomes empty)Add value for custom quote item attribute using REST apiREST API endpoint v1/carts/cartId/items always returns error messageCorrect way to save entries to databaseHow to remove all associated quote objects of a customer completelyMagento 2 - Save value from custom input field to quote_itemGet quote_item data using quote id and product id filter in Magento 2How to set additional data to quote_item table from controller in Magento 2?What is the purpose of additional_data column in quote_item table in magento2Set Custom Price to Quote item magento2 from controller

          How to solve knockout JS error in Magento 2 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?(Magento2) knockout.js:3012 Uncaught ReferenceError: Unable to process bindingUnable to process binding Knockout.js magento 2Cannot read property `scopeLabel` of undefined on Product Detail PageCan't get Customer Data on frontend in Magento 2Magento2 Order Summary - unable to process bindingKO templates are not loading in Magento 2.1 applicationgetting knockout js error magento 2Product grid not load -— Unable to process binding Knockout.js magento 2Product form not loaded in magento2Uncaught ReferenceError: Unable to process binding “if: function()return (isShowLegend()) ” magento 2