Currently geocsv only reads data in CSV format, because that was the original requirement. But the client side actually reads data in JSON format, so the CSV is currently converted to JSON server side.
A format parameter could be read from the URL with values
csv - this would remain the default;
edn;
json
possibly others
This would mean that json could be passed straight through to the client, and edn could be transformed to json, which is trivial. It would make linking up feeds from other sources even easier.
Currently geocsv only reads data in CSV format, because that was the original requirement. But the client side actually reads data in JSON format, so the CSV is currently converted to JSON server side.
A
format
parameter could be read from the URL with valuescsv
- this would remain the default;edn
;json
This would mean that json could be passed straight through to the client, and edn could be transformed to json, which is trivial. It would make linking up feeds from other sources even easier.