- This topic has 1 reply, 2 voices, and was last updated 1 month ago by
Dan Damelin.
-
AuthorPosts
-
Lee Creighton
ParticipantAttached is a dataset I downloaded to test mapping in the new beta. There is a difference between the way version 2 and version draws their maps. You’ll want to import it.
I now know that there are three rows in the data set that have “NR” as their longitude and latitude values. In v2, when you instantiate a map, those points are ignored, and a nice map along the Mississippi River appears. These are black carp, and were indeed collected from there. In v3, the map draws the whole world, with the NR points drawn at (I think) (0,0) latitude and longitude.
This lead me to first highlight and exclude them, and use the Rescale button to redraw the map with just the Mississippi river points. But rescale doesn’t do anything with the excluded points, so I decided to delete the points and see what happens. (I filed a bug about the non-Rescaling; I hope it is one and that I’m not just complaining.)
So I select the points in the map with the selection tool, and I see them highlighted in the data table. I want to delete them, but the clicks aren’t captured in a way that I can. To show the menu that allows me to delete rows, I have to long-press on the left mouse; right clicks bring up Safari’s context menu. But after selecting points on the map, I have to do multiple clicks to get back to the table, which deselects the three errant points. That is, there’s no way to keep these three (non-contiguous) points highlighted in the table and delete them. Am I doing something wrong?
Eventually I manually zoomed and slid the map to get a nice window. Naturally I’m curious where the heavy carp are, so I drag weight onto the map, to be greeted by a *monster big* legend. Apparently, the import engine didn’t assign this attribute to be numeric, and the mapper didn’t translate the ‘none’ attribute to something continuous. I changed the attribute type to Numeric and tried using Rescale to redraw it, to no avail. And the legend is so large that the close window button is covered up.
Once I figured out I could undo all the steps I’d done to create the uncloseable map, all was fine, but I just wanted to make sure these were the choices that CODAP wanted to make for situations like this.s
Attachments:
December 18, 2025 at 5:56 pm #14300
Dan DamelinKeymasterIt does seem that v3 should ignore those lat/long points with the “nr” designation as is done in v2. If you have not reported this issue, then I would suggest adding it to the beta feedback.
Regarding your description of difficulties in selecting cases on the map and then deleting them using the table, I can’t reproduce your issues. I can select map cases, then click anywhere on the table that is not one of the table rows to make the table active, and then click on the delete icon to delete those cases. Then the rescale works.
I do agree that if you hide those cases in the map and click rescale, it should rescale properly and that is a bug.
As for the “weight” attribute being interpreted as text, that is because there are some cells with the value “nr” in them, which is text, and so CODAP interprets that column as being text, so it is doing the right/expected thing here. We should probably have a better way to handle when people create a map or graph legend that has too many categories in it though.
Thank you for reporting your experience.
-
AuthorPosts
- You must be logged in to reply to this topic.