Sarah Hoffmann 987d60ccda place nodes can only be linked once against boundaries ... If a place node is already linked against a boundary, it should not be used for linking again. It is usually a sign of a mapping error, when there are multiple boundary candidates. This change just avoids inconsistent data in the database, it does not guarantee that the linking is against the more correct boundary.		2020-12-02 15:31:02 +01:00
..
address_lookup.sql	also add explicit cast for varchar	2020-12-01 22:15:51 +01:00
aux_property.sql	simplify getNearestRoadFeature function	2020-02-26 10:58:55 +01:00
importance.sql	move importance/wikipedia functions into separate file	2020-01-05 15:55:39 +01:00
interpolation.sql	factor out parent search from addr:street/addr:place	2020-01-23 22:28:43 +01:00
normalization.sql	Search housenumbers with unknown address parts by housenumber term	2020-11-25 11:36:10 +01:00
place_triggers.sql	remove ST_Covers check when also testing for ST_Intersects	2020-09-23 17:44:31 +02:00
placex_triggers.sql	place nodes can only be linked once against boundaries	2020-12-02 15:31:02 +01:00
postcode_triggers.sql	move ordering out of getNearFeatures	2020-10-13 15:24:54 +02:00
ranking.sql	search rank 30 must always go with address rank 30	2020-11-24 17:57:28 +01:00
utils.sql	use computed centroid for location_area_large	2020-10-15 17:30:52 +02:00