Re: [GRASS-user] Import Shape Files
Hi Martin, On Thu, Jul 2, 2020 at 1:57 PM Martin Bittens 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 ... ... 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",50], PARAMETER["false_northing",1000], 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 grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Question about Datum not recognised by GRASS
Sorry, the output of g.region -p is: projection: 99 (CGCS2000 / 3-degree Gauss-Kruger CM 120E) zone: 0 datum: ** unknown (default: WGS84) ** ellipsoid: grs80 north: 42.9967 south: 41.54 west: 118.6708 east: 121.465 nsres: 0.0008 ewres: 0.0008 rows: 1748 cols: 3353 cells: 5861044 -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Question about Datum not recognised by GRASS
Hi, I am quite new to GRASS and this is my first post, looking for some help here! I am now processing the dataset under *CGCS2000 / 3-degree Gauss-Kruger CM 120E*. But the dataset could not be recognised by GRASS when I trying to import the DEM data. The warning message kept poping up: WARNING: Datum not recognised by GRASS and no parameters found And the output from g.region -p is: projection: 99 (CGCS2000 / 3-degree Gauss-Kruger CM 120E) zone: 0 datum: ** unknown (default: WGS84) ** ellipsoid: grs80 north: 1 south: 0 west: 0 east: 1 nsres: 1 ewres: 1 rows: 1 cols: 1 cells: 1 How can I fix it? Best, Zac45 -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-dev] Testing the new GRASS GIS website: please help
On Thu, Jul 2, 2020 at 8:59 AM Rainer Krug wrote: > > It looks really I=nice - good job. That is the great design work done by Nicolas Bozon (in cc)! @all: Please be so kind to open issues here as they are much easier to deal with than through emails: https://github.com/OSGeo/grass-website/issues thanks Markus ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Testing the new GRASS GIS website: please help
On Wed, 1 Jul 2020, Markus Neteler wrote: As some of you might know, we have been working on the development and setup of a new and shiny GRASS GIS website (finally!) for a long time. It is now available for testing at: https://staging.grass.osgeo.org/ Markus, et al.: For the record, I prefer the current site's use of a single tab as I navigate from one page to another. The back button works reliably and keeps the top of the browser from becoming crowded with multiple tiny tabs. My preference is to not have a long string of tabs for a single application as I navigate among pages. I may well be in the minority on this and will, of course, accept whatever is decided yet still want my preference recorded for posterity. Best regards, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Storing raster maps
On Thu, 2 Jul 2020, Moritz Lennert wrote: There might be future changes to GRASS which would make this difficult with the current version of GRASS (e.g. plans to change the raster format / storage organisation). However, you will always have access to older versions of GRASS GIS and so should at least always be able to open old mapsets in those and then update if necessary. Otherwise, I think that well-compressed tiff files will remain readable for quite a long time. Moritz, Thanks for the insight. Perhaps if the raster storage format changes r.pack will be adapted to recognize an older format and automatically change it to the new format. Stay well, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Storing raster maps
On 1/07/20 23:55, Rich Shepard wrote: On Wed, 1 Jul 2020, Markus Neteler wrote: I see two options: - export the DEMs, still in GRASS GIS format, with r.pack (in a loop) - or simply package the mapset(s) containing the DEMs. Markus, With changes to GRASS over the years I was no sure whether making a tarball of the mapset would retain all information. There might be future changes to GRASS which would make this difficult with the current version of GRASS (e.g. plans to change the raster format / storage organisation). However, you will always have access to older versions of GRASS GIS and so should at least always be able to open old mapsets in those and then update if necessary. Otherwise, I think that well-compressed tiff files will remain readable for quite a long time. Moritz ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Import Shape Files
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 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 grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] How to user "solver=" option of r.cost/r.walk
Dear Benjamin,
On Wed, Jul 1, 2020 at 11:57 PM Benjamin Ducke wrote:
>
> Dear Grass Users --
>
> I am struggling to understand the usage of the
> "solver=" option featured by both r.cost and
> r.walk.
The implementation commit was this one (by Markus Metz):
https://github.com/OSGeo/grass/commit/2f86241cb733cf6c42a5f075aec9cb63be5bddc8
> The r.walk manual page gives no details about it.
That was probably an accidental omission and should be updated.
> The r.cost manual page does contain an illustration
> of the working principle, but no examples on how
> to quantify the cells in the solver map. So it's
> all a little too abstract for me.
>
> I understand the basic premise: I have a relatively
> coarse cost map, and r.cost's algorithm will often
> encounter cells with many neighbours that have the
> same cost. This produces ugly quantization effects
> ("steps") in least cost paths derived from such
> surfaces. To work around this problem, I have so
> far simply added some random noise to my cost
> maps. However, it seems to me that the "solver="
> option might be a more elegant, deterministic
> solution to this problem.
>
> So: Does anybody here have some experience with
> the "solver=" option of r.cost? What kind of
> values (ranges?) would a solver map contain?
> How does r.cost interpret theses values (as
> additional costs?). Could anyone come up with
> an example of how to quantify a useful solver
> map in practice?
Hope the author of the solver can enlighten us :-)
Best,
markusN
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-dev] Testing the new GRASS GIS website: please help
It looks really I=nice - good job. I haven’t tried many links, but the link to the WIKI opens in the same tab. I think it would be nice, if pages from different websites, i.e. with a different design language and navigation system, could open in a new tab. Also I am missing a link to installing GRASS from source. They should probably be in the Download section (source code download)? Just saw, that the source code is on the download page, but missing from the menu. Finally, the Manuals are also to download, so they should be probably also under Download? Cheers, Rainer > On 1 Jul 2020, at 20:28, Markus Neteler wrote: > > Dear all, > > As some of you might know, we have been working on the development and > setup of a new and shiny GRASS GIS website (finally!) for a long time. > It is now available for testing at: https://staging.grass.osgeo.org/ > > We will start the release procedure described in > https://github.com/OSGeo/grass-website/issues/180 in the next days. > Our goal is to officially announce the new website on the "birthday" > of GRASS GIS on July, 29th. By then all should be bright and nice, so > we need your feedback: please help with testing, checking links and > with solving of remaining issues: > https://github.com/OSGeo/grass-website/projects/1 > > Thanks so much for the final efforts! > > Best, > Markus and the new website team ([1]) > > [1] https://github.com/OSGeo/grass-website/graphs/contributors > ___ > grass-dev mailing list > grass-...@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
