Import Shape Files

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Import Shape Files

Martin Bittens
Hello,

I am trying to import shape-files from QGIS 3.12.3 to GRASS GIS 7.8.3).
CRS  QGIS: EPSG 31983; CRS GRASS: EPSG 31983. EPSG 31983 is: SIRGAS
2000/UTM zone 23S.

The import is working fine, the projection fits but when I check the
meta data of the imported files I receive the message "Projection: UTM
(zone invalid)". In order to narrow down that error I did the following
in GRASS:

1.) I created 2 fresh locations/map sets: Loc1/Wells and Loc2/Wells
using the same CRS (EPSG 31983);

2.) I did the import of a shape file from QGIS (EPSG 31983) to GRASS
Loc1/Wells;

3.) Checking the meta data of the imported file results in "Projection:
UTM (zone invalid)";

4.) I changed the location/map set from Loc1/Wells to Loc2/Wells;

5.) In Loc2/Wells I "transferred" the imported shape file from
Loc1/Wells to Loc2/Wells using the command "v.proj";

6.) Checking the meta data now the message shows the correct projection
"Projection: UTM (zone 23)".


Are there any ideas why the shape file import in step 3 results in the
error message "Projection: UTM (zone invalid)"?


Thank you for your help.


Regards


Martin



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

_______________________________________________
grass-user mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user
Reply | Threaded
Open this post in threaded view
|

Re: Import Shape Files

Markus Neteler
Hi Martin

On Wed, Jun 24, 2020 at 3:04 PM Martin Bittens <[hidden email]> wrote:

>
> Hello,
>
> I am trying to import shape-files from QGIS 3.12.3 to GRASS GIS 7.8.3).
> CRS  QGIS: EPSG 31983; CRS GRASS: EPSG 31983. EPSG 31983 is: SIRGAS
> 2000/UTM zone 23S.
>
> The import is working fine, the projection fits but when I check the
> meta data of the imported files I receive the message "Projection: UTM
> (zone invalid)". In order to narrow down that error I did the following
> in GRASS:
>
> 1.) I created 2 fresh locations/map sets: Loc1/Wells and Loc2/Wells
> using the same CRS (EPSG 31983);

I just tried:

grass78 -c epsg:31983 ~/grassdata/utm31983
Starting GRASS GIS...
Creating new GRASS GIS location <utm31983>...
...
Welcome to GRASS GIS 7.8.4dev (0798df3d0)
...

GRASS 7.8.4dev (utm31983):~/ec_cloud_expert > 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"]],
            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"]]


Does the `g.proj -w` output look like this for you?

All the other steps basically depend on this.

Best
Markus


> 2.) I did the import of a shape file from QGIS (EPSG 31983) to GRASS
> Loc1/Wells;
>
> 3.) Checking the meta data of the imported file results in "Projection:
> UTM (zone invalid)";
>
> 4.) I changed the location/map set from Loc1/Wells to Loc2/Wells;
>
> 5.) In Loc2/Wells I "transferred" the imported shape file from
> Loc1/Wells to Loc2/Wells using the command "v.proj";
>
> 6.) Checking the meta data now the message shows the correct projection
> "Projection: UTM (zone 23)".
>
>
> Are there any ideas why the shape file import in step 3 results in the
> error message "Projection: UTM (zone invalid)"?
>
>
> Thank you for your help.
>
>
> Regards
>
>
> Martin
>
_______________________________________________
grass-user mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user
Reply | Threaded
Open this post in threaded view
|

Re: Import Shape Files

Markus Neteler
(please keep the list in CC)

On Thu, Jun 25, 2020 at 1:57 PM Martin Bittens <[hidden email]> wrote:

>
> Hello Markus,
>
> thank you for your reply.
>
> Usually I am creating locations and map sets with the GRASS start-up
> screen. After opening my 31983 location/mapset the command  "g.proj -w"
> results in:
> 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"]]
>
> This is almost the same result you sent. Just line appears in addition:
> TOWGS84[0,0,0,0,0,0,0].
>
>
> Using the command "grass78 -c epsg:31983 ~/grassdata/utm31983" like you
> did "g.proj -w" results in:
>
> 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"]],
>              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"]]
>
> This looks exactly like the result you sent.

Ok, that looks fine to me.

> But anyhow, it does not
> matter how I am creating locations/mapsets imported shape files are
> showing in the meta data results "Projection UTM (zone invalid).

Then maybe the .proj file of te shape file(s) is incomplete?

Can you make one file available (even off-list)?

Best
Markus
_______________________________________________
grass-user mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user
Reply | Threaded
Open this post in threaded view
|

Re: Import Shape Files

Markus Neteler
Hello Martin,

(again the list was not in copy)


On Fri, Jun 26, 2020 at 1:19 PM Martin Bittens <[hidden email]> wrote:
>
> Hello Markus,
>
> attached you can find a *.prj file created by QGIS.

You may try to replace it with the one attached, generated by GRASS GIS.

Best,
Markus

> Thank you very much for your help.
>
> Martin
>
>
>
> Am 6/25/2020 um 4:44 PM schrieb Markus Neteler:
> > (please keep the list in CC)
> >
> > On Thu, Jun 25, 2020 at 1:57 PM Martin Bittens <[hidden email]> wrote:
> >> Hello Markus,
> >>
> >> thank you for your reply.
> >>
> >> Usually I am creating locations and map sets with the GRASS start-up
> >> screen. After opening my 31983 location/mapset the command  "g.proj -w"
> >> results in:
> >> 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"]]
> >>
> >> This is almost the same result you sent. Just line appears in addition:
> >> TOWGS84[0,0,0,0,0,0,0].
> >>
> >>
> >> Using the command "grass78 -c epsg:31983 ~/grassdata/utm31983" like you
> >> did "g.proj -w" results in:
> >>
> >> 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"]],
> >>               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"]]
> >>
> >> This looks exactly like the result you sent.
> > Ok, that looks fine to me.
> >
> >> But anyhow, it does not
> >> matter how I am creating locations/mapsets imported shape files are
> >> showing in the meta data results "Projection UTM (zone invalid).
> > Then maybe the .proj file of te shape file(s) is incomplete?
> >
> > Can you make one file available (even off-list)?
> >
> > Best
> > Markus
>
>
> --
> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user

LT_AOI_1.prj (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Import Shape Files

Martin Bittens
Hello Markus,

first of all thank very much for your efforts.

Unfortunately, the error message "Projection UTM (zone invalid) did
appear anyhow although I replaced the *.prj file by that one you sent. 
But now I figured out the following (after importing the shape file and
making active):

- using in the layers display the edit button (left click on it and then
selecting "Metadata"), the result is "Projection UTM (zone invalid)" as
I reported;

- selecting in the layers display from the vector menu "Reports and
statistics/Basic vector metadata" and then clicking on "Run", the result
is again: "Projection UTM (zone invalid)";

- selecting in the layers display from the vector menu "Reports and
statistics/Basic vector metadata" and additionally activating in the
"Print" tab the option (e) - "Print extended metadata info in shell
script style", the result is now "Projection=UTM, zone=-23".


I don't know why this happened but obviously GRASS provides different
metadata for the same shape-file depending on the command you are using.


Regards


Martin





Am 6/26/2020 um 11:56 AM schrieb Markus Neteler:

> Hello Martin,
>
> (again the list was not in copy)
>
>
> On Fri, Jun 26, 2020 at 1:19 PM Martin Bittens <[hidden email]> wrote:
>> Hello Markus,
>>
>> attached you can find a *.prj file created by QGIS.
> You may try to replace it with the one attached, generated by GRASS GIS.
>
> Best,
> Markus
>
>> Thank you very much for your help.
>>
>> Martin
>>
>>
>>
>> Am 6/25/2020 um 4:44 PM schrieb Markus Neteler:
>>> (please keep the list in CC)
>>>
>>> On Thu, Jun 25, 2020 at 1:57 PM Martin Bittens <[hidden email]> wrote:
>>>> Hello Markus,
>>>>
>>>> thank you for your reply.
>>>>
>>>> Usually I am creating locations and map sets with the GRASS start-up
>>>> screen. After opening my 31983 location/mapset the command  "g.proj -w"
>>>> results in:
>>>> 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"]]
>>>>
>>>> This is almost the same result you sent. Just line appears in addition:
>>>> TOWGS84[0,0,0,0,0,0,0].
>>>>
>>>>
>>>> Using the command "grass78 -c epsg:31983 ~/grassdata/utm31983" like you
>>>> did "g.proj -w" results in:
>>>>
>>>> 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"]],
>>>>                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"]]
>>>>
>>>> This looks exactly like the result you sent.
>>> Ok, that looks fine to me.
>>>
>>>> But anyhow, it does not
>>>> matter how I am creating locations/mapsets imported shape files are
>>>> showing in the meta data results "Projection UTM (zone invalid).
>>> Then maybe the .proj file of te shape file(s) is incomplete?
>>>
>>> Can you make one file available (even off-list)?
>>>
>>> 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

_______________________________________________
grass-user mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user
Reply | Threaded
Open this post in threaded view
|

Re: Import Shape Files

Markus Neteler
Hi Martin,

On Wed, Jul 1, 2020 at 4:29 PM Martin Bittens <[hidden email]> wrote:
...
> I don't know why this happened but obviously GRASS provides different
> metadata for the same shape-file depending on the command you are using.

To analyse this in depth access to the dataset would be required (even
an excerpt as a reproducible example will do, i.e. one extracted
polygon or whatever is in your dataset).
Without that I would not know how to find out...

Regards,
Markus
_______________________________________________
grass-user mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user
Reply | Threaded
Open this post in threaded view
|

Re: Import Shape Files

Martin Bittens
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".

Regards


Martin



Am 7/1/2020 um 1:23 PM schrieb Markus Neteler:

> Hi Martin,
>
> On Wed, Jul 1, 2020 at 4:29 PM Martin Bittens <[hidden email]> wrote:
> ...
>> I don't know why this happened but obviously GRASS provides different
>> metadata for the same shape-file depending on the command you are using.
> To analyse this in depth access to the dataset would be required (even
> an excerpt as a reproducible example will do, i.e. one extracted
> polygon or whatever is in your dataset).
> Without that I would not know how to find out...
>
> Regards,
> Markus

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

_______________________________________________
grass-user mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user

Test_SG.zip (23K) Download Attachment
QGIS_LT_AOI_3.zip (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Import Shape Files

Markus Neteler
Hi Martin,

On Thu, Jul 2, 2020 at 1:57 PM Martin Bittens <[hidden email]> 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
_______________________________________________
grass-user mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user
Reply | Threaded
Open this post in threaded view
|

Re: Import Shape Files

Markus Neteler
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:

I have opened an issue for this:

(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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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


--

_______________________________________________
grass-user mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-user