From: Regina Obe <lr@pcorp.us>
Date: Thu, 24 Feb 2011 17:39:13 +0000 (+0000)
Subject: fix typo
X-Git-Tag: 2.0.0alpha1~1939
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=770e61b5eb93f69f675370d7e09481379ceda97f;p=postgis

fix typo

git-svn-id: http://svn.osgeo.org/postgis/trunk@6862 b70326c6-7e19-0410-871a-916f4a2858ee
---

diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml
index 8859728e0..8ee1a5c4a 100644
--- a/doc/extras_tigergeocoder.xml
+++ b/doc/extras_tigergeocoder.xml
@@ -24,7 +24,7 @@
 		<note><para>The <varname>tiger</varname> schema must be added to the database search path for the functions to work properly.</para></note>
      </sect1info>
      
-     <para>There is another geocoder for PostGIS gaining in popularity and more suitable for international use.  It is called <ulink url="http://wiki.openstreetmap.org/wiki/Nominatim">Nomatim</ulink>
+     <para>There is another geocoder for PostGIS gaining in popularity and more suitable for international use.  It is called <ulink url="http://wiki.openstreetmap.org/wiki/Nominatim">Nominatim</ulink>
      and uses OpenStreetMap gazeteer formatted data.  It requires osm2pgsql for loading the data, PostgreSQL 8.4+ and PostGIS 1.5+ to function.  It also a webservice interface and was more designed to be call as a webservice.
      Just like the tiger geocoder, it has both a geocoder and reverse geocoder component.  From the documentation, it is unclear if it has a pure SQL interface like the tiger geocoder, or if a good deal of the logic is implemented in the web interface.</para>