Does anyone know of a Travel Wiki?

I am looking to plan a long trip (2-3 months) along with a friend parttime, in Europe, which is a long way from home (Australia), It will include House Sitting, friends, accommodation, flights, and car rental.

I was wondering if there is any “prior art” in the public domain.

TiddlyWiki Would be ideal for organising a long trip and can be placed online, behind a password, and a local copy retained.

You’ll be the first. But it’s a perfect application:

1 Note-taking which will include time stamps (via the “created” field).

2 Import anything capability: photos, videos and sound recordings. Also PDF and HTML such as itinerary and timetables.

3 Export updates daily HTML blogs which include the photos, videos and sound recordings. Example: Day 1: Landed Charles De Gaule loc: OpenStreetMap

Include embedded maps:


大きな地図を表示

And why couldn’t you update us here??

Could we use this post as a portal for ideas on your application, Tones?

1 Like

Isn’t that your list of wants already solved?

FWIW …

  1. Time-stamped RECORD Tiddlers (What Happened When);
  2. Geo-Location data enabled because you WANT to be Tracked;
  3. PLANNING SECTION of one of many TW Calander plugs;
  4. Go Full PROJECT Planning (some available).

I’m interested to see how you manage.
It seems pretty easy to me?

Happy Truckin
TT

Hello @TW_Tones
I don’t have answer re Travel Wiki, but you could use @fastfreddy’s Simple checklist macro
Here is the plugin
My examples, not great, which you could adapt or use.
travel_tiddlers.json (11.0 KB)

I was not thinking of publishing my journey beyond my fellow travelers but it’s well worth thinking about.

I was thinking more around planing, bookings, reservations and contacts. Certainly notes on the road but a lot of this would be safer as confidential.

So if I was to have a seperate public wiki it may make sense if in my private wiki I could prepare and post from there :thinking: to a seperate site?

  • of course media is always more bytes

keep the ideas coming I will share back my thoughts

There are likely a bunch of ways to achieve that?

An approach I have used successfully is …

  1. Have a “base” TW in which is everything you need. The TW to coordinate and record thy travels. ADD to that TW the InnerWiki plugin.

  2. DEFINE the payload (i.e. a subset of #1) for an InnerWiki instance you save at a fixed (local) address.

  3. Every so often, using an SFTP browser extension, upload #2 to your online public host.

Side note: I personally prefer not having to schlep a node / electron system (i.e. needing more than a standard browser) around the globe to achieve #3 when it can be done largely in-browser.

But this is just one approach.

Interesting topic!
TT

Update: If you registered output of #2 on a host like TiddlyHost then SFTP would not be needed.

I’m very interested as well on the taxonomy and structuring of a Travel TW :slight_smile:

I assume you know of Wikitravel.org? As a possible starting point for destination ideas but also structuring ideas.

I would start by creating tags for what you just mentioned (maybe upgrade to fields later on, if needed). Maybe also add concepts like sightseeing, lodging, eating etc and bind them together with location based tags or fields like country, city? Then you could quickly add an idea, tag it accordingly and it should end up at it’s right place (hopefully), in some form of a TOC list.

1 Like

My Key interest here is planning and recording details before the holiday

I think with such a large trip, perhaps having a hierarchical tree for both location EU > France > Paris and structured subject areas like accommodation where a tiddler can reside in one or more, and one can be fuzzy, eg something that applies to all of EU or France or just a region/town in France.

  • This would allow different perspectives and more or less details.

I may include projectify to manage todo items.

1 Like

Right.

Makes sense. Though travel planning often starts logically structured (medical, travel, region, timing etc.) but often needs deal with serendipitous and unforeseen events in-travel.

Your idea of “hierarchical tree” plus cross-cutting free-search / taggery(?) sounds pretty fit.

FWIW it got me thinking about using the TW Explorer / Tree as the planning interface. AND a bespoke filter to the Tree Macro that can filter that tree to only show those branches/leaves relevant to a query.

Just a thought
TT

Update: A logistical comment I forgot to emphasize.
I am assuming that in-travel you won’t want complexities or have time for tweaking.
Rather a sys that instantly returns All-But-Only needed info.

1 Like

I have not seen a wiki like this, but I have heard good thing about Wanderlog, at least for the itinerary planning side of it. If you want to make a wiki with those features, it may be worth a try to get some prior art.

Hope you have a great holiday.

2 Likes

I’m planning a trip too and the following may provide useful ideas. Please note that I do not describe the complete system here, but only the main idea. In actual practice what I use is more sophisticated.

I use Projectify to create a project say, Europe Trip and record main things to do. I take advantage of the Schedule feature in Projectify to set a few important deadlines.

I create to do items in the Projectify project which I label for example, Rome/Accomodation, Rome/Transport, Rome/Sightseeing, Rome/Eating, Rome/Shopping. Similarly for other cities, say Paris/Accommodation, Paris/Transport etc. Each tiddler is tagged either Rome or Paris as the case may be plus Accommodation or Transport etc.

I create a dashboard with the following tiddler links: Pre-Travel, Cities To Visit, Transport, Accommodation, Shopping, Sightseeing, Post-Travel. “Cities to Visit” has links to tiddlers “Rome” and “Paris” or if you prefer it you could have both cities inside the same tiddler.

Here’s an example of a to do:
Say, I want to create a to do for taxi hire from Fumicino to Rome. I create a task in Projectify Rome/Transport which I tag Rome and Transport.

I create a dynamic table inside the tiddler “Rome” where I filter by the tag Rome and tag not done (!tag[done]) and todo. So now my “Rome” tiddler shows this to do for taxi hire.

I also create a dynamic table inside the tiddler “Transport” with a filter by the tag Transport and tag not done (!tag[done]).

Why do I do this? I do it because if I view the tiddler “Rome”, the dynamic table will show me the transport-related to do.

If I want to see everything related to transport arrangements for both Rome and Paris, I can see the taxi hire task in the Transport tiddler.

Refinement: My tiddlers actually include a second dynamic table as follows. Using the above example, the filter is based on the tag Rome and done. This shows immediately which tasks are done. Same for the Transport tiddler (tag Transport and tag done).

Planning a trip is tricky and pending matters may be easily overlooked. I want to ensure that a to do is visible from different relevant viewpoints. For example, the city concerned and the subject matter.

Further refinement if you are a little paranoid. Use the field status which is already in dynamic tables and create a sanity check filter:

Cases for investigation

1. Tagged done but status field value is "open"

This handles the case where a tiddler is marked as finished via tag but remains “open” in the field.

Logic: status = open AND tag = done “[tag[Europe Trip]tag[done]field:status[open]]”

2. Status is “closed” or “complete” but missing done tag

This identifies tiddlers where the field indicates completion but the corresponding tag is missing.Logic: (status = closed OR status = complete) AND tag ≠ done “[tag[Europe Trip]!tag[done]field:status[complete]] [tag[Europe Trip]!tag[done]field:status[closed]]”

3. Status Field is Missing or Blank

TiddlyWiki’s !has[status] operator conveniently catches both tiddlers where the field does not exist and tiddlers where the field exists but is empty.Logic: missing field OR blank value “[tag[Europe Trip]!has[status]]”

The actual filter is:

“[tag[Europe Trip]tag[done]field:status[open]] [tag[Europe Trip]!tag[done]field:status[complete]] [tag[Europe Trip]!tag[done]field:status[closed]] [tag[Europe Trip]!has[status]]”

N.B. the tags todo and done are used by Projectify.

The system benefits a lot by using a navigation scheme between the main dashboard and the secondary dashboards (tiddlers).

TLDR: Use Projectify, dashboards and dynamic tables.

3 Likes

While you are traveling, you will no doubt want to take lots of pictures, perhaps with a dedicated digital camera, but also maybe using TiddlyWiki on your phone or tablet, in which case you might find these TiddlyTools add-ons especially useful:

For general mapping with GPS coordinates + map image capture

For capturing and managing photos

Notes:

  • TiddlyTools/Panels/Maps + Geospatial Utilities plugin uses FREE server-based resources OpenStreetMap for roadmaps and ESRI World Imagery for satellite views.
  • Dom-to-image plugin is an unpublished TWCore plugin that hopefully will be included in the upcoming TW5.4.0 release. In the meantime, you can get a functioning beta copy at TWCore Dom-to-image plugin.
  • TiddlyTools/Panels/StreetView uses the Google Places API which requires a FREE registered “API key” (see Set up the Places API (New)  |  Google for Developers).
  • TiddlyTools/Panels/Images + TiddlyTools/Camera/action-camera.js can capture still images (jpg, png, or webp) or video (webm), and now also includes optional “geotagging” to save the current latitude/longitude as fields in the captured image/video tiddler.
  • TiddlyTools/Camera/TopToolbar provides a button for fast access to capture images/video without needing to open TiddlyTools/Panels/Images.
  • By default, the camera geotagging option is initially disabled for privacy and performance reasons. To enable geotagging, create a tiddler named $:/config/TiddlyTools/Camera containing a geotag field with a value of yes.

enjoy,
-e

4 Likes