gvSIG bugs #2621
Check the units of measure in the User CRS wizard
Status: | Closed | % Done: | 100% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | Joaquín del Cerro Murciano | |||
Category: | CRS | |||
Target version: | 2.1.0-2249-testing | |||
Severity: | Major | Add-on version: | ||
gvSIG version: | 2.1.0 | Add-on build: | ||
gvSIG build: | Add-on resolve version: | |||
Operative System: | Add-on resolve build: | |||
Keywords: | crs, units, semiaxis | Proyecto: | ||
Has patch: | Yes | Hito: | ||
Add-on name: | Unknown |
Description
If I select an User CRS (e.g. 3857) in the "New CRS" wizard and then click on the Edit button, I see the semiaxis expressed in millimeters, instead of meters.
Associated revisions
"New CRS" wizard, on the Edit button, I see the semiaxis expressed in millimeters, instead of meters. refs #2621
History
#1 Updated by Antonio Falciano over 9 years ago
- % Done changed from 0 to 100
- File DefinirDatum.patch added
Has patch: Yes
New unities of measure (uom) has been introduced in the latest versions of EPSG Registry, but they are unusual or inappropriate in reference to semiaxis and longitude measures. Skipping these unities, the old values of uom are restored in the comboboxes of the User CRS wizard. I attach the patch that solves the issue.
#2 Updated by Álvaro Anguix over 9 years ago
- Has patch set to Yes
#3 Updated by Álvaro Anguix over 9 years ago
- Assignee set to Joaquín del Cerro Murciano
#4 Updated by Antonio Falciano over 9 years ago
- Target version set to 2.1.0-2259-rc3
#5 Updated by Joaquín del Cerro Murciano over 9 years ago
- Status changed from New to Fixed
#6 Updated by Joaquín del Cerro Murciano over 9 years ago
- Target version changed from 2.1.0-2259-rc3 to 2.1.0-2248-testing
#7 Updated by Antonio Falciano over 9 years ago
- Target version changed from 2.1.0-2248-testing to 2.1.0-2259-rc3
- Status changed from Fixed to New
Hi Joaquín, I reopen the ticket because only 50% of the patch was applied in gvsig-jcrs:r277, i.e. the correction of longitude is missing.
#8 Updated by Joaquín del Cerro Murciano over 9 years ago
Antonio Falciano wrote:
Hi Joaquín, I reopen the ticket because only 50% of the patch was applied in gvsig-jcrs:r277, i.e. the correction of longitude is missing.
Disculpa, tube problemas al aplicar los ultimos parches de jCRS y acabe metiendolos a mano y se me escaparia ese pedazo. Si no me he equivocado esta terminado de aplicar en gvsig-jcrs:r285.
#9 Updated by Joaquín del Cerro Murciano over 9 years ago
- Status changed from New to Fixed
#10 Updated by Joaquín del Cerro Murciano over 9 years ago
- Target version changed from 2.1.0-2259-rc3 to 2.1.0-2249-testing
#11 Updated by Antonio Falciano over 9 years ago
- Status changed from Fixed to Closed