This seems like a silly problem, but when I am going to set up a new
location, my database name appears to be restricted in terms of a max number
of characters. Is there anyway to get around this short of making the
database at a higher level in short directory names?
--j
--
Jonathan A. Greenberg, PhD
NRC Research Associate
NASA Ames Research Center
AIM: jgrn307
MSN: jgrn307@hotmail.com
On Wed, Jan 12, 2005 at 12:01:31PM -0800, Jonathan Greenberg wrote:
This seems like a silly problem, but when I am going to set up a new
location, my database name appears to be restricted in terms of a max number
of characters. Is there anyway to get around this short of making the
database at a higher level in short directory names?
How many chars do you want for the database name?
Maybe we can extend it a bit.
I think making the name length arbitrarily long (or at least very, very
long) would be the best approach -- I'm thinking of users of macs and pcs,
mind you, where minimally they have to include:
/Users/username/Documents (mac)
/Documents and Settings/Username/My Documents (pcs)
I think the database name I was trying to use under MacOS X was:
/Users/username/Documents/projects/yosemite/grassdata or something along
those lines.
Would this be difficult to do?
--j
On 1/13/05 6:15 AM, "Markus Neteler" <neteler@itc.it> wrote:
On Wed, Jan 12, 2005 at 12:01:31PM -0800, Jonathan Greenberg wrote:
This seems like a silly problem, but when I am going to set up a new
location, my database name appears to be restricted in terms of a max number
of characters. Is there anyway to get around this short of making the
database at a higher level in short directory names?
How many chars do you want for the database name?
Maybe we can extend it a bit.
Markus
--
Jonathan A. Greenberg
Ph.D., Ecology
AIM: jgrn307 or jgrn3007
MSN: jgrn307@hotmail.com or jgrn3007@hotmail.com
>> This seems like a silly problem, but when I am going to set up a
>> new location, my database name appears to be restricted in terms of
>> a max number of characters. Is there anyway to get around this
>> short of making the database at a higher level in short directory
>> names?
I think making the name length arbitrarily long (or at least very,
very
long) would be the best approach -- I'm thinking of users of macs and
pcs, mind you, where minimally they have to include:
/Users/username/Documents (mac)
/Documents and Settings/Username/My Documents (pcs)
note that you can start GRASS with longer names via alternate ways:
when you start grass, e.g.:
$ grass57 /path/to/database/location/mapset
with g.mapset:
G> g.mapset mapset=new_long_mapset_name
with g.gisenv:
G> g.gisenv set="MAPSET=new_long_mapset_name"
the length is still finite, but longer than on the text startup screen.