Opened 22 years ago
Closed 5 years ago
#159 closed enhancement (wontfix)
WISH: ASCII read support enabling for ogr/avc driver
Reported by: | Markus Neteler | Owned by: | warmerdam |
---|---|---|---|
Priority: | low | Milestone: | closed_because_of_github_migration |
Component: | default | Version: | unspecified |
Severity: | minor | Keywords: | AVC E00 Shapefile |
Cc: | Mateusz Łoskot |
Description (last modified by )
Frank,
might be there a chance to enable ASCII reading for E00 files?
I have looked at
ogr/ogrsf_frmts/avcavc_e00read.c
which reads binary coverages. Since it internally converts to an ASCII coverage and then parses it, it would be great to have that directly enabled.
Eg.
* Purpose: Functions to open a binary coverage and read it as if it * was an ASCII E00 file. This file is the main entry point * for the library. [...] * AVCE00ReadRewind() * * Rewinds the AVCE00ReadPtr just like the stdio rewind() * function would do if you were reading an ASCII E00 file.
etc.
Then we could convert SHAPE files to binary E00 coverages etc.
Sorry for this time consuming idea,
Markus
Change History (16)
comment:3 by , 18 years ago
Frank, apparently this was recently implemented? Cool! A quick test was successful (with uncompressed E00). Best regards Markus
comment:4 by , 18 years ago
Markus, It has been incorporated in CVS but there appear to be outstanding issues with the the polygon (PAL) geometry reading.
comment:5 by , 18 years ago
Frank, another issue are splitted E00 files: namsoil.e00 namsoil.e01 namsoil.e02 namsoil.e03 namsoil.e04 namsoil.e05 namsoil.e06 namsoil.e07 It only reads the first file. However, cat namsoil.e0? > namsoil_all.e00 is accepted with ogr2ogr. I think that the original avcimport checked the presense of E01..E0n, but I am not sure. best regards Markus
comment:6 by , 18 years ago
FYI see also the related AVCE00 bug about the changes required to AVCE00 to add E00 support in OGR: http://bugzilla.maptools.org/show_bug.cgi?id=1497 About the split E00 (e01, e02, etc) files: I don't think avcimport ever supported that either
comment:7 by , 18 years ago
Daniel, I just discovered that I test in my GRASS/v.in.e00 script for split E00 files: http://freegis.org/cgi-bin/viewcvs.cgi/grass6/scripts/v.in.e00/v.in.e00?rev=HEAD&content-type=text/vnd.viewcvs-markup So I may probably mention this as wish? Low priority of course... Or print a warning if map.e01 is the same directory. Best Markus
comment:8 by , 18 years ago
You could create a enhancement bug in the AVCE00 bugzilla (http://bugzilla.maptools.org/) for the split files, but since switching back and forth between files would imply a performance hit and increase code complexity, that would remain very low priority in my opinion (users should merge their files instead). As an interim solution, a warning could probably be put in place relatively easily if the corresponding .e01 is found in the same dir as you suggest.
comment:9 by , 18 years ago
Daniel, I have submitted the wish: http://bugzilla.maptools.org/show_bug.cgi?id=1517 Markus
comment:10 by , 17 years ago
Frank, do you know if there are still outstanding issues with the the polygon (PAL) geometry reading? If not, I'll simplify v.in.e00 in GRASS to use OGR instead of avcimport (one less dependency...). Best regards Markus
comment:11 by , 17 years ago
Markus, Unfortunately, as far as I know the problem with polygons remains.
comment:12 by , 17 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Keywords: | AVC E00 Shapefile added |
comment:13 by , 16 years ago
Frank,
are the outstanding issues with the the polygon (PAL) geometry reading on the plate somehow?
Curious, Markus
comment:14 by , 16 years ago
Markus,
I do not anticipate dealing with this issue in the next few months. Ideally I'd like to turn it over to a paid maintainer when time is available.
comment:16 by , 5 years ago
Milestone: | → closed_because_of_github_migration |
---|---|
Resolution: | → wontfix |
Status: | assigned → closed |
This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.