search

melowntech / workshop

Workshop of Melown 3D stack
10 stars 3 forks source link

Running lodtree2vts produces tilesets with zero lod, tile ranges #22

Open dominoc opened 5 years ago

dominoc commented 5 years ago

I am trying to run the lodtree2vts encoder on my sample lodtree.xml exported from Ultramap but the resultant tileset.conf has zero lod ranges, tile ranges, and positions, which don't look right to me. There are no error messages when running. Do you have any idea what can be wrong?

The resultant tileset.conf: { "boundLayers" : [], "credits" : [], "driver" : { "binaryOrder" : 5, "metaUnusedBits" : 5, "type" : "plain", "uuid" : "01ea3428-8a72-4926-9289-9cab0280979f" }, "id" : "from_um", "lodRange" : [ 0, 0 ], "position" : [ "obj", 0, 0, "fixed", 0, 0, 0, 0, 0, 0 ], "referenceFrame" : "melown2015", "revision" : 3, "spatialDivisionExtents" : {}, "tileRange" : [ 0, 0, 0, 0 ], "version" : 1 }

The following are the processing messages: vts@myws04-ubuntu:~/mapproxy/datasets$ lodtree2vts --input export2/ --output from-um --referenceFrame melown2015 --tilesetId from_um - -overwrite
2018-07-24 15:27:21 I3 [23114(main)]: LODTree: SRS="epsg:32633", origin: 3 {lodtreefile.cpp:buildParams():207}
2018-07-24 15:27:21 I3 [23114(main)]: Parsing block "Sheet-000009_000013/Sheet- 000009_000013.xml". {lodtreefile.cpp:openArchive():239}
2018-07-24 15:27:21 I3 [23114(main)]: Parsing block "Sheet-000010_000013/Sheet- 000010_000013.xml". {lodtreefile.cpp:openArchive():239}
2018-07-24 15:27:21 I3 [23114(main)]: Parsing block "Sheet-000011_000013/Sheet- 000011_000013.xml". {lodtreefile.cpp:openArchive():239}
2018-07-24 15:27:21 I3 [23114(main)]: Parsing block "Sheet-000012_000013/Sheet- 000012_000013.xml". {lodtreefile.cpp:openArchive():239}
2018-07-24 15:27:21 I3 [23114(main)]: Parsing block "Sheet-000013_000013/Sheet-

and the following is a snippet of the input LODTreeExport.xml file: `<?xml version="1.0" encoding="utf-8"?>

EPSG:32633 NodeCenter

`

vaclavblazek commented 5 years ago

Can you please run the tool again with increased logging via --log.mask=I1W1E1 option. You'd have to delete the existing output or use --overwrite option.

dominoc commented 5 years ago

I did that. The resultant log file is attached here lodtree.zip