<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: -t parameter - tile size ? in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/t-parameter-tile-size/m-p/69896#M4024</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It depends on what your map units are.&amp;nbsp; If the data is degrees, then the default is two degrees.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If the data is feet, the default is two feet.&amp;nbsp; If your data is in meters, it would be unwise to grid&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;at one meter (you might want to file a bug report on that, since the utility would have to expect&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to generate 750 *million* grid cells, and over 32k or so is too many).&amp;nbsp; Frankly, the only sensible&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;default value would be the grid size of first level spatial index (gsize0).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 May 2010 10:42:46 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2010-05-21T10:42:46Z</dc:date>
    <item>
      <title>-t parameter - tile size ?</title>
      <link>https://community.esri.com/t5/data-management-questions/t-parameter-tile-size/m-p/69895#M4023</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;hi, &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;i use sdegroup.exe utility and i would like to group features by tile size. default is 2. but 2 of what ? it is in miles or what ? i have an area which has about 30x25 kilometers, what tile size have i to choose normaly ? i have chosen 1 and it works 16 hours and still works.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;thank you for advice and sorry for my english.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;david&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 May 2010 06:03:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/t-parameter-tile-size/m-p/69895#M4023</guid>
      <dc:creator>davidsponka</dc:creator>
      <dc:date>2010-05-21T06:03:32Z</dc:date>
    </item>
    <item>
      <title>Re: -t parameter - tile size ?</title>
      <link>https://community.esri.com/t5/data-management-questions/t-parameter-tile-size/m-p/69896#M4024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It depends on what your map units are.&amp;nbsp; If the data is degrees, then the default is two degrees.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If the data is feet, the default is two feet.&amp;nbsp; If your data is in meters, it would be unwise to grid&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;at one meter (you might want to file a bug report on that, since the utility would have to expect&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to generate 750 *million* grid cells, and over 32k or so is too many).&amp;nbsp; Frankly, the only sensible&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;default value would be the grid size of first level spatial index (gsize0).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 May 2010 10:42:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/t-parameter-tile-size/m-p/69896#M4024</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2010-05-21T10:42:46Z</dc:date>
    </item>
    <item>
      <title>Re: -t parameter - tile size ?</title>
      <link>https://community.esri.com/t5/data-management-questions/t-parameter-tile-size/m-p/69897#M4025</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;BTW: If you assume that each spatial query takes only 200 milliseconds, 750M queries&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;will run 150M seconds (~41666 hours or ~1736 days or ~4.75 years) -- Even if each&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;query is only 20ms, you probably don't want to try to let that job run to completion.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This reminds me that I need to add a progress meter on my spatial fragmentation &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;calculation tool (very verbose option, or verbose with &amp;gt;32k cells).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 May 2010 13:54:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/t-parameter-tile-size/m-p/69897#M4025</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2010-05-21T13:54:05Z</dc:date>
    </item>
  </channel>
</rss>

