search

fititnt / spatial-data-maching

https://sdm.etica.ai/v/
GNU Affero General Public License v3.0
0 stars 0 forks source link

Implement configuration file #5

Closed fititnt closed 1 month ago

fititnt commented 1 month ago

Partially dependent on #4.

In special the first step (even without more options) could get more complex. And the webapp does not save these options. By implementing some kind of configuration file, user could save (and reuse) logic between attempts on how to initialize before the "Real time filter" step.

At the moment I'm not as sure if every option on configuration step would also be available on the UI.

About the language used to encode the configuration file, maybe we just go with YAML (sadly, it will require load one extra library) since is more human readable and have a side effect of not be confused by the importer with JSON/GeoJSON (which are actually used for data).

fititnt commented 1 month ago

Ok. Minimal viable product of this issue.

the parameter syntax uses conf[]= on the URL, and accept multiple configuration files. How they are merged in memory still need fine tunning (or documentation to make it predictable, however I'm not sure what would be a good default.

Also, the 1+ configuration files can be both be loaded by URL parameters or via upload. However, via upload the behavior if user upload both data files with the configuration and the configuration also reference remote URLs, is at the v0.6.0b2, also undefined (e.g. have a pattern, but unsure if document because migth want to change.