Hi Martin, (back to cc of list)
I just got a chance to test and also got the "invalid zone" message issue: v.info LT_AOI_3 +----------------------------------------------------------------------------+ | Name: LT_AOI_3 | | Mapset: PERMANENT | | Location: sirgas_2000 | | Database: /home/mneteler/grassdata | | Title: | | Map scale: 1:1 | | Name of creator: mneteler | | Organization: | | Source date: Tue Aug 11 11:44:55 2020 | | Timestamp (first layer): none | |----------------------------------------------------------------------------| | Map format: native | |----------------------------------------------------------------------------| | Type of map: vector (level: 2) | | | | Number of points: 5 Number of centroids: 0 | ... | Projection: UTM (zone invalid) | ... This looks ok: g.region vector=LT_AOI_3 -p projection: 1 (UTM) zone: -23 datum: sirgas2000 ellipsoid: grs80 north: 7397570.18085686 south: 7397525.93235069 west: 303308.13155207 east: 303364.49017572 nsres: 1.00564787 ewres: 1.00640399 rows: 44 cols: 56 cells: 2464 I checked the source code and it "simply" a bug in the printing logic in v.info, as far as I see. Means: all fine, just v.info gets confused with negative UTM zone values: https://github.com/OSGeo/grass/blob/719725c22c9b2ceadbd009ae2f8acdeeef5a0fc9/vector/v.info/print.c#L497 I have opened an issue for this: https://github.com/OSGeo/grass/issues/892 (with a GitHub account you can "subscribe" to it be remain informed. You may simply ignore this "invalid zone" message for now. Best, Markus On Tue, Jul 7, 2020 at 2:18 PM Martin Bittens <martin.bitt...@gmx.de> wrote: > Hello Markus, > > what is the edit button? > Is that in GRASS? > > Sorry, that I have confused you a bit. Attached I am sending 2 > screenshots for a better explanation (GRASS_Edit_Button.jpg, > GRASS_Edit_Metadata.jpg) > > Just to summarize our discussion: > > 1.) Creating a location/mapset by: > > # create new location from SHAPE file: > grass78 -c LT_AOI_3.shp ~/grassdata/sirgas_2000 > Starting GRASS GIS... > Creating new GRASS GIS location <sirgas_2000>... > > 2.) g.proj -w is showing beside other information the correct > projection: "SIRGAS 2000 / UTM zone 23S" > > 3.) Import of LT_AOI_3.shp into the GRASS location/mapset which was > created in 1.) > > 4.) Checking the metadata of the imported shape file by using (in GRASS): > > - the edit button (explanation see attached screenshots) results in: > Projection UTM (zone invalid); > > - the v.info command results in: Projection UTM (zone invalid); > > - the v.info -w command results in: Projection UTM, zone -23. > > > That's where we are now. > > > Regards > > > Martin > > > > > > > > Regards > > Martin > > > > > Am 7/2/2020 um 5:53 PM schrieb Markus Neteler: > > Hi Martin, > > > > On Thu, Jul 2, 2020 at 10:03 PM Martin Bittens <martin.bitt...@gmx.de> > wrote: > >> Hello Markus, > >> > >> > >> that is exactly what I got (see one of my previous emails). > > I read them several times but I am still lost: > > > >> But...:-): > >> > >> If you import the shape-file you used for the setup of the > >> location/mapset into this location/mapset and then check the metadata of > >> the imported shape-file by > >> > >> -using the edit button; > > what is the edit button? > > Is that in GRASS? > > > > Sorry, I am doing so many things in parallel, I need a bit of more > detail. > > > > Cheers > > Markus > > > >> -the v.info command; > >> > >> -the v.info -w command; > >> > >> what do you get? > >> > >> > >> I get: > >> > >> -using the edit button: Projection UTM (zone invalid); > >> > >> -the v.info command: Projection UTM (zone invalid); > >> > >> -the v.info -w command: Projection UTM, zone -23 > >> > >> > >> That is what I did not figure out, why GRASS provides different meta > >> data for the same shape-file although the location/mapset meta did not > >> change and remains "SIRGAS 2000 / UTM zone 23S". > >> > >> > >> Regards > >> > >> > >> Martin > >> > >> > >> > >> Am 7/2/2020 um 3:26 PM schrieb Markus Neteler: > >>> Hi Martin, > >>> > >>> On Thu, Jul 2, 2020 at 1:57 PM Martin Bittens <martin.bitt...@gmx.de> > wrote: > >>>> Hello Markus, > >>>> > >>>> ok, let us try. > >>>> > >>>> Attached I send (as zip files): > >>>> > >>>> 1.) QGIS_LT_AOI_3.zip with a shape layer created in QGIS 2.14.0. It > >>>> contains contains 5 sample points extracted from an existing site > (EPSG > >>>> 31983); > >>>> > >>>> 2.) Test_SG.zip with the files from the grassdata directory created by > >>>> GRASS 7.8.3 after establishing the location "Test_SG" (EPSG 31983) and > >>>> importing the shape layer into "Test_SG". > >>> I tried and got this: > >>> > >>> # create new location from SHAPE file: > >>> grass78 -c LT_AOI_3.shp ~/grassdata/sirgas_2000 > >>> Starting GRASS GIS... > >>> Creating new GRASS GIS location <sirgas_2000>... > >>> ... > >>> Welcome to GRASS GIS 7.8.4dev (0798df3d0) > >>> ... > >>> > >>> GRASS 7.8.4dev (sirgas_2000):/tmp > g.proj -w > >>> PROJCS["SIRGAS 2000 / UTM zone 23S", > >>> GEOGCS["SIRGAS 2000", > >>> > DATUM["Sistema_de_Referencia_Geocentrico_para_las_AmericaS_2000", > >>> SPHEROID["GRS 1980",6378137,298.257222101, > >>> AUTHORITY["EPSG","7019"]], > >>> TOWGS84[0,0,0,0,0,0,0], > >>> AUTHORITY["EPSG","6674"]], > >>> PRIMEM["Greenwich",0, > >>> AUTHORITY["EPSG","8901"]], > >>> UNIT["degree",0.0174532925199433, > >>> AUTHORITY["EPSG","9122"]], > >>> AUTHORITY["EPSG","4674"]], > >>> PROJECTION["Transverse_Mercator"], > >>> PARAMETER["latitude_of_origin",0], > >>> PARAMETER["central_meridian",-45], > >>> PARAMETER["scale_factor",0.9996], > >>> PARAMETER["false_easting",500000], > >>> PARAMETER["false_northing",10000000], > >>> UNIT["metre",1, > >>> AUTHORITY["EPSG","9001"]], > >>> AXIS["Easting",EAST], > >>> AXIS["Northing",NORTH], > >>> AUTHORITY["EPSG","31983"]] > >>> > >>> To me it looks as expected. > >>> > >>> My software versions: > >>> > >>> g.version -rge > >>> version=7.8.4dev > >>> date=2020 > >>> revision=0798df3d0 > >>> build_date=2020-07-02 > >>> build_platform=x86_64-pc-linux-gnu > >>> build_off_t_size=8 > >>> libgis_revision=8e4dab571 > >>> libgis_date=2020-05-05T09:05:27+00:00 > >>> proj=6.3.2 > >>> gdal=3.0.4 > >>> geos=3.8.1 > >>> sqlite=3.32.2 > >>> > >>> Might it be that your PROJ installation is somehow broken? > >>> > >>> best, > >>> Markus > >> -- > >> This email has been checked for viruses by Avast antivirus software. > >> https://www.avast.com/antivirus > >> > > > > > -- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog
_______________________________________________ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user