GeoJSON file created in QGIS not accepted for import

[severinmenard]

This GeoJSON file is rejected, though it was simply created in QGIS OSM data downloaded with QuickOSM and saved as a GeoJSON file with the default options. Conakry_banques.zip

[Gaetanbrl]

@severinmenard works fine with this dataset if you export geojson as GeometryCollection geom types.

[Gaetanbrl]

@severinmenard issue to close ?

[jusabatier]

Just tried to export this data via QGIS : https://cloud.lepuyenvelay.fr/index.php/s/GmcmfBmeWaRrtoA

exactly as you did :

Notice : the wrning for SRS is because I transform from 2154 to 4326 and there is a loss of precision.

But it doesn't work :

Version de QGis : 3.22.4

[Gaetanbrl]

@jusabatier could you share the localConfig section for this plugin please ?

See https://mapstore.geosolutionsgroup.com/mapstore/docs/api/plugins#plugins.MapImport

(=> I'm not sur but GeoJSON seems activate by default)

[jusabatier]

I have no specific configuration, just the "MapImport".

[Gaetanbrl]

Toolip display something like "Out of limit" when i import your GeoJSON.

After reproject GeoJSON in 3857, @jusabatier it works

[Gaetanbrl]

@tdipisa nothing in the doc talk about "no reprojection available" or something like "default pojection to use is 3857 or 4326" :

https://docs.mapstore.geosolutionsgroup.com/en/latest/user-guide/import/

[jusabatier]

I just tried to export it as 3857, but it still not work : https://cloud.lepuyenvelay.fr/index.php/s/EiDjJmXMnppsKDR

[Gaetanbrl]

Ok, i test locally, so diff version...

[Gaetanbrl]

Ok @jusabatier my bad, my geojson was in 4326 and works here :

https://geoportail.lepuyenvelay.fr/mapstore/#/

[jusabatier]

Did you export it from QGis ? Because when I export it as GeometryCollection and 4326, it still not work ...

[Gaetanbrl]

yes from Qgis. See param and here i don't use specific params.

[jusabatier]

It still not work :

https://cloud.lepuyenvelay.fr/index.php/s/TsYR6mTxSrnGzec

I tested all possibility, 2154 / 3857 / 4326 with Automatic and GeometryCollection but nothing work

[Gaetanbrl]

A little analyse to understand because it's weird :

1. On import, MapStore will detect if we import layer or map, and will check extent validity

https://github.com/geosolutions-it/MapStore2/blob/master/web/client/components/import/dragZone/enhancers/useFiles.js#L42

2. Next The test will be :

https://github.com/geosolutions-it/MapStore2/blob/master/web/client/utils/CoordinatesUtils.js#L1069

If i use 4326 layer it works well with 3857 BBOX because 4326 BBOX values are lower than 3857 bbox values...

==== Example 1

with @jusabatier original 2154 layer

Will return False : return minx >= crsMinX && minY >= crsMinY && maxX <= crsMaxX && maxY <= crsMaxY;

== Example 2 - not better

with 3857 data

[Gaetanbrl]

Here, 3857 and 4326 seems suported but 3857 seems not detect as valid by the importer :

https://github.com/geosolutions-it/MapStore2/blob/fb3cafc486c2e03e093a957ccd891c4fe50b7bad/web/client/components/import/dragZone/enhancers/processFiles.jsx#L67-L68

Next, on import, the original file contain the correct CRS :

Later, MapStore will transform GeoJSON here :

https://github.com/geosolutions-it/MapStore2/blob/fb3cafc486c2e03e093a957ccd891c4fe50b7bad/web/client/components/import/dragZone/enhancers/processFiles.jsx#L151

... but harcode 4326 CRS here even if features have 3857 or 2157 CRS :

https://github.com/geosolutions-it/MapStore2/blob/ded5b4bf431187b0d32ccc8a87e7551a1609cf5b/web/client/utils/LayersUtils.js#L515-L522

... :/

[severinmenard]

No tag, update, or planed fix for this issue, @GeoSolutions?

[landryb]

hardcoding the CRS is gross, it should be taken (if available) from crs.properties.name and also translated from its urn: form.. i guess there's probably already a nodejs library handling such things, like https://www.npmjs.com/package/proj4

[Gaetanbrl]

Up with this geosolution topic (mail) :

https://groups.google.com/g/mapstore-developers/c/ZzBjY4zZ_F0