Mercartor Output, doesnt specify crs in GeoJSON file

[Scartography]

How it is:

{
"type": "FeatureCollection",
"features": [
{"geometry": {"coordinates": [[[1066449.4186347763, 6271505.296742128], [1066449.4186347763, 6281289.2363626305], [1056665.4790142737, 6281289.2363626305], [1056665.4790142737, 6271505.296742128], [1066449.4186347763, 6271505.296742128]]], "type": "Polygon"}, "properties": {"col": 2156, "row": 1406, "zoom": 14}, "type": "Feature"},
...

How it should be:

{
"type": "FeatureCollection",
"crs": { "type": "name", "properties": { "name": "urn:ogc:def:crs:EPSG::3857" } },
"features": [
{"geometry": {"coordinates": [[[1066449.4186347763, 6271505.296742128], [1066449.4186347763, 6281289.2363626305], [1056665.4790142737, 6281289.2363626305], [1056665.4790142737, 6271505.296742128], [1066449.4186347763, 6271505.296742128]]], "type": "Polygon"}, "properties": {"col": 2156, "row": 1406, "zoom": 14}, "type": "Feature"},
...
I suspect, this might be an issue for the mapchete Geotiff Outputs, as well. Please double-check the writer driver if there is any.

Petr

[ungarj]

Custom CRS has been removed from the spec, so a GeoJSON should only contain WGS84 lat/lon coordinates.

You are right, the current implementation is not optimal. I think the best way to be standard conform would be to reproject mercator tile boundaries to WGS84 before dumping a GeoJSON.