Convert X and Y values from an Israeli source to match the WGS 84 / Pseudo-Mercator CRS in QGIS
up vote
2
down vote
favorite
I have an Israeli database with X and Y values that I need to upload into QGIS.
I have converted the Excel file into a CSV UTF-8 (Comma delimited) file and upload it as Delimited Text Layer.
I have tried all the Israeli CRS listed in QGIS, and that data is still not matching.
It sure do look like the Israel outlines, but it is about 700kM off somewhere in the Egyptian desert.
What is needed in order to fix this problem?
qgis coordinate-system
edited Nov 22 at 13:49
Vince
14.3k32646
asked Nov 22 at 10:27
Nitzan Matan
1,6021027
add a comment |
up vote
2
down vote
favorite
I have an Israeli database with X and Y values that I need to upload into QGIS.
I have converted the Excel file into a CSV UTF-8 (Comma delimited) file and upload it as Delimited Text Layer.
I have tried all the Israeli CRS listed in QGIS, and that data is still not matching.
It sure do look like the Israel outlines, but it is about 700kM off somewhere in the Egyptian desert.
What is needed in order to fix this problem?
qgis coordinate-system
edited Nov 22 at 13:49
Vince
14.3k32646
asked Nov 22 at 10:27
Nitzan Matan
1,6021027
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have an Israeli database with X and Y values that I need to upload into QGIS.
I have converted the Excel file into a CSV UTF-8 (Comma delimited) file and upload it as Delimited Text Layer.
I have tried all the Israeli CRS listed in QGIS, and that data is still not matching.
It sure do look like the Israel outlines, but it is about 700kM off somewhere in the Egyptian desert.
What is needed in order to fix this problem?
qgis coordinate-system
edited Nov 22 at 13:49
Vince
14.3k32646
asked Nov 22 at 10:27
Nitzan Matan
1,6021027
I have an Israeli database with X and Y values that I need to upload into QGIS.
I have converted the Excel file into a CSV UTF-8 (Comma delimited) file and upload it as Delimited Text Layer.
I have tried all the Israeli CRS listed in QGIS, and that data is still not matching.
It sure do look like the Israel outlines, but it is about 700kM off somewhere in the Egyptian desert.
What is needed in order to fix this problem?
qgis coordinate-system
qgis coordinate-system
edited Nov 22 at 13:49
Vince
14.3k32646
asked Nov 22 at 10:27
Nitzan Matan
1,6021027
edited Nov 22 at 13:49
Vince
14.3k32646
asked Nov 22 at 10:27
Nitzan Matan
1,6021027
edited Nov 22 at 13:49
Vince
14.3k32646
edited Nov 22 at 13:49
Vince
14.3k32646
edited Nov 22 at 13:49
Vince
14.3k32646
14.3k32646
asked Nov 22 at 10:27
Nitzan Matan
1,6021027
asked Nov 22 at 10:27
Nitzan Matan
1,6021027
asked Nov 22 at 10:27
Nitzan Matan
1,6021027
1,6021027
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
Your problem is related with the incompatibility of the decimal separator of your software, your system and maybe your data also. It is a quite common challenge, see PEP-378 and it deserve a lot of care to deal with it properly, specially if you are reading data from other
The decimal separator comes togheter with the list separator, thousands separator and other "cultural issues". I would say that in Qgis the dot as decimal separator is the best option becuase Python (and C) uses it internally and not all tools handle the local configuration in a good way.
Incompatible decimal separators is a pain we must learn to live with.
answered Nov 22 at 13:13
Marco
2,005524
add a comment |
up vote
2
down vote
accepted
I seem that I have figured it up, and the problem is quite an odd one.
The X and Y values are listed with a dot between the third and fifth numbers. In QGIS the CRS values are written without a dot, so obviously it cannot work like that.
Once I multiplied the numbers by 1,000 and uploaded the values as a whole number it fits the Israeli CRS.
answered Nov 22 at 10:48
Nitzan Matan
1,6021027
It should be possible to eliminate the thousands separator dot inside Excel cell/number formatting before exporting. Or you can use a simple text editor like notepad++ to exchange all dots inside the csv to nothing.
– AndreJ
Nov 22 at 15:01
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f303593%2fconvert-x-and-y-values-from-an-israeli-source-to-match-the-wgs-84-pseudo-merca%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Your problem is related with the incompatibility of the decimal separator of your software, your system and maybe your data also. It is a quite common challenge, see PEP-378 and it deserve a lot of care to deal with it properly, specially if you are reading data from other
The decimal separator comes togheter with the list separator, thousands separator and other "cultural issues". I would say that in Qgis the dot as decimal separator is the best option becuase Python (and C) uses it internally and not all tools handle the local configuration in a good way.
Incompatible decimal separators is a pain we must learn to live with.
answered Nov 22 at 13:13
Marco
2,005524
add a comment |
up vote
3
down vote
Your problem is related with the incompatibility of the decimal separator of your software, your system and maybe your data also. It is a quite common challenge, see PEP-378 and it deserve a lot of care to deal with it properly, specially if you are reading data from other
The decimal separator comes togheter with the list separator, thousands separator and other "cultural issues". I would say that in Qgis the dot as decimal separator is the best option becuase Python (and C) uses it internally and not all tools handle the local configuration in a good way.
Incompatible decimal separators is a pain we must learn to live with.
answered Nov 22 at 13:13
Marco
2,005524
add a comment |
up vote
3
down vote
up vote
3
down vote
Your problem is related with the incompatibility of the decimal separator of your software, your system and maybe your data also. It is a quite common challenge, see PEP-378 and it deserve a lot of care to deal with it properly, specially if you are reading data from other
The decimal separator comes togheter with the list separator, thousands separator and other "cultural issues". I would say that in Qgis the dot as decimal separator is the best option becuase Python (and C) uses it internally and not all tools handle the local configuration in a good way.
Incompatible decimal separators is a pain we must learn to live with.
answered Nov 22 at 13:13
Marco
2,005524
Your problem is related with the incompatibility of the decimal separator of your software, your system and maybe your data also. It is a quite common challenge, see PEP-378 and it deserve a lot of care to deal with it properly, specially if you are reading data from other
The decimal separator comes togheter with the list separator, thousands separator and other "cultural issues". I would say that in Qgis the dot as decimal separator is the best option becuase Python (and C) uses it internally and not all tools handle the local configuration in a good way.
Incompatible decimal separators is a pain we must learn to live with.
answered Nov 22 at 13:13
Marco
2,005524
answered Nov 22 at 13:13
Marco
2,005524
answered Nov 22 at 13:13
Marco
2,005524
answered Nov 22 at 13:13
Marco
2,005524
2,005524
add a comment |
add a comment |
up vote
2
down vote
accepted
I seem that I have figured it up, and the problem is quite an odd one.
The X and Y values are listed with a dot between the third and fifth numbers. In QGIS the CRS values are written without a dot, so obviously it cannot work like that.
Once I multiplied the numbers by 1,000 and uploaded the values as a whole number it fits the Israeli CRS.
answered Nov 22 at 10:48
Nitzan Matan
1,6021027
It should be possible to eliminate the thousands separator dot inside Excel cell/number formatting before exporting. Or you can use a simple text editor like notepad++ to exchange all dots inside the csv to nothing.
– AndreJ
Nov 22 at 15:01
add a comment |
up vote
2
down vote
accepted
I seem that I have figured it up, and the problem is quite an odd one.
The X and Y values are listed with a dot between the third and fifth numbers. In QGIS the CRS values are written without a dot, so obviously it cannot work like that.
Once I multiplied the numbers by 1,000 and uploaded the values as a whole number it fits the Israeli CRS.
answered Nov 22 at 10:48
Nitzan Matan
1,6021027
It should be possible to eliminate the thousands separator dot inside Excel cell/number formatting before exporting. Or you can use a simple text editor like notepad++ to exchange all dots inside the csv to nothing.
– AndreJ
Nov 22 at 15:01
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
I seem that I have figured it up, and the problem is quite an odd one.
The X and Y values are listed with a dot between the third and fifth numbers. In QGIS the CRS values are written without a dot, so obviously it cannot work like that.
Once I multiplied the numbers by 1,000 and uploaded the values as a whole number it fits the Israeli CRS.
answered Nov 22 at 10:48
Nitzan Matan
1,6021027
I seem that I have figured it up, and the problem is quite an odd one.
The X and Y values are listed with a dot between the third and fifth numbers. In QGIS the CRS values are written without a dot, so obviously it cannot work like that.
Once I multiplied the numbers by 1,000 and uploaded the values as a whole number it fits the Israeli CRS.
answered Nov 22 at 10:48
Nitzan Matan
1,6021027
answered Nov 22 at 10:48
Nitzan Matan
1,6021027
answered Nov 22 at 10:48
Nitzan Matan
1,6021027
answered Nov 22 at 10:48
Nitzan Matan
1,6021027
1,6021027
It should be possible to eliminate the thousands separator dot inside Excel cell/number formatting before exporting. Or you can use a simple text editor like notepad++ to exchange all dots inside the csv to nothing.
– AndreJ
Nov 22 at 15:01
add a comment |
It should be possible to eliminate the thousands separator dot inside Excel cell/number formatting before exporting. Or you can use a simple text editor like notepad++ to exchange all dots inside the csv to nothing.
– AndreJ
Nov 22 at 15:01
It should be possible to eliminate the thousands separator dot inside Excel cell/number formatting before exporting. Or you can use a simple text editor like notepad++ to exchange all dots inside the csv to nothing.
– AndreJ
Nov 22 at 15:01
It should be possible to eliminate the thousands separator dot inside Excel cell/number formatting before exporting. Or you can use a simple text editor like notepad++ to exchange all dots inside the csv to nothing.
– AndreJ
Nov 22 at 15:01
add a comment |
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f303593%2fconvert-x-and-y-values-from-an-israeli-source-to-match-the-wgs-84-pseudo-merca%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
