Feature Crosswalk

[traffordbrown]

Hello, Wondering if a crosswalk doc. has been created between OSM and TDS 6 for feature types?

Thanks

[mattjdnv]

I have not created a crosswalk document for the TDS61 <> OSM translation.

To build the translator, I crawled through the TDS61 spec and used existing OSM tags + values or created new ones for each of the features.

From the $HOOT_HOME directory:

• plugins/fcode_common.js - This has the one to one mappings for an FCODE and and OSM tag + value
• plugins/tds61.js - This has the To OSM & To TDS functions as well as the pre and post processing steps
• plugins/tds61_rules.js - This has the one2one rules for the TDS61 attributes as well as look up tables for the ESRI FCSUBTYPE.
• plugins/tds61_schema.js - This has the TDS61 output schema. This is built from the NGA TDS schema excel workbooks.

Mattj

[traffordbrown]

Thanks for your response.

We're still in the process of getting Hootenanny installed. Is anyone intending/thinking about creating a TDS61/OSM crosswalk (or translator) vis-a-vis feature types? I can see it having a lot of value.

[MikeTho16]

In the context of this discussion is there a difference between a "crosswalk" and a "translator"? mattjdnv you indicated that there is no crosswalk, but seemed to suggest that you had created a translator.

[mattjdnv]

I think of a crosswalk as a document.

We have TDSv40 & TDSv61 translators that convert to/from TDS and OSM+.
OSM+ is "standard" OSM (http://wiki.openstreetmap.org/wiki/Map_Features) with a lot of extra tags added to it to support features and attributes that are NGA product specific.

From the command line:

• Converting from a TDSv61 FGDB to an OSM+ file: hoot ogr2osm $HOOT_HOME/translations/TDSv61.js tds.gdb tds.osm
• Converting from an OSM file to a set of TDSv61 shapefiles: hoot osm2ogr $HOOT_HOME/translations/TDSv61.js tds.osm output_tds61_tds.shp

This gives shapefiles that are "thematic groups" like this:

matt@dg:/data/matt_test/hoot_test$ ls output_tds61_tds
AeronauticPnt.dbf  HydrographyCrv.dbf  SettlementSrf.dbf  TransportationGroundCrv.dbf
AeronauticPnt.prj  HydrographyCrv.prj  SettlementSrf.prj  TransportationGroundCrv.prj
AeronauticPnt.shp  HydrographyCrv.shp  SettlementSrf.shp  TransportationGroundCrv.shp
AeronauticPnt.shx  HydrographyCrv.shx  SettlementSrf.shx  TransportationGroundCrv.shx
FacilityPnt.dbf    RecreationSrf.dbf   StructurePnt.dbf   TransportationGroundPnt.dbf
FacilityPnt.prj    RecreationSrf.prj   StructurePnt.prj   TransportationGroundPnt.prj
FacilityPnt.shp    RecreationSrf.shp   StructurePnt.shp   TransportationGroundPnt.shp
FacilityPnt.shx    RecreationSrf.shx   StructurePnt.shx   TransportationGroundPnt.shx
FacilitySrf.dbf    SettlementPnt.dbf   StructureSrf.dbf   UtilityInfrastructurePnt.dbf
FacilitySrf.prj    SettlementPnt.prj   StructureSrf.prj   UtilityInfrastructurePnt.prj
FacilitySrf.shp    SettlementPnt.shp   StructureSrf.shp   UtilityInfrastructurePnt.shp
FacilitySrf.shx    SettlementPnt.shx   StructureSrf.shx   UtilityInfrastructurePnt.shx

• You can also output TDS shapefiles that are the individual layers (1 x FCODE / layer)

hoot osm2ogr -D ogr.tds.structure=false tds.osm output_tds61.shp

matt@dg:/data/matt_test/hoot_test$ ls output_tds61
AIRCRAFT_HANGAR_P.dbf          BUILT_UP_AREA_S.shp  HUT_P.dbf      SHED_P.shp
AIRCRAFT_HANGAR_P.prj          BUILT_UP_AREA_S.shx  HUT_P.prj      SHED_P.shx
AIRCRAFT_HANGAR_P.shp          CART_TRACK_C.dbf     HUT_P.shp      SHED_S.dbf
AIRCRAFT_HANGAR_P.shx          CART_TRACK_C.prj     HUT_P.shx      SHED_S.prj
BUILDING_P.dbf                 CART_TRACK_C.shp     PYLON_P.dbf    SHED_S.shp
BUILDING_P.prj                 CART_TRACK_C.shx     PYLON_P.prj    SHED_S.shx
BUILDING_P.shp                 CONTROL_TOWER_P.dbf  PYLON_P.shp    STADIUM_S.dbf
BUILDING_P.shx                 CONTROL_TOWER_P.prj  PYLON_P.shx    STADIUM_S.prj
BUILDING_S.dbf                 CONTROL_TOWER_P.shp  RAILWAY_C.dbf  STADIUM_S.shp
BUILDING_S.prj                 CONTROL_TOWER_P.shx  RAILWAY_C.prj  STADIUM_S.shx
BUILDING_S.shp                 CROSSING_P.dbf       RAILWAY_C.shp  TOWER_P.dbf
BUILDING_S.shx                 CROSSING_P.prj       RAILWAY_C.shx  TOWER_P.prj
BUILDING_SUPERSTRUCTURE_P.dbf  CROSSING_P.shp       RIVER_C.dbf    TOWER_P.shp
BUILDING_SUPERSTRUCTURE_P.prj  CROSSING_P.shx       RIVER_C.prj    TOWER_P.shx
BUILDING_SUPERSTRUCTURE_P.shp  FACILITY_P.dbf       RIVER_C.shp    TRAIL_C.dbf
BUILDING_SUPERSTRUCTURE_P.shx  FACILITY_P.prj       RIVER_C.shx    TRAIL_C.prj
BUILT_UP_AREA_P.dbf            FACILITY_P.shp       ROAD_C.dbf     TRAIL_C.shp
BUILT_UP_AREA_P.prj            FACILITY_P.shx       ROAD_C.prj     TRAIL_C.shx
BUILT_UP_AREA_P.shp            FACILITY_S.dbf       ROAD_C.shp     TRANSPORTATION_STATION_P.dbf
BUILT_UP_AREA_P.shx            FACILITY_S.prj       ROAD_C.shx     TRANSPORTATION_STATION_P.prj
BUILT_UP_AREA_S.dbf            FACILITY_S.shp       SHED_P.dbf     TRANSPORTATION_STATION_P.shp
BUILT_UP_AREA_S.prj            FACILITY_S.shx       SHED_P.prj     TRANSPORTATION_STATION_P.shx

• Note: If you want a FGDB instead of shapefiles as the output, put "*.gdb" at the end of the output name instead of ".shp". I'm showing shapefiles in this example as it is easier to see the layer names in a directory than look at the output from ogrinfo.

[traffordbrown]

Thanks.

[bwitham]

Closing due to inactivity. If this issue still requires work, please reopen.