gvSIG bugs #2877
WFS spatial filter is not persistent
| Status: | Invalid | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: | - | |||
| Category: | WFS | |||
| Target version: | - | |||
| Severity: | Minor | Add-on version: | ||
| gvSIG version: | 2.1.0 | Add-on build: | ||
| gvSIG build: | 2249 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
If I load a WFS layer using the spatial filter and then open its properties, the spatial filter extent is not visible and so it can't be saved in a project.
Related issues
History
#1
Updated by Álvaro Anguix over 9 years ago
- Related to gvSIG bugs #1281: Add WFS with filter area does not works added
#2
Updated by Antonio Falciano over 9 years ago
- Status changed from New to Invalid
Antonio Falciano wrote:
If I load a WFS layer using the spatial filter and then open its properties, the spatial filter extent is not visible
and so it can't be saved in a project.
After further testing, I found that if I open a project containing some WFS layers (both WFS 1.0.0 and 1.1.0), the spatial filter is persistent, while the "Enable cache" not (#2831). So I set this ticket as invalid. I'm sorry for the inconvenience.