#3486: v.in.ogr: default format in online manual
-------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.1
Component: Docs | Version: unspecified
Keywords: v.out.ogr | CPU: Unspecified
Platform: Unspecified |
-------------------------+-------------------------
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?
#3486: v.in.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.1
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mmetz):
Replying to [ticket:3486 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.
#3486: v.in.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.1
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by neteler):
Replying to [comment:1 mmetz]:
> Replying to [ticket:3486 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:
#3486: v.in.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.1
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by martinl):
Replying to [comment:1 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.
#3486: v.in.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.1
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mmetz):
Replying to [comment:3 martinl]:
> Replying to [comment:1 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.
#3486: v.in.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.1
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mlennert):
Replying to [comment:2 neteler]:
> Replying to [comment:1 mmetz]:
> > Replying to [ticket:3486 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...
#3486: v.in.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.1
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by neteler):
Replying to [comment:5 mlennert]:
> Replying to [comment:2 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.
#3486: v.in.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.2
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by neteler):
Replying to [comment:6 neteler]:
> Replying to [comment:5 mlennert]:
> > Replying to [comment:2 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.
#3486: v.in.ogr/v.out.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.2
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by neteler):
Replying to [comment:8 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:
#3486: v.in.ogr/v.out.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.5
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by sylvain):
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).
#3486: v.in.ogr/v.out.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.5
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by martinl):
Replying to [comment:14 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).
#3486: v.in.ogr/v.out.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.5
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mmetz):
Replying to [comment:14 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)
#3486: v.in.ogr/v.out.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.5
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by 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)
#3486: v.in.ogr/v.out.ogr: default format in online manual
--------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: new
Priority: normal | Milestone: 7.4.5
Component: Docs | Version: unspecified
Resolution: | Keywords: v.out.ogr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mmetz):
Replying to [comment:19 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.
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.