Here's one suggestion. Use a Bufferer to set a 100 m buffer around streets, grouped on street names. The buffers get the street name. <redundant>Then use a Dissolver to make one big buffer around each street, by grouping on street name. (Send the streets both through the Bufferer and past it, to keep both.)</redundant> Then put a Counter on the buffers to get a unique combination of street name and buffer count. Finally use a LineOnAreaOverlayer to match the streets to their buffer and make them inherit the buffer's count attribute. Now you should have street features with a unique combination of street name and count number. This should work for a scenario where you don't want to aggregate or join the lines, but just want to give them a unique, searchable attribute.
(Edit: Marked the redundant part of my suggestion, but kept it in there to make the following answers and comments understandable.)
Thank you very much for your suggestion! I really appreciate you help.
I did almost everything as you suggested and I'm now analyzing the results (trying to confirm that the suggested logic can be applied to my data).
One thing I didn't understand is this step: "Then use a Dissolver to make one big buffer around each street, by grouping on street name. (Send the streets both through the Bufferer and past it, to keep both.)"
I didn't understand why I need dissolver because bufferer already dissolves buffers by street names - If I understood the help manual. And the instruction in parentheses I didn't understand - it seems unnecessary but I would like to discuss because maybe I didn't fully understand something.
So, I did it like this:
- I used bufferer to create 100m buffer polygon around all streets with Group by parameter on street name >>> as a result, all buffers that overlaps and have the same street name are dissolved into one buffer (am I right?)
- I added a counter to produce unique identifier for the each buffer
- I used the LineOnAreaOverlayer to intersect streets and buffers so that each street gets the buffer ID
- I selected streets which belong to the same buffer, i.e. have the same buffer ID and have the same name.
I can not find a flaw in this 4 steps, but maybe I'm missing something and should also include those extra steps you suggested (dissolver and parentheses...)
Thank you very much for your suggestion! I really appreciate you help.
I did almost everything as you suggested and I'm now analyzing the results (trying to confirm that the suggested logic can be applied to my data).
One thing I didn't understand is this step: "Then use a Dissolver to make one big buffer around each street, by grouping on street name. (Send the streets both through the Bufferer and past it, to keep both.)"
I didn't understand why I need dissolver because bufferer already dissolves buffers by street names - If I understood the help manual. And the instruction in parentheses I didn't understand - it seems unnecessary but I would like to discuss because maybe I didn't fully understand something.
So, I did it like this:
- I used bufferer to create 100m buffer polygon around all streets with Group by parameter on street name >>> as a result, all buffers that overlaps and have the same street name are dissolved into one buffer (am I right?)
- I added a counter to produce unique identifier for the each buffer
- I used the LineOnAreaOverlayer to intersect streets and buffers so that each street gets the buffer ID
- I selected streets which belong to the same buffer, i.e. have the same buffer ID and have the same name.
I can not find a flaw in this 4 steps, but maybe I'm missing something and should also include those extra steps you suggested (dissolver and parentheses...)
You're right. My suggestions were from the top of my head, so a slight redundancy crept in there.
Your four steps should do the trick. Have you reached your wanted result?
You're right. My suggestions were from the top of my head, so a slight redundancy crept in there.
Your four steps should do the trick. Have you reached your wanted result?
Yes, I believe so. With my test data with only 10 streets it works great but I have more than 100000 streets so I wasn't sure if I have missed something important in your suggestions which doesn't affect the results of my test data but could give false results in my real data (some special cases which haven't come to my mind while preparing my test data).
So, once again, thank you very much!
M