Hi,
We have two alternatives for saving data into PostGIS: "PostGIS table" and
"PostGIS table (new)". I wonder if "new" in the latter means that the driver
is new and better and it will replace the old driver in the future. Or does
"new" mean that the driver can only create new tables and not
Hi Jukka,
PostGIS table (new) is supposed to replace the old one at some point,
but both have a rich set of options which makes the comparison difficult
and I have only had very few feedback on the second until now.
Fundamentally, the old one load a table, then disconnect, then offers a
few opti
Revision: 5138
http://sourceforge.net/p/jump-pilot/code/5138
Author: edso
Date: 2016-11-02 13:21:37 + (Wed, 02 Nov 2016)
Log Message:
---
deprecate old WorkbenchFrame.log() methods
Modified Paths:
--
core/trunk/src/com/vividsolutions/jump/workbench/ui/Wo
Revision: 5139
http://sourceforge.net/p/jump-pilot/code/5139
Author: edso
Date: 2016-11-02 13:25:13 + (Wed, 02 Nov 2016)
Log Message:
---
deprecate old WorkbenchFrame.log() methods, missing tag
Modified Paths:
--
core/trunk/src/com/vividsolutions/jump/wo
On 01.11.2016 14:57, jump-pilot-...@lists.sourceforge.net wrote:
> Revision: 5137
> http://sourceforge.net/p/jump-pilot/code/5137
> Author: michaudm
> Date: 2016-11-01 13:57:35 + (Tue, 01 Nov 2016)
> Log Message:
> ---
> Fix #438 Exception while saving the project before
Mike, you mean WorkbenchFrame.log(...)? the missing t should be the reason that
it does not print a stack.
i guess what i wanted to achieve was some backward compatible info logging.
level info shouldn't print stacks, so it is ignored. but let me fix it as
ignore or use it, depending on the log
Revision: 5140
http://sourceforge.net/p/jump-pilot/code/5140
Author: edso
Date: 2016-11-02 13:44:14 + (Wed, 02 Nov 2016)
Log Message:
---
inform user of projects saving issues, log properly
Modified Paths:
--
core/trunk/src/com/vividsolutions/jump/workbe
Hi,
Perhaps at some point the old one could be changed back to read-only with
dynamic refresh.
I made some tests and at least I can edit, delete, and insert features into
tables which are created with GDAL and with OpenJUMP itself. I had brand new
versions: PostgreSQL 9.6.1 and PostGIS 2.3.
Revision: 5141
http://sourceforge.net/p/jump-pilot/code/5141
Author: edso
Date: 2016-11-02 15:38:01 + (Wed, 02 Nov 2016)
Log Message:
---
make Logger more robust
Modified Paths:
--
core/trunk/src/com/vividsolutions/jump/workbench/Logger.java
Modified: c
Revision: 5142
http://sourceforge.net/p/jump-pilot/code/5142
Author: edso
Date: 2016-11-02 15:42:27 + (Wed, 02 Nov 2016)
Log Message:
---
better errorhandling when exiting OJ
Modified Paths:
--
core/trunk/src/com/vividsolutions/jump/workbench/ui/Workbenc
Mike,
i just refined the errorhandling r5142 and fixed the NPE you mentioned. thx for
pointing that out! ..ede
On 02.11.2016 15:02, Michaud Michael wrote:
> OK, I'll check your change tonight, thanks,
>
>
>
> Michaël
>
> De : edgar.sol...@web.de
>
> Date d'envoi : mercredi 2 novembre 2016
Hi,
I opened some data from GeoJSON and I can't edit the schema. Apply changes
yields just an error message. However, if I save the data into JML or GeoJSON
and open it from the disk, then I can edit the schema. So unfortunately I
can't provide with test data. Here is the error, though
java
Jukka,
can you send me a small GeoJSON example file to replicate your issue? ..ede
On 02.11.2016 17:12, Rahkonen Jukka (MML) wrote:
> Hi,
>
>
>
> I opened some data from GeoJSON and I can’t edit the schema. Apply changes
> yields just an error message. However, if I save the data into JML or
is this sensitive data, or why did you write "So unfortunately I can’t provide
with test data." ..ede
On 02.11.2016 17:16, edgar.sol...@web.de wrote:
> Jukka,
>
> can you send me a small GeoJSON example file to replicate your issue? ..ede
>
> On 02.11.2016 17:12, Rahkonen Jukka (MML) wrote:
>>
Hi Ede,
Sorry, I have problems with creating a small GeoJSON that leads to this issue.
I got the problematic layer by opening a big GeoJSON file but if I copy a few
features from that layer to a new layer with Replicate features, then the
problem disappears. I have also tried to make a short Ge
Thanks,
Should be fine now ;-)
Michaël
Le 02/11/2016 à 16:43, edgar.sol...@web.de a écrit :
> Mike,
>
> i just refined the errorhandling r5142 and fixed the NPE you mentioned. thx
> for pointing that out! ..ede
>
> On 02.11.2016 15:02, Michaud Michael wrote:
>> OK, I'll check your change tonig
Hi Jukka,
Thanks for the tests.
You table has been created with GDAL right ? Because when a table is
created from OpenJUMP, I declare only "geometry"
without further constraint as a OpenJUMP layer can contains any geometry.
To achieve what you ask in the general case may be quite complex,
be
Hi,
Yes, that table was created with GDAL. By default it takes the first feature
from a shapefile and uses that as a template for creating the PostGIS table.
Quite often it is polygon, which leads to an error when the first multipolygon
is met, and a new conversion with an option "-nlt promote_
nice :).. ede
On 02.11.2016 19:48, Michaël Michaud wrote:
> Thanks,
>
> Should be fine now ;-)
>
> Michaël
>
>
> Le 02/11/2016 à 16:43, edgar.sol...@web.de a écrit :
>> Mike,
>>
>> i just refined the errorhandling r5142 and fixed the NPE you mentioned. thx
>> for pointing that out! ..ede
>>
>
19 matches
Mail list logo