|
From: Torben B. <tba...@bo...> - 2015-06-02 19:01:41
|
On Tue, Jun 2, 2015 at 10:15 AM, Andrea Aime <and...@ge...> wrote: > On Tue, Jun 2, 2015 at 6:13 PM, Torben Barsballe < > tba...@bo...> wrote: > >> >> One warning - Last time I interacted with the CSV datastore (in March) >> and GeoServer importer, it looked like it was still missing a few things. >> It seems the CSV datastore does not handle geometry columns especially >> well. CSV Import via the GeoServer importer UI only supports CSVs as lists >> of attributes (no geometry). >> > > This is because the code makes no attempt to figure out which strategy to > use, it could just parse the file once to figure out the best strategy, and > then again to actually > import it. That's what I did for the GML reader, where there is no good > way to just read the headers and guess the GML version, sometimes the > geometry type, and its CRS (under the common case that the schema is > nowhere to be found) > > I have done a bit of work trying to get this working for CSV stores in the GeoServer importer, although I haven't got anything final yet. I may get this working sometime in the future. Torben |