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

UDOT - Travel Demand Model #500

Open
rkelson opened this issue Nov 14, 2024 · 4 comments
Open

UDOT - Travel Demand Model #500

rkelson opened this issue Nov 14, 2024 · 4 comments
Assignees
Labels
paying This issue earns $$ status: help wanted Extra attention is needed status: in progress This issue or pull request is being worked on

Comments

@rkelson
Copy link
Member

rkelson commented Nov 14, 2024

Benefit

SBA- Draft

One of the inputs to UDOT’s travel demand models is socioeconomic data (households and jobs). UDOT would like to use county parcel data to identify primary residences and use that as a proxy for households in all counties outside of the Wasatch Front (Davis, Salt Lake, Utah, and Weber).

Acceptance Criteria

  1. Designation of each residential parcel as a primary or secondary residences.
  2. Classification of residence by general type:
  • Single family detached, duplex, townhome, condominiums (includes all individually deeded multifamily units except duplexes and townhomes), apartment, mobile home, etc.
  • The number of units for multi-family apartments. This may not be an attribute kept within the Assessor database but can be estimated with support from an address point GIS layer, aerial or street view photography (for example)
  • The original year the primary residential structure was built.
  • Property size (acres)
  • Building square feet (primary structure)
  • Total assessed tax valuation for the property.

UGRC will create the following deliverables as funding allows:

  1. File geodatabase with the parcel boundaries and the following fields:
  • A field to indicate whether the parcel is a primary residence or a secondary residence.

  • For the primary residences: fields specifying primary/secondary residence status, residential type, unit count, built year, acres, building square feet, and assessed value.

  • For secondary residences: only Summit, Wasatch, and Iron counties are needed and only these attributes: the residential type, unit count, and built year (where available).

  1. Classifications needed for secondary residencies are second home, recreational single unit (e.g. cabin), recreation multi-unit, and hotels. UDOT will get the number of hotel rooms for hotels/resorts with one parcel representing the entire hotel, UGRC should only classify the parcel as a hotel and infer the number of rooms for hotels with a parcel for each room.
  • If resources allow (time and budget): classify secondary residencies for the counties with National Parks:
    Arches & Canyonlands: Grand & San Juan counties
    Bryce: Garfield county
    Capitol Reef: Wayne County
    Zions: Washington county

Notes

  • We are starting in Iron County to see how this plays out with the information we can pull together.

Risks

  • It is possible the information currently available will not fit UDOT's needs. However it is also possible UDOT will be able to utilize what we can provide.

Issue Reference

@rkelson rkelson added status: help wanted Extra attention is needed status: in progress This issue or pull request is being worked on paying This issue earns $$ labels Nov 14, 2024
@rkelson
Copy link
Member Author

rkelson commented Nov 14, 2024

Working through Iron Co I have found problems with how OSA is ingesting county data and issues with the accuracy and completeness of county information. OSA is currently looking into whey some residential parcels are coded as agricultural

@rkelson
Copy link
Member Author

rkelson commented Nov 26, 2024

Had a discussion with Alex @ OSA 11/25/24 and determined I need to use the data that comes directly from the counties considering the amount of manipulation OSA does to the data to categorize and standardize the attribute values. Because they pull data straight from the county systems, Alex is not willing to give me the original county data. I already have the Iron Co data pulled from their Tyler system but we will need to start requesting the county tax roll information for the other counties and this will be discussed in our meeting today with Natalia.

@rkelson
Copy link
Member Author

rkelson commented Dec 4, 2024

Worked with Natalia to revise the schema and attributes for the deliverable. Sent her a draft 12/4/24 of the work I've done in Iron with just the OSA data as a preliminary review to see if it will work for their project. I'm going to start working on Juab and Cache next.

@rkelson
Copy link
Member Author

rkelson commented Dec 16, 2024

UDOT has accepted Iron Co as it was processed 12/12/24 and is moving forward with the layer provided unless they find some other issues to address during the heavy lifting stage.

Moving on to Juab

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
paying This issue earns $$ status: help wanted Extra attention is needed status: in progress This issue or pull request is being worked on
Projects
Status: No status
Development

No branches or pull requests

2 participants