gvSIG bugs #3584
RealVista 1.0 OPEN WMS is not loaded at all in gvSIG 2.1 and 2.2
| Status: | New | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: | - | |||
| Category: | WMS | |||
| Target version: | - | |||
| Severity: | Minor | Add-on version: | ||
| gvSIG version: | 2.2.0 | Add-on build: | ||
| gvSIG build: | 2313 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
The RealVista 1.0 OPEN WMS (registration needed here in order to obtain the service URL and use it according a dual CC license) is not loaded at all in gvSIG 2.1 and 2.2. Instead, the same service works perfectly in gvSIG 1.12 (very fast) and other clients. This is an extract from the gvSIG.log:
INFO AWT-EventQueue-0 org.gvsig.raster.wms.app.wmsclient.gui.wizard.WMSWizard - The layer cannot be added
org.gvsig.fmap.dal.exception.InitializeException: Exception intializing 'Wms Store'.
at org.gvsig.fmap.dal.impl.DefaultDataManager.createProvider(DefaultDataManager.java:761)
at org.gvsig.fmap.dal.impl.DefaultDataManager.intializeDataStore(DefaultDataManager.java:722)
at org.gvsig.fmap.dal.impl.DefaultDataManager.localOpenStore(DefaultDataManager.java:396)
at org.gvsig.fmap.dal.impl.DefaultDataManager.openStore(DefaultDataManager.java:405)
at org.gvsig.raster.wms.app.wmsclient.layer.FLyrWMS.setParameters(FLyrWMS.java:1016)
at org.gvsig.raster.wms.app.wmsclient.gui.panel.WMSParamsPanel.getLayerPlain(WMSParamsPanel.java:1663)
at org.gvsig.raster.wms.app.wmsclient.gui.panel.WMSParamsPanel.getLayer(WMSParamsPanel.java:1512)
at org.gvsig.raster.wms.app.wmsclient.gui.wizard.WMSWizard.getLayer(WMSWizard.java:877)
at org.gvsig.raster.wms.app.wmsclient.gui.wizard.WMSWizard.execute(WMSWizard.java:852)
[...]
On the other side, the same service as WMTS works fine, but it's offered only in EPSG:3857. So it's useless if e.g. someone wants to use it in gvSIG 3D in Italy at least.
History
#1
Updated by Antonio Falciano over 8 years ago
- File gvSIG_BN2415.log added
The issue persists also in gvSIG 2.3, build 2415. I attach the gvSIG.log, more verbose now.
For instance, there are some "I cannot get the transformation between..." e.g. EPSG:4326 and EPSG:32632, but this is only a conversion, so the trasformation parameters aren't necessary.