Discussions

I am working on a project focused on analyzing pedestrian trespassing along railroad networks across the United States. We are evaluating whether StreetLight data can support this work, and I wanted to reach out with a few specific questions about feasibility before scheduling a conversation.

The overall idea is to characterize pedestrian activity in and around rail corridors at a level of detail that lets us understand where, when, and how people are crossing or accessing the right-of-way outside of legitimate crossings. This is part of broader work on safety and the human-infrastructure interface in cybernized transportation systems.

To assess fit, I have four specific questions:

1. Spatial aggregation. What is the smallest spatial unit you can deliver pedestrian data for? We are particularly interested in short corridor sections, on the order of 100 to 500 meters along a specific stretch of rail right-of-way. Are custom zones at that scale supported for pedestrian metrics, and what are the practical sample-size limits we should expect at that resolution?

2. Temporal resolution. What is the finest temporal granularity available for pedestrian data? Specifically, are sub-hourly bins available (minute or second resolution), or is hourly the practical floor for pedestrian metrics?

3. Trajectory data. We are interested in being able to identify individual pedestrian trajectories where the path crosses a rail right-of-way, ideally as continuous (anonymized) location pings rather than aggregated counts. Do you offer any product that exposes device-level continuous trajectories, or is everything delivered as zone-level aggregates?

4. Specific US corridors. Can you confirm coverage and data availability for specific named rail corridors across the US? We would want to select a small number of corridors for an initial analysis and would like to understand any geographic coverage gaps before doing so.