gvSIG bugs #1887
User defined CRS. Bad refresh when messuring and values do not appear.
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  Juan Lucas Domínguez | |||
| Category: | CRS | |||
| Target version: | - | |||
| Severity: | Add-on version: | |||
| gvSIG version: | 2.0.0 | Add-on build: | ||
| gvSIG build: | 2066 | Add-on resolve version: | ||
| Operative System: | Linux | Add-on resolve build: | ||
| Keywords: | User CRS | Proyecto: | ||
| Has patch: | No | Hito: | ||
| Add-on name: | CRS management (org.gvsig.crs.extension) |
Description
When I created a new CRS (user defined), and add a layer for measuring a distance or an area, I had some troubles in order to define the polyline for measuring. It happened in both Distance and Area tool.
And also, none of the measures appeared on the bottom bar of the view.
I made the same test with a predefined CRS (an EPSG for instance) and the refresh goes ok and the values appeared on the bottom bar. It seems to be ONLY with user defined CRS.
You can test it adding the following wkt string for creating a new CRS:
PROJCS["ROU_USAMS",GEOGCS["GCS_Yacare",DATUM["D_Yacare",SPHEROID["International_1924",6378388.0,297.0]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",10002288.299],PARAMETER["Central_Meridian",-55.80],PARAMETER["Scale_Factor",1.0],PARAMETER["Latitude_Of_Origin",-0],UNIT["Meter",1.0]]
Thanks!
History
#1
Updated by Juan Lucas Domínguez over 10 years ago
- Assignee set to Juan Lucas Domínguez
#2
Updated by Álvaro Anguix over 10 years ago
- Status changed from New to Closed
En 2166 funciona correctamente. Lo cierro.