r.tileset.html 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105
  1. <h2>DESCRIPTION</h2>
  2. <em>r.tileset</em> generates sets of tiles in another projection that
  3. cover a region in this projection with adequate resolution. By default
  4. the current region and its resolution are used, the bounds and
  5. resolution of another region can be used via the region option.
  6. <h2>NOTES</h2>
  7. <em>r.tileset</em> does not make "optimal" tilings (as few tiles of
  8. the largest size less than the maximums). This means that from
  9. latitude longitude projection to an appropriate projection for a
  10. region, in the degenerate case, it may create tiles demanding up to
  11. twice the necessary information. Furthermore, generating a tiling near
  12. a divergant point of a source projection, such as the poles of a
  13. cylindrical source projections, results in divergence of the tile set.
  14. <p>
  15. Not generating "optimal" tilings may have another consequence; the
  16. aspect ratio of cells in the destination region will not necessarily
  17. carry over to the source region and generated tiles may have cells of
  18. strange aspect ratios. This might be a problem for some map request
  19. services presenting data in an inappropriate projection or with strict
  20. constraints on cell aspect ratio.
  21. <h2>OUTPUT FORMAT</h2>
  22. Each tile is listed on a separate line in the output. The lines are
  23. formatted as follows:
  24. <dl>
  25. <dt>
  26. <span class="code"><tt>
  27. 5|125|45|175|80|100
  28. </tt></span>
  29. <dd>This is the default output format. It is the tile's minimum x
  30. coordinate, minimum y coordinate, maximum x coordinate, maximum y
  31. coordinate, width in cells, and height in cells separated by the "|"
  32. character. The fields can be separated by a different character by
  33. changing the fs option.
  34. <dt>
  35. <span class="code"><tt>
  36. w=5;s=125;e=45;n=175;cols=80;rows=100;
  37. </tt></span>
  38. <dd>This is output in a format convinent for setting variables in a shell
  39. script.
  40. <dt>
  41. <span class="code"><tt>
  42. bbox=5,125,45,175&amp;width=80&amp;height=100
  43. </tt></span>
  44. <dd>This is output in a format convinent for requesting data from some
  45. http services.
  46. </dl>
  47. <h2>EXAMPLES</h2>
  48. Generates tiles in latitude longitude that cover the current
  49. region, each tile will be less than 1024 cells high and 2048 cells
  50. across. The bounds and sizes of tiles in the output are separated by | (pipe):
  51. <p>
  52. <div class="code"><pre>
  53. r.tileset sourceproj=+init=epsg:4326 maxrows=1024 maxcols=2048
  54. </pre></div>
  55. Generates tiles in latitude longitude projection that cover the
  56. named region "ne-rio". The tiles will have 2 cells of overlap. The
  57. output format will be strings like the bbox requests for WMS servers:
  58. <p>
  59. <div class="code"><pre>
  60. r.tileset sourceproj=+init=epsg:4326 overlap=2 -w region=ne-rio
  61. </pre></div>
  62. Generates tiles in the projection of the location
  63. "IrishGrid". Each tile will be less than 300x400 cells in size, with 3
  64. cells of overlap in the top and right sides of each tile. The output
  65. is in a format where each line is in shell script style. The
  66. substitution <code>`g.proj -j location=IrishGrid`</code> will only
  67. work in a unix style shell:
  68. <p>
  69. <div class="code"><pre>
  70. r.tileset sourceproj="`g.proj -j location=IrishGrid`" maxrows=400 maxcols=300 overlap=3 -g
  71. </pre></div>
  72. <h2>KNOWN ISSUES</h2>
  73. <ul>
  74. <li><em>r.tileset</em> does not know about meridians that
  75. "wrap-around" in projections.</li>
  76. </ul>
  77. <h2>AUTHORS</h2>
  78. Cedric Shock<br>
  79. Updated for GRASS 7 by Martin Landa, CTU in Prague, Czech Republic
  80. <p>
  81. <i>Last changed: $Date$</i>