Folder structure making data extraction painful

[rbanick]

This is an outtake from the OpenDRI Comoros team's use of OpenMapKit

This is not an issue but a feature request. The use of a folder structure on the backend makes data extraction very painful if you want individual .OSM files or the whole mess in any way other than what's exported directly from OMK Server. Scripting and command line tools to accomplish this are beyond the capabilities of many of our users.

It would be helpful to have a feature where you could dump to a database or dump all .OSM into one folder.

[dalekunce]

dumping all osm or csv is possible via API endpoints already. @hallahan can you bump this into the documentation to make it more explicit.

I like the idea of getting a zip of the osm files as well. @hallahan is that possible

[rbanick]

I made a mistake and posted this in the OMK Server. The problem for our team was the folder structure on the Androids themselves. This was a problem as they discarded the Server and extracted directly from the phones during our project.

I do think the API calls need to be more extensively documented. If memory serves correctly some of the more complex ones are only documented on Github isssue tickets from months and months ago.

Sorry for any confusion. Shall I cross-post this to OMK Android?