chore: fix test by using PDOK endpoint

examples/config_3d.yaml

@@ -1,6 +1,6 @@
 ---
 version: 1.0.0
-title: New York in 3D
+title: Example 3D
 # shortened title, used in breadcrumb path
 serviceIdentifier: 3D
 abstract: >-
@@ -23,16 +23,7 @@ availableLanguages:
   - en
 ogcApi:
   3dgeovolumes:
-    tileServer: https://maps.ecere.com/3DAPI/collections/
+    tileServer: https://api.pdok.nl/kadaster/3d-basisvoorziening/ogc/v1/collections
     collections:
-      - id: newyork
-        # optional basepath to 3D tiles on the tileserver. Defaults to the collection ID.
-        tileServerPath: "NewYork/3DTiles"
-        # URI template for individual 3D tiles
-        uriTemplate3dTiles: "3DTiles/{level}/{x}/{y}.b3m"
-
-        # optional URI template for subtrees, only required when "implicit tiling" extension is used
-        # uriTemplateImplicitTilingSubtree: ""
-
-        # URI template for digital terrain model (DTM) in Quantized Mesh format, REQUIRED when you want to serve a DTM
-        # uriTemplateDTM: ""
+      - id: gebouwen
+        uriTemplate3dTiles: "t/{level}/{x}/{y}.glb"

examples/config_all.yaml

@@ -102,12 +102,11 @@ ogcApi:
         tableName: addresses
 
   3dgeovolumes:
-    tileServer: https://maps.ecere.com/3DAPI/collections/
+    tileServer: https://api.pdok.nl/kadaster/3d-basisvoorziening/ogc/v1/collections
     collections:
       - id: addresses  # same collection as the tiles/features
-        metadata: *addressMetadata
-        tileServerPath: "NewYork/3DTiles"
-        uriTemplate3dTiles: "3DTiles/{level}/{x}/{y}.b3m"
+        tileServerPath: "gebouwen"
+        uriTemplate3dTiles: "t/{level}/{x}/{y}.glb"
 
   styles:
     default: dummy-style