Travel Planner - Itinerary, Costs and Bookings (Open Data Sources Only)

justcomplaining commented 5 months ago

Project description

UI-wise, a great travel itinerary app would IMO need:

Data entry for several types of elements (inspiration for sensible categories can be got from travel guides), e.g. transport/trip (modes, length, cost, start/end), accomodation/stay (type, length, cost), activity (museum, booked day trip etc with cost/length/type) and food etc.
Both Timeline & Map Overviews
Cost overview

Non-free example: Lambus for everything, Rome2Rio Trip Planner for transport / stops overview

I would advise building basic search-functionalities for all such elements and add actual connections to real data sources later. Such sources should be open. This is a great opportunity to link many open projects (see technology below).

Relevant Technology

Map base should be OpenStreetMap with inspiration from projects such as OpenTripMap / maybe with the feature to leave comments as well.

Map/trip planning should be focused on entering the relevant data (itinerary & booking info) & displaying it in the map & timeline overviews, NOT on finding routes & booking, there are better tools for this. Once there are resources to get to it, you might want to look at projects such as OpenTripPlanner and the library behind Öffi and Transportr.

For activity and attraction info, apart from OSM POI and Wikipedia articles, esp. WikiVoyage might be a good source, ideally with editing functionality to get closer to #324 . Something like OpenPlaceReviews integrated would be nice, but that seems dead. LibReviews might be an option.

All data should be exportable and importable via standards such as CSV (itinerary & costs) or GPX (routes).

Complexity and required time

Complexity

No idea...

[ ] Beginner - This project requires no or little prior knowledge of the technolog(y|ies) specified to contribute to the project
[x] Intermediate - The user should have some prior knowledge of the technolog(y|ies) to the point where they know how to use it, but not necessarily all the nooks and crannies of the technology
[ ] Advanced - The project requires the user to have a good understanding of all components of the project to contribute

Required time (ETA)

[ ] Little work - A couple of days
[ ] Medium work - A week or two
[x] Much work - The project will take more than a couple of weeks and serious planning is required