BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.staging.osgeo.org//foss4g-2022//talk//NRSLYC
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-foss4g-2022-NRSLYC@talks.staging.osgeo.org
DTSTART;TZID=CET:20220825T093000
DTEND;TZID=CET:20220825T100000
DESCRIPTION:It seems to be conventional wisdom that a search engine for geo
 data is best implemented with a text search engine like OpenSearch or Solr
 . Most of available open-source geocoders follow that wisdom. Nominatim is
  the odd one out. OpenStreetMap's main geocoder was originally developed 1
 2 years ago as a proof of concept that a geocoder can be efficiently imple
 mented on top of a PostgreSQL/PostGIS database. Since then it has grown in
 to mature project. And so have the PostgreSQL database and the OpenStreetM
 ap project.\n\nIn this talk\, I will share some of the experiences of work
 ing with PostGIS on a growing OpenStreetMap dataset. The talk starts with 
 a quick overview about what the Nominatim database looks like under the ho
 od. It then goes on to present some of the lessons we have learned over th
 e last 10 years on managing a PostGIS database with more than 270 million 
 searchable places. We talk about features that improved performance and ab
 out some that are best avoided. The talk concludes with some general obser
 vation about implementing search on top of an SQL database.
DTSTAMP:20260403T222555Z
LOCATION:Room 9
SUMMARY:Building a Geocoder on top of PostGIS - a Field Report - Sarah Hoff
 mann
URL:https://talks.staging.osgeo.org/foss4g-2022/talk/NRSLYC/
END:VEVENT
END:VCALENDAR