You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: workshop/content/docs/introduction.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ The core design principles are as follows:
54
54
- long term sustainability
55
55
- modularity
56
56
- extensibility
57
-
- building on a large ecosystem of Free Open Source and OSGeo components such as GDAL, rasterio, Shapely, Pandas, Elasticsearch, PostGIS and many others
57
+
- building on a large ecosystem of Free Open Source and OSGeo components such as GDAL, Rasterio, Shapely, Pandas, Elasticsearch, PostGIS and many others
58
58
59
59
The project was initiated by [Tom Kralidis](https://github.com/tomkralidis). Within weeks, several talented
60
60
developers joined the project, which led to the formation of a core team and [Project Steering Committee (PSC)](https://pygeoapi.io/community/psc). Contributions continued
Copy file name to clipboardExpand all lines: workshop/content/docs/publishing/ogcapi-coverages.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ data (grids, remote sensing data, multidimensional data cubes):
11
11
12
12
## pygeoapi support
13
13
14
-
pygeoapi supports the OGC API - Coverages draft specification, with [rasterio](https://rasterio.readthedocs.io) and [xarray](https://docs.xarray.dev) as core backends
14
+
pygeoapi supports the OGC API - Coverages draft specification, with [Rasterio](https://rasterio.readthedocs.io) and [xarray](https://docs.xarray.dev) as core backends
15
15
as well as [CoverageJSON](https://covjson.org) and native output.
16
16
17
17
!!! note
@@ -21,7 +21,7 @@ as well as [CoverageJSON](https://covjson.org) and native output.
21
21
22
22
## Publish a raster dataset
23
23
24
-
In the previous exercises we have demonstrated the steps involved to publish vector data and update the pygeoapi configuration. In this section we are going to publish a raster file in GeoTIFF format, from a [rasterio](https://rasterio.readthedocs.io) source provider.
24
+
In the previous exercises we have demonstrated the steps involved to publish vector data and update the pygeoapi configuration. In this section we are going to publish a raster file in GeoTIFF format, from a [Rasterio](https://rasterio.readthedocs.io) source provider.
25
25
26
26
27
27
!!! question "Update the pygeoapi configuration"
@@ -58,7 +58,7 @@ In the previous exercises we have demonstrated the steps involved to publish vec
58
58
59
59
!!! tip
60
60
61
-
The rasterio provider `format.name` directive **requires** a valid [GDAL raster driver short name](https://gdal.org/drivers/raster/index.html)
61
+
The Rasterio provider `format.name` directive **requires** a valid [GDAL raster driver short name](https://gdal.org/drivers/raster/index.html)
62
62
63
63
Save the configuration and restart Docker Compose. Navigate to <http://localhost:5000/collections> to evaluate whether the new dataset has been published.
Copy file name to clipboardExpand all lines: workshop/content/docs/publishing/ogcapi-edr.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,9 @@ Let's try publishing some ICOADS data via the EDR xarray plugin. The sample ICOA
66
66
Save the configuration and restart Docker Compose. Navigate to <http://localhost:5000/collections> to evaluate whether the new dataset has been published.
67
67
68
68
At first glance, the `icoads-sst` collection appears as a normal OGC API - Coverages collection. Look a bit closer at the collection description, and notice
69
-
that there is a `parameter_names' key that describes EDR parameter names for the collection queries.
69
+
that there is a `parameter_names` key that describes EDR parameter names for the collection queries.
70
+
71
+
Try visualizing the following EDR position query in a web browser: <http://localhost:5000/collections/icoads-sst/position?coords=POINT(174.7645%20-36.8509)>
70
72
71
73
### OWSLib - Advanced
72
74
@@ -107,9 +109,9 @@ that there is a `parameter_names' key that describes EDR parameter names for the
107
109
>>> len(collections['collections'])
108
110
13
109
111
>>> icoads_sst = w.collection('icoads-sst')
110
-
>>> icoads_sst['parameter-names'].keys()
112
+
>>> icoads_sst['parameter_names'].keys()
111
113
dict_keys(['SST', 'AIRT', 'UWND', 'VWND'])
112
-
>>> data = w.query_data('icoads_sst', 'position', coords='POINT(-75 45)', parameter_names=['SST', 'AIRT'])
114
+
>>> data = w.query_data('icoads-sst', 'position', coords='POINT(174.7645 -36.8509)', parameter_names=['SST', 'AIRT'])
113
115
>>> data # CoverageJSON data
114
116
```
115
117
</div>
@@ -127,9 +129,9 @@ that there is a `parameter_names' key that describes EDR parameter names for the
127
129
>>> len(collections['collections'])
128
130
13
129
131
>>> icoads_sst = w.collection('icoads-sst')
130
-
>>> icoads_sst['parameter-names'].keys()
132
+
>>> icoads_sst['parameter_names'].keys()
131
133
dict_keys(['SST', 'AIRT', 'UWND', 'VWND'])
132
-
>>> data = w.query_data('icoads_sst', 'position', coords='POINT(-75 45)', parameter_names=['SST', 'AIRT'])
134
+
>>> data = w.query_data('icoads-sst', 'position', coords='POINT(174.7645 -36.8509)', parameter_names=['SST', 'AIRT'])
0 commit comments