[GRASS5] Re: [GRASSLIST:2717] How to get topology of area edges

[Glynn Clements]

Radim Blazek wrote:

> > > > > as long as the file format (and vectors in general) is changing
> > > > > for 5.7, is it too confusing to switch to x,y? maybe with an added
> > > > > header line"FORMAT: X,Y" or something? Now would be the time if we
> > > > > are ever going to fix that...
> > > >
> > > > "FORMAT: X,Y" is good idea, but still could make much confusion,
> > > > there are many scripts working with ascii format.
> > >
> > > I agree about the creating confusion. BUT the existing way creates
> > > confusion too. Question is, which way causes LESS confusion and is
> > > easier to work on in the future?
> > >
> > > Will those 5.0 scripts not break & need updating to work with the new
> > > 5.7 ascii format anyway?
> > >
> > > > Maybe another directory?
> > >
> > > Moving things into the vector/ directory just cleaned things up, do we
> > > really want to go back and add more clutter?
> > 
> > [replying to myself..]
> >
> > ... maybe make an "ascii" file in the new vector/$MAPNAME/ directory for
> > the changed format. Putting new 5.7 data in dig_ascii/ seems wrong.
> > That should be reserved for old GRASS 5.0 files.. Otherwise we never get
> > away from the dig_* directory clutter even when 5.0 is history.
> 
> I don't like vector/$MAPNAME/ascii, vector/$MAPNAME/ should be used only for
> binary format, I think. You are right that old scripts cannot read new 
> format anyway. What about vector_ascii/?
> 
> v.out.ascii has already -o flag, the same could have v.in.ascii.

v.{in,out}.ascii should behave like other in/out programs, and treat
the in/out (respectively) parameter as a filename, not a map name. 
Simple names should be relative to the current directory.

No dig_ascii/vector_ascii directory, no $MAPNAME/ascii file. IOW, just
like v.{in,out}.<everything else>.

-- 
Glynn Clements <glynn.clements at virgin.net>