osm2pgsql
osm2pgsql copied to clipboard
osm2pgsql-dev
OpenStreetMap data to PostgreSQL converter
( copied over from #1663) We should think about ways of doing attribute-based "expire" and re-processing. One option would be to add some kind of hash to each database entry....
Sometimes it can be useful to mark certain OSM objects as changed so that osm2pgsql behaves as if it has read that object from an OSM change file. This can...
The node location store currently has a very simple array structure which makes it easy to use and and very fast to access. The downside is that it needs nearly...
osm2pgsql doesn't check for settings it doesn't know about so that we can introduce them later without old versions of osm2pgsql breaking. But maybe we should at least check and...
[Storage-Optimizing PostGIS Geometries](http://www.danbaston.com/posts/2018/02/15/optimizing-postgis-geometries.html) describes a neat trick. It should be really simple to build this into osm2pgsql. Question is: Is it worth it for our data?
In general osm2pgsql is built around the principle that while it does its processing you only look at one OSM object at a time and process that. But this is...
osm2pgsql by default "clusters" all output tables by geometry. I have put "clusters" in quotes, because this doesn't use the CLUSTER functionality of the database, but we are doing this...
Identifiers for classes, functions, classes etc. should [follow our coding styles](https://github.com/osm2pgsql-dev/osm2pgsql/blob/master/CONTRIBUTING.md#code-style). Most use lower case with underscore, classes have postfix `_t` etc. clang-tidy can check this. See https://clang.llvm.org/extra/clang-tidy/checks/readability/identifier-naming.html . Here...
In the pgsql middle we [get the maximum id](https://github.com/osm2pgsql-dev/osm2pgsql/blob/master/src/middle-pgsql.cpp#L113-L123) used for all of the tables when updating. Then we know that we don't need to DELETE any objects with an...
Metadata
Owner
Metadata
OpenStreetMap data to PostgreSQL converter