OpenAtlas

Just wanted to add it would be very useful to add many geometries in one go just in case this wasn't meant implicit already. What I mean is not just many geometries for one entry but also for multiple entities.
But first we should implement adding entities themselves.

• link to existing Place entity through id field
• link to types through id if geojson import creates a new entity
• create one entity with n geometries

with any amount of geometries coming from a geojson. Of course, it does only basic forms of data validation, but if the input data is fine, it works like a charm.

I will try to write specifications of such an import function until the meeting 28.01.21, so we can discuss this. The main format of data import will be json. Later we can add something like csv, excel and xml, because they are quite easy to convert to json.

Some libraries for reading shapefile:
https://gis.stackexchange.com/questions/113799/reading-shapefile-in-python

If we consider a shapefile import, this would probably need its own user interface in order to select which feature of the shapefile is considered to be imported.
A shapefile can contain multiple geometries/features like a "geom" table in PostGIS. So we would have to read the shapefile and let the user select from a list or table with a geometry preview which feature should be imported and linked to the respective entity. Also the Coordinate Reference System needs to be transformed to WGS84. Therefore the shapefile must contain the respective information or the user has to provide it.
I think also some kind of bulk import would be a good idea. Given the example of a cemetery plot, one could enter all the graves first and then load the shapefile of the graves. In the next step the OpenAtlas features could be correlated with the ones from the shapefile. This would really accelerate the data acquisition with already existing digital geometries e.g. in shapefile format.
Technically this could also be done with shp2pgsql in PostGIS: https://gis.stackexchange.com/questions/39238/how-to-import-using-shp2pgsql

This would also be interesting for INDIGO to import our sections, which we created in GIS.

shp2pgsql seems to be already part of the PostGIS Debian package and can be called (in bullseye, 3.1.1)
Next step would be to design the workflow when importing shape files.

Added a switch, if a polygon is entered, to choose if area or shape.

I have one major issue, since leaflet uses reversed coordinate system, the entered coordinates have to be reversed. I got it working for points and linestrings, but the polygon coordinates won't change. I have really no idea why and maybe someone who is more educated in JavaScript can take a look at it.

Otherwise, it is working with these test WKT strings:

POINT(30 10)
LINESTRING(30 10, 10 30, 40 40)    
POLYGON((30 10, 40 40, 20 40, 10 20, 30 10))    

Fixed the problem with the polygon.
There is one UI issue left, which I need help with. It is very Leaflet specific, so I maybe ask Christoph.

After that, it is ready to deploy.

Translations done