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/outputs/ogcfeatures.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,10 +121,21 @@ new VectorLayer({
121
121
122
122
1. Modify the `workshop\exercises\mapfiles\railways.map` to enable the OGC Features API. You will need to add a new entry to the `MAPS` section in `workshop\exercises\mapfiles\mapserver.conf` and restart the Docker container to be able to browse the OGC Features API interface.
123
123
124
+
```scala
125
+
MAPS
126
+
...
127
+
RAILWAYS"/etc/mapserver/railways.map"
128
+
END
129
+
```
130
+
131
+
You also need to add the following to `WEB` `METADATA` so MapServer can correctly construct the URLs: `"oga_onlineresource" "/railways/ogcapi"`
132
+
124
133
!!! tip
125
134
126
-
You need to add `TEMPLATE "void"` to each of the layers you want to make available through the OGC Features API.
127
-
[TEMPLATE](https://mapserver.org/mapfile/layer.html#mapfile-layer-template) is a left-over from when HTML templates were used to return features, and allows the layer to be queried.
135
+
You need to add `TEMPLATE "void"` to each of the layers you want to make available through the OGCFeaturesAPI.
136
+
[TEMPLATE](https://mapserver.org/mapfile/layer.html#mapfile-layer-template) is a left-over from when HTML templates were used to return features, and allows the layer to be queried.
137
+
138
+
Once setup correctly you should be able to browse the OGCFeaturesAPI at <http://localhost:5000/railways/ogcapi/>.
0 commit comments