Paul Norman

Store slim table tags in hstore

5

I did some testing, and the representation of tags in a hstore is more efficient than our current `text[]` array of alternating keys and values. For testing latter can be...

Figure out a way to use fastupdate on indexes

5

fastupdate does not work with osm2pgsql because with a high work_mem it builds up a large temporary part of the index it has to sequentially scan, slowing down updates significantly...

https://github.com/openstreetmap/osm2pgsql/issues/419#issuecomment-126644507 showed that with diff updates, relations can be processed twice, once in parsing and once in pending relations. The output is correct, but doing so twice is wasteful. Two...

PostgreSQL processing stage - output ideas

3

Currently the output for the last stage where indexes are created and clustering is done looks like this ``` Sorting data and creating indexes for planet_osm_point Sorting data and creating...

Remove tile.openstreetmap.org from listing

2

https://github.com/AliFlux/MapTilesDownloader/blob/69f48a75cab94644894329b2f7cd564941ed4d28/UI/main.js#L28 The OSMF tile usage policy [states](https://operations.osmfoundation.org/policies/tiles/) > In particular, downloading significant areas of tiles at zoom levels 17 and higher for offline or later usage is forbidden without prior...

Add new command to create generalized tables

1

It would be useful when importing to be able to split the generalization off from the import stage. When we have a database that has existed for some time, being...

Using the config files in #227, I get an error with this geojson ```json { "type": "FeatureCollection", "features": [ { "type": "Feature", "properties": { "m49": "001", "wikidata": "Q2", "nameEn": "World",...

Using the config files in #227, I get an error with this geojson ```json { "type": "FeatureCollection", "features": [ { "type": "Feature", "properties": { "iso1A2": "AQ", "iso1A3": "ATA", "iso1N3": "010",...

## Context Right now when specifying a geojson file for `geojson_intersects_feature` it needs to be specified as an absolute path or relative to the imposm binary. This makes it difficult...

https://github.com/omniscale/imposm3/commit/d29a56e542c8652561fdb79604e64fb6cd14dd34 introduced a new column type of `geojson_intersects_feature`, but called it `geojson_intersects_field` in the documentation. When trying to use the latter, I got the error `0:00:00 [error] reading mapping file:...