simon-brooke / geocsv Goto Github PK

The REST call get-pin-image-names fails with an error

{"error":"java.lang.IllegalArgumentException: Not a file: jar:file:/home/simon/tmp/geocsv.jar!/public/img/map-pins"}

when 'geocsv' is run from a jar file (which is as I think it normally should be). We need to trap that error and, if we find it, search the jar file for the pin image names.

The set of pin images in the current repo are those needed by the project for which this was originally written. But it isn't much good as a general tool if it doesn't offer a broad range of pin images to pick from.

There's potentially two stages to this:

1. Ignore wrap-around across the international date line. That makes scaling and centring much easier!
2. If you have a small cluster of data that spans the international dateline, it would be really annoying if you got the whole world as your default map and had to zoom in. That's not going to be a common use case, so I suggest ignoring it for now.

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

1. csv - this would remain the default;
2. edn;
3. json
4. 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.

Is always good. I'd suggest using my internationalisation library.

If a user has deleted all the links to a particular page, the markdown file still exists; it would be useful to have a list of all the markdown pages in the content directory to allow users to locate files they want to link to.

(for Smeagol - damn, I've added it to the wrong project) An extension to gracefully display a collection of images.