GeoBrowser(CSV) does not display a CSV file

[emanueldima]

@fungunga We tested the GeoBrowser with a csv file but it does not display anything on the map, only the first two columns of the csv file (attached, renamed to .txt because github would not attach it otherwise).

all-test-geo.csv.txt

[fungunga]

Same here: https://geobrowser.de.dariah.eu/beta/doc/geobrowser.html#specification-for-use, see https://projects.gwdg.de/projects/geo-browser/work_packages/34360

[emanueldima]

Ok, so the documentation says these fields are mandatory:

• Address
• TimeStamp, or TimeSpan:begin and TimeSpan:end
• Longitude
• Latitude

Do any other columns matter, or are they silently ignored? Would any csv work as long as it has these columns?

[fungunga]

I do not know either :-) Maybe you would need a title row? --> also improve error handling, and maybe documentation, too!

[fungunga]

It does work with the following file (created with the Datasheet Editor): https://cdstar.de.dariah.eu/dariah/EAEA0-0CB7-1F90-DF1B-0
In short that would be:
Address,Longitude,Latitude
University of Vienna,16.36077,48.213023
Karl Franzens University Graz - FÖDT/OEDT,15.447049,47.07874
Karl Franzens University of Graz - Romance Studies,15.45751183,47.07057311
Austrian Academy Corpus,16.37727769,48.20909235

Without time fields you just get places visualized.

[fungunga]

See a repository file here: https://trep.de.dariah.eu/1.0/dhcrud/21.T11991/0000-001B-4223-1/index

We do call https://switchboard.clarin-dev.eu/switchboard-test/#/trep/https%3A%2F%2Ftrep.de.dariah.eu%2F1.0%2Fdhcrud%2Fhdl:21.T11991%2F0000-001B-4223-1%2Fdata/application%2Fvnd.dariahde.geobrowser.csv from this index page, and we do not get the correct mimetype from swotchboard? Something wrong with the URL?

[emanueldima]

The switchboard does not yet distinguish between pure plain/text files and text/comma-separated-value files. You have to go to the switchboard and change the mediatype manually:

[fungunga]

But we give the correct mimetype with the switchboard call, and this mimetype is existing in the Switchboard, too. Don't you take the minetype from the API call, if existing?

[emanueldima]

In some cases the provided mimetype cannot be trusted and because of that we currently ignore it. I think you're right that we should not ignore it in this particular case (clarin-eric/switchboard#197)