This is a static archive of our old OpenStreetMap Help Site. Please post any new questions and answers at community.osm.org.

nominatim problem after installing TIGER data

Hi,

I'm trying to install TIGER data on a local Nominatim server.

During the first step in the installation, I started seeing errors like the one pasted below (only for numbers larger than about 60000).

After installing the TIGER data (as specified at the bottom of the installation instructions page) it stopped working fine.

Reverse geo queries return blank pages, if I view the source I only see "1" on the page. Geo coding queries seem not to find any results.

The table location_property_tiger still exists.

Any clues? Thanks, Raz

Traceback (most recent call last):
  File "/home/raz/Downloads/Nominatim-2.1/utils/tigerAddressImport.py", line 4064, in <module>
    shape_to_osm( shape, osm, id )
  File "/home/raz/Downloads/Nominatim-2.1/utils/tigerAddressImport.py", line 3955, in shape_to_osm
    parsed_features = parse_shp_for_osm( shp_filename )
  File "/home/raz/Downloads/Nominatim-2.1/utils/tigerAddressImport.py", line 3475, in parse_shp_for_osm
    tags.update( fipsstate(statefp, countyfp) )
  File "/home/raz/Downloads/Nominatim-2.1/utils/tigerAddressImport.py", line 3344, in fipsstate
    county = county_fips[county_fips_code]
KeyError: '60010'
Failed parse (/data1/EDGES/tl_2013_60010_edges.zip)

tiger nominatim

asked 19 Jan '14, 08:00

RazAlon
61●9●9●14
accept rate: 0%

edited 20 Feb '14, 11:56

Can you check if the table location_property_tiger still exists in your DB?

(20 Jan '14, 08:20) lonvia

yes, it's there

(20 Jan '14, 12:00) RazAlon

One Answer:

Your problems are not related to the error messages you got during import. They just indicate that some edge files couldn't be processed and have been skipped. All other edge files will have worked fine.

To find the source of your problem you need to find out more about what exactly happens when sending the requests. A few places to start looking:

Check the postgresql log for errors.
Run the query with the additional parameter debug=1. It should give you a lot of debug output. See if you can find something about an SQL error there.
Make sure the php code has not been modified and there are no syntax errors in setting/local.php.

answered 21 Feb '14, 12:32

lonvia
6.2k●2●57●89
accept rate: 40%

thank you for the advice. it was due to "www-data" versus "apache" username. I should have imported the TIGER data before changing the username, or, change back, import, and change back again... :)

(27 Feb '14, 11:39) RazAlon