@amapanda

BTW do you know about Postpass?

Yes, I’ve seen this project. It looks interesting, but it doesn’t cover all my needs.

Thank you for spending your time, @Nakaner,

I wonder why you need changesets, user IDs and user names.

I am using a version with metadata to make the experience more similar to using global Overpass instances. It makes it easier to create a project that needs such data. For example, it’s common in Overpass to filter objects by a specific user or changesets (e.g. for stats or QA), which I would like to achieve using PostGIS.

I grepped through your source code and the string “changeset” only exists in your import style file for Osm2pgsql and test data.

Yes, in this or the linked example, I don’t use metadata for any specific case. I actually don’t use any OSM data (excluding just filtering/replicating) in these repositories. They are only to simplify setup and manage replication for a PostGIS DB.

protect the privacy of OSM contributors

I don’t want to argue about privacy in this diary, but in my opinion it doesn’t change anything here, because you can already get this data from another source. You’ve done great work at GeoFabrik by preparing these extracts, allowing people to save time and resources by getting it faster, but even if you remove it, people can still get this data, so I don’t see a reason to restrict access or avoid using it in a README as an instruction, if it’s completely public (assuming no country-specific law requires it from you).

That’s why I suggest to instruct users to download the cleaned files from the public servers without authentication. I can change it to include both, with a recommendation to use the cleaned files. Would that satisfy you?