[GRASS-dev] g.mlist list multiple types from all mapsets

[Anna Petrášová]

Hi,

another option (you might have considered it already) is to allow option
mapset to have multiple inputs. So 2 steps would be needed, first get all
mapsets with g.mapsets -l and then g.mlist with these mapsets. I suppose
you need it for the wxDataCatalog?

Anna


On Sun, May 25, 2014 at 7:45 AM, Huidae Cho <grass4u at gmail.com> wrote:

> Martin,
>
> g.mlist already has -t flag for printing element types.
> rast/x at g6
> vect/b at g6
> vect/obce6 at g6
> vect/kltm50 at PERMANENT
>
> Regarding all mapsets search, it should be (1) because a new flag for all
> mapsets & mapset=. (default for the current mapset) have a conflict meaning
> and can be confusing. Maybe, mapset=- (minus)?
>
> Curious why we need all mapsets search..
>
> Huidae
>
>
> On Sun, May 25, 2014 at 3:43 AM, Martin Landa <landa.martin at gmail.com>wrote:
>
>> Hi all,
>>
>> I would like to modify `g.mlist` to enable listing multiple types from
>> all mapsets in the given location. Now you can list multiple types
>> from search path, ie.
>>
>> $ g.mlist rast,vect -m
>> raster map(s) available in mapset <g6>:
>> x at g6
>> vector map(s) available in mapset <g6>:
>> b at g6
>> obce6 at g6
>> vector map(s) available in mapset <PERMANENT>:
>> kltm50 at PERMANENT
>> lesy at PERMANENT
>> merene_body at PERMANENT
>> obce at PERMANENT
>> obce_b at PERMANENT
>> orp at PERMANENT
>> zel_stan at PERMANENT
>> zelez at PERMANENT
>>
>> but it's hardly parsable
>>
>> $ g.mlist rast,vect -m --q
>> x at g6
>> b at g6
>> obce6 at g6
>> kltm50 at PERMANENT
>> lesy at PERMANENT
>> merene_body at PERMANENT
>> obce at PERMANENT
>> obce_b at PERMANENT
>> orp at PERMANENT
>> zel_stan at PERMANENT
>> zelez at PERMANENT
>>
>> so I was thinking to add a new flag which prints also element type
>>
>> rast x at g6
>> vect b at g6
>> vect obce6 at g6
>> vect kltm50 at PERMANENT
>> ...
>>
>> (do we really need a new flag for that? There is probably nobody who
>> is parsing multiple types from `g.mlist`. So probably element type
>> could be automatically printed when mutiple types and `--q` flag are
>> given (?) Maybe too tricky...
>>
>> The remaining question how to implement all mapsets search.
>>
>> mapset=.
>>
>> means search path
>>
>> 1) do we introduce special character for all mapsets ? (preferable I
>> would say)
>> 2) do we introduce new flag ?
>>
>> Thanks for your ideas in advance! Martin
>>
>> --
>> Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140525/274d9e14/attachment-0001.html>