gvSIG bugs #1551
Null pointer exception when strange coordinates are reprojected
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  Juan Lucas Domínguez | |||
| Category: | - | |||
| Target version: | 2.0.0-rc5 | |||
| Severity: | Add-on version: | |||
| gvSIG version: | 2.0.0 | Add-on build: | ||
| gvSIG build: | 2062 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: | Unknown |
Description
Null pointer exception when strange coordinates are reprojected
Example:
We have Canada in EPSG:23030 (somebody created it) and we want to reproject to EPSG:4326.
In this case, the reprojection library can have issues in its computation and returns a NULL point
History
#1
Updated by Juan Lucas Domínguez over 11 years ago
Added utility run-time exception class and used it when null point is returned by reprojection library.
Test:
- Create view in EPSG:4326 and load table "canada" from Postgis testing DB (the table is in EPSG:23030 even if it is Canada)
- An error message appears because the reprojection library ws unable to reproject those strange points
That is the expected behavior. We don't know what the reprojection library will do with strange reprojections like this, so if there is a problem like this, we show an error message and the layer is set to not visible
#2
Updated by Juan Lucas Domínguez over 11 years ago
- Status changed from New to Fixed
#3
Updated by Joaquín del Cerro Murciano over 11 years ago
- Target version changed from 2.0.0-final to 2.0.0-rc5
#4
Updated by Álvaro Anguix over 10 years ago
- Status changed from Fixed to Closed