Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
otb
otb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 298
    • Issues 298
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 14
    • Merge Requests 14
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Main Repositories
  • otbotb
  • Issues
  • #149

Closed
Open
Opened Mar 25, 2010 by Sébastien Dinot@sdinotOwner

UTM projection supposed WGS84 ellipsoid

Mantis Issue 149, reported by echristophe, assigned to jmichel, created: 2010-03-25

Apparently, when confronted with another UTM projection, for example epsg 23030 which is using and ED50 datum (http://en.wikipedia.org/wiki/ED50), OTB supposed that the datum is WGS84 and end up 100m away.

See discussion on otb user list: http://groups.google.com/group/otb-users/browse_thread/thread/5358d28341046f8d

1429255266 - julienWe should have a look at supported projections in OTB (with other datum for instance).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: orfeotoolbox/otb#149