Jerome St-Louis

> Does this too strongly assume that refinement is top-down? There may be other traversal strategies or analytics that benefit from availability being present in memory and fast random access....

If the content can be split up in nodes, one approach might be to include the geometry in only one of the tile (e.g. where its centre of mass lies),...

@lilleyse The confusion between content and tilesets was a great challenge for us in our implementation. It would be great to differentiate those better. See also https://github.com/CesiumGS/cesium/issues/9356 . With implicit...

I agree that a distinction between paths on disk vs. URL paths should be made. Regarding storing on disk, one file per tile might easily be too much overhead See...

@lilleyse > On top of easier editing and inspection we've found that geometry defined in a local coordinate system has better compression characteristics from an early test with EXT_meshopt_compression. For...

> with quantization it will have some arbitrary scaling factor, with an inverse scaling factor applied somewhere in the glTF node hierarchy. > Coming back to #504, it is an...

Hi @mingodad, wondering if you had a chance to figure out what issue that you ran into was? As I had mentioned, I think it likely had to do with...

@philvarner Regarding: > 2. I assume "NOT IS NULL" would also work, but this isn't mentioned. My understanding is that this is _not_ supported by cql2-text.

@cportele @pvretano all, As I brought up in #705 (with draft rules organization [suggestion here](https://github.com/opengeospatial/ogcapi-features/issues/723#issuecomment-1172603159)), I think that different rules for the expression types (e.g., boolean, array, number, text, that...

Ecere commits to an implementation in its GNOSIS Map Server.