Hi Jukka,
> I made some quick tests and did not notice any troubles with those.
> Improvement 5) with updated list of datasets is valueable.
>
> I have three suggestions about SRID:
>
> 1) The Open database layer UI might show the SRID info from the
> geometry_columns table for the selected dataset.
Good idea. I might wait after 1.6 because it is not a bug,
but I had a look and it should be easy to do.
(I will add the info in the combo box whowing the geometry column name)
> 2) User should be able to give the SRID while saving a new layer throug Save
> dataset as
It is already possible with Layer > Change SRID...
Agree that it would be useful in the Save as PostGIS menu,
It will need a bit more work though : everything in relation with SRID is
a bit confused in OJ (it is not SRID aware but there are some pieces
of code dealing with SRID here and there).
> 3) You should perhaps check the changes in AddGeometryColumn introduced in
> PostGIS version 2.0. I am not sure about what they mean in practise but they
> may have some consequences.
Shoud be OK.
I use AddGeometryColumn without the last argument added in PostGIS 2.0.
As a result, it should work with PostGIS 1.x, and geometries should be
defined
the new way in PostGIS 2.0 (i.e. geometry type + srid are defined as,
specific datatypes not as SQL constraint).
Michaël
> 4) There may be datatype error in this SQL which is sent by OpenJUMP
> SELECT
> AddGeometryColumn('uu'::varchar,'st_concavehull'::varchar,-1,'GEOMETRY'::varchar,2)
> SRID in the geometry_columns is integer, not varchar, and therefore I suppose
> that PostGIS takes the defaulut SRID. Therefore with PostGIS 1.5 new tables
> are getting SRID -1 but with PostGIS 2.0 which is the new default and means
> "Undefined - Geographic".
>
> SRID is not important for OpenJUMP but if the data are to be used with other
> programs or for direct operations with PostGIS functions it would be really
> good to have correct SRIDs in the database.
>
> -Jukka Rahkonen-
>
> Michaël Michaud wrote:
>
>> Hi Uwe, Jukka
>> 1 - I still cannot reproduce the WKB type 0 bug.
> Instead, I get from time to time a warning : "No such object exists".
> I had a look, but I think this is a concurent threading issue, that I'll
> not be able to solve in a short delay (just a warning though).
>
>> 2 - I made the writer / loader plugin case sensitive in a more
> consistent way.
> I agree this may puzzle users used to pure SQL, but I think there should be
> no severe drawback, and that we avoid many problems like that.
>
>> 3 - The name of the saved layer should always be displayed in the monitor
> (no more Saving 'null'...)
>
>> 4 - I improved error handling both in Data Store Layer and in Run
> DataStore Query.
> In both plugins, we now get the full SQL message (which is much more
> informative), and in DataStore Query, there is a special message if one
> forget to
> include a geometry column in the query.
>
>> 5 - The list of available datasets in DataStore Layer should always be
> uptodate
> (after a new table has been inserted from OJ for example). Before, the
> code used
> the same list of tables again and again to avoid useless queries, but
> it seems that
> the query against geometry_columns table is cheap and that one can do it as
> needed (I test with a local connection though).
>
>> 6 - A broken connection should not stop a project opening anymore. The user
> is invited to accept (the broken layer will throw warnings in OJ
> everywhen) or
> to remove the layer during the import.
>
>> Please test and let me know
>> Michaël
>
>>> Hi Landon,
>>> this only happens with PostGIS tables.
>>> There is no stack trace because
>> this error message only appears in the
>> statusline of OpenJUMP (left textfield).
>>
>> uwe
>> Am 21.03.2013 18:22, schrieb Landon Blake:
>>> Uwe:
>>>
>>> Does this happen with any layer, or just with PostGIS layers?
>>>
>>> Can you show me the stack trace?
>>>
>>> Landon
>>>
>>> On Thu, Mar 21, 2013 at 5:42 AM, Uwe Dalluege
>>> <uwe.dallu...@hcu-hamburg.de> wrote:
>>>> Hi,
>>>>
>>>> when I start OJ and open
>>>> a Data Store Layer I receive the error:
>>>>
>>>> com.vividsolution.jts.io.ParseException:
>>>> Unknown WKB type 0 (Runtime Exception)
>>>>
>>>> OpenJUMP shows the layer correct.
>>>> When I open the same table again
>>>> OJ reads the table without error.
>>>>
>>>> It seems that this error only appears
>>>> at first time I load the table.
>>>>
>>>> Regards
>>>>
>>>> Uwe
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Everyone hates slow websites. So do we.
>>>> Make your web apps faster with AppDynamics
>>>> Download AppDynamics Lite for free today:
>>>> http://p.sf.net/sfu/appdyn_d2d_mar
>>>> _______________________________________________
>>>> Jump-pilot-devel mailing list
>>>> Jump-pilot-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_d2d_mar
>> _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
