#1905: Import modules allow to import into northern UTM location southern data
--------------------------------+-------------------------------------------
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 6.4.3
Component: Projections/Datums | Version: svn-releasebranch64
Keywords: v.in.ogr, r.in.ogr | Platform: Unspecified
Cpu: Unspecified |
--------------------------------+-------------------------------------------
Steps to reproduce:
* create a new location from EPSG code 32636
* create a new shapefile in QGIS with EPSG code 32736
* import shapefile with v.in.ogr
Import should fail as there's a "small" difference between UTM 36N and 36S
but GRASS just announces "location appears to match" and imports file.
Blocking release as it might cause hard to catch nastiness later and might
indicate more serious breakage in projection code matching. Sorry.
Tested on:
14th March WinGRASS 6.4.x 55376 (or whatever as it's not possible to copy
revision number)
Originally reported in ML. http://osgeo-org.1560.n6.nabble.com/bug-with-
projection-systems-td5040244.html
Replying to [ticket:1905 marisn]:
...
> Import should fail as there's a "small" difference between UTM 36N and
36S but GRASS just announces "location appears to match" and imports file.
Replying to [comment:1 neteler]:
>
> There is no check for UTM in terms of "north" and "south". Since I
always struggle
> with strings, no idea how to implement that. Might be easy, though.