Thanks again - just spotted the Points2One plugin which will join points based on field - allowing me to create a line to use as a route.
> Spencer wrote: > > > Thanks all for your speedy weekend replies! The points to paths plugin is the > easy answer I'm looking for. It's pretty straight forward to convert a line > defined by two points to a series of points in GRASS, but converting them > back to a multinode line was the stumbling block. Drawing them manually > didn't appeal. > > Does the points to paths line appear in v1.7.4? I can't currently see it, > although Martin Dobias' sandbox is not loading this evening... > > Cheers, > M > > > Zirneklitis wrote: > > > > Another option: Spreadsheet + trigonometry + Add Delimited Text Layer > > plug-in (+ Points to Paths plug-in) > > > > K. > > > > Kris Nackaerts wrote: > > > .. > > > I would opt to use PostGIS as backend. .. > > > > > > If you like working with python, Shapely could be an option too, .. > > >.. > > >> > > >> From: [email protected] > > >> [mailto:[email protected]] On Behalf Of Michael > > >> Spencer > > >> .. > > >> I'm trying to create a .gpx route along a straight line, but with a > > >> node ~100m. i.e. I have a transect and wish to survey every 100m. How > > >> can I split straight polylines with a node every 100m, but keep the > > >> same line? > > >>.. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.osgeo.org/pipermail/qgis-user/attachments/20120311/da33e97b/attachment-0001.html > > ------------------------------ > > Message: 5 > Date: Sun, 11 Mar 2012 16:16:57 -0700 > From: john raskulinecz <[email protected]> > Subject: [Qgis-user] advice on the right hardware and o.s. to maximise > qgis potential > To: <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > > DEAR LIST, > WAS WONDERING IF ANYONE CAN GIVE ME SOME ADVICE AS TO WHAT WOULD BE THE BEST > HARD WARE AND OPERATING SYSTEM TO COMPILE SO AS TO MAXIMISE GQGIS'S POTENTIAL > AND UTILITIES. I AM ABOUT TO BUY A NEW DESK TOP SPECIFICALY TO RUN QGIS AND > ALL PLUGINS AND WILL BE BUILDING FROM SCRATCH. ANY IDEAS AS TO MAC VS. PC OR > INTEL VS. AMD OR HOW MUCH MEMORY, SPEED IS ENOUGH OR IS OVERKILL. I DON'T > WANT TO INCITE THE TRADITIONAL MAC -PC WAR BUT ANY HELP OR GUIDENCE EOULD BE > GREATLY APPRECIATED. > J.R. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.osgeo.org/pipermail/qgis-user/attachments/20120311/2468d475/attachment-0001.html > > ------------------------------ > > Message: 6 > Date: Sun, 11 Mar 2012 16:34:49 -0700 > From: Alex Mandel <[email protected]> > Subject: Re: [Qgis-user] advice on the right hardware and o.s. to > maximise qgis potential > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > On 03/11/2012 04:16 PM, john raskulinecz wrote: > > > > DEAR LIST, > > WAS WONDERING IF ANYONE CAN GIVE ME SOME ADVICE AS TO WHAT WOULD BE THE > > BEST HARD WARE AND OPERATING SYSTEM TO COMPILE SO AS TO MAXIMISE GQGIS'S > > POTENTIAL AND UTILITIES. I AM ABOUT TO BUY A NEW DESK TOP SPECIFICALY TO > > RUN QGIS AND ALL PLUGINS AND WILL BE BUILDING FROM SCRATCH. ANY IDEAS AS TO > > MAC VS. PC OR INTEL VS. AMD OR HOW MUCH MEMORY, SPEED IS ENOUGH OR IS > > OVERKILL. I DON'T WANT TO INCITE THE TRADITIONAL MAC -PC WAR BUT ANY HELP > > OR GUIDENCE EOULD BE GREATLY APPRECIATED. > > J.R. > > > > > > Those answers actually depend more on your budget than anything else. > > Best operating system - Linux, > because 64bit builds are packaged and compiling is easy (Mac compiling > is not so easy for add ons, and Windows compiling at this point in time > seems to require Visual Studio). Note even if you do buy Windows, make > sure you get 64 bit, you will need to compile QGIS yourself to get a 64 > bit version at this time. > A large number of QGIS developers/power users are on linux too. > > Your bottleneck is actually most likely going to be disk speed for > read/write. > > A minimum spec GIS workstation(Assuming we mean desktop not server or > laptop) for reasonable performance: > Intel i7 > 4 GB ram (min, 8-16 better) > an SSD for the OS (Intel's have the best reliability) > an SATA III, big drive for storage (WD, Seagate, Hitach or Samsung) > an PCI express graphics card of 256MB+ > > There's no way to know what would be overkill without knowing what kind > of datasets you'll be working on and how big they are. The bigger the > datasets the more RAM you'll want. > > Enjoy, > Alex > > > ------------------------------ > > Message: 7 > Date: Mon, 12 Mar 2012 02:36:46 +0200 > From: Zirneklitis <[email protected]> > Subject: [Qgis-user] Re: Qgis-user Digest, Vol 73, Issue 35 > Cc: QGIS Users <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > 'Points2One' is an alternative. > > K. > > Michael Spencer wrote: > > .. > > > Does the points to paths line appear in v1.7.4? I can't currently see > > it, although Martin Dobias' sandbox is not loading this evening... > >.. > > > ------------------------------ > > Message: 8 > Date: Sun, 11 Mar 2012 17:45:21 -0700 (PDT) > From: [email protected] > Subject: Re: [Qgis-user] advice on the right hardware and o.s. to > maximise qgis potential > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > One additional point, while I agree that Linux is the optimal operating > system, if you are not an existing Linux user, then you'll get lots of > conflicting advice as to which Linux distribution is best. So I'll start the > conflict :-) > > I use both OpenSuse & Ubuntu & would rank OpenSuse as slightly ahead at the > moment. Fedora is another viable alternative. All have extensive GIS software > repositories which make the installation & upgrading of QGIS and related > applications a pretty straightforward exercise. > > Many Linux purists prefer Debian, which is certainly robust & stable, but I > find more complex to administer than some more user friendly distros. > > I'd look around & see which of the above you have some local support for & > run with that, if you are new to Linux, having a colleague to help is more > useful than your choice of distribution. > > Otherwise Alex's reply pretty much covers it. > > Cheers, > > Brent Wood > > > > > --- On Mon, 3/12/12, Alex Mandel <[email protected]> wrote: > > From: Alex Mandel <[email protected]> > Subject: Re: [Qgis-user] advice on the right hardware and o.s. to maximise > qgis potential > To: [email protected] > Date: Monday, March 12, 2012, 12:34 PM > > On 03/11/2012 04:16 PM, john raskulinecz wrote: > > > > DEAR LIST, > > WAS WONDERING IF ANYONE CAN GIVE ME SOME ADVICE AS TO WHAT WOULD BE THE > > BEST HARD WARE AND OPERATING SYSTEM TO COMPILE SO AS TO MAXIMISE GQGIS'S > > POTENTIAL AND UTILITIES. I AM ABOUT TO BUY A NEW DESK TOP SPECIFICALY TO > > RUN QGIS AND ALL PLUGINS AND WILL BE BUILDING FROM SCRATCH. ANY IDEAS AS TO > > MAC VS. PC OR INTEL VS. AMD OR HOW MUCH MEMORY, SPEED IS ENOUGH OR IS > > OVERKILL. I DON'T WANT TO INCITE THE TRADITIONAL MAC -PC WAR BUT ANY HELP > > OR GUIDENCE EOULD BE GREATLY APPRECIATED. > > J.R. > > > > > > Those answers actually depend more on your budget than anything else. > > Best operating system - Linux, > because 64bit builds are packaged and compiling is easy (Mac compiling > is not so easy for add ons, and Windows compiling at this point in time > seems to require Visual Studio). Note even if you do buy Windows, make > sure you get 64 bit, you will need to compile QGIS yourself to get a 64 > bit version at this time. > A large number of QGIS developers/power users are on linux too. > > Your bottleneck is actually most likely going to be disk speed for > read/write. > > A minimum spec GIS workstation(Assuming we mean desktop not server or > laptop) for reasonable performance: > Intel i7 > 4 GB ram (min, 8-16 better) > an SSD for the OS (Intel's have the best reliability) > an SATA III, big drive for storage (WD, Seagate, Hitach or Samsung) > an PCI express graphics card of 256MB+ > > There's no way to know what would be overkill without knowing what kind > of datasets you'll be working on and how big they are. The bigger the > datasets the more RAM you'll want. > > Enjoy, > Alex > _______________________________________________ > Qgis-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-user > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.osgeo.org/pipermail/qgis-user/attachments/20120311/cc7d7767/attachment.html > > ------------------------------ > > _______________________________________________ > Qgis-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-user > > > End of Qgis-user Digest, Vol 73, Issue 36 > *****************************************
_______________________________________________ Qgis-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-user
