Changes between Version 3 and Version 4 of Ticket #1484


Ignore:
Timestamp:
Apr 2, 2007, 8:38:31 AM (17 years ago)
Author:
warmerdam
Comment:

There seem to be potentially serious issues with the geodatabase driver. I have moved this to 1.4.1 milestone, and I will review the points that Mateusz has raised.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1484

    • Property Cc warmerdam added
    • Property Summary ogr2ogr translation of NHD geodatabase to PostGIS is incomplete → NHD (ESRI) geodatabase reading problems
    • Property Priority highest → high
    • Property Milestone → 1.4.1
    • Property Keywords geodatabase added

  • Ticket #1484 – Description

    v3 v4  
     1
     2The USGS NHD data is in ESRI geodatabase mdb format. Example cmd line:
    13{{{
    2 The USGS NHD data is in ESRI geodatabase mdb format. Example cmd line:
    34ogr2ogr -f PostgreSQL PG:"user=user dbname=NHD host=localhost password=pass port=5432" NHDH0104.mdb
    4 
    5 The above cmd line creates a set of PostGIS tables, but some of the tables' wkb_geometry fields are empty - for example NHDARea, HYDRO_NET_Junctions.
    6 The NHD shape fields appear to have type 19 for polygons and type 9 for points which are unknown types, to me. The shape object signatures appear to match PolygonM, 25, and PointM, 21, but since the types do not match measure features the Mmin, Mmax, Marray may mean something different.
     5}}}
     6The above cmd line creates a set of PostGIS tables, but some of the tables' wkb_geometry fields are empty - for example NHDARea, HYDRO_NET_Junctions. The NHD shape fields appear to have type 19 for polygons and type 9 for points which are unknown types, to me. The shape object signatures appear to match PolygonM, 25, and PointM, 21, but since the types do not match measure features the Mmin, Mmax, Marray may mean something different.
    77
    88thanks
    9 }}}