v.in.ogr/v.out.ogr: default format in online manual

[martinl]

Hi,

the online manual for G74:v.out.ogr still shows 'Esri Shapefile' as default format. Default format should be GPKG source:grass/branches/releasebranch_7_4/vector/v.out.ogr/list.c#L99​.

Any chance to update GDAL to version 2 on build server?

[mmetz]

Replying to martinl:

Hi,

the online manual for G74:v.out.ogr still shows 'Esri Shapefile' as default format. Default format should be GPKG source:grass/branches/releasebranch_7_4/vector/v.out.ogr/list.c#L99​.

Any chance to update GDAL to version 2 on build server?

Earlier versions of GDAL also support GPKG. Is it possible that the build server has a minimal GDAL installation built without SQLite3? The GeoPackage driver needs SQLite3.

[neteler]

Replying to mmetz:

Replying to martinl:

...

Any chance to update GDAL to version 2 on build server?

Earlier versions of GDAL also support GPKG. Is it possible that the build server has a minimal GDAL installation built without SQLite3? The GeoPackage driver needs SQLite3.

Yes, the grass.osgeo.org server is meanwhile a bit antique:

neteler@osgeo6:~$ cat /etc/issue
Debian GNU/Linux 8 \n \l

neteler@osgeo6:~$ gdal-config --version
1.10.1

neteler@osgeo6:~$ which gdal-config
/usr/bin/gdal-config

Anyone with more Debian experience than me: is there a better GDAL binary package we could install? Or do I/MartinL have to compile GDAL from scratch?

[martinl]

Replying to mmetz:

Earlier versions of GDAL also support GPKG. Is it possible that the build server has a minimal GDAL installation built without SQLite3? The GeoPackage driver needs SQLite3.

There is SQLite support included

martinl@osgeo6:~$ ogrinfo --formats | grep GPKG
martinl@osgeo6:~$ ogrinfo --formats | grep SQLite
  -> "SQLite" (read/write)

It seems to me that GPKG driver has been introduced in GDAL 1.11. Probably we should fix G74:v.out.ogr to reflect also this version.

[mmetz]

Replying to martinl:

Replying to mmetz:

Earlier versions of GDAL also support GPKG. Is it possible that the build server has a minimal GDAL installation built without SQLite3? The GeoPackage driver needs SQLite3.

There is SQLite support included

martinl@osgeo6:~$ ogrinfo --formats | grep GPKG
martinl@osgeo6:~$ ogrinfo --formats | grep SQLite
  -> "SQLite" (read/write)

It seems to me that GPKG driver has been introduced in GDAL 1.11. Probably we should fix G74:v.out.ogr to reflect also this version.

The GPKG driver is only the default if it is available, therefore the manual on the build server is correct.

[mlennert]

Replying to neteler:

Replying to mmetz:

Replying to martinl:

...

Any chance to update GDAL to version 2 on build server?

Earlier versions of GDAL also support GPKG. Is it possible that the build server has a minimal GDAL installation built without SQLite3? The GeoPackage driver needs SQLite3.

Yes, the grass.osgeo.org server is meanwhile a bit antique:

neteler@osgeo6:~$ cat /etc/issue
Debian GNU/Linux 8 \n \l

neteler@osgeo6:~$ gdal-config --version
1.10.1

neteler@osgeo6:~$ which gdal-config
/usr/bin/gdal-config

Anyone with more Debian experience than me: is there a better GDAL binary package we could install? Or do I/MartinL have to compile GDAL from scratch?

There are no gdal packages in jessie-backports, so I'm afraid that compilation is necessary.

Jessie is old-stable. The current Debian stable release (stretch) has gdal 2.12.

Following stable releases would probably be enough to have relatively up to date packages...

[neteler]

Replying to mlennert:

Replying to neteler: There are no gdal packages in jessie-backports, so I'm afraid that compilation is necessary.

Jessie is old-stable. The current Debian stable release (stretch) has gdal 2.12.

Inded, having an updated server would solve several issues.

Following stable releases would probably be enough to have relatively up to date packages...

Fully agreed. However, the osgeo6 machine hosts git, grass, ossim, svn, and trac.

Hence an update is complex and needs to be done by OSGeo-SAC.

[neteler]

Replying to neteler:

Replying to mlennert:

Replying to neteler: There are no gdal packages in jessie-backports, so I'm afraid that compilation is necessary.

Jessie is old-stable. The current Debian stable release (stretch) has gdal 2.12.

Inded, having an updated server would solve several issues.

Following stable releases would probably be enough to have relatively up to date packages...

Fully agreed. However, the osgeo6 machine hosts git, grass, ossim, svn, and trac.

Hence an update is complex and needs to be done by OSGeo-SAC.

Well, we could compile GRASS GIS within a docker container on osgeo6. As soon as I find the time I'll look into this.

[neteler]

Replying to neteler:

Well, we could compile GRASS GIS within a docker container on osgeo6. As soon as I find the time I'll look into this.

First attempt, compilation within docker manually triggered:

https://grass.osgeo.org/grass76/manuals/v.out.ogr.html

[neteler]

Ticket retargeted after milestone closed

[martinl]

Bump milestone to 7.4.4

[neteler]

Ticket retargeted after milestone closed

[Sylvain POULAIN]

Hi, I was happy to see support for geopackage under grass but when I would like to use it, it's only available for v.out.ogr ! Is there plan to add support for v.in.ogr and r.out.gdal (geopackage support rasters).

Sincerely,

Sylvain

[martinl]

Replying to Sylvain POULAIN:

I was happy to see support for geopackage under grass but when I would like to use it, it's only available for v.out.ogr ! Is there plan to add support for v.in.ogr and r.out.gdal (geopackage support rasters).

please create a new issue.

[martinl]

Is there a plan to use Docker on osgeo build server to solve this issue?

[Neteler]

Replying to martinl:

Is there a plan to use Docker on osgeo build server to solve this issue?

Yes, it is all prepared. Just need to find some time to activate it - no need for a new ticket.

[mmetz]

Replying to Sylvain POULAIN:

Hi, I was happy to see support for geopackage under grass but when I would like to use it, it's only available for v.out.ogr ! Is there plan to add support for v.in.ogr

v.in.ogr can already read GPKG (automatically recognized by OGR)

and r.out.gdal (geopackage support rasters).

r.out.gdal already supports GPKG: r.out.gdal format=GPKG

What exactly is the problem?

[Sylvain POULAIN]

Problem is about wxgui sorry for this misunderstanding ! With v.in.ogr, GPKG is not present in file listing but is present in directory (I didn't notice that until today). Even with that, you could not select gpkg from file with the GUI ("v.in.ogr -f | grep GPKG" is ok !) With r.out.gdal, it's not present in the list but could be changed manually. ("r.out.gdal -l | grep GPKG" is ok !

But Idea is : some promotes gpkg but it's not in the totally support in Grass Gui (r.in.gdal is ok)

[mmetz]

Replying to Sylvain POULAIN:

Problem is about wxgui sorry for this misunderstanding ! With v.in.ogr, GPKG is not present in file listing but is present in directory (I didn't notice that until today). Even with that, you could not select gpkg from file with the GUI ("v.in.ogr -f | grep GPKG" is ok !) With r.out.gdal, it's not present in the list but could be changed manually. ("r.out.gdal -l | grep GPKG" is ok !

But Idea is : some promotes gpkg but it's not totally support in Grass Gui (r.in.gdal is ok)

I see. Changed in trunk r74122, the GUI knows now about GeoPackages.

[martinl]

Probably solvable with new LXD container?

[neteler]

Yes, grass lxd container based on Debian9 solved it:

​https://lists.osgeo.org/pipermail/grass-dev/2019-April/091965.html

neteler@grass:~/www/grass77/manuals$ ogrinfo --formats | grep GPKG
  GPKG -raster,vector- (rw+vs): GeoPackage

I have a compile environment ready on the new grasslxd server, we may now decide if to copy the manual pages over to grass.osgeo.org or migrate the CMS to new grasslxd server and switch the IP.

[Sylvain POULAIN]

Replying to mmetz:

Replying to Sylvain POULAIN:

Problem is about wxgui sorry for this misunderstanding ! With v.in.ogr, GPKG is not present in file listing but is present in directory (I didn't notice that until today). Even with that, you could not select gpkg from file with the GUI ("v.in.ogr -f | grep GPKG" is ok !) With r.out.gdal, it's not present in the list but could be changed manually. ("r.out.gdal -l | grep GPKG" is ok !

But Idea is : some promotes gpkg but it's not totally support in Grass Gui (r.in.gdal is ok)

I see. Changed in trunk r74122, the GUI knows now about GeoPackages.

Sorry for the late answer, Yes it works now since 7.6.2 Many thanks !

[neteler]

Replying to neteler:

Yes, grass lxd container based on Debian9 solved it:

​https://lists.osgeo.org/pipermail/grass-dev/2019-April/091965.html

neteler@grass:~/www/grass77/manuals$ ogrinfo --formats | grep GPKG
  GPKG -raster,vector- (rw+vs): GeoPackage

I have a compile environment ready on the new grasslxd server, we may now decide if to copy the manual pages over to grass.osgeo.org or migrate the CMS to new grasslxd server and switch the IP.

I have spent some hours today and implemented some new cronjobs for G78 and G79 on the new (upcoming) GRASS server which is based on a more recent Debian.

Since today:

• G74 + G76 are built on grass.osgeo.org (ancient Debian with Python 2)
• G78 + G79 are built on grass.lxd (recent Debian with Python 3)
• the G78 + G79 source code, Linxu snapshop binaries, programming7 and manual pages are copied over to grass.osgeo.org.

Hope the cronjobs run properly. Please let me know if anything is missing.

TODO (note to self): implement removal of old snapshots from grass.osgeo.org.