Marketing Performance and Growth Efficiency Analysis
A strategy-oriented analysis of trivago’s marketing efficiency, examining how increased brand investment, traffic mix shifts, and marketplace changes affect sustainable…
Are you a sales leader, coach, or founder? Turn your sales conversations into clear insights with Sales Signals — from call analysis to coaching, performance tracking, and forecasting.
Aleksei Prishchepo
May 18, 2026
Most hotel search interfaces treat location as a distance problem: how close is a hotel to the city centre or another point on the map? But distance is only a rough proxy for what travelers actually experience. A hotel a few kilometres away can be much easier or harder to reach depending on the public-transit network.
This project explores a different approach: rank hotels by total transit time to the places a traveler wants to visit. Berlin was used as a proof-of-concept city, with hotels, points of interest, public-transit routing, and traveler scenarios combined into a single analytical workflow.
The result is a geospatial model that turns transit accessibility into a measurable feature and makes differences that are invisible in conventional distance-based maps visible at a glance.
Data Analyst & Developer
R, sf, H3, Google Maps API, gstat, ggplot2
Geospatial Analysis, Travel Technology, Product Analytics
Reframes hotel location as an accessibility problem rather than a proximity problem, using actual public-transit travel time between hotels and destinations.
Combines an OpenStreetMap extract of Berlin with hotel locations and points of interest, then enriches destinations with Google Places review data to identify popular locations.
Reduces 455 hotel locations to 189 H3 spatial cells before routing, cutting the potential routing workload from 22,750 to 9,450 origin-destination pairs while retaining useful spatial resolution.
Handles thousands of routing requests with rate limiting, error handling, and intermediate data storage so that individual API failures do not interrupt the analysis and completed API calls do not need to be repeated.
Tests the accessibility model against different traveler profiles and sets of destinations rather than relying on a single generic definition of a “good location.”
Interpolates sparse transit-time measurements into continuous spatial surfaces with isolines, turning point-level routing results into maps that reveal the geography of accessibility.
Read the concept behind the project and the technical proof of concept.
Defined hotel location as an accessibility problem and formulated total transit time to user-selected destinations as the core measure.
Collected Berlin points of interest from OpenStreetMap and filtered them to culturally and commercially relevant destination types.
Enriched the POI dataset with Google Places ratings and selected popular destinations for the scenario analysis.
Collected 455 hotel locations and used H3 spatial indexing to group nearby hotels into 189 cells before routing.
Calculated thousands of public-transit travel times through a routing API, with rate limiting, error handling, and cached intermediate results.
Aggregated travel times across destination sets representing different traveler interests.
Used spatial interpolation and isolines to convert discrete travel-time measurements into continuous accessibility maps.
Demonstrates that geographic proximity and public-transit accessibility produce substantially different views of hotel location.
Reduces a 22,750-request routing problem to 9,450 requests through spatial clustering while preserving useful geographic detail.
Turns API-based point measurements into an interpretable spatial model that can be explored visually across different traveler scenarios.
Provides a reusable analytical pattern for accessibility, catchment-area, and location-based decision problems.
Geospatial analysis • Spatial data engineering • API integration • R programming • H3 spatial indexing • Routing analysis • Spatial interpolation • Data visualization • Scenario modelling • Analytical problem solving
If you need to turn location, operational, or customer data into a model that supports a real business decision, feel free to reach out via the contact page to discuss how I can help.