Opened 16 years ago
Closed 8 years ago
#2269 closed enhancement (wontfix)
GDAL/OGR cannot access ArcInfo Network coverages properly
Reported by: | PeterHalls | Owned by: | chaitanya |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | OGR_SF | Version: | 1.5.0 |
Severity: | normal | Keywords: | AVCBin |
Cc: | Daniel Morissette, warmerdam |
Description
GDAL/OGR only opens the arc (line) component of ESRI Network coverages and it does not seem possible to access the associated tables, particularly the .NAT, through OGR.
OGR uses the AVCE00 library to provide coverage access, but the version shipped with GDAL 1.5.0 is 1.2.2, which has limited capability to access the non-geometry tables. AVCE00 version 2.0 was released in August 2006 and provides significantly enhanced capabilities for working with the associated coverage tables, including (for Network coverages) .NAT, .SEC, .RAT and .TRN.
As ESRI still use this format for Network datasets, would it please be possible to enhance OGR to use the later version of AVCE00 and provide layer access to the NAT, etc., where these exist in a line covarage?
Many thanks.
Change History (7)
comment:1 by , 16 years ago
Cc: | added |
---|---|
Component: | default → OGR_SF |
Keywords: | AVCBin added |
Milestone: | → 1.6.0 |
Owner: | changed from | to
comment:2 by , 15 years ago
Owner: | changed from | to
---|
Chaitanya,
Please treat this as a low priority todo item.
comment:3 by , 15 years ago
Milestone: | 1.6.1 → 1.7.0 |
---|
comment:4 by , 9 years ago
If this was set to low priority 6 years ago, should it be set to no priority and wontfix now?
comment:6 by , 8 years ago
Really hard to believe that anybody would start to work on this. Closing.
comment:7 by , 8 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Mateusz,
Could you upgrade to the latest AVCE00 code in GDAL SVN in trunk, and look into supporting network coverages if it is practical? You might need to ask Daniel (as AVCE00 maintainer) some questions, and I have added him as a cc:.
Try to work this out in time for 1.6.0 release.