On Wed, Nov 7, 2018 at 8:47 AM Bernardo Santos <
bernardo_brand...@yahoo.com.br> wrote:
>
> thanks for that, it'll be very useful. I think a similar approach can be
> used to build repositories for addons within GitHub, right?
>
Yes, when you involve Travis CI.
> Do you see clear advantages of
On Wed, 7 Nov 2018, Rich Shepard wrote:
Almost all issues are now resolved,
The issues with specifying database paths and needing a filled cat column
in the stations table have been resolved. v.db.connect shows a valid
connection to the database table:
v.db.connect map=stations -p
Vector
On Wed, 7 Nov 2018, Markus Metz wrote:
I am afraid that manually adding a cat column and populating it with
sequential numbers will not work: how do you assure that the cat numbers
and corresponding attribute values indeed correspond to the cat values of
the vector features? Chances are high
On Wed, Nov 7, 2018 at 8:40 PM Rich Shepard
wrote:
>
> On Wed, 7 Nov 2018, Moritz Lennert wrote:
>
> > I think you need to slow down a bit and try to review your basic
> > understanding of things (maybe [1] could do with a bit more substance).
>
> Moritz,
>
>I do need to step back a bit.
>
>
Thank you both,
I got confused between first and last row tiles and the middle ones.
The overlap is fine on first and last row tiles.
Regards
Sajid
On Wed, Nov 7, 2018 at 7:37 PM Markus Metz
wrote:
>
>
> On Wed, Nov 7, 2018 at 7:06 PM Veronica Andreo
> wrote:
> >
> > Hi Sajid,
> >
> > I
On Wed, 7 Nov 2018, Moritz Lennert wrote:
I think you need to slow down a bit and try to review your basic
understanding of things (maybe [1] could do with a bit more substance).
Moritz,
I do need to step back a bit.
You are trying to connect to a database that is called
Hi Rich,
On 7/11/18 19:55, Rich Shepard wrote:
Grass seems to recognize the postgres data base and that I'm logged
in to
it:
db.connect -p
driver: pg
database:
/home/rshepard/data/grassdata/willamette_basin/willamette-river-hg
db.login driver=pg database=willamette-river-hg --o
Grass seems to recognize the postgres data base and that I'm logged in to
it:
db.connect -p
driver: pg
database: /home/rshepard/data/grassdata/willamette_basin/willamette-river-hg
db.login driver=pg database=willamette-river-hg --o
WARNING: DB connection already exists and will be
On Wed, 7 Nov 2018, Markus Metz wrote:
for pg you don't specify a path/to/file as database, instead you use a
name: database=willamette-river-hg
Markus M,
Well, darn! I did not pick up on this difference when reading the manual
pages. It certainly makes a difference!
When I get the maps
On Wed, Nov 7, 2018 at 7:06 PM Veronica Andreo wrote:
>
> Hi Sajid,
>
> I have never used r.tile before, but checking the code [1], it multiplies
the overlap by 2, so there's why. Now guesstimating, if I set an overlap of
50, I would expect to have that overlap on both sides of the desired size
On Wed, 7 Nov 2018, Rich Shepard wrote:
Other maps still have their tables in the sqlite.db; e.g.,
1/FishD_AllSpecies_January2012|all_species|cat|$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db|sqlite
Perhaps this is the problem: some maps seem to have a source name as well
as a table
On Wed, Nov 7, 2018 at 7:06 PM Rich Shepard
wrote:
>
> On Wed, 7 Nov 2018, Markus Metz wrote:
>
> > for sqlite, the database must be a path to a sqlite database, in your
> > case, as you used yourself before:
> >
database="$HOME/data/grassdata/willamette_basin/mercury/sqlite/sqlite.db"
>
>
Hi Sajid,
I have never used r.tile before, but checking the code [1], it multiplies
the overlap by 2, so there's why. Now guesstimating, if I set an overlap of
50, I would expect to have that overlap on both sides of the desired size
of the tiles, so maybe that's why it is doubled ?
HTH,
Vero
On Wed, 7 Nov 2018, Markus Metz wrote:
for sqlite, the database must be a path to a sqlite database, in your
case, as you used yourself before:
database="$HOME/data/grassdata/willamette_basin/mercury/sqlite/sqlite.db"
Well, the situation here has become FUBAR and I need help fixing things.
Hello all,
If I use instruction inside my psmap file the command > ps.map
input=myfile.psmap output=myfile.ps does not work and the exit message is :
enter 'help' for help, 'end' when done, 'exit' to quit
But if I execute inside a shell loop, like > ls 01*.psmap |while read
fic;do ps.map
On Wed, 7 Nov 2018, Markus Metz wrote:
for sqlite, the database must be a path to a sqlite database, in your case,
as you used yourself before:
database="$HOME/data/grassdata/willamette_basin/mercury/sqlite/sqlite.db"
Markus M,
Thanks again for your advice here and using only db.connect -p
Gitlab supports private repositories. Useful for early development for some
people
Please excuse brevity. Sent from tiny pocket computer with non-haptic
feedback keyboard.
On Wed, Nov 7, 2018, 05:47 Bernardo Santos Hi Vaclav,
>
> thanks for that, it'll be very useful. I think a similar approach
On Wed, Nov 7, 2018 at 5:03 PM Markus Metz
wrote:
>
>
>
> On Wed, Nov 7, 2018 at 4:51 PM Rich Shepard
wrote:
> >
> > On Wed, 7 Nov 2018, Markus Metz wrote:
> >
> > > v.db.connect sets the table and database connection for a given,
existing
> > > vector. The default database connection can be
On Wed, Nov 7, 2018 at 4:51 PM Rich Shepard
wrote:
>
> On Wed, 7 Nov 2018, Markus Metz wrote:
>
> > v.db.connect sets the table and database connection for a given,
existing
> > vector. The default database connection can be overridden with the
driver=
> > and database= options
>
>I reset the
On Wed, 7 Nov 2018, Markus Metz wrote:
v.db.connect sets the table and database connection for a given, existing
vector. The default database connection can be overridden with the driver=
and database= options
I reset the attribute database to the sqlite default with 'db.connect
Gitlab supports private repositories. Useful for early development for some
people.
Please excuse brevity. Sent from tiny pocket computer with non-haptic
feedback keyboard.
On Wed, Nov 7, 2018, 05:47 Bernardo Santos Hi Vaclav,
>
> thanks for that, it'll be very useful. I think a similar
On Wed, 7 Nov 2018, Markus Metz wrote:
a short summary (others may have similar problems).
db.connect sets the default database connection for subsequently created
vector maps, already existing vector maps are not affected
v.db.connect sets the table and database connection for a given,
Hi all
The r.tile module don't have overwrite flag, so if we re run the module
with different parameters but with same output prefix name, then it will
rewrite output with out warning.
Is this intentional?
Another point is, if I use overlap option it adds double the overlap cells
to the output
On Wed, Nov 7, 2018 at 2:39 PM Rich Shepard
wrote:
>
> On Wed, 7 Nov 2018, Markus Metz wrote:
>
> > I suggested v.db.droptable, not db.droptable. db.* commands work on
> > databases whereas v.* commands work on vectors. Thus you need to use
> > v.db.connect, not db.connect, to connect a table to
Hi Vaclav,
thanks for that, it'll be very useful. I think a similar approach can be used
to build repositories for addons within GitHub, right?Do you see clear
advantages of using GitLab instead of GitHub for this purposes?
Best,Bernardo Niebuhr
Em segunda-feira, 5 de novembro de 2018
On Wed, 7 Nov 2018, Markus Metz wrote:
I suggested v.db.droptable, not db.droptable. db.* commands work on
databases whereas v.* commands work on vectors. Thus you need to use
v.db.connect, not db.connect, to connect a table to a vector, e.g.:
v.db.connect map=stations driver=pg
On Wed, Nov 7, 2018 at 11:18 AM Frank David wrote:
>
> Le 06/11/2018 à 21:36, Markus Metz a écrit :
>
>
>
> On Tue, Nov 6, 2018 at 4:03 PM Frank David wrote:
> >
> >
> > Le 05/11/2018 à 14:23, Frank David a écrit :
> > >
> > > Le 02/11/2018 à 22:27, Markus Metz a écrit :
> > >>
> > >>
> > >> On
27 matches
Mail list logo
