gvSIG bugs #2739
Conversion between EPSG:3857 and EPSG:4326 doesn't match
Status: | Closed | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | Joaquín del Cerro Murciano | |||
Category: | CRS | |||
Target version: | 2.3.0-2416 (rev. org.gvsig.desktop-2.0.122) | |||
Severity: | Major | Add-on version: | ||
gvSIG version: | 2.1.0 | Add-on build: | ||
gvSIG build: | 2239 | Add-on resolve version: | ||
Operative System: | Add-on resolve build: | |||
Keywords: | 3857, web_mercator, proj4 | Proyecto: | ||
Has patch: | Hito: | |||
Add-on name: | Unknown |
Description
Steps in order to reproduce the issue:
- create a view and set its CRS as EPSG:3857;
- add an OSM layer (e.g. Mapnik) to the view;
- add an administrative boundaries layer defined in EPSG:4326.
Result: there's a quite consistent shift between the OSM layer and the boundaries one along the North direction (see the screenshot in attachment).
See also #2738.
Related issues
History
#1 Updated by Álvaro Anguix almost 10 years ago
- Related to gvSIG bugs #2738: EPSG:3857 Proj4 representation is not correct added
#2 Updated by Álvaro Anguix almost 10 years ago
- Assignee set to Joaquín del Cerro Murciano
#3 Updated by Álvaro Anguix over 9 years ago
- Related to gvSIG bugs #2793: WMTS en 3857 no se carga added
#4 Updated by Álvaro Anguix over 9 years ago
- Related to gvSIG feature requests #2864: Update the GDAL library added
#5 Updated by Álvaro Anguix about 9 years ago
- Related to gvSIG bugs #2526: CRS management with OSM layers added
#6 Updated by Álvaro Anguix over 8 years ago
- Target version set to 2.3.0-2416 (rev. org.gvsig.desktop-2.0.122)
- Status changed from New to Closed
It works now (2415)
#7 Updated by Antonio Falciano over 8 years ago
- Target version changed from 2.3.0-2416 (rev. org.gvsig.desktop-2.0.122) to 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153)
- Status changed from Closed to New
#8 Updated by Álvaro Anguix over 8 years ago
- File 3857_4326.png added
In my case (2415 in Lin64) it works fine (Image attached)
Before I had the same problem that you.
#9 Updated by Antonio Falciano over 8 years ago
Wonderful! Maybe the issue depends by the specific version of GDAL/OGR libraries used in Linux and win. There's no other explanation.
#10 Updated by Antonio Falciano over 8 years ago
- Status changed from New to Closed
#11 Updated by Joaquín del Cerro Murciano over 8 years ago
- Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.3.0-2416 (rev. org.gvsig.desktop-2.0.122)