misaligned lookup table values?

[udst]

misaligned lookup table values?

[mkreilly]

also the TR (in my codes) has been named AP. Not sure if that convention happened elsewhere.

[janowicz]

Good catch, Mike. Thanks for the correction, will update. I was trying to
follow the coding here, but must have made typos:
https://github.com/MetropolitanTransportationCommission/rtp-2017-urbansim-inputs/blob/master/bldgtypes.csv

On Tue, May 26, 2015 at 3:42 PM, Michael Reilly [email protected]
wrote:

@janowicz https://github.com/janowicz: So, I think I may be getting an
idea of devtypes and devids and where they all get set up in spandex. And I
think I found "the problem" at:

https://github.com/synthicity/bayarea_urbansim/blob/master/data_regeneration/match_aggregate.py#L780-L781

The crosswalk coding here deviates from the codes I set up. I think this
wrong unless it’s been done consistently this other way somewhere else. But
Fletcher did mention seeing a lot of transport parcels (which I think are
supposed to be vacant ones). So the correct look up to match the codes I
specified is (others look right):
VA 21
PG 22
PL 23
TR 24
LD 25

I'm a little scared of trying to change anything bc spandex still confuses
me a bit. Thanks!

—
Reply to this email directly or view it on GitHub
#42.

[mkreilly]

yeah it's mostly in line with that until near the end when it gets out of line. Hopefully will increase capacity.

[janowicz]

Corrected now:
88d2c03

Thanks for catching.