Hi,

OJ can't support multiple geometries and it would be a difficult task to make this change.

Object type can be used

- to preserve original data as much as possible, but will generally not survive a complete roundtrip (maybe a more specific serialization format could achieve this goal, but with format like shapefile, we will rapidly encounter the 255 char problem).

- to offer plugin developpers a way to store structured data for in-memory usage (e.g. multiscale display as suggested by Jukka). I'm not aware of a concrete use-case though.

Michaël

envoyé : 29 septembre 2020 à 12:30
de : edgar.sol...@web.de
à : jump-pilot-devel@lists.sourceforge.net
objet : Re: [JPP-Devel] Run datastore query too tied to schema with Spatialide DS


On 9/29/2020 12:14, Rahkonen Jukka (MML) wrote:

edgar.sol...@web.de wrote:
29.9. 2020 13.01

On 9/29/2020 11:57, Rahkonen Jukka (MML) wrote:

>>> 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?

The above query without ST_AsText gives me a field with datatype "Object" and it contains value [B@11031df7

that's because everything without datatype is loaded as Object type, which default attrib representation is a simpy toString(), which "surprise" works well with Strings ;)

Perhaps it is good so? I have no idea about what to do with such object and if it round trips nicely in save-reload cycle with our supported file formats. I guess that object could as well be a jpeg image or any other blob.

yeah, more thinking of applying the blob-autodetecting here, in case we come around to it. keep in mind, we are talking merely representation in the attrib table. it'd be still backed by the blob based Object. and you are are right the question remains, how our writers/readers handle blobs, especially those that are text based (like GeoJSON). sure we could base64 encode it or such, but what i am saying is, i'm pretty sure it currently will blow up ;)

..ede


_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to