Can't import terminals using a geojson that doesn't have a field called "name"
Sarah Salem
I was trying to import a geojson that has 2 polygon geometries and one field called "nom" (in French) for terminal name, but when I clicked Process File it said that it's Invalid.
I tried again with the same geometry but with a field called "name" and it worked.
---
--> make sure it's clearly stated that the geojson MUST have a field called "name" for the terminal name
Photo Viewer
View photos in a modal
i
ibrahim Mohammed
Sarah Salem iif you scroll down or collapse the empty geometry overview it will give you detailed errors about what's exactly wrong with your imported data
and also give you an option to edit the record which has the issue directly from the window
i will enhance the style to make it more obvious and reduce the size of the collapsable map.
A
Abdelrahman Melegy
Actually the downloadable terminal template says we need to have "nameEn" and "confirmationStatus" + states that the geometry type is "polygon" not "multipolygon" ibrahim Mohammed
i
ibrahim Mohammed
Abdelrahman Melegy it does support MultiPolygon, i will add it to be the default in the downloadable template
H
Hazem Fahmi
ibrahim Mohammed MultiPolygon is an internal representation. It's an implementation detail. Most users will have terminals that are single polygons. We'll need the validation schema in the import to support both polygon and multipolygon. I'll create an issue to discuss this as I don't recall if the import command supports both already or not. You might not need to do any conversion on the frontend already.
i
ibrahim Mohammed
Hazem Fahmi
we do support multipolygon shape for the same terminal
on the commands and the schema validates against that, i tested with the mutliple files including a mixed file with some features polygon and some are multipolygons