Details Ticket 1434


Comment | Reply | Take | Resolve


Serial Number 1434
Subject the *.in.* man pages don't mention the file extensions they deal with
Area wish
Queue grass
Requestors jidanni@dman.ddts.net
Owner none
Status open
Last User Contact Tue Jul 4 14:40:22 2006 (2 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Tue Jul 4 14:40:22 2006 (2 yr ago)
Created Wed Nov 20 09:41:27 2002 (6 yr ago)

Transaction History Ticket 1434


Wed, Nov 20 2002 09:41:27    Request created by jidanni@dman.ddts.net  
Return-Path <jidanni@dman.ddts.net>
Delivered-To grass-bugs@lists.intevation.de
To grass-bugs@intevation.de
Subject the *.in.* man pages don't mention the file extensions they deal with
From Dan Jacobson <jidanni@dman.ddts.net>
User-Agent Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Date 20 Nov 2002 11:27:29 +0800
Message-ID <87k7j8apjy.fsf@jidanni.org>
Lines 47
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
X-Spam-Status No, hits=-1.6 required=5.0 tests=DATE_IN_PAST_03_06,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01, USER_AGENT version=2.41
X-Spam-Level
The various *.in.* man pages should mention what file extensions they
deal with.

For instance
$ man v.in.arc
does not mention up front that it deals with file.ABC or file.EFG

It says 
The v.in.arc program will convert
       vector  data  in  ARC/INFO's  "Generate" format to GRASS's
       vector file format, and bring it into the  user's  current
       GRASS  mapset.

Hmm, those files maybe are called file.GEN or file.ARC: who knows. The
man page assumes one knows.

$ man v.in.shape|grep -i shp
is another example showing that the author doesn't think it is
necessary to mention the extensions of files the command deals with,
as the user certainly has years of GIS background.

Oh, the shp file apparently has more to do with r.in.shape ... ok,
wish the v.in.shape man page would mention that.

Mainly all *.in.shape man pages should mention all the things you
might want to do with all the different file extensions one might
encounter.

BTW on the man page it says
  NOTE
       r.in.shape   creates   ASCII   file  first  and  then  run
       r.in.poly.

you better say "runs" or else we think we should run it ourselves. 

By the way, the s.in.shape man page says
       Grass files created have the name extracted from the base
       name of the shapefile.

i.e. s.in.shape doesn't accept a out= parameter, whereas r.in.shape
and v.in.shape wont work without one!

also error messages arent informative:
$ s.in.shape /var/tmp/ec5212NW/EC5212NW    
ERROR: Unable to process shapefile - Aborting.
-- 
http://jidanni.org/ Taiwan(04)25854780


Fri, Nov 29 2002 09:41:39    Mail sent by mneteler  
Please update the pages for us and send them to us.
Using open source software always invites the user to
participate :-)

Markus
Wed, Dec 4 2002 10:20:49    Area changed to wish by mneteler  
Tue, Jul 4 2006 14:40:22    Mail sent by guest  
hi,

this report can be probably closed since import
business is done by v.in.ogr which accepts
various file extensions depending on the format.

Markus
Comment | Reply | Take | Resolve

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request