-
Presently, GAM uses its own directory structure; however if one wants to package this application for system installation, GAM will not (and should not) have access to alter its installation directori…
-
### Is your feature request related to a problem? Please describe.
Currently we mix all types of files in `/srv/off`:
- code
- static configurations files (like the taxonomy)
- local configuration…
-
### Checked for duplicates
No - I haven't checked
### 🐛 Describe the bug
Errors found in log:
While loading: https://pds-geosciences.wustl.edu/insight/urn-nasa-pds-insight_seis/data/xb/continuous_…
-
Seems like your Geo_data is assumed to be located outside of the `crop` directory with code.
Judging from this error trace.
I guess we should amend the code to retrieve data from the `.` folder, i…
-
### What's the issue?
The coverage and performance data are currently written to a GitHub Gist hosted by @tp832944. It will be more maintainable to write it to a location where all repo maintainers c…
-
The user input for locations is more often than not sub-standard. There are many items with locations like this:
```
"location": {
"type": "Place",
"geo": {
"type": "GeoCoordinates",
…
-
we have to talk about the locations for the test data
I put the LPJ folder structure from Maurizio in tests. But there is also data-raw and inst/extdata
I would put data that is only used for th…
-
### Checklist
- [X] I've looked through [the documentation](https://clementtsang.github.io/bottom/nightly/) and [existing open issues](https://github.com/ClementTsang/bottom/issues?q=is%3Aopen+is%…
-
We currently have `static-build/faqs` and `tests`. Would it make sense to have `data/faqs` and `data/tests`? Or move `tests` into `static-build`?
-
Hi. With cities=T, some texts with short sentences tend to favor United States:
`loc_data