gvSIG bugs #4581

PostGIS: Zoom to layer with wrong extent

Added by Antonio Falciano almost 7 years ago. Updated over 6 years ago.

Status:Closed% Done:

0%

Priority:HighSpent time:-
Assignee:-
Category:Database
Target version:2.4.0-2830 (rev. org.gvsig.desktop-2.0.196)
Severity:Minor Add-on version:
gvSIG version:2.4.0 Add-on build:
gvSIG build:2829 Add-on resolve version:
Operative System: Add-on resolve build:
Keywords: Proyecto:
Has patch: Hito:
Add-on name:Unknown

Description

Steps to reproduce it:
  • create and open a view in EPSG:4326;
  • add a PostGIS layer defined in a different CRS than the view (e.g. EPSG:23032) as first layer;
  • add the same PostGIS layer of before as second layer;
  • change the view extent panning or zooming;
  • execute "Zoom to layer" in reference to the second one.
Result:
  • the view extent is different from the layer one.

esp_provincias_and_country.zip (2.06 MB) Joaquín del Cerro Murciano, 08/06/2017 12:11 PM

History

#1 Updated by Joaquín del Cerro Murciano over 6 years ago

  • Priority changed from Normal to High

#2 Updated by Joaquín del Cerro Murciano over 6 years ago

No he podido reproducir el error.
Las pruebas que he hecho son:
  • He cargado el shape "esp_provincias" en una vista en 23030.
  • Lo he exportado a una BBDD postgres.
  • He creado una vista en 4326.
  • He cargado la tabla "esp_provincia", en la ventana de abrir capa me ha reconocido la proyeccion como 23030.
  • No me ha hecho zoom automaticamente a la capa, esto seria un error.
  • La he vuelto a cargar la capa de nuevo.
  • He hecho zoom a la segunda capa que he caragado (la primera en el TOC), y lo ha hecho correctamente.
  • He desplazado la vista (PAN) y he hecho zoom a la primera capa. Lo ha hecho correctamente.
  • He cargado el shape "country" (que esta en 4326), y he comprobado que las capas estanam em su sitio.

El unico error que obserbo es que no me hace zoom automaticamente al cargar la primera capa de postgreSQL si la capa esta reproyectada.

#3 Updated by Antonio Falciano over 6 years ago

Joaquín, the error you mentioned is reported in #4579 yet. I can't reproduce it again too, very strange.
I will check it better tomorrow.

#4 Updated by Antonio Falciano over 6 years ago

  • Target version changed from 2.4.0-2850-final (rev. org.gvsig.desktop-2.0.220) to 2.4.0-2831 (rev. org.gvsig.desktop-2.0.197)
  • Status changed from New to Closed

I can't reproduce again the issue in build 2729, so I close the ticket. Sorry for the waste of time.

#5 Updated by Joaquín del Cerro Murciano over 6 years ago

  • Target version changed from 2.4.0-2831 (rev. org.gvsig.desktop-2.0.197) to 2.4.0-2830 (rev. org.gvsig.desktop-2.0.196)

Also available in: Atom PDF