QGIS how to handle circular but non-closed lines Planned maintenance scheduled April 17/18,...
Amount of permutations on an NxNxN Rubik's Cube
How to Make a Beautiful Stacked 3D Plot
Do I really need recursive chmod to restrict access to a folder?
What's the meaning of "fortified infraction restraint"?
Fundamental Solution of the Pell Equation
For a new assistant professor in CS, how to build/manage a publication pipeline
Most bit efficient text communication method?
How could we fake a moon landing now?
Can anything be seen from the center of the Boötes void? How dark would it be?
Why didn't Eitri join the fight?
How do I make this wiring inside cabinet safer? (Pic)
Why do the resolve message appear first?
What are the out-of-universe reasons for the references to Toby Maguire-era Spider-Man in ITSV
How to down pick a chord with skipped strings?
What does the "x" in "x86" represent?
8 Prisoners wearing hats
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
Is it cost-effective to upgrade an old-ish Giant Escape R3 commuter bike with entry-level branded parts (wheels, drivetrain)?
Do jazz musicians improvise on the parent scale in addition to the chord-scales?
What is the longest distance a player character can jump in one leap?
Using et al. for a last / senior author rather than for a first author
On SQL Server, is it possible to restrict certain users from using certain functions, operators or statements?
Is the Standard Deduction better than Itemized when both are the same amount?
First console to have temporary backward compatibility
QGIS how to handle circular but non-closed lines
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?How to clean layers from non topological databases?What am I doing wrong with QGIS v.clean?How to remove identical lines from layer in QGIS?Solve wrong topological error after union?Drag points on lines with snapping in QGIS 2.18Dissolve fails, geometry errors, and cleaning problemsFinding intersection topology errors in QGISGet rid of line inside polygon after mergeConvert polygons to lines ignoring redundant vertices in QGISRemoving pseudo-nodes with QGIS?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I use QGIS 2.18.3 and I have a shapefile with around 30,000 lines and a lot of invalid geometries. It is imported from a CAD project. I managed to solve most of the invalidities with the break function of the v.clean tool from the GRASSGIS toolset.
The remaining errors, around 180, all have the same nature: they used to be closed lines in the CAD project (the outlines of stones) but are now open. So the two endpoints have exactly the same coordinates, therefore they overlap and the geometry is invalid.
Solutions I've tried:
Used the snap function of the v.clean tool - the tool runs without problems but there are still errors afterwards. I've put the threshold on 0.005 m. In advanced parameters I've put the v.in.ogr snap tolerance to 0.005 m as well and the v.in.ogr min area to 0.0
Used "lines to polygons" from the vector menu and converted the polygons back to lines again. All polygons were valid but when I convert them back to lines using "polygons to lines" the errors are still there.
Did I do something wrong or do you have any idea how to solve it in an automated way?
qgis line qgis-2.18
edited Sep 13 '18 at 13:06
BERA
17.2k62044
asked Feb 9 '17 at 16:36
a.urbanitea.urbanite
426
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I use QGIS 2.18.3 and I have a shapefile with around 30,000 lines and a lot of invalid geometries. It is imported from a CAD project. I managed to solve most of the invalidities with the break function of the v.clean tool from the GRASSGIS toolset.
The remaining errors, around 180, all have the same nature: they used to be closed lines in the CAD project (the outlines of stones) but are now open. So the two endpoints have exactly the same coordinates, therefore they overlap and the geometry is invalid.
Solutions I've tried:
Used the snap function of the v.clean tool - the tool runs without problems but there are still errors afterwards. I've put the threshold on 0.005 m. In advanced parameters I've put the v.in.ogr snap tolerance to 0.005 m as well and the v.in.ogr min area to 0.0
Used "lines to polygons" from the vector menu and converted the polygons back to lines again. All polygons were valid but when I convert them back to lines using "polygons to lines" the errors are still there.
Did I do something wrong or do you have any idea how to solve it in an automated way?
qgis line qgis-2.18
edited Sep 13 '18 at 13:06
BERA
17.2k62044
asked Feb 9 '17 at 16:36
a.urbanitea.urbanite
426
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Update: i used the Check Validity tool to isolate the invalid geometries in a seperate layer, then used "explode lines" and then dissolved them by their unique identifier (luckily there was one in the attribute table). This reduced the number of invalid geometries to 54. If i repeat the process the number doesnt decrease anymore although the rest of the invalid geometries have the same issue
– a.urbanite
Feb 9 '17 at 18:16
I would recommend trying to use the MMQGIS plugin's "Delete Duplicate Geometries".
– JohnR
Feb 9 '17 at 20:42
wasnt that tool only for complete geometries like points/lines/polygons instead of vertices? anyway, i tried it but it didnt help.
– a.urbanite
Feb 10 '17 at 13:11
update: ok i tried the workflow described in my first update with another shapefile with the same problem.
– a.urbanite
Mar 3 '17 at 12:45
update2: ok i tried the workflow mentioned in my first update with another shapefile which has the same problem. workflow as follows: run "check validity"-tool, run "explode lines"-tool on invalid output, run "dissolve"-tool, run "Check validity"-tool ->no errors. if i now copy these valid geometries into the valid output of the validity check of the original shapefile and run the validity check again the errors are back! this has to be a bug or i am missing something about the specs of a shapefile...
– a.urbanite
Mar 3 '17 at 12:58
add a comment |
I use QGIS 2.18.3 and I have a shapefile with around 30,000 lines and a lot of invalid geometries. It is imported from a CAD project. I managed to solve most of the invalidities with the break function of the v.clean tool from the GRASSGIS toolset.
The remaining errors, around 180, all have the same nature: they used to be closed lines in the CAD project (the outlines of stones) but are now open. So the two endpoints have exactly the same coordinates, therefore they overlap and the geometry is invalid.
Solutions I've tried:
Used the snap function of the v.clean tool - the tool runs without problems but there are still errors afterwards. I've put the threshold on 0.005 m. In advanced parameters I've put the v.in.ogr snap tolerance to 0.005 m as well and the v.in.ogr min area to 0.0
Used "lines to polygons" from the vector menu and converted the polygons back to lines again. All polygons were valid but when I convert them back to lines using "polygons to lines" the errors are still there.
Did I do something wrong or do you have any idea how to solve it in an automated way?
qgis line qgis-2.18
edited Sep 13 '18 at 13:06
BERA
17.2k62044
asked Feb 9 '17 at 16:36
a.urbanitea.urbanite
426
I use QGIS 2.18.3 and I have a shapefile with around 30,000 lines and a lot of invalid geometries. It is imported from a CAD project. I managed to solve most of the invalidities with the break function of the v.clean tool from the GRASSGIS toolset.
The remaining errors, around 180, all have the same nature: they used to be closed lines in the CAD project (the outlines of stones) but are now open. So the two endpoints have exactly the same coordinates, therefore they overlap and the geometry is invalid.
Solutions I've tried:
Used the snap function of the v.clean tool - the tool runs without problems but there are still errors afterwards. I've put the threshold on 0.005 m. In advanced parameters I've put the v.in.ogr snap tolerance to 0.005 m as well and the v.in.ogr min area to 0.0
Used "lines to polygons" from the vector menu and converted the polygons back to lines again. All polygons were valid but when I convert them back to lines using "polygons to lines" the errors are still there.
Did I do something wrong or do you have any idea how to solve it in an automated way?
qgis line qgis-2.18
qgis line qgis-2.18
edited Sep 13 '18 at 13:06
BERA
17.2k62044
asked Feb 9 '17 at 16:36
a.urbanitea.urbanite
426
edited Sep 13 '18 at 13:06
BERA
17.2k62044
asked Feb 9 '17 at 16:36
a.urbanitea.urbanite
426
edited Sep 13 '18 at 13:06
BERA
17.2k62044
edited Sep 13 '18 at 13:06
BERA
17.2k62044
edited Sep 13 '18 at 13:06
BERA
17.2k62044
17.2k62044
asked Feb 9 '17 at 16:36
a.urbanitea.urbanite
426
asked Feb 9 '17 at 16:36
a.urbanitea.urbanite
426
asked Feb 9 '17 at 16:36
a.urbanitea.urbanite
426
426
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Update: i used the Check Validity tool to isolate the invalid geometries in a seperate layer, then used "explode lines" and then dissolved them by their unique identifier (luckily there was one in the attribute table). This reduced the number of invalid geometries to 54. If i repeat the process the number doesnt decrease anymore although the rest of the invalid geometries have the same issue
– a.urbanite
Feb 9 '17 at 18:16
I would recommend trying to use the MMQGIS plugin's "Delete Duplicate Geometries".
– JohnR
Feb 9 '17 at 20:42
wasnt that tool only for complete geometries like points/lines/polygons instead of vertices? anyway, i tried it but it didnt help.
– a.urbanite
Feb 10 '17 at 13:11
update: ok i tried the workflow described in my first update with another shapefile with the same problem.
– a.urbanite
Mar 3 '17 at 12:45
update2: ok i tried the workflow mentioned in my first update with another shapefile which has the same problem. workflow as follows: run "check validity"-tool, run "explode lines"-tool on invalid output, run "dissolve"-tool, run "Check validity"-tool ->no errors. if i now copy these valid geometries into the valid output of the validity check of the original shapefile and run the validity check again the errors are back! this has to be a bug or i am missing something about the specs of a shapefile...
– a.urbanite
Mar 3 '17 at 12:58
add a comment |
Update: i used the Check Validity tool to isolate the invalid geometries in a seperate layer, then used "explode lines" and then dissolved them by their unique identifier (luckily there was one in the attribute table). This reduced the number of invalid geometries to 54. If i repeat the process the number doesnt decrease anymore although the rest of the invalid geometries have the same issue
– a.urbanite
Feb 9 '17 at 18:16
I would recommend trying to use the MMQGIS plugin's "Delete Duplicate Geometries".
– JohnR
Feb 9 '17 at 20:42
wasnt that tool only for complete geometries like points/lines/polygons instead of vertices? anyway, i tried it but it didnt help.
– a.urbanite
Feb 10 '17 at 13:11
update: ok i tried the workflow described in my first update with another shapefile with the same problem.
– a.urbanite
Mar 3 '17 at 12:45
update2: ok i tried the workflow mentioned in my first update with another shapefile which has the same problem. workflow as follows: run "check validity"-tool, run "explode lines"-tool on invalid output, run "dissolve"-tool, run "Check validity"-tool ->no errors. if i now copy these valid geometries into the valid output of the validity check of the original shapefile and run the validity check again the errors are back! this has to be a bug or i am missing something about the specs of a shapefile...
– a.urbanite
Mar 3 '17 at 12:58
Update: i used the Check Validity tool to isolate the invalid geometries in a seperate layer, then used "explode lines" and then dissolved them by their unique identifier (luckily there was one in the attribute table). This reduced the number of invalid geometries to 54. If i repeat the process the number doesnt decrease anymore although the rest of the invalid geometries have the same issue
– a.urbanite
Feb 9 '17 at 18:16
Update: i used the Check Validity tool to isolate the invalid geometries in a seperate layer, then used "explode lines" and then dissolved them by their unique identifier (luckily there was one in the attribute table). This reduced the number of invalid geometries to 54. If i repeat the process the number doesnt decrease anymore although the rest of the invalid geometries have the same issue
– a.urbanite
Feb 9 '17 at 18:16
I would recommend trying to use the MMQGIS plugin's "Delete Duplicate Geometries".
– JohnR
Feb 9 '17 at 20:42
I would recommend trying to use the MMQGIS plugin's "Delete Duplicate Geometries".
– JohnR
Feb 9 '17 at 20:42
wasnt that tool only for complete geometries like points/lines/polygons instead of vertices? anyway, i tried it but it didnt help.
– a.urbanite
Feb 10 '17 at 13:11
wasnt that tool only for complete geometries like points/lines/polygons instead of vertices? anyway, i tried it but it didnt help.
– a.urbanite
Feb 10 '17 at 13:11
update: ok i tried the workflow described in my first update with another shapefile with the same problem.
– a.urbanite
Mar 3 '17 at 12:45
update: ok i tried the workflow described in my first update with another shapefile with the same problem.
– a.urbanite
Mar 3 '17 at 12:45
update2: ok i tried the workflow mentioned in my first update with another shapefile which has the same problem. workflow as follows: run "check validity"-tool, run "explode lines"-tool on invalid output, run "dissolve"-tool, run "Check validity"-tool ->no errors. if i now copy these valid geometries into the valid output of the validity check of the original shapefile and run the validity check again the errors are back! this has to be a bug or i am missing something about the specs of a shapefile...
– a.urbanite
Mar 3 '17 at 12:58
update2: ok i tried the workflow mentioned in my first update with another shapefile which has the same problem. workflow as follows: run "check validity"-tool, run "explode lines"-tool on invalid output, run "dissolve"-tool, run "Check validity"-tool ->no errors. if i now copy these valid geometries into the valid output of the validity check of the original shapefile and run the validity check again the errors are back! this has to be a bug or i am missing something about the specs of a shapefile...
– a.urbanite
Mar 3 '17 at 12:58
add a comment |
1 Answer
1
active
oldest
votes
Try to create new layer using function 'Buffer' from vector menu using 0 as parameter
answered Feb 10 '17 at 6:38
JendruskJendrusk
2,318414
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
used the "fixed distance buffer" tool from te vector menu. Distance put at 0 and segments per default at 5. The resulting vectorlayer has all entries in the attribute table but no visible geometries. makes sense to me because we are creating polygons without area. but when i run "polyons to lines" the resulting line-layer also has no visible geometries
– a.urbanite
Feb 10 '17 at 13:48
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',
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
});
}
});
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%2f227788%2fqgis-how-to-handle-circular-but-non-closed-lines%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try to create new layer using function 'Buffer' from vector menu using 0 as parameter
answered Feb 10 '17 at 6:38
JendruskJendrusk
2,318414
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
used the "fixed distance buffer" tool from te vector menu. Distance put at 0 and segments per default at 5. The resulting vectorlayer has all entries in the attribute table but no visible geometries. makes sense to me because we are creating polygons without area. but when i run "polyons to lines" the resulting line-layer also has no visible geometries
– a.urbanite
Feb 10 '17 at 13:48
add a comment |
Try to create new layer using function 'Buffer' from vector menu using 0 as parameter
answered Feb 10 '17 at 6:38
JendruskJendrusk
2,318414
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
used the "fixed distance buffer" tool from te vector menu. Distance put at 0 and segments per default at 5. The resulting vectorlayer has all entries in the attribute table but no visible geometries. makes sense to me because we are creating polygons without area. but when i run "polyons to lines" the resulting line-layer also has no visible geometries
– a.urbanite
Feb 10 '17 at 13:48
add a comment |
Try to create new layer using function 'Buffer' from vector menu using 0 as parameter
answered Feb 10 '17 at 6:38
JendruskJendrusk
2,318414
Try to create new layer using function 'Buffer' from vector menu using 0 as parameter
answered Feb 10 '17 at 6:38
JendruskJendrusk
2,318414
answered Feb 10 '17 at 6:38
JendruskJendrusk
2,318414
answered Feb 10 '17 at 6:38
JendruskJendrusk
2,318414
answered Feb 10 '17 at 6:38
JendruskJendrusk
2,318414
2,318414
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
used the "fixed distance buffer" tool from te vector menu. Distance put at 0 and segments per default at 5. The resulting vectorlayer has all entries in the attribute table but no visible geometries. makes sense to me because we are creating polygons without area. but when i run "polyons to lines" the resulting line-layer also has no visible geometries
– a.urbanite
Feb 10 '17 at 13:48
add a comment |
used the "fixed distance buffer" tool from te vector menu. Distance put at 0 and segments per default at 5. The resulting vectorlayer has all entries in the attribute table but no visible geometries. makes sense to me because we are creating polygons without area. but when i run "polyons to lines" the resulting line-layer also has no visible geometries
– a.urbanite
Feb 10 '17 at 13:48
used the "fixed distance buffer" tool from te vector menu. Distance put at 0 and segments per default at 5. The resulting vectorlayer has all entries in the attribute table but no visible geometries. makes sense to me because we are creating polygons without area. but when i run "polyons to lines" the resulting line-layer also has no visible geometries
– a.urbanite
Feb 10 '17 at 13:48
used the "fixed distance buffer" tool from te vector menu. Distance put at 0 and segments per default at 5. The resulting vectorlayer has all entries in the attribute table but no visible geometries. makes sense to me because we are creating polygons without area. but when i run "polyons to lines" the resulting line-layer also has no visible geometries
– a.urbanite
Feb 10 '17 at 13:48
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.
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%2f227788%2fqgis-how-to-handle-circular-but-non-closed-lines%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
Update: i used the Check Validity tool to isolate the invalid geometries in a seperate layer, then used "explode lines" and then dissolved them by their unique identifier (luckily there was one in the attribute table). This reduced the number of invalid geometries to 54. If i repeat the process the number doesnt decrease anymore although the rest of the invalid geometries have the same issue
– a.urbanite
Feb 9 '17 at 18:16
I would recommend trying to use the MMQGIS plugin's "Delete Duplicate Geometries".
– JohnR
Feb 9 '17 at 20:42
wasnt that tool only for complete geometries like points/lines/polygons instead of vertices? anyway, i tried it but it didnt help.
– a.urbanite
Feb 10 '17 at 13:11
update: ok i tried the workflow described in my first update with another shapefile with the same problem.
– a.urbanite
Mar 3 '17 at 12:45
update2: ok i tried the workflow mentioned in my first update with another shapefile which has the same problem. workflow as follows: run "check validity"-tool, run "explode lines"-tool on invalid output, run "dissolve"-tool, run "Check validity"-tool ->no errors. if i now copy these valid geometries into the valid output of the validity check of the original shapefile and run the validity check again the errors are back! this has to be a bug or i am missing something about the specs of a shapefile...
– a.urbanite
Mar 3 '17 at 12:58