Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • otb otb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 214
    • Issues 214
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Main Repositories
  • otbotb
  • Issues
  • #1883

"Error invalid index : -1" in applications using vector data

Description

We observed a strange message with some OTB applications that use vector data :

otbcli_VectorDataTransform -vd extract_segments.shp -in extract_zone_WV.tif -out test.shp -transform.tx 0 -transform.ty 0 -transform.ro -15 -transform.scale 1 -transform.centerx 370433 -transform.centery 48331881

`2019-04-12 14:46:04 (INFO): Default RAM limit for OTB is 128 MB
019-04-12 14:46:04 (INFO): GDAL maximum cache size is 12854 MB
2019-04-12 14:46:04 (INFO): OTB will use at most 48 threads 2019-04-12 14:46:04 (INFO): No kwl metadata found in file extract_zone_WV.tif

ERROR 1: Invalid index : -1

ERROR 1: Invalid index : -1

ERROR 1: Invalid index : -1 [ ... ]`

It seems that OTB may not use OGR field wrapper properly, in ./OTB/Modules/Adapters/GdalAdapters/src/otbOGRFieldWrapper.cxx The message is activated if OGR can not access to m_index value.

The dataset seems to be clean and consistent.

Steps to reproduce

The following zip file contain a small dataset that shows the error log shown here before. bug_OTB_OGR.zip

Configuration information

OTB 6.6 but it seems to be an old problem. It occurs in different applications that read or produce vector files.

Edited Apr 12, 2019 by Yannick TANGUY
Assignee
Assign to
Time tracking