Guest User

Untitled

a guest
Jan 14th, 2018
334
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.88 KB | None | 0 0
  1. [lidar@rsgisvmw02 gdal]$ las2oci --block-table-name lidar_block --t_srs EPSG:4326+4326 --global-extent 180.0,-90.0,180.0,90.0 --block-capacity 5000 --offset '0 0 0' --srid 4326 --post-sql "begin execute immediate 'alter procedure build_max_density compile'; build_max_density; end;" --scale 0.0000001 0.0000001 0.0001 -c lidar/lidar@rsgisvmw02.crrel.usace.army.mil/orcl --base-table-name lidar_base_pc --header-blob-column header -i /u02/LASdata/Office_of_Americas/Concord_NH/LAS/0101.las --cloud-column-name pc --a_srs EPSG:26919+4326 --debug
  2. Opening /u02/LASdata/Office_of_Americas/Concord_NH/LAS/0101.las to fetch header
  3. Setting output base table to: lidar_base_pc
  4. Setting output block table to: lidar_block
  5. Setting output point cloud column to: pc
  6. Setting header blob column to: header
  7. Setting block capacity to: 5000
  8. Setting precision to: 8
  9. Setting output Oracle SRID to: 4326
  10. Setting output post-sql to: begin execute immediate 'alter procedure build_max_density compile'; build_max_density; end;
  11. Setting offsets to: 0 0 0
  12. Setting scales to: 1e-07 1e-07 0.0001
  13. Setting input SRS to 'EPSG:26919+4326'
  14. Setting output SRS to EPSG:4326+4326
  15. GDAL Debug: OGRCT: Source: +proj=utm +zone=19 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
  16. GDAL Debug: OGRCT: Target: +proj=longlat +datum=WGS84 +no_defs
  17. GDAL Debug: OGRCT: Source: +proj=utm +zone=19 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
  18. GDAL Debug: OGRCT: Target: +proj=longlat +datum=WGS84 +no_defs
  19. Connecting with username: lidar password: lidar instance: rsgisvmw02.crrel.usace.army.mil/orcl
  20. Base table name lidar_base_pc cloud column: pc block table: lidar_block
  21. Oracle connection succeded
  22. GDAL Debug: PL/SQL:
  23. select table_name from user_tables where table_name like upper('%%lidar_block%%')
  24.  
  25. Using existing block table ...
  26. Chipping data for loading into Oracle with 5000 block capacity
  27. GDAL Debug: PL/SQL:
  28. SELECT COORD_REF_SYS_KIND from MDSYS.SDO_COORD_REF_SYSTEM WHERE SRID = :1
  29.  
  30. GDAL Debug: PL/SQL:
  31. declare
  32. pc_id NUMBER := :1;
  33. pc sdo_pc;
  34. begin
  35. -- Initialize the Point Cloud object.
  36. pc := sdo_pc_pkg.init(
  37. 'LIDAR_BASE_PC', -- Table that has the SDO_POINT_CLOUD column defined
  38. 'PC', -- Column name of the SDO_POINT_CLOUD object
  39. 'LIDAR_BLOCK', -- Table to store blocks of the point cloud
  40. 'blk_capacity=5000', -- max # of points per block
  41. mdsys.sdo_geometry(2003, 4326, null,
  42. mdsys.sdo_elem_info_array(1,1003,3),
  43. mdsys.sdo_ordinate_array(
  44. -71.6388,43.3043,-71.6137,43.323)), -- Extent
  45. 0.5, -- Tolerance for point cloud
  46. 5, -- Total number of dimensions
  47. null);
  48. :1 := pc.pc_id;
  49. -- Insert the Point Cloud object into the "base" table.
  50. insert into LIDAR_BASE_PC ( ID, PC,HEADER) values ( pc.pc_id, pc, :1);
  51. end;
  52.  
  53.  
  54. error: GDAL Failure number=1: ORA-01036: illegal variable name/number
Add Comment
Please, Sign In to add comment