gvSIG bugs #3437
GetFeatureInfo en WMS 1.3.0 con CRS 4326
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  Cesar Martinez Izquierdo | |||
| Category: | WMS | |||
| Target version: | 2.2.0-2311-rc2 | |||
| Severity: | Minor | Add-on version: | ||
| gvSIG version: | 2.1.0 | Add-on build: | ||
| gvSIG build: | 2269 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
No funciona la herramienta info sobre un WMS 1.3.0 cuando hacemos una petición con un sistema de referencia con coordenadas en latitud/longitud.
El problema es debido a que en WMS 1.3.0, para sistemas de referencia con coordenadas en lat/lon, los ejes x e y están invertidos.
Por ejemplo, la siguiente petición no da ningún resultado:
http://localhost/cgi-bin/mapserv?map=/home/jvhigon/test/wms/mapfile.map&&REQUEST=GetFeatureInfo&SERVICE=WMS&QUERY_LAYERS=ejesycbfin2_wgs84&VERSION=1.3.0&INFO_FORMAT=application/vnd.ogc.gml&LAYERS=ejesycbfin2_wgs84&CRS=EPSG:4326&BBOX=-0.40093909481829637,39.44565064655173,-0.3326530258713589,39.50465387931035&WIDTH=537&HEIGHT=464&FORMAT=image/png&STYLES=default&TRANSPARENT=TRUE&I=38&J=149&FEATURE_COUNT=10000&EXCEPTIONS=XML
Porque el orden de las coordenadas es incorrecta y debería indicarse:
http://localhost/cgi-bin/mapserv?map=/home/jvhigon/test/wms/mapfile.map&&REQUEST=GetFeatureInfo&SERVICE=WMS&QUERY_LAYERS=ejesycbfin2_wgs84&VERSION=1.3.0&INFO_FORMAT=application/vnd.ogc.gml&LAYERS=ejesycbfin2_wgs84&CRS=EPSG:4326&BBOX=39.44565064655173,-0.40093909481829637,39.50465387931035,-0.3326530258713589&WIDTH=537&HEIGHT=464&FORMAT=image/png&STYLES=default&TRANSPARENT=TRUE&I=38&J=149&FEATURE_COUNT=10000&EXCEPTIONS=XML
Related issues
Associated revisions
Check the full layer extent for the isInside method. Don't swap the point coordinates on the featureInfo 1.3.0 request, as they are in xy screen coordinates. Fixes: #3437
History
#1
Updated by Álvaro Anguix about 9 years ago
Parece relacionado con este (ya resuelto): https://redmine.gvsig.net/redmine/issues/3266
Si tienes algún WMS para testearlo, puedo comprobar si pasa en el último build
#2
Updated by Álvaro Anguix about 9 years ago
- Related to gvSIG bugs #3266: Incorrect axis order on WMS 1.3.0 for some CRSs added
#3
Updated by Cesar Martinez Izquierdo almost 9 years ago
- Assignee set to Cesar Martinez Izquierdo
- Status changed from New to Fixed
#4
Updated by Cesar Martinez Izquierdo almost 9 years ago
- Related to gvSIG add-on requests #3470: New add-on for org.gvsig.raster.wms.app.wmsclient-2.2.10-65 added
#5
Updated by Álvaro Anguix almost 9 years ago
- Status changed from Fixed to Closed
#6
Updated by Joaquín del Cerro Murciano almost 9 years ago
- Target version set to 2.2.0-2311-rc2