[GRASS-user] Re: grass-user Digest, Vol 33, Issue 39
Richard Chirgwin
rchirgwin at ozemail.com.au
Mon Jan 19 23:10:49 EST 2009
>
> ------------------------------ Message: 5 Date: Mon, 19 Jan 2009
> 12:00:08 +0100 From: Moritz Lennert <mlennert at club.worldonline.be>
> Subject: Re: [GRASS-user] generating lines from points To: Martin
> Landa <landa.martin at gmail.com> Cc: GRASS users list
> <grass-user at lists.osgeo.org> Message-ID:
> <49745D38.9030904 at club.worldonline.be> Content-Type: text/plain;
> charset=ISO-8859-1; format=flowed On 18/01/09 18:08, Martin Landa wrote:
>> > Hi,
>> >
>> > 2009/1/18 Martin Landa <landa.martin at gmail.com>:
>> >
>> > [...]
>> >
>>
>>> >> The more lines you need to generate the longer list of categories will
>>> >> be, not possible to give the list as the parameter. Then v.edit could
>>> >> read categories from stdin, simillary to v.net.path. Hm, what about
>>> >> v.net? New tool to generate network from points?
>>> >>
>>> >> v.net input=points output=net operation=lines line_file=- << EOF
>>> >> 1 1 2
>>> >> 2 2 3
>>> >> EOF
>>> >>
>>> >> creates edges between points 1-2 and 2-3 with category 1 and 2?
>>>
>> >
>> > better
>> >
>> > v.net points=points output=net operation=net file=- << EOF
>> > 1 1 2
>> > 2 2 3
>> > EOF
>> >
>> > What do you think about that?
>>
>
> I think that a GRASS module for connecting lines between chosen points
> is a definite yes (think of point coordinates of airports with
> information about flight connections between airports). Up to now I've
> been doing it with a simple script + v.in.ascii.
>
I think a module would be wonderful, since I've struggled with this task
a few times. Would it be rude to ask about your script, Moritz?
Richard
> Not sure v.net is the most logical place to have this. Maybe a
> stand-alone module v.points2lines ?
>
> Moritz
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 19 Jan 2009 12:04:26 +0100
> From: Moritz Lennert <mlennert at club.worldonline.be>
> Subject: Re: [GRASS-user] Original location: Hot to create from the
> command line ?
> To: peter.loewe at gmx.de
> Cc: grass-user at lists.osgeo.org
> Message-ID: <49745E3A.1000904 at club.worldonline.be>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 19/01/09 10:47, peter.loewe at gmx.de wrote:
>
>> > Hi,
>> >
>> > is there an (easy) recipe to create a completely new location from
>> > scratch without using a GUI ?
>> >
>> > To be precise: If GRASS is started for the first time in "-text" mode
>> > (=no GUI) ** without having a sample location like Spearfish or North
>> > Carolina around**, how can location parameters (projection, extent,
>> > EPSG...) be handed over to set up a very first location ?
>>
>
> Just type in the name of the location you want to create and GRASS will
> prompt you for the parameters.
>
> Moritz
>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 19 Jan 2009 12:06:56 +0100
> From: "Peter L?we" <peter.loewe at gmx.de>
> Subject: Re: [GRASS-user] Original location: Hot to create from the
> command line ?
> To: Moritz Lennert <mlennert at club.worldonline.be>
> Cc: grass-user at lists.osgeo.org
> Message-ID: <20090119110656.4810 at gmx.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>
>>> > > is there an (easy) recipe to create a completely new location from
>>> > > scratch without using a GUI ?
>>> > >
>>> > > To be precise: If GRASS is started for the first time in "-text" mode
>>> > > (=no GUI) ** without having a sample location like Spearfish or North
>>> > > Carolina around**, how can location parameters (projection, extent,
>>> > > EPSG...) be handed over to set up a very first location ?
>>>
>> >
>> > Just type in the name of the location you want to create and GRASS will
>> > prompt you for the parameters.
>> >
>> > Moritz
>>
>
> That's true. But is there also a way to provide the parameters _without_ interaction with the user (-> GRASS scripting & automation) ?
>
> Peter
> -- Dr. Peter Lo"we <peter.loewe at gmx.de> Sensationsangebot verla"ngert:
> GMX FreeDSL - Telefonanschluss + DSL fu"r nur 16,37 Euro/mtl.!*
> http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a
> ------------------------------ Message: 8 Date: Mon, 19 Jan 2009
> 12:23:37 +0100 From: Nikos Alexandris
> <nikos.alexandris at felis.uni-freiburg.de> Subject: Re: [GRASS-user]
> v.digit under wxGUI To: Vincent Bain <bain at toraval.fr> Cc: GRASS user
> list <grass-user at lists.osgeo.org> Message-ID:
> <1232364217.6974.0.camel at vertical> Content-Type: text/plain On Sun,
> 2009-01-18 at 19:30 +0100, Vincent Bain wrote:
>> > OK,
>> >
>> > so in order to fully enjoy the wxpython GUI on an 64 bit architecture
>> > (especially the wxdigit module) one should first read carefully the
>> > README file located in the your_grass_source_location/gui/wxpython
>> > directory.
>> >
>> > The section named "7 - VECTOR DIGITIZER" tells you to create a symbolic
>> > link to a wx library :
>> >
>> > sudo ln -s `locate _gdi_.so` /usr/local/lib/libgdi.so
>> >
>> > The command locate _gdi_.so may points towards the 32 bit library and
>> > ignore (?) the 64 bit libs path (/usr/lib64/...), so it fails. In my
>> > configuration I had to type :
>> >
>> > sudo ln -s /usr/lib64/python2.5/site-packages\
>> > /wx-2.8-gtk2-unicode/wx/_gdi_.so /usr/local/lib/libgdi.so
>> >
>> > And it worked !
>>
>
> Geat! Thanks ;-)
>
>
>
> ------------------------------
>
> Message: 9
> Date: Mon, 19 Jan 2009 11:36:07 +0000
> From: Glynn Clements <glynn at gclements.plus.com>
> Subject: Re: [GRASS-user] Original location: How to create from the
> command line ?
> To: grass-user at lists.osgeo.org
> Message-ID: <18804.26023.425982.30077 at cerise.gclements.plus.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> peter.loewe at gmx.de wrote:
>
>
>> > is there an (easy) recipe to create a completely new location from
>> > scratch without using a GUI ?
>> >
>> > To be precise:
>> > If GRASS is started for the first time in "-text" mode (=no GUI) **
>> > without having a sample location like Spearfish or North Carolina
>> > around**, how can location parameters (projection, extent, EPSG...)
>> > be handed over to set up a very first location ?
>>
>
> You can create a new location via the curses dialog, and specify
> projection information interactively, but you can't use an EPSG code
> here.
>
> However, you can just provide bogus projection information at that
> point, then correct it with "g.proj -c ..." once the startup is
> complete.
>
> -- Glynn Clements <glynn at gclements.plus.com>
> ------------------------------ Message: 10 Date: Mon, 19 Jan 2009
> 12:40:06 +0100 From: Nikos Alexandris
> <nikos.alexandris at felis.uni-freiburg.de> Subject: Re: [GRASS-user]
> Landsat classification with CORINE CLC color codes? To: Markus Neteler
> <neteler at osgeo.org> Cc: GRASS user list <grass-user at lists.osgeo.org>,
> dimos_anastasiou at yahoo.com Message-ID:
> <1232365206.6974.28.camel at vertical> Content-Type: text/plain On Mon,
> 2009-01-19 at 08:25 +0100, Markus Neteler wrote:
>> > On Mon, Jan 19, 2009 at 7:42 AM, Dimos <dimos_anastasiou at yahoo.com> wrote:
>>
>>> > > Hello,
>>> > >
>>> > > My apologies if this question is already covered in this list...
>>> > >
>>> > > 44 CORINE CLC RGB color codes are mentioned for each of the 44 land use
>>> > > classes at:
>>> > > http://dataservice.eea.europa.eu/download.asp?id=14234&filetype=.csv
>>> > >
>>> > > Can we classify a Landsat RGB image based on these rgb color codes in
>>> > > GRASS GIS and how?
>>>
>> >
>> > In my opinion it doesn't make much sense to use the RGB colors here
>> > since they are arbitrary (well, ok, ideally "close" to natural colors).
>> >
>> > What you can do:
>> > - download the related CORINE shape file(s)
>> > - extract training areas
>> > - run i.gensigset to generate statistics
>> > - run i.smap to do the classification
>> > - validate
>> >
>> > Markus
>>
>
> Hi! Markus suggestion is one solution.
>
> I just want to add that, if you take samples (=areas) from CORINE (as
> they are), they can be a bit rough to classify a, let's say, 15m
> pixel-resolution Landsat satellite image. In my humble opinion, there is
> no way in this case to completely avoid some manual digitisation of
> training samples, or edit the samples you will extract from CORINE.
>
> Well, it depends also on what (e.g. which land cover classes) you want
> to extract from Landsat.
>
> There is, on the web, a nice step-by-step which uses COREIN + i.smap on
> Landsat [1].
>
> Dimo, if you could be a bit more precise... ?
> Kind regards, Nikos
>
> [1] http://www.custom-scenery.org/Building-Scener.331.0.html
>
>
>
> ------------------------------
>
> Message: 11
> Date: Mon, 19 Jan 2009 14:02:04 +0200
> From: Dimos <dimos_anastasiou at yahoo.com>
> Subject: Re: [GRASS-user] Landsat classification with CORINE CLC color
> codes?
> To: Nikos Alexandris <nikos.alexandris at felis.uni-freiburg.de>
> Cc: GRASS user list <grass-user at lists.osgeo.org>
> Message-ID: <1232366524.2844.19.camel at uno>
> Content-Type: text/plain
>
> Thanks for the great input!
>
> I just want to create a high resolution land use map, based on an
> already existing classification such as CORINE using Landsat data: I
> will follow your instructions as below.
>
> Regards, Dimos
>
>
>
> On Mon, 2009-01-19 at 12:40 +0100, Nikos Alexandris wrote:
>
>> > On Mon, 2009-01-19 at 08:25 +0100, Markus Neteler wrote:
>>
>>> > > On Mon, Jan 19, 2009 at 7:42 AM, Dimos <dimos_anastasiou at yahoo.com> wrote:
>>>
>>>> > > > Hello,
>>>> > > >
>>>> > > > My apologies if this question is already covered in this list...
>>>> > > >
>>>> > > > 44 CORINE CLC RGB color codes are mentioned for each of the 44 land use
>>>> > > > classes at:
>>>> > > > http://dataservice.eea.europa.eu/download.asp?id=14234&filetype=.csv
>>>> > > >
>>>> > > > Can we classify a Landsat RGB image based on these rgb color codes in
>>>> > > > GRASS GIS and how?
>>>>
>>> > >
>>> > > In my opinion it doesn't make much sense to use the RGB colors here
>>> > > since they are arbitrary (well, ok, ideally "close" to natural colors).
>>> > >
>>> > > What you can do:
>>> > > - download the related CORINE shape file(s)
>>> > > - extract training areas
>>> > > - run i.gensigset to generate statistics
>>> > > - run i.smap to do the classification
>>> > > - validate
>>> > >
>>> > > Markus
>>>
>> >
>> > Hi! Markus suggestion is one solution.
>> >
>> > I just want to add that, if you take samples (=areas) from CORINE (as
>> > they are), they can be a bit rough to classify a, let's say, 15m
>> > pixel-resolution Landsat satellite image. In my humble opinion, there is
>> > no way in this case to completely avoid some manual digitisation of
>> > training samples, or edit the samples you will extract from CORINE.
>> >
>> > Well, it depends also on what (e.g. which land cover classes) you want
>> > to extract from Landsat.
>> >
>> > There is, on the web, a nice step-by-step which uses COREIN + i.smap on
>> > Landsat [1].
>> >
>> > Dimo, if you could be a bit more precise... ?
>> > Kind regards, Nikos
>> >
>> > [1] http://www.custom-scenery.org/Building-Scener.331.0.html
>> >
>>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
>
> End of grass-user Digest, Vol 33, Issue 39
> ******************************************
>
>
More information about the grass-user
mailing list