britiger / osm_address_db Goto Github PK

A new entry in the database config_values should be added for programs using the database where you can see that an update process is running or not.

UseCase:

I want to reference the issue in my changeset via link.

Right now, I can link to the issue list like https://addresses.lorenz.lu/oad_dach/roadDuplicatesDist/-162550 but that will not really anyone understand the issue.

A permalink per issue which also shows the issue after it was solved where ideal.

Thanks for the great tool.

The materialized view import.city_suburb can be replaced by a simple view using the tables import.osm_admin_hierarchy and import.osm_admin_city

Using the imposm3 branch this tool during first "copy elements" it uses more memory than osm2pgsql
e.g. Germany osm2pgsql: 5GB imposm3: >25GB with shared memory 4GB + work mem 1GB

Create a Script for exporting data for an city and/or postal-code as textfile or HTML:

• list of addresses without postcode/city
• list of addresses without assigned street (direct or relation)
• display list of house numbers by street
  • every number
  • cobined numbers (first - last)
• choosing suburb

TMC Relation https://www.openstreetmap.org/relation/4108738 was added to https://addresses.lorenz.lu/oad_dach/cityDetail/-1334092

This has an highway-tag but it is not a highway.

Should be excludes here:

-946195;"Ziesar";"Magdeburgerforth";-3724543;9

-422435;"Luckenwalde";"Woltersdorf";-4192779;9
-422434;"Nuthe-Urstromtal";"Woltersdorf";-4192779;9

There should be a machnism to save the URL for diffs in the database, so it's save for update if you have more instances.

Modify web.update_invalid_addresses functions to find addresses which doesn't match to road with no addr:suburb or a road with equal addr:subrub

For all samples:
address addr:street=Dorfstraße, addr:suburb=Nattwerder

Sample 1:
road1 name=Dorfstraße, addr:subrub=Satzkorn
road2 name=Dorfstraße, addr:suburb=null
=> Valid address, match with road2, cause null accept all addr:suburb of addresses

Sample 2:
road1 name=Dorfstraße, addr:subrub=Satzkorn
road2 name=Dorfstraße, addr:suburb=Werder
=> Invalid address, doesn't match with any road, they have different addr:suburb values, no null value found

Apply relations type=associatedStreet ...
psql:sql/applyAssociatedStreet.sql:19: ERROR: upper bound of FOR loop cannot be null
CONTEXT: PL/pgSQL function getmembersroletype(text,text,text[]) line 8 at FOR with integer loop variable

Adding highway=* in osm_roads table

Remove highway=rest_area from list of roads.

Build a script to import using imposm3

https://1011.link/oad_brb/cityDetail/-55770

"19 b-e" is at end of Karl-Liebknecht-Straße => should be after 19

Error while update using PostgreSQL 12
psql:sql/importUpdateMatViewsFull.sql:11: ERROR: LWGEOM_dwithin: Operation on mixed SRID geometries (Polygon, 0) != (Polygon, 3857)

It seams running web.update_invalid_addresses it is very slow using PostgreSQL 12.

https://addresses.lorenz.lu/oad_dach/impress show

Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.
Sun Mar 31 13:50:06 CEST 2019
There was an unexpected error (type=Not Found, status=404).
No message available

Also, I suggest "imprint" over "impress" for the URL.

Is this possible? And thank you for the scripts!!

If starting osmupdate.sh addresses the scripts shouldn't remove calculated addr:city, addr:country and addr:postcode.
Solution:
while update with parameter addresses it should save all data from update_* tables into a separate table and remove them from the update_* tables. While starting next osmupdate.sh full, the saved date sould be restore into update_* tables.

Recently, the iD editor added validation layers / Q/A-layers.
They allow mapper to see validation issues inside the mapping UI and fix them right away.
The github-tickets list for "validation" provides an overview of validation layers / Q&A-layers (but also inline validation).

• ImproveOSM https://github.com/openstreetmap/iD/blob/master/CHANGELOG.md#2140
• KeepRight https://github.com/openstreetmap/iD/blob/master/CHANGELOG.md#2130

This data set looks like a great addition to this validation list.

However, as far as i can see this app needs an API first, that would allow the iD editor to show and finish the issues. Things like

• list all issues for a given bounding box
• per issue, a list all features that area involved (iD can then over+highlight the roads/houses that are "involved" with the issue)
• provide an issue type id that can be used for translations inside of iD
• allow Id to mark issues as "ignored" or "solved" (similar to the KeepRight solution)
• a unique issue id and permalink that can be used by iD to link to the issue and also reference it inside the changeset-tags.

On the other hand – since the dataset is limited to a few countries –, iD probably needs to extend the feature that lists all available validation layer to be map-location-sensitive. Like with the "Deutsche Bahn" data layer that iD only shows in Germany.

PS, thanks for the tool and the update at https://www.youtube.com/watch?v=AIBi2aD-4n0

Is the current app at https://addresses.lorenz.lu/oad_dach/countries or at https://1011.link/oad_brb/search ?

I suggest redirecting them all to one place and then to update the github description link.

It will make it easier to bookmark, share and know the service.

all places which are boundary=* and admin_level=* shouldn't be imported into osm_places

Add an SQL-Script for executing VACUUM on public.planet_* tables.