MySQL 8.0 Error Code: 3617. Latitude is out of range in function st_geomfromtext The 2019...
Aging parents with no investments
What is the closest word meaning "respect for time / mindful"
Deal with toxic manager when you can't quit
Why do UK politicians seemingly ignore opinion polls on Brexit?
Am I thawing this London Broil safely?
What is the meaning of the verb "bear" in this context?
Can one be advised by a professor who is very far away?
What is the motivation for a law requiring 2 parties to consent for recording a conversation
Geography at the pixel level
Which Sci-Fi work first showed weapon of galactic-scale mass destruction?
Earliest use of the term "Galois extension"?
Apparent duplicates between Haynes service instructions and MOT
Why didn't the Event Horizon Telescope team mention Sagittarius A*?
Are there incongruent pythagorean triangles with the same perimeter and same area?
Right tool to dig six foot holes?
Did Section 31 appear in Star Trek: The Next Generation?
Protecting Dualbooting Windows from dangerous code (like rm -rf)
What did it mean to "align" a radio?
Identify boardgame from Big movie
Is three citations per paragraph excessive for undergraduate research paper?
Who coined the term "madman theory"?
What tool would a Roman-age civilization have for the breaking of silver and other metals into dust?
How to manage monthly salary
What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?
MySQL 8.0 Error Code: 3617. Latitude is out of range in function st_geomfromtext
The 2019 Stack Overflow Developer Survey Results Are In
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
First of all: Hello to everybody, this is my first post!
I have a problem creating spatial index in MySQL 8.0. Here the description:
- I have a collection of several thousand species range maps (polygon & multi-polygon) which is provided by IUCN as a single shapefile.
- I opened this shapefile in QGIS 3.6 and performed geometry check (Vector/Geometry Tools/Check validity).
- All valid range maps have been exported into a new shapefile.
- I imported this new shapefile into MySQL 8.0 via command line tool ogr2ogr.
- For the ogr2ogr import I had to use the option "-skipfailures". Reason: ogr2ogr considered some of the range maps as invalid.
- The remaining maps were imported into a MySQL table. And it seems all ok, at least you can run queries successfully. But the queries are slow, because MySQL always reads the whole table.
- So I decided to create a spatial index and here the problem starts:
“03:10:32 UPDATE gis.all_reptiles_innodb SET SHAPE =
ST_GeomFromText(ST_AsText(shape), 4326) Error Code: 3617. Latitude
124.241900 is out of range in function st_geomfromtext. It must be within [-90.000000, 90.000000]. 0.000 sec”
A latitude of "124.241900" is obviously impossible, because latitude can only range from -90 and +90 degrees. It seems to happen quite often, that people mix up longitude (allowed range: -180 and +180 degrees) with latitude.
Additional information: QIS shows these properties for the shapefile:
“-181.5899672849999718,-54.0594466929999840 : 181.1581243180000911,71.1881355930000836”
Does somebody have an idea what went wrong and how I could prevent this error?
Something in the interaction between shapefile, QGIS, ogr2ogr and MySQL obviously caused problems. The map display in QGIS, however, seems to work fine.
I would like to import only valid maps into MySQL because I need the spatial data index. Without an index a single query takes >8 seconds and that is too slow.
Looking forward to your feedback!
qgis shapefile ogr2ogr mysql-spatial
New contributor
add a comment |
First of all: Hello to everybody, this is my first post!
I have a problem creating spatial index in MySQL 8.0. Here the description:
- I have a collection of several thousand species range maps (polygon & multi-polygon) which is provided by IUCN as a single shapefile.
- I opened this shapefile in QGIS 3.6 and performed geometry check (Vector/Geometry Tools/Check validity).
- All valid range maps have been exported into a new shapefile.
- I imported this new shapefile into MySQL 8.0 via command line tool ogr2ogr.
- For the ogr2ogr import I had to use the option "-skipfailures". Reason: ogr2ogr considered some of the range maps as invalid.
- The remaining maps were imported into a MySQL table. And it seems all ok, at least you can run queries successfully. But the queries are slow, because MySQL always reads the whole table.
- So I decided to create a spatial index and here the problem starts:
“03:10:32 UPDATE gis.all_reptiles_innodb SET SHAPE =
ST_GeomFromText(ST_AsText(shape), 4326) Error Code: 3617. Latitude
124.241900 is out of range in function st_geomfromtext. It must be within [-90.000000, 90.000000]. 0.000 sec”
A latitude of "124.241900" is obviously impossible, because latitude can only range from -90 and +90 degrees. It seems to happen quite often, that people mix up longitude (allowed range: -180 and +180 degrees) with latitude.
Additional information: QIS shows these properties for the shapefile:
“-181.5899672849999718,-54.0594466929999840 : 181.1581243180000911,71.1881355930000836”
Does somebody have an idea what went wrong and how I could prevent this error?
Something in the interaction between shapefile, QGIS, ogr2ogr and MySQL obviously caused problems. The map display in QGIS, however, seems to work fine.
I would like to import only valid maps into MySQL because I need the spatial data index. Without an index a single query takes >8 seconds and that is too slow.
Looking forward to your feedback!
qgis shapefile ogr2ogr mysql-spatial
New contributor
add a comment |
First of all: Hello to everybody, this is my first post!
I have a problem creating spatial index in MySQL 8.0. Here the description:
- I have a collection of several thousand species range maps (polygon & multi-polygon) which is provided by IUCN as a single shapefile.
- I opened this shapefile in QGIS 3.6 and performed geometry check (Vector/Geometry Tools/Check validity).
- All valid range maps have been exported into a new shapefile.
- I imported this new shapefile into MySQL 8.0 via command line tool ogr2ogr.
- For the ogr2ogr import I had to use the option "-skipfailures". Reason: ogr2ogr considered some of the range maps as invalid.
- The remaining maps were imported into a MySQL table. And it seems all ok, at least you can run queries successfully. But the queries are slow, because MySQL always reads the whole table.
- So I decided to create a spatial index and here the problem starts:
“03:10:32 UPDATE gis.all_reptiles_innodb SET SHAPE =
ST_GeomFromText(ST_AsText(shape), 4326) Error Code: 3617. Latitude
124.241900 is out of range in function st_geomfromtext. It must be within [-90.000000, 90.000000]. 0.000 sec”
A latitude of "124.241900" is obviously impossible, because latitude can only range from -90 and +90 degrees. It seems to happen quite often, that people mix up longitude (allowed range: -180 and +180 degrees) with latitude.
Additional information: QIS shows these properties for the shapefile:
“-181.5899672849999718,-54.0594466929999840 : 181.1581243180000911,71.1881355930000836”
Does somebody have an idea what went wrong and how I could prevent this error?
Something in the interaction between shapefile, QGIS, ogr2ogr and MySQL obviously caused problems. The map display in QGIS, however, seems to work fine.
I would like to import only valid maps into MySQL because I need the spatial data index. Without an index a single query takes >8 seconds and that is too slow.
Looking forward to your feedback!
qgis shapefile ogr2ogr mysql-spatial
New contributor
First of all: Hello to everybody, this is my first post!
I have a problem creating spatial index in MySQL 8.0. Here the description:
- I have a collection of several thousand species range maps (polygon & multi-polygon) which is provided by IUCN as a single shapefile.
- I opened this shapefile in QGIS 3.6 and performed geometry check (Vector/Geometry Tools/Check validity).
- All valid range maps have been exported into a new shapefile.
- I imported this new shapefile into MySQL 8.0 via command line tool ogr2ogr.
- For the ogr2ogr import I had to use the option "-skipfailures". Reason: ogr2ogr considered some of the range maps as invalid.
- The remaining maps were imported into a MySQL table. And it seems all ok, at least you can run queries successfully. But the queries are slow, because MySQL always reads the whole table.
- So I decided to create a spatial index and here the problem starts:
“03:10:32 UPDATE gis.all_reptiles_innodb SET SHAPE =
ST_GeomFromText(ST_AsText(shape), 4326) Error Code: 3617. Latitude
124.241900 is out of range in function st_geomfromtext. It must be within [-90.000000, 90.000000]. 0.000 sec”
A latitude of "124.241900" is obviously impossible, because latitude can only range from -90 and +90 degrees. It seems to happen quite often, that people mix up longitude (allowed range: -180 and +180 degrees) with latitude.
Additional information: QIS shows these properties for the shapefile:
“-181.5899672849999718,-54.0594466929999840 : 181.1581243180000911,71.1881355930000836”
Does somebody have an idea what went wrong and how I could prevent this error?
Something in the interaction between shapefile, QGIS, ogr2ogr and MySQL obviously caused problems. The map display in QGIS, however, seems to work fine.
I would like to import only valid maps into MySQL because I need the spatial data index. Without an index a single query takes >8 seconds and that is too slow.
Looking forward to your feedback!
qgis shapefile ogr2ogr mysql-spatial
qgis shapefile ogr2ogr mysql-spatial
New contributor
New contributor
New contributor
asked 1 min ago
stssts
1
1
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
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',
autoActivateHeartbeat: false,
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
});
}
});
sts is a new contributor. Be nice, and check out our Code of Conduct.
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%2f318438%2fmysql-8-0-error-code-3617-latitude-is-out-of-range-in-function-st-geomfromtext%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
sts is a new contributor. Be nice, and check out our Code of Conduct.
sts is a new contributor. Be nice, and check out our Code of Conduct.
sts is a new contributor. Be nice, and check out our Code of Conduct.
sts is a new contributor. Be nice, and check out our Code of Conduct.
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.
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%2f318438%2fmysql-8-0-error-code-3617-latitude-is-out-of-range-in-function-st-geomfromtext%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