SafePaths: AI-Powered Sustainable & Secure Urban Mobility Application

1) Does the system rely entirely on existing data sources or is there any field data collection involved (e.g., citizen sensors, surveys)?

2) The Municipality of Rethymno already operates cameras and equipment that monitor road users. How will your proposed system reliably detect pedestrians and cyclists located outside of roadway areas, such as sidewalks, parks, or pedestrian-only zones?

3) In what format will your deliverables be provided, and who will be the intended recipients? Ideally, the Municipality of Rethymno would need access to the full dataset, and it would be beneficial if some of the insights or visualisations could also be made publicly accessible. How do you plan to support both internal use and public transparency in your solution?

Find answers below. César López CEO - Findspo. 1) Data sources and field collection The system is designed to be flexible. We can work entirely with existing municipal data—as long as it is curated and accessible, ideally via API. When needed, we can also integrate complementary data layers, including citizen-generated input (e.g. mobile surveys or sensors). This ensures adaptability to the city’s existing infrastructure and data maturity. 2) Detection beyond roadways We understand that the municipality already uses cameras and equipment to monitor roads. Our system is not intended to replace these, but rather to enrich the existing setup. We propose integrating with vision-based data (where feasible) and complementing it with our spatial mobility analysis—helping to identify movement in sidewalks, parks, and pedestrian-only zones through predictive modeling and additional contextual data. 3) Deliverables and accessibility We will provide: Full internal access to the datasets and dashboards for the municipality. A public-facing layer with selected insights published via an open data portal. Please note that while most project-generated data will be accessible, some content (such as synthetic or proprietary elements) may be considered outside the project scope and excluded from full download. This approach ensures both operational value and transparency, while maintaining clarity on data ownership and use.