doc(3DTiles): Replace C3DTilesLayer by OGC3DTilesLayer in the documentation

jailln · jailln · commit 049198344db8 · 2025-06-24T14:32:33.000+02:00
diff --git a/docs/config.json b/docs/config.json
@@ -50,7 +50,6 @@
                 "PotreeLayer",
                 "CopcLayer",
                 "Potree2Layer",
-                "C3DTilesLayer",
                 "OGC3DTilesLayer",
                 "LabelLayer",
                 "GlobeLayer",
@@ -123,16 +122,6 @@
                 "RasterTile"
             ],
 
-            "3D Tiles": [
-                "3dTilesProcessing",
-                "C3DTileset",
-                "C3DTBatchTable",
-                "C3DTBoundingVolume",
-                "C3DTExtensions",
-                "C3DTBatchTableHierarchyExtension",
-                "C3DTFeature"
-            ],
-
             "Plugins": [
                 "DragNDrop",
                 "FeatureToolTip",
@@ -147,7 +136,6 @@
                 "Minimap",
                 "Scale",
                 "Searchbar",
-                "C3DTilesStyle"
             ]
         },
         "tutorialSections": {
diff --git a/docs/tutorials/Fundamentals.md b/docs/tutorials/Fundamentals.md
@@ -47,7 +47,7 @@ with `{@link WFSSource}` and [Tile Map Service](https://wiki.osgeo.org/wiki/Tile
 
 iTowns also has sources for many data formats: [vector tile](https://docs.mapbox.com/help/glossary/vector-tiles/) resources from [MapBox](https://www.mapbox.com/) with `{@link VectorTilesSource}`, [Potree](https://github.com/potree/potree) (`{@link PotreeSource}`) and 
 [Entwine](https://entwine.io/) (`{@link EntwinePointTileSource}`) 3D point clouds, [3DTiles](https://www.ogc.org/standards/3DTiles) 
-mesh (b3dm) and point clouds (pnts) from web servers (`{@link C3DTilesSource}`), Cesium ion `{@link C3DTilesIonSource}` and from Google api `{@link C3DTilesGoogleSource}`, 
+mesh (b3dm) and point clouds (pnts) from web servers (`{@link OGC3DTilesSource}`), from Cesium ion `{@link OGC3DTilesIonSource}` and from the Google API `{@link OGC3DTilesGoogleSource}`, 
 [GeoJSON](https://geojson.org/) with `{@link FileSource}` and `{@link GeoJsonParser}`, 
 [KML](https://www.ogc.org/standards/kml) with `{@link FileSource}` and `{@link KMLParser}`, [GPX](https://www.topografix.com/gpx.asp)
 with `{@link FileSource}` and `{@link GpxParser}` and oriented images with `{@link OrientedImageSource}`.
@@ -67,8 +67,8 @@ Several specific types of `Layers` exist, the use of which depends on the data t
 - `{@link FeatureGeometryLayer}` is a pre-configured `{@link GeometryLayer}` which simplifies its implementation in given cases (e.g. to extrude 3D buildings).
 - `{@link PointCloudLayer}` can be used to display 3D point clouds. Any point cloud formats are supported as long as the corresponding `Source` is provided.
 Some point clouds formats such as Potree, Las and Entwine already have parsers defined in itowns that you can use. For 3D Tiles point clouds (pnts), use
-`C3DTilesLayer`.
-- `{@link C3DTilesLayer}` can be used to display 3D Tiles datasets in version 1.0 (b3dm, pnts and gltf tiles are supported).
+`OGC3DTilesLayer`.
+- `{@link OGC3DTilesLayer}` can be used to display 3D Tiles datasets in version 1.0 (b3dm, pnts and gltf tiles are supported).
 - `{@link OrientedImageLayer}` can be used to display oriented images.
 
 
