Some zones disappear when running Zonal Statistics as Table in ArcGIS Planned maintenance...

Denied boarding although I have proper visa and documentation. To whom should I make a complaint?

When the Haste spell ends on a creature, do attackers have advantage against that creature?

Would "destroying" Wurmcoil Engine prevent its tokens from being created?

Is it cost-effective to upgrade an old-ish Giant Escape R3 commuter bike with entry-level branded parts (wheels, drivetrain)?

Can melee weapons be used to deliver Contact Poisons?

How do I make this wiring inside cabinet safer? (Pic)

Why do we bend a book to keep it straight?

また usage in a dictionary

Amount of permutations on an NxNxN Rubik's Cube

How to react to hostile behavior from a senior developer?

Is the Standard Deduction better than Itemized when both are the same amount?

Can a new player join a group only when a new campaign starts?

Fundamental Solution of the Pell Equation

Around usage results

How to convince students of the implication truth values?

Is it common practice to audition new musicians one-on-one before rehearsing with the entire band?

What does "lightly crushed" mean for cardamon pods?

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

Why wasn't DOSKEY integrated with COMMAND.COM?

In what way is everyone not a utilitarian

If a VARCHAR(MAX) column is included in an index, is the entire value always stored in the index page(s)?

Can a party unilaterally change candidates in preparation for a General election?

Do I really need to have a message in a novel to appeal to readers?

Generate an RGB colour grid



Some zones disappear when running Zonal Statistics as Table in ArcGIS



Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Zonal statistics tool excluding some features in ArcMap?Why is ArcGIS Tabulate Area Better to Calculate Unique Landuse Values in Zone?Running zonal statistics and not all zones represented?Zonal Statistics as Table ToolIncluding NoData zones in zonal statistics tableZonal Statistics as Table output is missing some polygons ONLY when run from Python scriptBatch Zonal Statistics as table?Zones missing after running zonal statistics in ArcGIS Spatial Analyst?Inconsistent results using Zonal Statistics by Table for Min in ArcGIS Desktop?Zonal Statistics or Tabulate Area by Multiple, Cascading ZonesRunning Zonal Statistics as table 2Zonal Statistics as Table: Generic 99999 Error on Some Features





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







6















I'm new to GIS. I want the sum of nighttime lights (DMSP) by district for some country. I'm running this arcpy.gp.ZonalStatisticsAsTable_sa(Limites_distritales, "IDDIST", rc, temp_table, "DATA", "") and then converting to .csv. However, when I check the output some districts (identified by IDDIST) are missing. I've checked all my script and they shouldn't be dropped; my guess is that they are being assigned NoData because they overlap multiple grids (and no single grid is in the polygon) and thus no statistics are being calculated for them.



One of the problematic districts is shown in the picture below.



Is there a workaround for this?



enter image description here










share|improve this question































    6















    I'm new to GIS. I want the sum of nighttime lights (DMSP) by district for some country. I'm running this arcpy.gp.ZonalStatisticsAsTable_sa(Limites_distritales, "IDDIST", rc, temp_table, "DATA", "") and then converting to .csv. However, when I check the output some districts (identified by IDDIST) are missing. I've checked all my script and they shouldn't be dropped; my guess is that they are being assigned NoData because they overlap multiple grids (and no single grid is in the polygon) and thus no statistics are being calculated for them.



    One of the problematic districts is shown in the picture below.



    Is there a workaround for this?



    enter image description here










    share|improve this question



























      6












      6








      6


      2






      I'm new to GIS. I want the sum of nighttime lights (DMSP) by district for some country. I'm running this arcpy.gp.ZonalStatisticsAsTable_sa(Limites_distritales, "IDDIST", rc, temp_table, "DATA", "") and then converting to .csv. However, when I check the output some districts (identified by IDDIST) are missing. I've checked all my script and they shouldn't be dropped; my guess is that they are being assigned NoData because they overlap multiple grids (and no single grid is in the polygon) and thus no statistics are being calculated for them.



      One of the problematic districts is shown in the picture below.



      Is there a workaround for this?



      enter image description here










      share|improve this question
















      I'm new to GIS. I want the sum of nighttime lights (DMSP) by district for some country. I'm running this arcpy.gp.ZonalStatisticsAsTable_sa(Limites_distritales, "IDDIST", rc, temp_table, "DATA", "") and then converting to .csv. However, when I check the output some districts (identified by IDDIST) are missing. I've checked all my script and they shouldn't be dropped; my guess is that they are being assigned NoData because they overlap multiple grids (and no single grid is in the polygon) and thus no statistics are being calculated for them.



      One of the problematic districts is shown in the picture below.



      Is there a workaround for this?



      enter image description here







      arcpy spatial-analyst zonal-statistics arcgis-10.5






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 10 '17 at 19:51









      PolyGeo

      54k1782246




      54k1782246










      asked Nov 10 '17 at 17:13









      Leandro PezánLeandro Pezán

      313




      313






















          3 Answers
          3






          active

          oldest

          votes


















          4














          The Zonal Statistics as Table documentation states the following:




          If the areas of single features are similar to or smaller than the
          area of single cells in the value raster, in the feature-to-raster
          conversion some of these zones may not be represented.




          I suspect the algorithm assigns raster values to the zone if that zone contains the raster centroid. In your example, no raster cell centroids exist within the zone.






          share|improve this answer































            3














            I had the same problem. spent a lot of time discussing it with ESRI support and the end resolution was that the code behind zonal stats looks for the center of the pixel to be contained by the polygon zone.



            If the zone doesn't contain a pixel center (or if a pixel does not have its center inside a zone) - even if it overlaps with the area of the pixel, it's omitted from calculations.



            My work around was to convert my raster data to polygons and then do a bunch of overlay analysis to get my totals. it takes way more time and memory, but I like that it takes partial coverage into account, which actually gave me correct averages for my coverages.






            share|improve this answer
























            • are you please able to give brief description of this "bunch of overlay analysis" workflow?

              – sparky
              Mar 6 at 3:58











            • Well, the specific workflow would depend on your end goal, but overlay analysis in general includes operations like "intersect" "clip" "union". in teh OP's case, a union of the polygonized grid and the zones will produce a new set of polygons with borders from both inputs. The output will of course have a new area attribute but it also retains the input zones' original square footage number too. so for each input zone, you will get the area intersecting each grid and the area of the zone as a whole, with which you can calculate sums or percentages etc.

              – Zipper1365
              Mar 6 at 14:26











            • thanks. My end goal is to have zonal statistics for all of my polygons, right now missing about 100 out of 7295, but it will make it hard to analyze them equally when some don't have these statistics. The problem with unions and other overlay analysis for me is there are overlapping polygons, so those are lost in certain geoprocesses.

              – sparky
              Mar 7 at 0:49



















            0














            your zone for this analysis probably does not overlap any cell center from the value raster and hence is not counted as a valid zone.
            A workaround for this is to specify a smaller cell size in the ZonalStatisticsAsTable tool environment while running the tool.
            See the blog to learn more about it: https://www.esri.com/arcgis-blog/products/spatial-analyst/analytics/getting-the-most-out-of-zonal-statistics/
            Hope that helps, thanks, Sarmistha






            share|improve this answer








            New contributor




            Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.





















              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%2f261429%2fsome-zones-disappear-when-running-zonal-statistics-as-table-in-arcgis%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              4














              The Zonal Statistics as Table documentation states the following:




              If the areas of single features are similar to or smaller than the
              area of single cells in the value raster, in the feature-to-raster
              conversion some of these zones may not be represented.




              I suspect the algorithm assigns raster values to the zone if that zone contains the raster centroid. In your example, no raster cell centroids exist within the zone.






              share|improve this answer




























                4














                The Zonal Statistics as Table documentation states the following:




                If the areas of single features are similar to or smaller than the
                area of single cells in the value raster, in the feature-to-raster
                conversion some of these zones may not be represented.




                I suspect the algorithm assigns raster values to the zone if that zone contains the raster centroid. In your example, no raster cell centroids exist within the zone.






                share|improve this answer


























                  4












                  4








                  4







                  The Zonal Statistics as Table documentation states the following:




                  If the areas of single features are similar to or smaller than the
                  area of single cells in the value raster, in the feature-to-raster
                  conversion some of these zones may not be represented.




                  I suspect the algorithm assigns raster values to the zone if that zone contains the raster centroid. In your example, no raster cell centroids exist within the zone.






                  share|improve this answer













                  The Zonal Statistics as Table documentation states the following:




                  If the areas of single features are similar to or smaller than the
                  area of single cells in the value raster, in the feature-to-raster
                  conversion some of these zones may not be represented.




                  I suspect the algorithm assigns raster values to the zone if that zone contains the raster centroid. In your example, no raster cell centroids exist within the zone.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 10 '17 at 20:05









                  AaronAaron

                  38.4k21110259




                  38.4k21110259

























                      3














                      I had the same problem. spent a lot of time discussing it with ESRI support and the end resolution was that the code behind zonal stats looks for the center of the pixel to be contained by the polygon zone.



                      If the zone doesn't contain a pixel center (or if a pixel does not have its center inside a zone) - even if it overlaps with the area of the pixel, it's omitted from calculations.



                      My work around was to convert my raster data to polygons and then do a bunch of overlay analysis to get my totals. it takes way more time and memory, but I like that it takes partial coverage into account, which actually gave me correct averages for my coverages.






                      share|improve this answer
























                      • are you please able to give brief description of this "bunch of overlay analysis" workflow?

                        – sparky
                        Mar 6 at 3:58











                      • Well, the specific workflow would depend on your end goal, but overlay analysis in general includes operations like "intersect" "clip" "union". in teh OP's case, a union of the polygonized grid and the zones will produce a new set of polygons with borders from both inputs. The output will of course have a new area attribute but it also retains the input zones' original square footage number too. so for each input zone, you will get the area intersecting each grid and the area of the zone as a whole, with which you can calculate sums or percentages etc.

                        – Zipper1365
                        Mar 6 at 14:26











                      • thanks. My end goal is to have zonal statistics for all of my polygons, right now missing about 100 out of 7295, but it will make it hard to analyze them equally when some don't have these statistics. The problem with unions and other overlay analysis for me is there are overlapping polygons, so those are lost in certain geoprocesses.

                        – sparky
                        Mar 7 at 0:49
















                      3














                      I had the same problem. spent a lot of time discussing it with ESRI support and the end resolution was that the code behind zonal stats looks for the center of the pixel to be contained by the polygon zone.



                      If the zone doesn't contain a pixel center (or if a pixel does not have its center inside a zone) - even if it overlaps with the area of the pixel, it's omitted from calculations.



                      My work around was to convert my raster data to polygons and then do a bunch of overlay analysis to get my totals. it takes way more time and memory, but I like that it takes partial coverage into account, which actually gave me correct averages for my coverages.






                      share|improve this answer
























                      • are you please able to give brief description of this "bunch of overlay analysis" workflow?

                        – sparky
                        Mar 6 at 3:58











                      • Well, the specific workflow would depend on your end goal, but overlay analysis in general includes operations like "intersect" "clip" "union". in teh OP's case, a union of the polygonized grid and the zones will produce a new set of polygons with borders from both inputs. The output will of course have a new area attribute but it also retains the input zones' original square footage number too. so for each input zone, you will get the area intersecting each grid and the area of the zone as a whole, with which you can calculate sums or percentages etc.

                        – Zipper1365
                        Mar 6 at 14:26











                      • thanks. My end goal is to have zonal statistics for all of my polygons, right now missing about 100 out of 7295, but it will make it hard to analyze them equally when some don't have these statistics. The problem with unions and other overlay analysis for me is there are overlapping polygons, so those are lost in certain geoprocesses.

                        – sparky
                        Mar 7 at 0:49














                      3












                      3








                      3







                      I had the same problem. spent a lot of time discussing it with ESRI support and the end resolution was that the code behind zonal stats looks for the center of the pixel to be contained by the polygon zone.



                      If the zone doesn't contain a pixel center (or if a pixel does not have its center inside a zone) - even if it overlaps with the area of the pixel, it's omitted from calculations.



                      My work around was to convert my raster data to polygons and then do a bunch of overlay analysis to get my totals. it takes way more time and memory, but I like that it takes partial coverage into account, which actually gave me correct averages for my coverages.






                      share|improve this answer













                      I had the same problem. spent a lot of time discussing it with ESRI support and the end resolution was that the code behind zonal stats looks for the center of the pixel to be contained by the polygon zone.



                      If the zone doesn't contain a pixel center (or if a pixel does not have its center inside a zone) - even if it overlaps with the area of the pixel, it's omitted from calculations.



                      My work around was to convert my raster data to polygons and then do a bunch of overlay analysis to get my totals. it takes way more time and memory, but I like that it takes partial coverage into account, which actually gave me correct averages for my coverages.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Nov 10 '17 at 21:31









                      Zipper1365Zipper1365

                      523313




                      523313













                      • are you please able to give brief description of this "bunch of overlay analysis" workflow?

                        – sparky
                        Mar 6 at 3:58











                      • Well, the specific workflow would depend on your end goal, but overlay analysis in general includes operations like "intersect" "clip" "union". in teh OP's case, a union of the polygonized grid and the zones will produce a new set of polygons with borders from both inputs. The output will of course have a new area attribute but it also retains the input zones' original square footage number too. so for each input zone, you will get the area intersecting each grid and the area of the zone as a whole, with which you can calculate sums or percentages etc.

                        – Zipper1365
                        Mar 6 at 14:26











                      • thanks. My end goal is to have zonal statistics for all of my polygons, right now missing about 100 out of 7295, but it will make it hard to analyze them equally when some don't have these statistics. The problem with unions and other overlay analysis for me is there are overlapping polygons, so those are lost in certain geoprocesses.

                        – sparky
                        Mar 7 at 0:49



















                      • are you please able to give brief description of this "bunch of overlay analysis" workflow?

                        – sparky
                        Mar 6 at 3:58











                      • Well, the specific workflow would depend on your end goal, but overlay analysis in general includes operations like "intersect" "clip" "union". in teh OP's case, a union of the polygonized grid and the zones will produce a new set of polygons with borders from both inputs. The output will of course have a new area attribute but it also retains the input zones' original square footage number too. so for each input zone, you will get the area intersecting each grid and the area of the zone as a whole, with which you can calculate sums or percentages etc.

                        – Zipper1365
                        Mar 6 at 14:26











                      • thanks. My end goal is to have zonal statistics for all of my polygons, right now missing about 100 out of 7295, but it will make it hard to analyze them equally when some don't have these statistics. The problem with unions and other overlay analysis for me is there are overlapping polygons, so those are lost in certain geoprocesses.

                        – sparky
                        Mar 7 at 0:49

















                      are you please able to give brief description of this "bunch of overlay analysis" workflow?

                      – sparky
                      Mar 6 at 3:58





                      are you please able to give brief description of this "bunch of overlay analysis" workflow?

                      – sparky
                      Mar 6 at 3:58













                      Well, the specific workflow would depend on your end goal, but overlay analysis in general includes operations like "intersect" "clip" "union". in teh OP's case, a union of the polygonized grid and the zones will produce a new set of polygons with borders from both inputs. The output will of course have a new area attribute but it also retains the input zones' original square footage number too. so for each input zone, you will get the area intersecting each grid and the area of the zone as a whole, with which you can calculate sums or percentages etc.

                      – Zipper1365
                      Mar 6 at 14:26





                      Well, the specific workflow would depend on your end goal, but overlay analysis in general includes operations like "intersect" "clip" "union". in teh OP's case, a union of the polygonized grid and the zones will produce a new set of polygons with borders from both inputs. The output will of course have a new area attribute but it also retains the input zones' original square footage number too. so for each input zone, you will get the area intersecting each grid and the area of the zone as a whole, with which you can calculate sums or percentages etc.

                      – Zipper1365
                      Mar 6 at 14:26













                      thanks. My end goal is to have zonal statistics for all of my polygons, right now missing about 100 out of 7295, but it will make it hard to analyze them equally when some don't have these statistics. The problem with unions and other overlay analysis for me is there are overlapping polygons, so those are lost in certain geoprocesses.

                      – sparky
                      Mar 7 at 0:49





                      thanks. My end goal is to have zonal statistics for all of my polygons, right now missing about 100 out of 7295, but it will make it hard to analyze them equally when some don't have these statistics. The problem with unions and other overlay analysis for me is there are overlapping polygons, so those are lost in certain geoprocesses.

                      – sparky
                      Mar 7 at 0:49











                      0














                      your zone for this analysis probably does not overlap any cell center from the value raster and hence is not counted as a valid zone.
                      A workaround for this is to specify a smaller cell size in the ZonalStatisticsAsTable tool environment while running the tool.
                      See the blog to learn more about it: https://www.esri.com/arcgis-blog/products/spatial-analyst/analytics/getting-the-most-out-of-zonal-statistics/
                      Hope that helps, thanks, Sarmistha






                      share|improve this answer








                      New contributor




                      Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.

























                        0














                        your zone for this analysis probably does not overlap any cell center from the value raster and hence is not counted as a valid zone.
                        A workaround for this is to specify a smaller cell size in the ZonalStatisticsAsTable tool environment while running the tool.
                        See the blog to learn more about it: https://www.esri.com/arcgis-blog/products/spatial-analyst/analytics/getting-the-most-out-of-zonal-statistics/
                        Hope that helps, thanks, Sarmistha






                        share|improve this answer








                        New contributor




                        Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.























                          0












                          0








                          0







                          your zone for this analysis probably does not overlap any cell center from the value raster and hence is not counted as a valid zone.
                          A workaround for this is to specify a smaller cell size in the ZonalStatisticsAsTable tool environment while running the tool.
                          See the blog to learn more about it: https://www.esri.com/arcgis-blog/products/spatial-analyst/analytics/getting-the-most-out-of-zonal-statistics/
                          Hope that helps, thanks, Sarmistha






                          share|improve this answer








                          New contributor




                          Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.










                          your zone for this analysis probably does not overlap any cell center from the value raster and hence is not counted as a valid zone.
                          A workaround for this is to specify a smaller cell size in the ZonalStatisticsAsTable tool environment while running the tool.
                          See the blog to learn more about it: https://www.esri.com/arcgis-blog/products/spatial-analyst/analytics/getting-the-most-out-of-zonal-statistics/
                          Hope that helps, thanks, Sarmistha







                          share|improve this answer








                          New contributor




                          Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.









                          share|improve this answer



                          share|improve this answer






                          New contributor




                          Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.









                          answered 14 mins ago









                          Sarmistha ChatterjeeSarmistha Chatterjee

                          1




                          1




                          New contributor




                          Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.





                          New contributor





                          Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.






                          Sarmistha Chatterjee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.






























                              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%2f261429%2fsome-zones-disappear-when-running-zonal-statistics-as-table-in-arcgis%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

                              Щит и меч (фильм) Содержание Названия серий | Сюжет |...

                              is 'sed' thread safeWhat should someone know about using Python scripts in the shell?Nexenta bash script uses...

                              Meter-Bus Содержание Параметры шины | Стандартизация |...