You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Kyle,
I've only recently started work on population synthesis for a transport model research project. I have a (n00b) question:
Is it possible to set constraints to different geographies for the primary seed table?
My use case is to ensure household counts are sensible at both regional and SA1 levels. However, I am not able to to have two geo_ columns in one target. I get the following error.
Error in check_geo_fields(primary_seed, tbl, name) :
target table 'hhtype' has more than one geo column (starts with 'geo_'
Since this seems to be design, could you please explain why two geographic constraints are disallowed? 👍
Any suggestions for working through this use case would be greatly appreciated. :-)
Thanks!
Shrividya
The text was updated successfully, but these errors were encountered:
Hi Kyle,
I've only recently started work on population synthesis for a transport model research project. I have a (n00b) question:
My use case is to ensure household counts are sensible at both regional and SA1 levels. However, I am not able to to have two
geo_
columns in one target. I get the following error.Since this seems to be design, could you please explain why two geographic constraints are disallowed? 👍
Any suggestions for working through this use case would be greatly appreciated. :-)
Thanks!
Shrividya
The text was updated successfully, but these errors were encountered: