- This topic has 5 replies, 2 voices, and was last updated 5 days ago by
.
-
Posts
-
I have been having trouble with a dataset where I have two different types of spatial data. I have census tracks with their boundaries and I have the GPS coordinates of dollar store, grocery stores, and liquor stores in a county. The stores are nested in the census tracks. We are using the workspace to explore food access issues in relations to SES and racial segregation factors. The problem we are having is graph attributes on both the census tracks and the stores nested within them at the same time on the map. For example is we place poverty rate for the census tracks and store type for the store locations on the map at the same time we only see when store type graphs rather than the three that are in the data. Another issue is the when we just add a census track attribute to the graph it also colors the store locations based on the census track variable making it hard to see the store locations. Does anyone else have experience working with such spatial data in CODAP? Perhaps we are trying to do something it doesn’t do yet?
There are some known bugs with having both boundaries and lat/long points on a graph. Can you provide a share link to your CODAP doc, so we can take a look and see the issues you are describing?
Here it is <span style=”font-size: 9pt; font-family: Montserrat, sans-serif; color: #1155cc; background-color: #eeeeee; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-alternates: normal; font-variant-position: normal; font-variant-emoji: normal; text-decoration-line: underline; text-decoration-skip-ink: none; vertical-align: baseline; white-space-collapse: preserve;”>https://codap.concord.org/app/static/dg/en/cert/index.html#shared=https%3A%2F%2Fcfm-shared.concord.org%2FXFSZJOVGRN8m70QskNWd%2Ffile.json</span>
Sorry bad copy here it it
Some of your issues are caused by the fact that you have multiple tables with boundaries and lat/longs, not just the one being shown on the canvas. If you click on the tables button in the toolbar and delete the other datasets, then the map will behave better. You have also found one of our bugs. If you have both boundaries and lat/long points in a dataset, then you must drop the attribute to color the boundaries first, and then the attribute to color the lat/long points. This is a bug on our side and we do plan to fix this. However, I don’t have a specific timeline for you on this.
Note, you can customize the colors by clicking on the layers tool in the map tool palette.
Attachments:
- You must be logged in to reply to this topic.