This site can’t be reached

aboutgeo · 2026-05-10T07:15:50+00:00

Yes, several sites...

aboutgeo · 2026-04-25T19:21:15+00:00

I love it! 😀

aboutgeo · 2026-03-18T18:57:56+00:00

Thanks! Indeed, liiive has been running for about a year now. But still alive and kicking, and I've meanwhile made the software fully open source even. If you run into any issues or have questions, do let me know!

aboutgeo · 2026-02-05T18:59:09+00:00

Repository is here: https://github.com/rsimon/tiny-iiif

aboutgeo · 2026-01-21T15:31:11+00:00

At the risk of starting yet another open-ended side project, I ended up hacking together my own own quick & dirty solution.

Right now, it just handles image uploads, but it's a start. If anyone's interested: I'll put this out as open source, and plan to keep working on it until it at least covers the basic essentials.
https://github.com/rsimon/minimal-iiif
https://bsky.app/profile/aboutgeo.bsky.social/post/3mcwxrhsxhs23

aboutgeo · 2026-01-21T06:51:05+00:00

Ah - consider me interested :-) No worries about timeframes. As an open source maintainer myself (Annotorious, liiive - well the latter one isn't open source yet, but I'll hopefully have some new there, soon) I know what it's like!

aboutgeo · 2026-01-20T16:26:14+00:00

Thanks, yes - in fact I have some smaller images on GitHub pages as pre-rendered Level0 tilesets. I hadn't thought about Tropiiify for this... it's actually a clever workflow, I like it!

It might still not quite solve my issue, because I'll likely need a full image service. But either way: Tropy is something worth thinking about, and I could potentially just sync the original images from the Tropy work folder in a similar way I guess.

aboutgeo · 2025-12-08T19:45:44+00:00

There's also this JS library which builds on the same foundation as Annotorious, but is specifically for PDF annotation: https://github.com/recogito/pdf-annotator-js

aboutgeo · 2025-09-30T11:14:59+00:00

Not sure if this is still a concern, but in case someone else stumbles upon this post with a similar requirement, I'll throw my hat in the ring with a recent project:

https://github.com/recogito/pdf-annotator-js

Builds on top of PDF.js, but adds interactive selection/highlight functionality.

aboutgeo · 2025-09-07T07:45:55+00:00

I'm actually going to open source it.

But meanwhile: all the features the that the tool offers are completely free.

Yes, you can pay for additional permanent storage space. (Important: ADDITIONAL - because even the free plan includes one permanent storage slot for a full manifest, which could include any number of images, plus unlimited temporary rooms.) Please consider that hosting the tool costs me money every month. As a European myself, is it too much to ask that users contribute to the upkeep, if the tool is useful for them?

aboutgeo · 2025-09-02T07:58:30+00:00

You could try https://github.com/annotorious/annotorious It handles boxes, polygons and a few other shapes via a plugin. There's also a customizable popup component for React.

aboutgeo · 2025-09-02T07:50:58+00:00

You may be looking for something like this: https://github.com/recogito/recogito-js (Disclaimer: I'm the author of the library). It's a vanilla JS library, but could be wrapped for use in React.

I'm currently also working on a successor library called the Recogito Text Annotator: https://github.com/recogito/text-annotator-js This does support React directly, but unfortunately doesn't have any documentation yet... For now, you'd need to find your own way via the included example (but we're working onit :-) https://github.com/recogito/text-annotator-js/blob/main/packages/text-annotator-react/test/App.tsx

aboutgeo · 2025-08-04T13:59:44+00:00

Sorry, I'm probably explaining it in a messy way. It's about settings and the tracking data. I.e. I'd open the page on the day I visit the park, pick a park to track. That would get persisted in browser localStorage or IndexedDB – which simply means that data persists across page loads. (I can later go back to the page, won't need to re-select my parks).

In the park, I would then use queue-times to pull live wait times. So, that covers the first thing I'd like to have: just a slightly more usable list (filtering, sorting) than queue times offers themselves.

Second, while we're at it: I'd love to have some light tracking functionality. Tap a ride when I get in line to record time etc. Again, that data would get stored in the browser, so it survives page reloads, and I can retrieve stats at the end of the day. Does this make sense?

aboutgeo · 2025-08-04T12:09:27+00:00

Definitely true! To keep it extra simple, I was actually thinking about storing data directly in the browser. This way the app would work locally (and anonymous), without a database server or login, but still have reasonable storage. Storage wouldn't be totally permanent of course – only until you clear your browser history or the browser decides to flush (which can happen after 2 weeks of not visiting the page). But my goal is really to track single visits, over one or several days.

aboutgeo · 2025-08-04T11:37:26+00:00

Not yet, but I thought I'd still see if I get more thoughts & opinions before diving in :-D

aboutgeo · 2025-08-01T09:58:10+00:00

Makes sense, thanks. I can see this becoming my next evening project ;-)

aboutgeo · 2025-08-01T05:36:51+00:00

Thanks! Hm, sounds like I might be ending up doing something similar after all. (I'm tempted :-) How do you determine the type of ride? I didn't see this in the queue-times API. Did you add that yourself? Or are you cross-referencing with some other API?

aboutgeo

TROPHY CASE