Optimize housenumbers table

[Sylade]

Hello
With your example-mapping.yml, I remark in the table housenumbers generated by your imposm that:

• there are several empty names (3th field).
• there are several identical names with the very near goemetries (< 1 meter)

Is it possible to remove them during imposm to optimize the table?
Thank you.

[olt]

This is just an example mapping. This file is not maintained to provide an optimized, modern OSM map.

[Sylade]

Hi olt,
I may not be clear.
I use your example mapping and I don't how to add a criterion to avoid the empty name in the housenumbers table.
I tried with reject filters but it isn't working:

tables:
  amenities:
    columns:
    - name: osm_id
      type: id
    - name: geometry
      type: geometry
    - key: name
      name: name
      type: string
    - name: type
      type: mapping_value
    filters:
      reject:
        name: ['']
    mapping:
      amenity:
      - bar

Is it possible to add a criteriion in the mapping to avoid the empty names?

I see in your your exemple mapping:

  landusages_gen0:
    source: landusages_gen1
    sql_filter: ST_Area(geometry)>500000.000000
    tolerance: 200.0

Is it possible to use a similar criterion in mapping to remove the identical names with the very near goemetries (< 1 meter) in the housenumbers table?

Thank you for reopening this issue.

[ImreSamu]

@Sylade :

Thank you for reopening this issue.

imho: the "imposm community mailing list" is a suggested method - for asking community help.
see: https://github.com/omniscale/imposm3#support

[Sylade]

OK. I do it.
Thank.