Skip to content
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

averages chart save dummy needs both space and time ID #408

Closed
lanselin opened this issue Apr 27, 2016 · 1 comment
Closed

averages chart save dummy needs both space and time ID #408

lanselin opened this issue Apr 27, 2016 · 1 comment

Comments

@lanselin
Copy link
Collaborator

currently, a file created with the save dummy button in the averages chart writes out a STID (space time id), a space id (e.g. FIPSNO) and a SPACE and (if appropriate) TIME and INTERACT dummy before the variable with the values; however, there is no time ID.
for example, selecting 1031 counties from natregimes and looking at HR in 60 for selected and unselected gives the following header:

STID,FIPSNO,SPACE,HR
1,27077,0, 0.000000000
2,53019,0, 0.000000000
3,53065,0, 1.863863416

there is no way to figure out what time period the HR pertains to

same for selected in two time periods:

STID,FIPSNO,TIME,SPACE,INTERACT,HR
1,18083,0,1,0, 3.208135833
2,29189,0,1,0, 1.895199271
3,51165,0,1,0, 4.116751060

i suggest STID,SPACEID,TIMEID,TIME,SPACE,INTERACT,VARIABLE
for example:
STID,FIPSNO,PERIOD,TIME,SPACE,INTERACT,HR
(note that the time id will need to be extracted from the time editor

the reason we need a TIME ID in addition to the space ID (and the STID) is for
compatibility with regression programs for panel data.

lixun910 referenced this issue in lixun910/geoda May 2, 2016
averages chart save dummy needs both space and time ID #408
@lixun910 lixun910 mentioned this issue May 2, 2016
@lixun910 lixun910 added this to the 1.8 milestone May 2, 2016
@lixun910 lixun910 self-assigned this May 2, 2016
@jkoschinsky
Copy link
Collaborator

Verified in GeoDa 1.8.6 (OSX Yosemite, 10.10.5 and Win 7 Professional (64-bit)).

screen shot 2016-05-18 at 6 40 56 pm

Note that you need to first specify the spatial variable in the weights creation dialogue before it is saved in the dummy file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants