Document the expected structure and format of custom areas files
Closed this issue · 2 comments
I tested the upload area tool with a geopackage containing one element in one layer.
Trying to upload a geopacakge with two elements in one layer failed with a verbose and not really user-friendly message, see screenshot at the end of the issue. The title is quite clear to me, but maybe not for everybody? I would also apply a defensive programming strategy so that the system fails nicely with a shorter and nicer error message instead of showing all details and traceback.
I think we should add a text mentioning:
- Which file formats are supported. At least list the most common you are sure about it.
- How many layers and how many elements the file should contain.
@niconoe: maybe the list above is not complete? Feel free to add more info if you think it's needed.
IMO showing this text on the my custom areas page is enough. If too long, we could bundle it in a "custom area file requirements" document visualized as a pop up? If a pop up is too much work, we can opt for a link to a GitHub page.
Hey @damianooldoni: all that is planned: the current error handling / polishing / design of the page is not good enough (that's why the page is hidden on the production site), I plan to largely improve all this at the end of August or early september!
That was done (directly on the "my custom areas" page)