Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Origo not taken into account #8

Open
ilwna opened this issue Feb 3, 2017 · 1 comment
Open

Origo not taken into account #8

ilwna opened this issue Feb 3, 2017 · 1 comment

Comments

@ilwna
Copy link

ilwna commented Feb 3, 2017

Some of my SOSI files have an origo different from 0;0. It looks like it's not taken into account so the result data is not at the right place.
Is there a way to fix this?
@espena
Copy link
Owner

espena commented Feb 9, 2017 •
edited
Loading

Sosicon does indeed read ORIGO; do you have a sample file? I know there have been issues where some applications write wrong offset values to the SOSI header. This might be one of these occations. What happens if you manually change origo to 0,0 before converting the file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@espena @ilwna