[epic] import/export
User story
- en tant qu’intégrateur web, je veux récupérer automatiquement les données par url
- en tant que nouvel utilisateur, je veux uploader mes données existantes
- en tant qu'utilisateur, je veux télécharger mes données pour les importer dans un autre outils
Fonctionnalités
Prototypes faits dans !481 (merged), !486 (merged) et !487 (merged), et on avait déjà un export geojson.
Problèmes identifiés et reste à faire:
-
basic export -
basic import -
export and import CLI -
fixes in export -
schema is missing a lot of stuff (wontfix) -
inconsistencies between csv and geojson -
stop using geo_attributes ? -
refactor in modules
-
-
export and import configuration -
column name mapping -
column exclusion -
geometry: -
wkt, geojson or lat/long -
projection
-
-
territory: table:colum = value -
files: paths or urls? separator? valeur vide? -
dates parsing -
boolean values
-
-
asynchronous import and export jobs -
import performance -
use column mapping (instead of finding the field by name for each row) -
batch by 100/1000 -
insert_all, maybe? ( -
improve turbo streaming by hooking stream notifications at the end of AR transactions (as mentioned in #196) -
read file in streaming
-
-
import auto-mapping -
support casing errors -
detect geometry:
-
-
import errors reporting -
invalid values (enum, bool, etc) -
blank for required -
line display
-
-
export performance -
write to file in streaming -
send_data in streaming? (This means we can’t know the file size in advance.)
-
-
reimport -
we need to specify the id column in the layer (see also #30)
-
-
import and export from Excel (and LibreOffice) (We need Roo for import and caxlsx for export) -
export the whole map -
as an excel multi-sheet table -
as a zip (#246)
-
-
support more formats -
shapefile -
geopackage -
umap “whole data” (it's a json of geojsons)
-
-
autocreate on import -
create columns when adding to a layer -
create a layer from scratch
-