Re: [udig-users] feature and data selection, etc.

["G. Allegri" <giohappy@xxxxxxxxx>]

Thanks for the hints about CQL and Axios extensions.

About the other points:

PostGIS: one could test table privileges using a query like this:
"SELECT has_table_privilege('my_table','SELECT');"
to be repeated on the db tables list.
it simply returns "t" or "f". It can be requested also against DELETE,
INSERT, etc.

SImbology: Mmm, maybe I wasn't clear. What I was proposing is to have
the possibility to set a number of classes, based on a vector
attribute, set the minimum and maximum size, and have this
classification used for the point size definition. It's easy to be
done... but I haven't setup the uDig dev environment to do it by
myself...
The same could be for color. Instead of having a fixed set of
palettes, the user should choose the end-members colors, the classes
and the attribute... et voilà.

2008/9/26 Jesse Eichar <jesse.eichar@xxxxxxxxxxxxxx>:
> Hi thanks for your comments:
>
>
>> Hi list.
>> I have a few questions about vector management:
>>
>> 1 - will feature selection with topolgical/geometrical tools be
>> supported? If yes, when?
>
> These are not difficult to implement the issue is more a danger of blowing
> out memory.  We are trying to find a nice way of detecting a large
> selection.  Possibly an method like that used in the TableView but I am
> undecided on the best method at the moment.  The functionality could be
> implemented in literally 1-2 days but the design is more problematic
>
>>
>> 2 - the same question is for SQL-like attributes selection
>
> You can select using CQL which is not as powerful as SQL but has
> similarities and can be quite powerful.  The implementation is becoming more
> and more powerful.  Maybe examples of what you desire would be helpful?
>
>>
>> 3 - proportional point symbols size: if I'm not wrong it isn't
>> possible at the moment. Will it be?
>
> This may be possible. Geotools comes with a number of functions for
> determining area and so on of a feature.  Since the size parameter of a
> point in SLD is an expression theoretically it could be the result of the
> function.   However I have not looked into this.  Perhaps a message to the
> Geotools-gt2-users list could answer this.
>
> If the question is about the UI component for doing this...
>
>
>>
>>
>> Two notes:
>> 4 - PostGIS connections: I've seen that an authenticated user can see
>> all the tables in a remote DB, even if he hasn't privileges on SELECT
>> on them. This raises an error if he tries to open them. Wouldn't be
>> better to avoid seeing the tables for which the users hasn't enough
>> grants?
>
> That does make sense.  I can add that if you give me the SQL to detect this.
>
>>
>> 5 - I don't know if it's a problem with the italian translation but
>> many tasks and elements have not intuitive denominations, like "Piano"
>> for what is commonly known as "Layer"...
>
> Translations are always tricky.  I think the Italian translation is very
> good but there is always room for improvement.  Not being an italian speaker
> I think someone else will have to comment on this.
>
> Jesse
>