Ortszeit

Ortszeit is in development. Sign-up is not open yet; if you are interested, write to me.

ORTSZEIT · DOCS · IMPORT

Import

Upload a .zip on the import page in the editor. It is read in the background and the result is reported in full, including everything that could not be taken.

Nothing an import brings in is published. Every post arrives as a draft and every trip arrives unlisted, whatever the source said. You review it and publish what you want.

Supported formats

The format is detected from the archive; you do not have to say which it is.

Source What comes across
An Ortszeit blog/ folder Everything, exactly. This is the portable format read back in — export, edit the files on your laptop, import again.
Polarsteps — account data export Trips with their dates, one post per step with its text and coordinates, and the photos and videos of each step.
Day One — JSON export One trip per journal, one post per entry. Entry text, capture times, coordinates, place names, photos and videos. A leading # Heading line becomes the post title; tags are kept as a trailing line in the body, because the format has no tag field and dropping your own taxonomy is worse than a visible line you can delete.
Google Takeout — Location History + Google Photos A trip skeleton. See below.

FindPenguins is not supported. There is no publicly documented structure for their export, and a converter written against a guess would fail silently on real data, which is the worst possible outcome for a migration. If you have a FindPenguins export and want to help, get in touch — one real file is all it takes to write the converter properly.

Every converter produces a blog/ folder first and then imports that. There is exactly one import pipeline, and it consumes the documented format — which is what keeps “files are canonical” honest rather than decorative.

Google Takeout, and what a trip skeleton is

Takeout is the most useful import and the strangest one. From your location history and your photos it reconstructs:

  • days you were away — visits far enough from wherever you usually are
  • the places you stopped, one post per place per day, dated at the visit
  • the photos taken during that visit, attached to the right post

and then it stops, because Takeout contains no writing. Every post comes out empty and untitled on purpose. You get the shape of the trip back — the days, the places, the photographs in order — and you write into the gaps.

Two consequences worth knowing before you upload half a decade of location history:

  • Days at home are dropped. They are not travel, and a location history is mostly them. This is the one large omission and it is deliberate.
  • Precision is not the goal. A day that should not be there is far easier to delete than a day you never got back.

What cannot travel

Named here and named again in the report you get after each import:

  • Trip passwords. A password cannot travel inside an archive. A protected trip is imported as unlisted, and you set a new password afterwards.
  • Co-authors. Names come across as text. They are not turned into accounts and nobody is given access to anything.
  • Blog identity. The title, bio, subdomain, custom domain and CSS in an archive’s blog.yaml are never applied. An import brings content into a blog that already exists and already belongs to you; it does not overwrite who you are. The skipped fields are listed in the report.
  • Place identity, sometimes. No third-party export carries OpenStreetMap references, so places from Polarsteps, Day One and Takeout are matched on name and coordinates instead.
  • Dates on text-only posts. A post with no photograph has nothing to carry its original date through publishing, so publishing it dates it today. Those posts and their intended dates are listed in the report so you can correct them — the loss is visible, never silent.

Limits

  • 1 GB per upload. If your archive is bigger, split it, or get in touch and we will import it for you.
  • One import at a time per blog. Two concurrent runs would race on slugs.
  • Imported posts and photos count against your plan’s limits like any others.

If an import comes out wrong

The third-party converters are written against each vendor’s documented export layout. Vendors rename fields without announcing it. If something looks missing rather than merely unpublished, keep the original archive and get in touch — the fix is a converter change, and your file is what makes it possible.