-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GEOGRID vs GEOGRIDATA #34
Comments
It is redundant, but it gives you the option of querying |
Yes, as @crisjf mentioned the GEOGRID is state "0" of this table (i.e taboola rasa). Later states are GEOGRIDDATA |
OK And is it necessary to store state 0 properties in GEOGRID? I mean in term of storing size (there was a time we were arguing wether we should use int or float to save space;-) ) Also Instead of writing issue for this kind of question is there an entry point for the meta structure of this json so I can look at it before to post an issue? |
It's not about storing state 0. GEOGRID is the baseline data for both geometry and meta for each grid cell. This is how we initiate a table with all its data in one place (vs the multi fields we used to have). |
So as we think about the Handler agent in GAMA, the |
I think we can close this, right? |
Closing for now, @agrignard open at will. |
In this table https://cityio.media.mit.edu/api/table/dungeonmaster/
Inside GEOGRID each block has this properties
and inside GEOGRIDDATA each block has this properties
Do we need to repeat the information in both field? Isn't it redundant? Also the color value are different
The text was updated successfully, but these errors were encountered: