Versioning

[JakobMiksch]

There is an attempt to add Themepark to the (inofficial) osm2pgsql Docker image, see iboates/osm-utilities-docker#12
There the used version of Themepark can only be specified by a commit hash. Example: https://github.com/JakobMiksch/osm-feature-info/blob/d2c00d2/docker/osm2pgsql/Dockerfile#L5 Having a proper version of Themepark would be much cleaner for this purpose.

I am aware that Themepark is still in beta, however it might still be useful to have a prelimniary versioning. Maybe start with v0.1.0. Once a stable version is reached version v1.0.0 could be released.

[joto]

I'll do versions once it is out of beta.

[travishathaway]

I'd like to add here that I'm interested in packaging this for conda-forge once it leaves beta.

If there's anything I can do to help with beta test, let me know. I'm just now starting to experiment with this new feature.

[joto]

If there's anything I can do to help with beta test, let me know. I'm just now starting to experiment with this new feature.

There is no specific beta testing needed, it just needs more people playing with it, finding out what works and what doesn't, what could be done simpler, reporting their experiences and so on.

[travishathaway]

Just FYI, this is my own public conda channel called, gis-forge.

I already created a conda package out of it, and you can see that recipe here:

• https://github.com/travishathaway/gis-forge/blob/main/osm2pgsql-themepark/recipe.yaml

I actually ran across a couple errors when using it with lua=5.4. The patches for fixing those can be found here:

• https://github.com/travishathaway/gis-forge/tree/main/osm2pgsql-themepark/patches

More context

To give a little more context around this, I'm actually working on a little hobby project at the moment called osmprj. It's basically asking the question, "what if managing OSM/PostgreSQL projects were more like working with package management tools like pixi/uv?"

One of my favorite "flex styles" was the one used in pgosm-flex, so I'm currently porting that over to use themepark. For the tool I'm writing, I'm envisioning the themes being installed as conda packages and then being discoverable by osmprj.

I'll be sure to report back how this experience goes and any problems I find with themepark as I work with it more.

[joto]

@travishathaway Can you create a PR for those changes you have?

"what if managing OSM/PostgreSQL projects were more like working with package management tools like pixi/uv?"

That is really great! We need tools like that. As a developer (on osm2pgsql and other tools) I have always argued that my job is to write the best software. And it is somebody else's job to integrate that software into packages for specific operating systems or specific audiences and so on. That's why I don't publish docker containers or debian packages or binaries to run here or there for my software. I try to help making my software easy to package though, and Themepark is a step in that direction, find a way to make different configurations work together.

[travishathaway]

@joto,

I made a lot of progress on this last weekend. I'm going to write up a blog-style post on HackMD to share everything I've been working on soon. I'll share that here when it's ready.

[travishathaway]

@joto,

Finally back with some updates. I released the project I'm working on (osmprj) that makes use osm2pgsql-themepark. You can read about it here:

• https://osmprj.dev/blog/2026/05/07/introducing-osmprj

I also have a branch I've been using to make packaging osm2pgsql-themepark here:

• https://github.com/travishathaway/osm2pgsql-themepark/tree/luarocks

I was using a tool called openspec to help me make the changes, so a high-level overview of everything can be found here (no need to keep that in the project; just wanted it there for now so others could read).

Another interesting link to check out is this repository. It's an example of how to create a new themepark theme and how it would be packaged:

• https://github.com/travishathaway/pgosm-themepark

I know this is a lot, so hopefully it all makes sense! It would be nice to see my changes eventually merged into the main project, but I think we need still need to iron out a few things. I am more than happy help out, especially as the packaging expert 🤓 📦 .