Re: [Qgis-user] Merge does work (at least not as I expect)
The layer being multilinestring just mean that you can create features with multi geometries in it. It says nothing about the actual features in it. A quarta, 2/10/2019, 17:04, escreveu: > On 10/2/2019 9:41 AM, Alexandre Neto wrote: > > Hi, > > Using your layer directly into merge lines algorithm worked properly on > QGIS 3.4 in Linux. That is, in the end, I got one single feature that is no > longer multi. (if I try to go multipart to single part I can't get the > individual segments). > > When I merge on the layer, I get a new layer that still reports as > multi-linestring > > > > However, it is internally different since now when I export as a gpx file, > it is a single segment, which was the goal. Curious that it still reports > the type as MultiLineString. > > > Hope it helps, > > Indeed, it solves the problem > ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Merge does work (at least not as I expect)
On 10/2/2019 9:41 AM, Alexandre Neto wrote: Hi, Using your layer directly into merge lines algorithm worked properly on QGIS 3.4 in Linux. That is, in the end, I got one single feature that is no longer multi. (if I try to go multipart to single part I can't get the individual segments). When I merge on the layer, I get a new layer that still reports as multi-linestring However, it is internally different since now when I export as a gpx file, it is a single segment, which was the goal. Curious that it still reports the type as MultiLineString. Hope it helps, Indeed, it solves the problem ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Merge does work (at least not as I expect)
Hi, Using your layer directly into merge lines algorithm worked properly on QGIS 3.4 in Linux. That is, in the end, I got one single feature that is no longer multi. (if I try to go multipart to single part I can't get the individual segments). What does not work (but it's intended) is if you have a layer full of single segments that connect to each other and try to merge them together using "merge lines". In that case, I needed to dissolve all layers first, and then use the merge line tool. Hope it helps, Alexandre Neto On Wed, Oct 2, 2019 at 4:18 PM wrote: > On 10/2/2019 12:33 AM, Alexandre Neto wrote: > > Hi, > > > > Can you provide a sample of your data? > > > > What version of QGIS are you using? What OS? > QGIS 3.4.2 on Windows 7 Pro, 64 bit > Full dataset is attached. > > ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Merge does work (at least not as I expect)
On 10/2/2019 12:33 AM, Alexandre Neto wrote: > Hi, > > Can you provide a sample of your data? > > What version of QGIS are you using? What OS? QGIS 3.4.2 on Windows 7 Pro, 64 bit Full dataset is attached. <> ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Merge does work (at least not as I expect)
Hi, Can you provide a sample of your data? What version of QGIS are you using? What OS? Alexandre Neto A quarta, 2/10/2019, 05:03, escreveu: > Nyall wrote: > > I suspect the lines aren't **exactly** coincident. I'd try: > > - multiparts to single parts > - snap geometries to layer, to snap the end points exactly to each other > - retry merge > > > I tried this, no joy. still getting multi-linestring with 2055 segments. > So here's what I tried next - > multiparts to singlepart > export to csv, saving geometry as wkt. > verify that endpoints match *exactly* to the precision written to the file > Import csv as layer > merge > > again, no luck > > I looked at the attribute table and the lines were in some random order- > adjacent segments were not consecutive rows in the attribute table. Then I > noticed that every row had the same FID. > I closed the layer, opened the .csv in excel, verified that the rows > represented consecutive points, then assigned consecutive FIDs. > imported csv as layer > merge > > again, no luck. Still have 2055 rows in the attribute table of the merged > layer, in that same seemingly random order as before. > > A purely brute force solution was to export as csv, as above, then edit > the file by removing the endpoint of each segment, and concatenate them > into a single linestring with 2055 points. > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Merge does work (at least not as I expect)
Nyall wrote: I suspect the lines aren't **exactly** coincident. I'd try: - multiparts to single parts - snap geometries to layer, to snap the end points exactly to each other - retry merge I tried this, no joy. still getting multi-linestring with 2055 segments. So here's what I tried next - multiparts to singlepart export to csv, saving geometry as wkt. verify that endpoints match exactly to the precision written to the file Import csv as layer merge again, no luck I looked at the attribute table and the lines were in some random order- adjacent segments were not consecutive rows in the attribute table. Then I noticed that every row had the same FID. I closed the layer, opened the .csv in excel, verified that the rows represented consecutive points, then assigned consecutive FIDs. imported csv as layer merge again, no luck. Still have 2055 rows in the attribute table of the merged layer, in that same seemingly random order as before. A purely brute force solution was to export as csv, as above, then edit the file by removing the endpoint of each segment, and concatenate them into a single linestring with 2055 points. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Merge does work (at least not as I expect)
On Tue, 1 Oct 2019 at 09:26, wrote: > > On 9/30/2019 1:21 PM, Bo Victor Thomsen wrote: > > Does the new multi-linestring contains the same number of seqment > > (~2000) as the original multi-linestring. > > > > Or has it fewer (but "larger") segments ? I suspect the lines aren't **exactly** coincident. I'd try: - multiparts to single parts - snap geometries to layer, to snap the end points exactly to each other - retry merge Nyall > > Same number > > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] Merge does work (at least not as I expect)
On 9/30/2019 1:21 PM, Bo Victor Thomsen wrote: > Does the new multi-linestring contains the same number of seqment > (~2000) as the original multi-linestring. > > Or has it fewer (but "larger") segments ? Same number ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Merge does work (at least not as I expect)
Does the new multi-linestring contains the same number of seqment (~2000) as the original multi-linestring. Or has it fewer (but "larger") segments ? -- Med venlig hilsen / Kind regards Bo Victor Thomsen Den 30-09-2019 kl. 19:01 skrev qgis-u...@stripfamily.net: I have a layer with a single multi-linestring, containing ~2000 segments. I have verified (by exporting as CSV with geometry as wkt) that the endpoint of each segment is coincident with the start point of the next to the nine decimal places shown in the wkt. I run Processing-->Vector Geometry-> Merge lines and the output is a new layer containing a single multilinesegment equal to the original. Seems like all segments should have been merged into a single linestring. Any thoughts as to what's going on? Thx ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] Merge does work (at least not as I expect)
I have a layer with a single multi-linestring, containing ~2000 segments. I have verified (by exporting as CSV with geometry as wkt) that the endpoint of each segment is coincident with the start point of the next to the nine decimal places shown in the wkt. I run Processing-->Vector Geometry-> Merge lines and the output is a new layer containing a single multilinesegment equal to the original. Seems like all segments should have been merged into a single linestring. Any thoughts as to what's going on? Thx ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
