#244: v.in.asci has no progress bar in any GUI (same as v.proj)
----------------------+-----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Vector | Version: svn-develbranch6
Keywords: | Platform: All
Cpu: All |
----------------------+-----------------------------------------------------
v.in.asci has no progress bar in any GUI (same as v.proj)
#244: v.in.ascii has no progress bar in any GUI (same as v.proj)
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Vector | Version: svn-develbranch6
Resolution: | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Changes (by glynn):
* summary: v.in.asci has no progress bar in any GUI (same as v.proj) =>
v.in.ascii has no progress bar in any GUI (same
as v.proj)
#244: v.in.ascii has no progress bar in any GUI (same as v.proj)
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Vector | Version: svn-develbranch6
Resolution: | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Comment (by hamish):
input can be piped from stdin, which is open-ended. So a progress bar
isn't appropriate. r.in.xyz does some checks to see what kind of input is
involved before checking filesize and rewinding, then using G_clicker()
instead of G_percent(), but really for v.in.ascii IMO I don't think it's
worth the trouble.
#244: v.in.ascii has no progress bar in any GUI (same as v.proj)
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Vector | Version: svn-develbranch6
Resolution: | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Comment (by martinl):
Replying to [comment:2 hamish]:
> input can be piped from stdin, which is open-ended. So a progress bar
isn't appropriate. r.in.xyz does some checks to see what kind of input is
involved before checking filesize and rewinding, then using G_clicker()
instead of G_percent(), but really for v.in.ascii IMO I don't think it's
worth the trouble.
It's seems to me that at least in points mode progress message info can be
printed. The file is scanned before the points are imported, see r32398
(not backported to devbr6).
#244: v.in.ascii has no progress bar in any GUI (same as v.proj)
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Vector | Version: svn-develbranch6
Resolution: | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Comment (by hamish):
Replying to [comment:3 martinl]:
> It's seems to me that at least in points mode progress message info can
be printed.
> The file is scanned before the points are imported, see r32398 (not
backported to
> devbr6).
i.e. in the first step of v.in.ascii the points are scanned for column
type and sanitized then saved into a temporary file. then in a second step
the temporary file is imported. G_percent() can work on the second stage
as the number of points is known (r32398).
so shall we close this wish as "already done by martin"?
as it's not a bugfix I don't think backporting to 6.3/4 is appropriate.