Questions about the data file structure for Monthly Patterns and Core Places

Hello! I’m sorry for duplicate questions. We are working on an airport project and got a few questions on the data. 1) We notice the data file structure change on Monthly Patterns at May 2020 and Dec 2020, and Core Places at Nov 2020. Could you provide more context and details on the changes? Is there any documentation? 2) Do data with parent id include all the child id data points? 3) Do the data include foot traffic of employees or just visitors? Thank you so much

This topic was automatically generated from Slack. You can find the original thread here.

Hey - thanks for reaching out!

  1. For any changes and updates to our data, it can be helpful to check out the Release Notes that we release monthly. Here are the release notes for May 2020, December 2020, and November 2020 going over any updates to our data.
  2. There’s some helpful documentation on the Visit Attribution for Special Cases section of this docs page. We attribute visits to the parent POI only when we determine that the parent completely encloses its children indoors. We attribute visits to both the parent POI and its children if the parent does not contain the children indoors.
  3. Data will include foot traffic of both employees and visitors. We tend to recommend using bucketed dwell times to remove longer duration visits if you’re trying to filter out employees. Here’s a previous thread that you might find helpful on this topic!

Is it possible to sort dwell time based on night time cbgs? I want to basically estimate commute distance for different types of visitors.

oh interesting… unfortunately you wouldn’t be able to disaggregate dwell time to identify the home cbgs. BUT we had a community member who built a time-aware Huff model using our data. Take a look at their approach, it might give you some ideas.