edgar.sol...@web.de wrote:
28.9. 2020 23.19
> On 28.09.2020 21:46, Rahkonen Jukka (MML) wrote:
>> Yes, the only robust way to deal with SpatiaLite and GeoPackage geometries
>> would probably be to use the duck test like our DB Query Plugin does. If the
>> result is a blob that like a SpatiaLite
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 obj
edgar.sol...@web.de wrote
29.9. 2020 11.57
> 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 sh
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 c
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 g
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 geom
Hi,>>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? ..edeFor postgis, as far as I remember, we read the first geometry column as geometry and following geometry columns as String or Object (don't remember).In the
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 fo
On 9/29/2020 13:00, Michaud Michael wrote:
> Hi,
>
> OJ can't support multiple geometries and it would be a difficult task to make
> this change.
well, in theory it can. the model as is merely limits geometry to be _only one_
of the attributes. as Geometry is a proper attribute type we can easily
Revision: 6556
http://sourceforge.net/p/jump-pilot/code/6556
Author: ma15569
Date: 2020-09-29 12:18:07 + (Tue, 29 Sep 2020)
Log Message:
---
Recalculate cols and rows to avoid resampling of cell size
Modified Paths:
--
core/trunk/src/org/openjump/core/r
Ede,OJ can't support multiple geometries and it would be a difficult task to makethis change.>well, in theory it can. the model as is merely limits geometry to be _only one_ of the attributes. as Geometry is a proper attribute type we can easily add more than one, they won't be displayed though ;
Revision: 6557
http://sourceforge.net/p/jump-pilot/code/6557
Author: ma15569
Date: 2020-09-29 12:28:03 + (Tue, 29 Sep 2020)
Log Message:
---
Added other options. Saved cell size on output
Modified Paths:
--
core/trunk/src/org/openjump/core/ui/plugin/too
On 9/29/2020 14:22, Michaud Michael wrote:
> Ede,
>
>
> OJ can't support multiple geometries and it would be a difficult task to make
> this change.
>
> >well, in theory it can. the model as is merely limits geometry to be _only
> one_ of the attributes. as Geometry is a proper attribute type we c
Rob,
does that happen with all files or can you pinpoint a specific layer/image?
@Peppe: any idea? ..ede
On 9/24/2020 18:37, Roberto Rossi wrote:
> Hi Ede,
> I tested the release 6530
>
> Now there is no any problem in loading the raster file (TIF).
> But there is new problem in visualization.
>
On 28.09.2020 21:46, Rahkonen Jukka (MML) wrote:
> We have the robust DB Query that works fine (despite with XYZ geometries but
> that's another thing).
yeah, noticed that DBQuery choked on some geometries from a gpkg test file.
Jukka, would you mind providing some test files for geometry blobs
Il 29/09/2020 15:00, edgar.sol...@web.de ha scritto:
Rob,
does that happen with all files or can you pinpoint a specific layer/image?
Ede,
I noticed it for the continuos raster ad Digital terrain models (DTM),
slope, hillshade.
Rob
@Peppe: any idea? ..ede
On 9/24/2020 18:37, Roberto R
Hi,
Michaël must remember this better, but JTS did not understand the ISO codes for
3 and 4 dimensional geometries. This is probably fixed in the locationtech
version. See
https://lists.osgeo.org/pipermail/geos-devel/2013-December/006757.html
So it may be that once we move to GitHub and to new
On 29.09.2020 19:45, Rahkonen Jukka (MML) wrote:
> select AsGPB(casttoxy(castautomagic(geom))) from test limit 1;
right
select casttoxy(castautomagic(geom)) from random_points
works for my test gpkg data set. wrt. DBQuery
..ede
___
Jump-pilot-devel
Hi Jukka,wrt. z/m reading, the patch I had submitted to JTS has been included in locationtech repo just before the 1.5 release. So you're right, with our 1.14 vividsolutions version, we probably can't read both forms of WKB. Hopefully, it will be easier after our migration to OJ 2.0.Michaëlenvoyé
Revision: 6558
http://sourceforge.net/p/jump-pilot/code/6558
Author: ma15569
Date: 2020-09-30 04:35:50 + (Wed, 30 Sep 2020)
Log Message:
---
small refinings
Modified Paths:
--
core/trunk/src/org/openjump/core/ui/plugin/tools/generate/RasterizePlugIn.jav
Revision: 6559
http://sourceforge.net/p/jump-pilot/code/6559
Author: ma15569
Date: 2020-09-30 04:51:09 + (Wed, 30 Sep 2020)
Log Message:
---
Updated language codes
Modified Paths:
--
core/trunk/src/language/jump.properties
core/trunk/src/language/jum
21 matches
Mail list logo
