How to convert several 'point' data to 'line' data?
I am using QGIS V3.4. I have over 1000 data points situated between a start and finish point expressing the Depth of coverage (DOC) of a pipeline. I need to identify the places along the pipeline which have a DOC lower than 0.6m to that which has coverage greater than 0.6m. the figure below identifies this, with grey data points identifying DOC greater than 0.6m and blue data points showing less than 0.6m.
it may look like a line (but a closer up image identifies its just multiple dots close together).
I have tried converting the point to line data by using the points to path tool
in the toolbox. This creates however a solid line from the start point to the finish point (as seen below) and doesn't include any other points within its attribute table. Additionally, it looks like it is plotted in a straight line rather than following the placement of the points.
I have also tried looking for the points2one
plugin, but this doesn't seem to exist on QGIS v3.4.
I need to be able to create this line but identify it as areas lower than 0.6 DOC and areas greater than DOC, highlighted with different colours. Does anyone know how to do this?
Possible suggestion have been to use the points to path
tool, however this creates issues as when I calculate it (knowing that it will arrange my data points from lowest to highest), I get as seen in the bottom figure, showing multiple lines.
I still haven't been able to solve my problem
qgis qgis-plugins point line convert
add a comment |
I am using QGIS V3.4. I have over 1000 data points situated between a start and finish point expressing the Depth of coverage (DOC) of a pipeline. I need to identify the places along the pipeline which have a DOC lower than 0.6m to that which has coverage greater than 0.6m. the figure below identifies this, with grey data points identifying DOC greater than 0.6m and blue data points showing less than 0.6m.
it may look like a line (but a closer up image identifies its just multiple dots close together).
I have tried converting the point to line data by using the points to path tool
in the toolbox. This creates however a solid line from the start point to the finish point (as seen below) and doesn't include any other points within its attribute table. Additionally, it looks like it is plotted in a straight line rather than following the placement of the points.
I have also tried looking for the points2one
plugin, but this doesn't seem to exist on QGIS v3.4.
I need to be able to create this line but identify it as areas lower than 0.6 DOC and areas greater than DOC, highlighted with different colours. Does anyone know how to do this?
Possible suggestion have been to use the points to path
tool, however this creates issues as when I calculate it (knowing that it will arrange my data points from lowest to highest), I get as seen in the bottom figure, showing multiple lines.
I still haven't been able to solve my problem
qgis qgis-plugins point line convert
add a comment |
I am using QGIS V3.4. I have over 1000 data points situated between a start and finish point expressing the Depth of coverage (DOC) of a pipeline. I need to identify the places along the pipeline which have a DOC lower than 0.6m to that which has coverage greater than 0.6m. the figure below identifies this, with grey data points identifying DOC greater than 0.6m and blue data points showing less than 0.6m.
it may look like a line (but a closer up image identifies its just multiple dots close together).
I have tried converting the point to line data by using the points to path tool
in the toolbox. This creates however a solid line from the start point to the finish point (as seen below) and doesn't include any other points within its attribute table. Additionally, it looks like it is plotted in a straight line rather than following the placement of the points.
I have also tried looking for the points2one
plugin, but this doesn't seem to exist on QGIS v3.4.
I need to be able to create this line but identify it as areas lower than 0.6 DOC and areas greater than DOC, highlighted with different colours. Does anyone know how to do this?
Possible suggestion have been to use the points to path
tool, however this creates issues as when I calculate it (knowing that it will arrange my data points from lowest to highest), I get as seen in the bottom figure, showing multiple lines.
I still haven't been able to solve my problem
qgis qgis-plugins point line convert
I am using QGIS V3.4. I have over 1000 data points situated between a start and finish point expressing the Depth of coverage (DOC) of a pipeline. I need to identify the places along the pipeline which have a DOC lower than 0.6m to that which has coverage greater than 0.6m. the figure below identifies this, with grey data points identifying DOC greater than 0.6m and blue data points showing less than 0.6m.
it may look like a line (but a closer up image identifies its just multiple dots close together).
I have tried converting the point to line data by using the points to path tool
in the toolbox. This creates however a solid line from the start point to the finish point (as seen below) and doesn't include any other points within its attribute table. Additionally, it looks like it is plotted in a straight line rather than following the placement of the points.
I have also tried looking for the points2one
plugin, but this doesn't seem to exist on QGIS v3.4.
I need to be able to create this line but identify it as areas lower than 0.6 DOC and areas greater than DOC, highlighted with different colours. Does anyone know how to do this?
Possible suggestion have been to use the points to path
tool, however this creates issues as when I calculate it (knowing that it will arrange my data points from lowest to highest), I get as seen in the bottom figure, showing multiple lines.
I still haven't been able to solve my problem
qgis qgis-plugins point line convert
qgis qgis-plugins point line convert
edited Jan 28 at 14:51
Bodhi
asked Jan 28 at 11:29
BodhiBodhi
17612
17612
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
in order to make Points to path tool works properly, you need to identify an order to the points so that the tool can follow the points based on the order you want:
Here is an example:
- Add field with integer type
- Add numbers based on the order you want from the start until the end
- Use point to path tool and order the line based on the field you created in the first step
Here is the output:
Would Converting points tom line(s) work in the same way?
– Bodhi
Jan 28 at 11:49
Points to path
tool easier to use. You need just to identify theOrder field
without considering theSeparation field
which is not clear to me what this field means.
– ahmadhanb
Jan 28 at 11:56
Ok so using points to path, following your instruction, an example would be to give all the points with a DOC <0.6m and id number e.g 1 - 600, then the remaining points with a DOC > 0.6 and id number 601 - 1000, and then run Points to line twice according to the id number?
– Bodhi
Jan 28 at 12:00
Yes, this is what I will try to do, and I hope you will get the desired results.
– ahmadhanb
Jan 28 at 12:05
add a comment |
I found the best way to solve this issue was to take the orginal excel sheet I was using and add two additional columns 1. Group & 2. Order. within the group column I indicated the length of data points used within the spread sheet e.g 1,2,3,4... 600. Within order I would paste 1 (indicating the start) for the whole column. Once completed, I would copy the data and paste it again at the end of the spread sheet. That way my 'group' column would repeat 1,2,3...600 again, but I would change my 'Order column' to consist of 2's (indicating the end of the string). After doing this I would sort the data by group and order (smallest to largest) resulting in my group and order column looking like the figure below. (KP indicates the distance points of the pipeline).
After creating the spreadsheet, I then added it as a delimited text file
to QGIS, which created multiple data points. using these data points I ran points to path
(situated in the processing toolbox
) this then created lines which were seperated between each point (shown below, red line highliting the break between each point).
The attribute table should like like the figure below.
The attribute table as it stands does not have the necessary fields and values to plot DOC, therefore it is necessary to join
the pipeline data poitns layer to the newely created line (path) layer. this is done by clicking on the 'Path/line layer' going to layer proprties
then joins
--> add vector join
. then join to the data points layer, with a join field and target field which is a column within the excell sheets which are common in both layers. e.g group
this then will add multiple fields to the new line/path attribute table.
Once created the data points layer can be unselected and using the Expression String Builder
rule-based symbology can be used to identify lengths of pipeline which are below DOC (0.60m) and length of pipeline which are above (0.60m).
The figure below indicates this. the red line shows DOC < 0.60M and the green line shows DOC > 0.60M
The final image indicates what the layer should look like in QGIS
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%2f310136%2fhow-to-convert-several-point-data-to-line-data%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
in order to make Points to path tool works properly, you need to identify an order to the points so that the tool can follow the points based on the order you want:
Here is an example:
- Add field with integer type
- Add numbers based on the order you want from the start until the end
- Use point to path tool and order the line based on the field you created in the first step
Here is the output:
Would Converting points tom line(s) work in the same way?
– Bodhi
Jan 28 at 11:49
Points to path
tool easier to use. You need just to identify theOrder field
without considering theSeparation field
which is not clear to me what this field means.
– ahmadhanb
Jan 28 at 11:56
Ok so using points to path, following your instruction, an example would be to give all the points with a DOC <0.6m and id number e.g 1 - 600, then the remaining points with a DOC > 0.6 and id number 601 - 1000, and then run Points to line twice according to the id number?
– Bodhi
Jan 28 at 12:00
Yes, this is what I will try to do, and I hope you will get the desired results.
– ahmadhanb
Jan 28 at 12:05
add a comment |
in order to make Points to path tool works properly, you need to identify an order to the points so that the tool can follow the points based on the order you want:
Here is an example:
- Add field with integer type
- Add numbers based on the order you want from the start until the end
- Use point to path tool and order the line based on the field you created in the first step
Here is the output:
Would Converting points tom line(s) work in the same way?
– Bodhi
Jan 28 at 11:49
Points to path
tool easier to use. You need just to identify theOrder field
without considering theSeparation field
which is not clear to me what this field means.
– ahmadhanb
Jan 28 at 11:56
Ok so using points to path, following your instruction, an example would be to give all the points with a DOC <0.6m and id number e.g 1 - 600, then the remaining points with a DOC > 0.6 and id number 601 - 1000, and then run Points to line twice according to the id number?
– Bodhi
Jan 28 at 12:00
Yes, this is what I will try to do, and I hope you will get the desired results.
– ahmadhanb
Jan 28 at 12:05
add a comment |
in order to make Points to path tool works properly, you need to identify an order to the points so that the tool can follow the points based on the order you want:
Here is an example:
- Add field with integer type
- Add numbers based on the order you want from the start until the end
- Use point to path tool and order the line based on the field you created in the first step
Here is the output:
in order to make Points to path tool works properly, you need to identify an order to the points so that the tool can follow the points based on the order you want:
Here is an example:
- Add field with integer type
- Add numbers based on the order you want from the start until the end
- Use point to path tool and order the line based on the field you created in the first step
Here is the output:
answered Jan 28 at 11:44
ahmadhanbahmadhanb
23.6k32154
23.6k32154
Would Converting points tom line(s) work in the same way?
– Bodhi
Jan 28 at 11:49
Points to path
tool easier to use. You need just to identify theOrder field
without considering theSeparation field
which is not clear to me what this field means.
– ahmadhanb
Jan 28 at 11:56
Ok so using points to path, following your instruction, an example would be to give all the points with a DOC <0.6m and id number e.g 1 - 600, then the remaining points with a DOC > 0.6 and id number 601 - 1000, and then run Points to line twice according to the id number?
– Bodhi
Jan 28 at 12:00
Yes, this is what I will try to do, and I hope you will get the desired results.
– ahmadhanb
Jan 28 at 12:05
add a comment |
Would Converting points tom line(s) work in the same way?
– Bodhi
Jan 28 at 11:49
Points to path
tool easier to use. You need just to identify theOrder field
without considering theSeparation field
which is not clear to me what this field means.
– ahmadhanb
Jan 28 at 11:56
Ok so using points to path, following your instruction, an example would be to give all the points with a DOC <0.6m and id number e.g 1 - 600, then the remaining points with a DOC > 0.6 and id number 601 - 1000, and then run Points to line twice according to the id number?
– Bodhi
Jan 28 at 12:00
Yes, this is what I will try to do, and I hope you will get the desired results.
– ahmadhanb
Jan 28 at 12:05
Would Converting points tom line(s) work in the same way?
– Bodhi
Jan 28 at 11:49
Would Converting points tom line(s) work in the same way?
– Bodhi
Jan 28 at 11:49
Points to path
tool easier to use. You need just to identify the Order field
without considering the Separation field
which is not clear to me what this field means.– ahmadhanb
Jan 28 at 11:56
Points to path
tool easier to use. You need just to identify the Order field
without considering the Separation field
which is not clear to me what this field means.– ahmadhanb
Jan 28 at 11:56
Ok so using points to path, following your instruction, an example would be to give all the points with a DOC <0.6m and id number e.g 1 - 600, then the remaining points with a DOC > 0.6 and id number 601 - 1000, and then run Points to line twice according to the id number?
– Bodhi
Jan 28 at 12:00
Ok so using points to path, following your instruction, an example would be to give all the points with a DOC <0.6m and id number e.g 1 - 600, then the remaining points with a DOC > 0.6 and id number 601 - 1000, and then run Points to line twice according to the id number?
– Bodhi
Jan 28 at 12:00
Yes, this is what I will try to do, and I hope you will get the desired results.
– ahmadhanb
Jan 28 at 12:05
Yes, this is what I will try to do, and I hope you will get the desired results.
– ahmadhanb
Jan 28 at 12:05
add a comment |
I found the best way to solve this issue was to take the orginal excel sheet I was using and add two additional columns 1. Group & 2. Order. within the group column I indicated the length of data points used within the spread sheet e.g 1,2,3,4... 600. Within order I would paste 1 (indicating the start) for the whole column. Once completed, I would copy the data and paste it again at the end of the spread sheet. That way my 'group' column would repeat 1,2,3...600 again, but I would change my 'Order column' to consist of 2's (indicating the end of the string). After doing this I would sort the data by group and order (smallest to largest) resulting in my group and order column looking like the figure below. (KP indicates the distance points of the pipeline).
After creating the spreadsheet, I then added it as a delimited text file
to QGIS, which created multiple data points. using these data points I ran points to path
(situated in the processing toolbox
) this then created lines which were seperated between each point (shown below, red line highliting the break between each point).
The attribute table should like like the figure below.
The attribute table as it stands does not have the necessary fields and values to plot DOC, therefore it is necessary to join
the pipeline data poitns layer to the newely created line (path) layer. this is done by clicking on the 'Path/line layer' going to layer proprties
then joins
--> add vector join
. then join to the data points layer, with a join field and target field which is a column within the excell sheets which are common in both layers. e.g group
this then will add multiple fields to the new line/path attribute table.
Once created the data points layer can be unselected and using the Expression String Builder
rule-based symbology can be used to identify lengths of pipeline which are below DOC (0.60m) and length of pipeline which are above (0.60m).
The figure below indicates this. the red line shows DOC < 0.60M and the green line shows DOC > 0.60M
The final image indicates what the layer should look like in QGIS
add a comment |
I found the best way to solve this issue was to take the orginal excel sheet I was using and add two additional columns 1. Group & 2. Order. within the group column I indicated the length of data points used within the spread sheet e.g 1,2,3,4... 600. Within order I would paste 1 (indicating the start) for the whole column. Once completed, I would copy the data and paste it again at the end of the spread sheet. That way my 'group' column would repeat 1,2,3...600 again, but I would change my 'Order column' to consist of 2's (indicating the end of the string). After doing this I would sort the data by group and order (smallest to largest) resulting in my group and order column looking like the figure below. (KP indicates the distance points of the pipeline).
After creating the spreadsheet, I then added it as a delimited text file
to QGIS, which created multiple data points. using these data points I ran points to path
(situated in the processing toolbox
) this then created lines which were seperated between each point (shown below, red line highliting the break between each point).
The attribute table should like like the figure below.
The attribute table as it stands does not have the necessary fields and values to plot DOC, therefore it is necessary to join
the pipeline data poitns layer to the newely created line (path) layer. this is done by clicking on the 'Path/line layer' going to layer proprties
then joins
--> add vector join
. then join to the data points layer, with a join field and target field which is a column within the excell sheets which are common in both layers. e.g group
this then will add multiple fields to the new line/path attribute table.
Once created the data points layer can be unselected and using the Expression String Builder
rule-based symbology can be used to identify lengths of pipeline which are below DOC (0.60m) and length of pipeline which are above (0.60m).
The figure below indicates this. the red line shows DOC < 0.60M and the green line shows DOC > 0.60M
The final image indicates what the layer should look like in QGIS
add a comment |
I found the best way to solve this issue was to take the orginal excel sheet I was using and add two additional columns 1. Group & 2. Order. within the group column I indicated the length of data points used within the spread sheet e.g 1,2,3,4... 600. Within order I would paste 1 (indicating the start) for the whole column. Once completed, I would copy the data and paste it again at the end of the spread sheet. That way my 'group' column would repeat 1,2,3...600 again, but I would change my 'Order column' to consist of 2's (indicating the end of the string). After doing this I would sort the data by group and order (smallest to largest) resulting in my group and order column looking like the figure below. (KP indicates the distance points of the pipeline).
After creating the spreadsheet, I then added it as a delimited text file
to QGIS, which created multiple data points. using these data points I ran points to path
(situated in the processing toolbox
) this then created lines which were seperated between each point (shown below, red line highliting the break between each point).
The attribute table should like like the figure below.
The attribute table as it stands does not have the necessary fields and values to plot DOC, therefore it is necessary to join
the pipeline data poitns layer to the newely created line (path) layer. this is done by clicking on the 'Path/line layer' going to layer proprties
then joins
--> add vector join
. then join to the data points layer, with a join field and target field which is a column within the excell sheets which are common in both layers. e.g group
this then will add multiple fields to the new line/path attribute table.
Once created the data points layer can be unselected and using the Expression String Builder
rule-based symbology can be used to identify lengths of pipeline which are below DOC (0.60m) and length of pipeline which are above (0.60m).
The figure below indicates this. the red line shows DOC < 0.60M and the green line shows DOC > 0.60M
The final image indicates what the layer should look like in QGIS
I found the best way to solve this issue was to take the orginal excel sheet I was using and add two additional columns 1. Group & 2. Order. within the group column I indicated the length of data points used within the spread sheet e.g 1,2,3,4... 600. Within order I would paste 1 (indicating the start) for the whole column. Once completed, I would copy the data and paste it again at the end of the spread sheet. That way my 'group' column would repeat 1,2,3...600 again, but I would change my 'Order column' to consist of 2's (indicating the end of the string). After doing this I would sort the data by group and order (smallest to largest) resulting in my group and order column looking like the figure below. (KP indicates the distance points of the pipeline).
After creating the spreadsheet, I then added it as a delimited text file
to QGIS, which created multiple data points. using these data points I ran points to path
(situated in the processing toolbox
) this then created lines which were seperated between each point (shown below, red line highliting the break between each point).
The attribute table should like like the figure below.
The attribute table as it stands does not have the necessary fields and values to plot DOC, therefore it is necessary to join
the pipeline data poitns layer to the newely created line (path) layer. this is done by clicking on the 'Path/line layer' going to layer proprties
then joins
--> add vector join
. then join to the data points layer, with a join field and target field which is a column within the excell sheets which are common in both layers. e.g group
this then will add multiple fields to the new line/path attribute table.
Once created the data points layer can be unselected and using the Expression String Builder
rule-based symbology can be used to identify lengths of pipeline which are below DOC (0.60m) and length of pipeline which are above (0.60m).
The figure below indicates this. the red line shows DOC < 0.60M and the green line shows DOC > 0.60M
The final image indicates what the layer should look like in QGIS
answered Feb 1 at 10:39
BodhiBodhi
17612
17612
add a comment |
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%2f310136%2fhow-to-convert-several-point-data-to-line-data%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