Scatterplot axis labels do not match data

[timstallmann]

#Hi -- I'm seeing this issue across several different datasets and across different views in the software, (v 1.8.14 on Mac OS X El Capitan). Scatter plot axis labels do not correspond to the actual data values in those positions. See example below, where the variable range is 0 to 1 but axis labels make it appear that the range is -0.7 to 2.3

[lixun910]

@timstallmann Thanks for reporting this! The figure you posted is Moran's I scatter plot, which the variable on x-axis are standardized so that the units in the graph correspond to standard deviation.

Do you have the same issue in regular scatter plot?

[timstallmann]

@lixun910 that makes sense! Would it be possible to add a label to the axes indicating they were standardized? For example VARIABLE_NAME (std. deviation) as the default axis label rather than just VARIABLE_NAME?

I have had this issue on other scatterplots, but perhaps I'm misunderstanding how the output should look. Here's a screenshot of a test case on a standard scatterplot. The highlighted point should have y-value 0.51 (third column from the right, since I accidentally cut off the table headers in the screenshot), but according to the plot axes it has a value below 0.5.

[lixun910]

@timstallmann Thank you! The regular scatter plots should use raw data unless you select "data->View standardized data" from the right-click popup menu. The screenshot you posted looks like not a completed one. Can you do another screenshot by hovering the mouse on the point you try to highlight, so that on the status bar, you can see the (x,y) value of the selected point. For example:

[lixun910]

@jkoschinsky as @timstallmann suggested, in moran scatterplot, "Would it be possible to add a label to the axes indicating they were standardized? For example VARIABLE_NAME (std. deviation) as the default axis label rather than just VARIABLE_NAME?"

[timstallmann]

@lixun910 sure thing - here's a screenshot. I can't get the cursor to appear, but I'm hovering over the selected point.

[lixun910]

@timstallmann Thanks! Will check on this issue soon, and keep you updated.

[lixun910]

@timstallmann I just checked on my side including the code, and can't replicate what you had. One more thing, can you check if the right click popup menu has "Data->View Original Data" checked?
For helping us troubleshooting this issue, is it possible to share your data with us privately? you can send it to [email protected] and we will delete it after troubleshooting. Thanks!

[timstallmann]

@lixun910 confirmed that that View Original Data is checked. And I know how frustrating it can be to try and duplicate an issue locally!!

This is all public data, so just posting the shapefile here. Here are the steps I followed:

• Open GeoDa
• Open the shapefile
• Click the "Scatterplot" button on the toolbar
• Select independent variable Pct_NHWht and dependent variable pct_trump

votes_by_county.zip

[lixun910]

@timstallmann Thanks for sharing! I actually figured out what was wrong in GeoDa using your data: the ticks on the vertical/horiz axis are (by default) set to with 1 display precision. The 0.5 tick on the y axis should be 0.54 (see this figure).

In our next release, GeoDa will set the default display precision=2, and also allows user to adjust this number. I could give you an internal build soon this week, and the official release will be out in this month. Let me know if you want to try it out. Thanks again for reporting this and helping solve this issue!

[timstallmann]

Wow — thanks for tracking this down!! I’m happy to wait for the next
official update now that I know what’s going on…

On November 14, 2016 at 1:41:06 PM, Xun Li ([email protected]) wrote:

@timstallmann https://github.com/timstallmann Thanks for sharing! I
actually figured out what was wrong in GeoDa using your data: the ticks on
the vertical/horiz axis are (by default) set to with 1 display precision.
The 0.5 tick on the y axis should be 0.54 (see this figure).
[image: screen shot 2016-11-14 at 12 33 10 pm]
https://cloud.githubusercontent.com/assets/2423887/20277749/79aa3854-aa67-11e6-8194-4e33393f9a1e.png
In our next release, GeoDa will set the default display precision=2, and
also allows user to adjust this number. I could give you an internal build
soon this week, and the official release will be out in this month. Let me
know if you want to try it out. Thanks again for reporting this and helping
solve this issue!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#524 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGbfsgYSVfmXaPGK143DWj3_YyuNERUgks5q-KtBgaJpZM4Kv9Re
.

[jkoschinsky]

GeoDa 1.8.15.5 — Mac OSX
Confirmed fix.