gvSIG feature requests #3079
Skip the GEOMETRY field from Filter
| Status: | Invalid | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: | - | |||
| Category: | - | |||
| Target version: | - | |||
| gvSIG version: | 2.1.0 | Add-on resolve version: | ||
| Keywords: | Add-on resolve build: | |||
| Has patch: | Yes | Proyecto: | ||
| Add-on name: | Unknown | Hito: | ||
| Add-on version: |
Description
Because the GEOMETRY field is useless in the Filter, it can be skipped in order to avoid errors.
Related issues
History
#1
Updated by Joaquín del Cerro Murciano over 9 years ago
Antonio Falciano wrote:
Because the GEOMETRY field is useless in the Filter, it can be skipped in order to avoid errors.
Estoy un poco perdido...
¿ Donde exactamente crees que habria que eliminarlo ?
#2
Updated by Antonio Falciano over 9 years ago
- File select_by_attributes.png added
Joaquín del Cerro Murciano wrote:
Antonio Falciano wrote:
Because the GEOMETRY field is useless in the Filter, it can be skipped in order to avoid errors.
Estoy un poco perdido...
¿ Donde exactamente crees que habria que eliminarlo ?
Hi Joaquín,
in "Select by attribute" (Filter) windows, where we can apply an SQL statement in order to do selections.
#3
Updated by Antonio Falciano over 9 years ago
- File skipGEOMETRYfromFilter.patch
added
Has patch: Yes
I attach a patch that fixes the feature request.
#4
Updated by Álvaro Anguix over 9 years ago
- Has patch set to Yes
#5
Updated by Antonio Falciano over 9 years ago
- Target version set to 2.1.0-2268-rc4
#6
Updated by Álvaro Anguix over 9 years ago
Hello Antonio,
I don't know if it's good idea to skyp the geometry field...Certainly, we need to explain the possibilities of this field, because you can access to the object "geometry" and you can access all functions...
As example, with "[GEOMETRY].centroid().getX()" you have the X coordinate of the centroid of geometry.
#7
Updated by Antonio Falciano over 9 years ago
Álvaro Anguix wrote:
I don't know if it's good idea to skyp the geometry field...Certainly, we need to explain the possibilities of this field, because you can access to the object "geometry" and you can access all functions...
As example, with "[GEOMETRY].centroid().getX()" you have the X coordinate of the centroid of geometry.
Hi Alvaro,
as in subject, filtering the GEOMETRY field could have a bit of sense only in case of multigeometry datasource, e.g. DXF. But in the most part of cases (e.g. SHP) is not useful and could be only source of errors.
Instead, the calculation of some expressions (like in your example) can be very useful without doubts. However, I'd create a new command type (e.g. "Geometric") in addiction to Numeric, String and Data ones and add a lot of new commands/functions, such as x(), y(), area(), perimeter(), xCentroid(), yCentroid() and a lot more, masking the whole stuff behind ("[GEOMETRY].centroid().getX()") in order to make it more user-friendly. On the other side, it could be very tricky the access to all hidden functions.
#8
Updated by Antonio Falciano over 9 years ago
Antonio Falciano wrote:
Instead, the calculation of some expressions (like in your example) can be very useful without doubts. However, I'd create a new command type (e.g. "Geometric") in addiction to Numeric, String and Data ones and add a lot of new commands/functions, such as x(), y(), area(), perimeter(), xCentroid(), yCentroid() and a lot more, masking the whole stuff behind ("[GEOMETRY].centroid().getX()") in order to make it more user-friendly. On the other side, it could be very tricky the access to all hidden functions.
FYI, I've just opened a new feature request about this (#3113) and set #3109 as Invalid.
#9
Updated by Álvaro Anguix over 9 years ago
- Related to gvSIG feature requests #3113: Add a new geometric command type in the Field Calculator added
#10
Updated by Joaquín del Cerro Murciano over 9 years ago
- Target version deleted (
2.1.0-2268-rc4)
#11
Updated by Antonio Falciano over 6 years ago
- Status changed from New to Invalid