Skip to content

Commit fb60be9

Browse files
snowman2snowman2
committed
Deploying to gh-pages from @ 06c08ff 🚀
1 parent cc08e0a commit fb60be9

File tree

7 files changed

+28
-31
lines changed

7 files changed

+28
-31
lines changed

‎latest/.doctrees/environment.pickle‎

0 Bytes
Binary file not shown.

‎latest/.doctrees/getting_started/crs_management.doctree‎

-214 Bytes
Binary file not shown.

‎latest/.doctrees/nbsphinx/getting_started/crs_management.ipynb‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@
4343
"If you have opened a dataset and the Coordinate Reference System (CRS) can be determined, you can access it via the `rio.crs` accessor.\n",
4444
"\n",
4545
"#### Search order for the CRS (DataArray and Dataset):\n",
46-
"1. Look in attributes (`attrs`) of your data array for the `grid_mapping` coordinate name.\n",
46+
"1. Look in `encoding` of your data array for the `grid_mapping` coordinate name.\n",
4747
" Inside the `grid_mapping` coordinate first look for `spatial_ref` then `crs_wkt` and lastly the CF grid mapping attributes.\n",
4848
" This is in line with the Climate and Forecast (CF) conventions for storing the CRS as well as GDAL netCDF conventions.\n",
4949
"2. Look in the `crs` attribute and load in the CRS from there. This is for backwards compatibility with `xarray.open_rasterio`, which is deprecated since version 0.20.0. We recommend using `rioxarray.open_rasterio` instead.\n",
@@ -73,7 +73,7 @@
7373
},
7474
{
7575
"cell_type": "code",
76-
"execution_count": 1,
76+
"execution_count": null,
7777
"metadata": {},
7878
"outputs": [],
7979
"source": [
@@ -84,7 +84,7 @@
8484
},
8585
{
8686
"cell_type": "code",
87-
"execution_count": 2,
87+
"execution_count": null,
8888
"metadata": {},
8989
"outputs": [],
9090
"source": [
@@ -93,7 +93,7 @@
9393
},
9494
{
9595
"cell_type": "code",
96-
"execution_count": 3,
96+
"execution_count": null,
9797
"metadata": {},
9898
"outputs": [
9999
{
@@ -113,7 +113,7 @@
113113
},
114114
{
115115
"cell_type": "code",
116-
"execution_count": 4,
116+
"execution_count": null,
117117
"metadata": {},
118118
"outputs": [
119119
{
@@ -497,7 +497,7 @@
497497
},
498498
{
499499
"cell_type": "code",
500-
"execution_count": 5,
500+
"execution_count": null,
501501
"metadata": {},
502502
"outputs": [
503503
{

‎latest/_sources/getting_started/crs_management.ipynb.txt‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@
4343
"If you have opened a dataset and the Coordinate Reference System (CRS) can be determined, you can access it via the `rio.crs` accessor.\n",
4444
"\n",
4545
"#### Search order for the CRS (DataArray and Dataset):\n",
46-
"1. Look in attributes (`attrs`) of your data array for the `grid_mapping` coordinate name.\n",
46+
"1. Look in `encoding` of your data array for the `grid_mapping` coordinate name.\n",
4747
" Inside the `grid_mapping` coordinate first look for `spatial_ref` then `crs_wkt` and lastly the CF grid mapping attributes.\n",
4848
" This is in line with the Climate and Forecast (CF) conventions for storing the CRS as well as GDAL netCDF conventions.\n",
4949
"2. Look in the `crs` attribute and load in the CRS from there. This is for backwards compatibility with `xarray.open_rasterio`, which is deprecated since version 0.20.0. We recommend using `rioxarray.open_rasterio` instead.\n",
@@ -73,7 +73,7 @@
7373
},
7474
{
7575
"cell_type": "code",
76-
"execution_count": 1,
76+
"execution_count": null,
7777
"metadata": {},
7878
"outputs": [],
7979
"source": [
@@ -84,7 +84,7 @@
8484
},
8585
{
8686
"cell_type": "code",
87-
"execution_count": 2,
87+
"execution_count": null,
8888
"metadata": {},
8989
"outputs": [],
9090
"source": [
@@ -93,7 +93,7 @@
9393
},
9494
{
9595
"cell_type": "code",
96-
"execution_count": 3,
96+
"execution_count": null,
9797
"metadata": {},
9898
"outputs": [
9999
{
@@ -113,7 +113,7 @@
113113
},
114114
{
115115
"cell_type": "code",
116-
"execution_count": 4,
116+
"execution_count": null,
117117
"metadata": {},
118118
"outputs": [
119119
{
@@ -497,7 +497,7 @@
497497
},
498498
{
499499
"cell_type": "code",
500-
"execution_count": 5,
500+
"execution_count": null,
501501
"metadata": {},
502502
"outputs": [
503503
{

‎latest/getting_started/crs_management.html‎

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ <h2>Accessing the CRS object<a class="headerlink" href="#Accessing-the-CRS-objec
121121
<section id="Search-order-for-the-CRS-(DataArray-and-Dataset):">
122122
<h3>Search order for the CRS (DataArray and Dataset):<a class="headerlink" href="#Search-order-for-the-CRS-(DataArray-and-Dataset):" title="Link to this heading"></a></h3>
123123
<ol class="arabic simple">
124-
<li><p>Look in attributes (<code class="docutils literal notranslate"><span class="pre">attrs</span></code>) of your data array for the <code class="docutils literal notranslate"><span class="pre">grid_mapping</span></code> coordinate name. Inside the <code class="docutils literal notranslate"><span class="pre">grid_mapping</span></code> coordinate first look for <code class="docutils literal notranslate"><span class="pre">spatial_ref</span></code> then <code class="docutils literal notranslate"><span class="pre">crs_wkt</span></code> and lastly the CF grid mapping attributes. This is in line with the Climate and Forecast (CF) conventions for storing the CRS as well as GDAL netCDF conventions.</p></li>
124+
<li><p>Look in <code class="docutils literal notranslate"><span class="pre">encoding</span></code> of your data array for the <code class="docutils literal notranslate"><span class="pre">grid_mapping</span></code> coordinate name. Inside the <code class="docutils literal notranslate"><span class="pre">grid_mapping</span></code> coordinate first look for <code class="docutils literal notranslate"><span class="pre">spatial_ref</span></code> then <code class="docutils literal notranslate"><span class="pre">crs_wkt</span></code> and lastly the CF grid mapping attributes. This is in line with the Climate and Forecast (CF) conventions for storing the CRS as well as GDAL netCDF conventions.</p></li>
125125
<li><p>Look in the <code class="docutils literal notranslate"><span class="pre">crs</span></code> attribute and load in the CRS from there. This is for backwards compatibility with <code class="docutils literal notranslate"><span class="pre">xarray.open_rasterio</span></code>, which is deprecated since version 0.20.0. We recommend using <code class="docutils literal notranslate"><span class="pre">rioxarray.open_rasterio</span></code> instead.</p></li>
126126
</ol>
127127
<p>The value for the <code class="docutils literal notranslate"><span class="pre">crs</span></code> is anything accepted by <code class="docutils literal notranslate"><span class="pre">rasterio.crs.CRS.from_user_input()</span></code></p>
@@ -146,7 +146,7 @@ <h3>API Documentation<a class="headerlink" href="#API-Documentation" title="Link
146146
<li><p><a class="reference internal" href="../rioxarray.html#rioxarray.rioxarray.XRasterBase.transform"><span class="std std-ref">rio.transform()</span></a></p></li>
147147
</ul>
148148
<div class="nbinput nblast docutils container">
149-
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[1]:
149+
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[ ]:
150150
</pre></div>
151151
</div>
152152
<div class="input_area highlight-ipython3 notranslate"><div class="highlight"><pre><span></span>import rioxarray # activate the rio accessor
@@ -156,41 +156,39 @@ <h3>API Documentation<a class="headerlink" href="#API-Documentation" title="Link
156156
</div>
157157
</div>
158158
<div class="nbinput nblast docutils container">
159-
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[2]:
159+
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[ ]:
160160
</pre></div>
161161
</div>
162162
<div class="input_area highlight-ipython3 notranslate"><div class="highlight"><pre><span></span>rds = xarray.open_dataset(&quot;../../test/test_data/input/PLANET_SCOPE_3D.nc&quot;, decode_coords=&quot;all&quot;)
163163
</pre></div>
164164
</div>
165165
</div>
166166
<div class="nbinput docutils container">
167-
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[3]:
167+
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[ ]:
168168
</pre></div>
169169
</div>
170170
<div class="input_area highlight-ipython3 notranslate"><div class="highlight"><pre><span></span>rds.green.attrs
171171
</pre></div>
172172
</div>
173173
</div>
174174
<div class="nboutput nblast docutils container">
175-
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[3]:
176-
</pre></div>
175+
<div class="prompt empty docutils container">
177176
</div>
178177
<div class="output_area docutils container">
179178
<div class="highlight"><pre>
180179
{&#39;units&#39;: &#39;DN&#39;, &#39;nodata&#39;: 0.0}
181180
</pre></div></div>
182181
</div>
183182
<div class="nbinput docutils container">
184-
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[4]:
183+
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[ ]:
185184
</pre></div>
186185
</div>
187186
<div class="input_area highlight-ipython3 notranslate"><div class="highlight"><pre><span></span>rds.green.spatial_ref
188187
</pre></div>
189188
</div>
190189
</div>
191190
<div class="nboutput nblast docutils container">
192-
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[4]:
193-
</pre></div>
191+
<div class="prompt empty docutils container">
194192
</div>
195193
<div class="output_area rendered_html docutils container">
196194
<div><svg style="position: absolute; width: 0; height: 0; overflow: hidden">
@@ -552,16 +550,15 @@ <h3>API Documentation<a class="headerlink" href="#API-Documentation" title="Link
552550
spatial_ref: PROJCS[&quot;WGS 84 / UTM zone 22S&quot;,GEOGCS[&quot;WGS 84&quot;,DATUM[&quot;WGS_1...</pre><div class='xr-wrap' hidden><div class='xr-header'><div class='xr-obj-type'>xarray.DataArray</div><div class='xr-array-name'>'spatial_ref'</div></div><ul class='xr-sections'><li class='xr-section-item'><div class='xr-array-wrap'><input id='section-ed98a4ac-15a8-4b42-a4d5-b41d08429b39' class='xr-array-in' type='checkbox' checked><label for='section-ed98a4ac-15a8-4b42-a4d5-b41d08429b39' title='Show/hide data repr'><svg class='icon xr-icon-database'><use xlink:href='#icon-database'></use></svg></label><div class='xr-array-preview xr-preview'><span>0</span></div><div class='xr-array-data'><pre>array(0)</pre></div></div></li><li class='xr-section-item'><input id='section-13a73705-474f-4849-a2b6-31c4c1cc60d7' class='xr-section-summary-in' type='checkbox' checked><label for='section-13a73705-474f-4849-a2b6-31c4c1cc60d7' class='xr-section-summary' >Coordinates: <span>(1)</span></label><div class='xr-section-inline-details'></div><div class='xr-section-details'><ul class='xr-var-list'><li class='xr-var-item'><div class='xr-var-name'><span>spatial_ref</span></div><div class='xr-var-dims'>()</div><div class='xr-var-dtype'>int64</div><div class='xr-var-preview xr-preview'>0</div><input id='attrs-ff9e3017-55fa-4eb5-af42-af1cc7f27bd4' class='xr-var-attrs-in' type='checkbox' ><label for='attrs-ff9e3017-55fa-4eb5-af42-af1cc7f27bd4' title='Show/Hide attributes'><svg class='icon xr-icon-file-text2'><use xlink:href='#icon-file-text2'></use></svg></label><input id='data-7a4c305b-e31f-4faa-a83f-8aeec07cc0ee' class='xr-var-data-in' type='checkbox'><label for='data-7a4c305b-e31f-4faa-a83f-8aeec07cc0ee' title='Show/Hide data repr'><svg class='icon xr-icon-database'><use xlink:href='#icon-database'></use></svg></label><div class='xr-var-attrs'><dl class='xr-attrs'><dt><span>spatial_ref :</span></dt><dd>PROJCS[&quot;WGS 84 / UTM zone 22S&quot;,GEOGCS[&quot;WGS 84&quot;,DATUM[&quot;WGS_1984&quot;,SPHEROID[&quot;WGS 84&quot;,6378137,298.257223563,AUTHORITY[&quot;EPSG&quot;,&quot;7030&quot;]],AUTHORITY[&quot;EPSG&quot;,&quot;6326&quot;]],PRIMEM[&quot;Greenwich&quot;,0,AUTHORITY[&quot;EPSG&quot;,&quot;8901&quot;]],UNIT[&quot;degree&quot;,0.0174532925199433,AUTHORITY[&quot;EPSG&quot;,&quot;9122&quot;]],AUTHORITY[&quot;EPSG&quot;,&quot;4326&quot;]],PROJECTION[&quot;Transverse_Mercator&quot;],PARAMETER[&quot;latitude_of_origin&quot;,0],PARAMETER[&quot;central_meridian&quot;,-51],PARAMETER[&quot;scale_factor&quot;,0.9996],PARAMETER[&quot;false_easting&quot;,500000],PARAMETER[&quot;false_northing&quot;,10000000],UNIT[&quot;metre&quot;,1,AUTHORITY[&quot;EPSG&quot;,&quot;9001&quot;]],AXIS[&quot;Easting&quot;,EAST],AXIS[&quot;Northing&quot;,NORTH],AUTHORITY[&quot;EPSG&quot;,&quot;32722&quot;]]</dd></dl></div><div class='xr-var-data'><pre>array(0)</pre></div></li></ul></div></li><li class='xr-section-item'><input id='section-6c56ca51-d50d-408e-8550-3fa40536ce7d' class='xr-section-summary-in' type='checkbox' checked><label for='section-6c56ca51-d50d-408e-8550-3fa40536ce7d' class='xr-section-summary' >Attributes: <span>(1)</span></label><div class='xr-section-inline-details'></div><div class='xr-section-details'><dl class='xr-attrs'><dt><span>spatial_ref :</span></dt><dd>PROJCS[&quot;WGS 84 / UTM zone 22S&quot;,GEOGCS[&quot;WGS 84&quot;,DATUM[&quot;WGS_1984&quot;,SPHEROID[&quot;WGS 84&quot;,6378137,298.257223563,AUTHORITY[&quot;EPSG&quot;,&quot;7030&quot;]],AUTHORITY[&quot;EPSG&quot;,&quot;6326&quot;]],PRIMEM[&quot;Greenwich&quot;,0,AUTHORITY[&quot;EPSG&quot;,&quot;8901&quot;]],UNIT[&quot;degree&quot;,0.0174532925199433,AUTHORITY[&quot;EPSG&quot;,&quot;9122&quot;]],AUTHORITY[&quot;EPSG&quot;,&quot;4326&quot;]],PROJECTION[&quot;Transverse_Mercator&quot;],PARAMETER[&quot;latitude_of_origin&quot;,0],PARAMETER[&quot;central_meridian&quot;,-51],PARAMETER[&quot;scale_factor&quot;,0.9996],PARAMETER[&quot;false_easting&quot;,500000],PARAMETER[&quot;false_northing&quot;,10000000],UNIT[&quot;metre&quot;,1,AUTHORITY[&quot;EPSG&quot;,&quot;9001&quot;]],AXIS[&quot;Easting&quot;,EAST],AXIS[&quot;Northing&quot;,NORTH],AUTHORITY[&quot;EPSG&quot;,&quot;32722&quot;]]</dd></dl></div></li></ul></div></div></div>
553551
</div>
554552
<div class="nbinput docutils container">
555-
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[5]:
553+
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[ ]:
556554
</pre></div>
557555
</div>
558556
<div class="input_area highlight-ipython3 notranslate"><div class="highlight"><pre><span></span>rds.green.rio.crs
559557
</pre></div>
560558
</div>
561559
</div>
562560
<div class="nboutput nblast docutils container">
563-
<div class="prompt highlight-none notranslate"><div class="highlight"><pre><span></span>[5]:
564-
</pre></div>
561+
<div class="prompt empty docutils container">
565562
</div>
566563
<div class="output_area docutils container">
567564
<div class="highlight"><pre>

‎latest/getting_started/crs_management.ipynb‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@
4343
"If you have opened a dataset and the Coordinate Reference System (CRS) can be determined, you can access it via the `rio.crs` accessor.\n",
4444
"\n",
4545
"#### Search order for the CRS (DataArray and Dataset):\n",
46-
"1. Look in attributes (`attrs`) of your data array for the `grid_mapping` coordinate name.\n",
46+
"1. Look in `encoding` of your data array for the `grid_mapping` coordinate name.\n",
4747
" Inside the `grid_mapping` coordinate first look for `spatial_ref` then `crs_wkt` and lastly the CF grid mapping attributes.\n",
4848
" This is in line with the Climate and Forecast (CF) conventions for storing the CRS as well as GDAL netCDF conventions.\n",
4949
"2. Look in the `crs` attribute and load in the CRS from there. This is for backwards compatibility with `xarray.open_rasterio`, which is deprecated since version 0.20.0. We recommend using `rioxarray.open_rasterio` instead.\n",
@@ -73,7 +73,7 @@
7373
},
7474
{
7575
"cell_type": "code",
76-
"execution_count": 1,
76+
"execution_count": null,
7777
"metadata": {},
7878
"outputs": [],
7979
"source": [
@@ -84,7 +84,7 @@
8484
},
8585
{
8686
"cell_type": "code",
87-
"execution_count": 2,
87+
"execution_count": null,
8888
"metadata": {},
8989
"outputs": [],
9090
"source": [
@@ -93,7 +93,7 @@
9393
},
9494
{
9595
"cell_type": "code",
96-
"execution_count": 3,
96+
"execution_count": null,
9797
"metadata": {},
9898
"outputs": [
9999
{
@@ -113,7 +113,7 @@
113113
},
114114
{
115115
"cell_type": "code",
116-
"execution_count": 4,
116+
"execution_count": null,
117117
"metadata": {},
118118
"outputs": [
119119
{
@@ -497,7 +497,7 @@
497497
},
498498
{
499499
"cell_type": "code",
500-
"execution_count": 5,
500+
"execution_count": null,
501501
"metadata": {},
502502
"outputs": [
503503
{

‎latest/searchindex.js‎

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)