On 9/29/2020 11:57, Rahkonen Jukka (MML) wrote: >> morning Jukka, >> On 9/29/2020 9:15, Rahkonen Jukka (MML) wrote: >>>> There would be still some corner cases left (select geom as geometry1, >>>> ST_Centroid(geom) as geometry2... >>> in theory our features may hold multiple geometries. just one can be shown >>> though and the second would be like some object attribute. not sure what'd >>> be a use case for that. >> what about the multiple geometry column issue? what would be a use case for >> that and how would you suggest to present those in OJ? ..ede > Use cases that I know are like having cities as polygons and points for > rendering at different scales, or having accurate/generalized geometries for > the same purpose. The same result can be achieved by having multiple layers > though there is then unnecessary multiplication of attributes as well. I > would wait until someone presents a really cool use case and pull request > about multiple geometry fields in OpenJUMP. Until that I suppose people feel > happy if this works also in the future as it works now and saves processed > geometry as WKT into text field. Example tested with Spatialite > > select geom, > ST_AsText(ST_Centroid(geom)) as centroid > from test limit 1;
do we currently warn/err out if someone actually selects two geometry columns? should we auto-convert to WKT additional geometry columns? ..ede _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
