I have a similar question to this one: "snapping" polygons together
I have drawn let's say 3 areas. The 1. is overlapping with the 2. and the 2. is overlapping with the 3.
I made sure that I was using the snapping tool and the outer lines are matching each other. That is all fine. But now I want them to be just one feature. So I marked the 3 features and hit "Merge Selected Features". It seemed to work, but there is still the line between them.
Then I gave "Dissolve" a try but it had the same result.
So I played around but did not find any way to handle that. What I more would like to have would be that I can join points. IS there maybe something like merge points? Any ideas are welcome.
Here a picture with the vertical unwanted line: http://imgur.com/mFkNzev
Overally merging features is working. But there is a big issue when one features has issues.
All you need to do is checking the to be merged features. Solve any issue like multiple points or intersections. Now try merging them again and it should work. At least for myself it did.
Another issue could be QGIS. Here it helps a simple restart of QGIS.
Related
I have a line chart that builds by a combination of several data. But the curve draws some strange straight lines on some areas.
How can i delete this line?
The problem is i think not related to the data because icannot touch with cursor to this straight line. I think curve automatically draws something like regression line, but icouldn't remove it.
Thank you.
Another example
if i chose dot data as true, you can see that there is no data point on these straight lines.
I solved my problem. For those who has the same issue, the data of the curve should be sorted. If your data is map, just turn the map to sorted with collection package with the following code;
data = SplayTreeMap();
That's it.
I've been trying to force a trendline through 0,0 for my scatter graph, but I can't seem to find a way to do this.
From the docs here, they don't give any information on it: https://developers.google.com/chart/interactive/docs/gallery/trendlines
But, I know there are lots of undocumented stuff in charts.
This is an example of what i am trying to do within Google charts(Done within excel)
The red dotted liner is the trendline, on the left is the default liniear regression that Google charts can give, but in many situations you would want to force a Y-intercept, in this example its forced to be at 0
No, you should NOT need values to force an intercept. This is a pretty standard option in graphing programs. Unfortunately, I don't see where Google Sheets gives you the option, which is one reason I don't recommend it for serious data analysis.
It's odd that the LINEST function allows you to force a zero Y-Intercept, but the trend-line tool in the Chart Editor does not. Excel offers a checkbox to force the line through the origin. (Of course, one should exercise caution when doing so. You really have to know something about the data your analyzing.)
I'm displaying a map that's been tiled (-p raster) using gdal2tiles.py. The X-coordinate is about [0..-1160]. The Y-coordinate, for some reason, is [-700,0]. Zoom-levels 0-5.
I simply cannot get a plausible display to work. Sometimes, if I zoom-out to level-zero, I see the map way down at the bottom of the display ... not centered. Nothing at all appears at other levels.
I am also seeing the display "bounce back and forth" between about a 3-o'clock and a 6-o'clock position. (Only, once again, at zoom-level zero.)
I am at my wit's end. Please give guidance. Complete examples. Anything ...
Well, I found my answer:
If you're going to be using several layers in your Leaflet map, add them in the constructor-call, using the layers parameter.
If you try to do things with the layers before joining them all together, or with the map with no layers added, "strange and default things will happen." (For example, although I requested the Simple CRS when constructing things (separately...), the net-effect was to actually try to use a different one. Therefore, "do what the author expected." Specify all the layers at once, to the Map constructor. Then, customize them as you need to. Make very sure that they all know about each other from the very start of things.
I have a group of polygons which I merged to create one large polygon using the editor toolbar. This worked fine but there are still 5 or 6 lines contained within the large polygon. I'm assuming these are contained within the polygon because when I select the polygon the lines are selected too - how can I get rid of these 'rogue' lines, if I merged the polygons how come I have lines now? Any help appreciated!
My guess is that your polygons don't have correct topology, I mean the sharing border is not exactly the same. There is very likely a tiny gap and when you merge your polygons, you see those tiny gaps as line (try zoom to very detail). If this was problem, solution is obvious - you should correct topology of your polygon before merge - you can use topology class with no gaps rule.
You can manually remove the lines by:
1) Enter an edit session
2) Selecting the feature
3) Select the "Edit Vertices" tool from the editor toolbar
4) Find the vertices of the rogue lines, select them, and delete them
5) End edit session and save edits
ESRI resource:
http://resources.arcgis.com/en/help/main/10.1/index.html#//01m80000003p000000
So I have 3 lines (technically patches) that have some transparency enabled. These lines were generated by the patchline FEX submission. The FEX entry works great by making patches seem like lines by adding a NaN to the end of the data so it doesn't create a big black patch between the end points of my line.
My lines looks like this
__ __
\ /
_ \ / _
\ \__/ /
\______/
The patch extends from the left end point to the right end point in a straight line across the top and then follows the line on the bottom. The actual patch is hidden (not drawn) though so all the user sees is the lines
The problem is if I wanted to click the bottom hump of the top line, it acts like I clicked the bottom line because it is part of that patch.
I have thought of a couple of workarounds and was hoping you guys could point out flaws or add ideas I might have missed with my workarounds.
Workaround #1
Ideally, I would create an actual line (line series obj.) over the transparent lines. I would turn hittest off on the patches and I would make the actual line invisible, but turn hittest on. The problem I am 99% sure exists is that if visibilty is off, you can't click the object. If anybody has a work around to that issue (documented or otherwise), that would be great.
Workaround #2
Turn the patchline hittest property to off. Make mock line objs. that follow the patchline coords. and have a line width very very small so as to make the line ideally pretty much invisible and have hit test clicks point to these lines instead. Has anybody tried something like this before? (I'm at work and can't try it now)
Workaround #3
NOTE THAT I REALLY DONT WANT TO DO THIS It is of course possible to turn off hittest for the patch/line objs and use the axes buttondown to figure out what patch obj (just the line part) it was closest to.
Once again, any insight would be much appreciated either about my possible work arounds, the situation in general, etc.
Thanks, Shaun
The problem can be illustrated with two line-thick patches, one of which is NOT parallel to the axes:
patch([2 8 8],[5 10 10],'w','EdgeColor','b','EdgeAlpha',0.4,'LineWidth',3)
patch([2 8 8],[4 4 4],'w','EdgeColor','r','EdgeAlpha',0.4,'LineWidth',3)
xlim([0 10])
ylim([3 11])
You cannot select but those lines which are parallel to one of the axes.
Workaround #1: impossible.
Workaround #2: quite visible, why would you need transparent lines then?
Workaround #3: the only way...
Workaround alternative: submit to the TMW a technical request to improve clickability of patches.
Oleg, your initial post somehow inspired me to come up with my elegant solution. (Don't ask me how, just accept my "thank you" haha)
The elegant solution to my problem required me to go beyond patch properties and turn to the axes child order. Under the assumption that none of the lines would intersect each other, I was able to plot them in a order where the bottom one was first, then the second lowest, etc. until I got to the top (effectively rearranging child order).
If anybody else stumbles upon this, what you can do (assuming your lines don't intersect) is to sort the first Y (or whatever values) to go from lowest to highest (in this case) in your plot, and make sure your sort function returns the indicies.
I don't have my computer in front of me, but what you end up doing is effectively making an acontinuous for loop, looping through the indicies.
something like:
for i=[6 2 5 4 1 3]
plot(X(:,i),Y(:,i))
end
Where the 6th column was my lowest data, 2nd column was second lowest on plot, etc.