gvSIG bugs #3508
cuelgue de gvSIG al cargar capa WFS
| Status: | New | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: | - | |||
| Category: | WFS | |||
| Target version: | - | |||
| Severity: | Minor | Add-on version: | ||
| gvSIG version: | 2.2.0 | Add-on build: | ||
| gvSIG build: | 2310 | Add-on resolve version: | ||
| Operative System: | Linux | Add-on resolve build: | ||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
- Creo una vista en EPSG:3857
- Cargo capa WFS en EPSG:900913
- gvSIG queda colgado
History
#1
Updated by Antonio Falciano almost 9 years ago
Hi José,
EPSG:900913 is not available in all versions of the EPSG Registry because it's ever been an official code (it was introduced by Google), so it should not be used in an OGC web service. The right code to use for Web Mercator is EPSG:3857 nowadays. gvSIG Can't convert value 'EPSG:900913' to Projection, simply because EPSG:900913 doesn't exist in its database.
#2
Updated by Antonio Falciano almost 9 years ago
But... if some CRSs (or coordinate operation methods) are not supported, gvSIG should not freeze. I confirm the bug.
#3
Updated by José Vicente Higón almost 9 years ago
Hi Antonio.
You're right. The correct EPSG it's EPSG:3857 for Web Pseudo-Mercator.
However, the problem is more related on the way gvSIG is requesting to WFS than the EPSG request itself. I think gvSIG is requesting without specifiying the CRS so the server is responsing with the default CRS the layer is configured.
In any case, gvSIG shouldn't freeze by this issue.
Regards.