docs(dem): v2 (MAPCO-8937) - #163
shimoncohen wants to merge 29 commits into
Conversation
|
| @@ -0,0 +1,965 @@ | |||
| --- | |||
There was a problem hiding this comment.
Decide if and where to put the WFS section
| <mc:links scheme="WCS" name="product-DSM" description="">{WCS_SERVICE_URL}/wcs?request=GetCapabilities</mc:links> | ||
| <mc:links scheme="WCS_BASE" name="product-DSM" description="">{WCS_SERVICE_URL}/wcs</mc:links> | ||
| <mc:links scheme="WFS_BASE" name="product-DSM" description="">{WFS_SERVICE_URL}/wfs?request=GetCapabilities</mc:links> |
There was a problem hiding this comment.
i don't recall we talked on the schemes mentioned here, WCS seems duplicate
There was a problem hiding this comment.
@asafmas-rnd We have WCS_BASE in our production too, we can think if we want to remove it.
I agree that going through the capabilities is the right call in general.
| @@ -42,7 +42,7 @@ flowchart LR | |||
|
|
|||
| Query **3D CSW catalog** service to find item(s) according to desired filter [example are here](/docs/ogc/protocols/ogc-csw/ogc-csw-examples) | |||
There was a problem hiding this comment.
Respond to each in a new comment, this isn't ok. And leave irrelevant things out of this PR.
There was a problem hiding this comment.
Terrain provider is part of 3d and will stay that way.
|
|
||
| :::warning | ||
|
|
||
| Currently the terrain provider is only available through the `3D catalog`. |
There was a problem hiding this comment.
That's not true in the "prod" environment, as we have several QMesh layers in the DEM catalog
There was a problem hiding this comment.
It is true. They are used for heights, not terrain.
| | **Field name / Partial name** | **Filter purpose** | | ||
| | ----------- | ----------- | | ||
| | footprint | Specific geographical area | | ||
| | ...Accuracy... | | |
There was a problem hiding this comment.
Please put valid values
There was a problem hiding this comment.
Why? Values shouldn't be here, they are in the catalog.
Merge dup added/removed field blocks into main tables. v2 gets a "Changes from last version" column (🆕), v1 gets "Changes in next version" (🗑️) — single source of truth per field instead of two tables listing the same rows. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
shimoncohen
left a comment
There was a problem hiding this comment.
Traced the guides step-by-step against dem-dev (helm-charts#684). WCS flow holds; catalog step issues below, plus deployment-side findings on helm-charts#684.
| <PropertyName>mc:productType</PropertyName> | ||
| <Literal>DTM</Literal> | ||
| </PropertyIsEqualTo> | ||
| <ogc:Intersects> |
There was a problem hiding this comment.
Fails against dem-dev pycsw v2: Invalid gml:LineString geometry. Missing gml:posList. The GML2 outerBoundaryIs/coordinates form isn't accepted; use GML3 gml:exterior > gml:LinearRing > gml:posList (lat lon order for EPSG:4326). Verified the GML3 form returns results.
| <mc:productVersion>1</mc:productVersion> | ||
| <mc:region>region</mc:region> | ||
| <mc:sensors>sensors</mc:sensors> | ||
| <mc:srsId>srs_id</mc:srsId> |
There was a problem hiding this comment.
srs_id placeholder; other examples use 4326. Same in download/README.md.
| <mc:productVersion>1</mc:productVersion> | ||
| <mc:region>region</mc:region> | ||
| <mc:sensors>sensors</mc:sensors> | ||
| <mc:srsId>srs_id</mc:srsId> |
There was a problem hiding this comment.
srs_id placeholder; should be 4326 like the other examples.
| <mc:id>d2d812ba-40b7-4dfe-b3e7-869356467d3a</mc:id> | ||
| <mc:ingestionDateUTC>2025-12-31T09:55:51Z</mc:ingestionDateUTC> | ||
| <mc:insertDateUTC>2025-12-31T11:00:00Z</mc:insertDateUTC> | ||
| <mc:links scheme="WCS" name="srtm30-DSM" description="">{WCS_SERVICE_URL}/wcs?request=GetCapabilities</mc:links> |
There was a problem hiding this comment.
Links named srtm30-DSM on a record with productType DTM.
| end | ||
|
|
||
| c[<b>Step 1</b><br/>Catalog] --> d | ||
| d[<b>Step 2</b><br/>Get Capabilities] --> e |
There was a problem hiding this comment.
GetCapabilities and DescribeCoverage are both labelled "Step 2" while the sections treat them as parts of Step 2; also no Metadata edge into GetCapabilities.
| | 🆕 | mc:maxAbsoluteAccuracyLEP90 | double | LEP90 max absolute vertical plane accuracy range in meters | | ||
| | 🆕 | mc:minRelativeAccuracyLEP90 | double | LEP90 min relative vertical plane accuracy range in meters | | ||
| | 🆕 | mc:maxRelativeAccuracyLEP90 | double | LEP90 max relative vertical plane accuracy range in meters | | ||
| | 🆕 | mc:minHorizontalAccuracyCEP90 | double | | |
There was a problem hiding this comment.
mc:min/maxHorizontalAccuracyCEP90 have no description.
| In the Response, look for desired data according to profile definition. | ||
|
|
||
| ## Get terrain provider URI (Step 2.1) {#step-2.1} | ||
| In the Response, look for a `link` tag with `schem="TERRAIN_QMESH"`, this will be the link you need to get the data. |
There was a problem hiding this comment.
Typo: schem= → scheme=.
|
|
||
| ```javascript | ||
| // **Optional** add to Cesium terrain provider in order to clamp 3d models to the ground or investigate terrain | ||
| viewer.terrainProvider = new Cesium.TerrainProvider({ |
There was a problem hiding this comment.
Cesium.TerrainProvider is an abstract interface, not constructible. Use Cesium.CesiumTerrainProvider.fromUrl(resource) (or new Cesium.CesiumTerrainProvider({ url }) on older Cesium). Also line 164 "v84": Cesium versions are 1.x, which one is meant?
| The following guide will help you understand, ***Step-by-step*** how to add a `terrain provider` to your application. | ||
|
|
||
| ## Flow diagram | ||
| ```mermaid |
There was a problem hiding this comment.
Diagram has a "STEP 3.1" node but there's no Step 3.1 section (Cesium is under Step 3).
The GML2 outerBoundaryIs/coordinates polygon is rejected by the catalog
("Missing gml:posList"); the GML3 exterior/posList form was verified on
dem-dev. productSubType is a declared v2 queryable (helm-charts#684
mappings.py / mc_dem profile) missing from the table.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Pushed 29d4148 from a
|
- height_extraction: coverageId prefix note is WCS-version specific (dem: in 1.0.0 and 2.0.1, dem__ only in 2.0.1); typos; srsId example - terrain_provider: terrain link is in the DEM catalog too; scheme= typo; link name matches live records; Cesium fromUrl (min 1.104) - CesiumTerrainProvider: replace removed url option and readyPromise with fromUrl; terrainProvider is set on viewer, not viewer.scene - download: srsId example Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>




No description provided.