As far as I understand the issue, there’s this another GML representation of EPSG:4326, which happens to be urn:ogc:def:crs:EPSG::4326 but isn’t included in the default CRS names.
This is how geoserver returns GeoJson when making WFS requests, just like in your example.
There are multiple solution to this :
My first (and ugly) solution was to load your geojson and manipulate it’s crs object to conform to the crs names that supported by Cesium before passing to GeoJsonDataSource, like this :
// Get your geojson from geoserver or wherever it is stored
var geojson = loadYourGeoJson();
// Change the projection to match the one supported by Cesium
geojson.crs.properties.name = “EPSG:4326”;
// Load the geojson
Cesium.GeoJsonDataSource.load(geojson);
``
My second approach was to add the CRS name to the static property on the GeoJsonDataSource, since it’s the same projection we can reuse the same function
// Just add our CRS to the crs names and point it to the same function
Cesium.GeoJsonDataSource.crsNames[‘urn:ogc:def:crs:EPSG::4326’] = Cesium.GeoJsonDataSource.crsNames[“EPSG:4326”];
``
My third solution would be to ask Cesium guys to simply add this CRS name to the defaults since it seems to be just another representation of those that are already there
var crsNames = {