Thank you, Glynn :)
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
On Tue, Dec 1, 2015 at 2:40 AM, Glynn Clements wrote:
>
> Panagiotis Mavrogiorgos wrote:
>
>> Are there any restrictions to the location/mapset names?
>
> They may not contain any of the characters:
[...]
Thanks, Glynn, for these detailed explanations.
So save them for the future, cited here no
Panagiotis Mavrogiorgos wrote:
> Are there any restrictions to the location/mapset names?
They may not contain any of the characters:
/ " ' @ , = *
or space, DEL (code 127/0x7F), any control character or any 8-bit
character.
[source: lib/gis/legal_name.c]
Also, because map, mapset an
Panagiotis Mavrogiorgos:
> Are there any restrictions to the location/mapset names?
If I read this (following) correctly, the definition is in
"grass70/dist.x86_64-unknown-linux-gnu/include/grass/defs/gis.h", line
427 and after:
--%<---
/* make_mapset.c */
int G_make_mapset(const char *, const
On Wed, Nov 25, 2015 at 7:28 PM, Panagiotis Mavrogiorgos
wrote:
> It took me sometime to figure it out,* and in retrospect you can imply
> this from the r.mapcalc manual, but I couldn't find any specific reference
> for naming restrictions. So, are there any?
The manual talks about map names,
Hi all,
Are there any restrictions to the location/mapset names?
I just found out that if you use a numeric mapset (e.g. 2014_123) you have
to use single quotes in mapcalc expressions. e.g the following example will
raise an error:
r.mapcalc expression="foo=R1@2014_123"
results in:
syntax erro
