Hi all,
Am I correct in understanding that v.in.mif is currently broken ?
If yes, what are the alternatives ?
Moritz
Moritz,
The current code is not usable at all. It is disabled from the default
build so will not appear in binary releases. A module based on existing
modules like v.in.shape is in development, but key parts still have to
be coded, tested etc, so it is not ready for the stable release, which
is now effectively frozen.
v.in.shape is now hopefully fully functional and stable, so one way is
to use third party utilities like Mitab and OGR to convert various other
kinds to shapefiles, and import that way.
David
Moritz Lennert wrote:
> Hi all,
>
> Am I correct in understanding that v.in.mif is currently broken ?
> If yes, what are the alternatives ?
>
> Moritz
> _______________________________________________
> grass5 mailing list
> grass5@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5
>
Just for info: it's still enabled in the (current for the next few days 
pre4 releasei, at least when built from source.
Moritz
On Thu, Jun 20, 2002 at 09:47:24PM +0100, David D Gray wrote:
Moritz,
The current code is not usable at all. It is disabled from the default
build so will not appear in binary releases. A module based on existing
modules like v.in.shape is in development, but key parts still have to
be coded, tested etc, so it is not ready for the stable release, which
is now effectively frozen.v.in.shape is now hopefully fully functional and stable, so one way is
to use third party utilities like Mitab and OGR to convert various other
kinds to shapefiles, and import that way.David
Moritz Lennert wrote:
> Hi all,
>
> Am I correct in understanding that v.in.mif is currently broken ?
> If yes, what are the alternatives ?
>
> Moritz
> _______________________________________________
> grass5 mailing list
> grass5@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5
>
I commented out the corresponding line for v.in.mif in lists/GRASS
because of the information below.
On Fri, Jun 21, 2002 at 01:30:47AM +0200, Moritz Lennert wrote:
Just for info: it's still enabled in the
(current for the next few days
at least when built from source.
On Thu, Jun 20, 2002 at 09:47:24PM +0100, David D Gray wrote:
> The current code is not usable at all. It is disabled from the default
> build so will not appear in binary releases. A module based on existing
> modules like v.in.shape is in development, but key parts still have to
> be coded, tested etc, so it is not ready for the stable release, which
> is now effectively frozen.
> > Am I correct in understanding that v.in.mif is currently broken ?
> > If yes, what are the alternatives ?