Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

insert data in ES #88

Closed
harksin opened this issue Jan 15, 2016 · 3 comments
Closed

insert data in ES #88

harksin opened this issue Jan 15, 2016 · 3 comments
Assignees

Comments

@harksin
Copy link

harksin commented Jan 15, 2016

hi,

I trying to import osm data for mys city (pbf file) in ES.

i have a custom config file with only OSM.

when i execute "node index.js" i catch the following error.

2016-01-15T18:06:01.105Z - info: [admin-lookup:master] Initializing workers.
2016-01-15T18:06:01.259Z - info: [admin-lookup:worker:admin1] Loading `admin1`.
ShapeFileStream { [Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_adm1.dbf']
  errno: -2,
  code: 'ENOENT',
  path: '/mnt/pelias/quattroshapes/qs_adm1.dbf' }
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_adm1.dbf'
    at Error (native)
2016-01-15T18:06:01.290Z - info: [admin-lookup:worker:locality] Loading `locality`.
2016-01-15T18:06:01.296Z - info: [admin-lookup:worker:local_admin] Loading `local_admin`.
ShapeFileStream { [Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_localities.dbf']
  errno: -2,
  code: 'ENOENT',
  path: '/mnt/pelias/quattroshapes/qs_localities.dbf' }
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_localities.dbf'
    at Error (native)
ShapeFileStream { [Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_localadmin.dbf']
  errno: -2,
  code: 'ENOENT',
  path: '/mnt/pelias/quattroshapes/qs_localadmin.dbf' }
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_localadmin.dbf'
    at Error (native)
2016-01-15T18:06:01.317Z - info: [admin-lookup:worker:admin2] Loading `admin2`.
ShapeFileStream { [Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_adm2.dbf']
  errno: -2,
  code: 'ENOENT',
  path: '/mnt/pelias/quattroshapes/qs_adm2.dbf' }
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_adm2.dbf'
    at Error (native)
2016-01-15T18:06:01.343Z - info: [admin-lookup:worker:neighborhood] Loading `neighborhood`.
ShapeFileStream { [Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_neighborhoods.dbf']
  errno: -2,
  code: 'ENOENT',
  path: '/mnt/pelias/quattroshapes/qs_neighborhoods.dbf' }
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: ENOENT, open '/mnt/pelias/quattroshapes/qs_neighborhoods.dbf'
    at Error (native)

Do you have seen this error before ?
And could you help me to solve them ?

thanks a lots for your great works.

harksin.

@orangejulius
Copy link
Member

hey @harksin,
This error is the importer telling you it can't find the data files for Quattroshapes. While you're importing OSM, the data files for Quattroshapes are used to make sure all the imported records have values set for country, city, etc, since many OSM records don't have those.

You can fix this in one of two ways:
1.) Filling in these values (we call it admn lookup) can be disabled, and then quattroshapes isn't needed. Find the openstreetmap section of your openstreetmap config, and set "adminLookup": false.
2.) Download the quattroshapes-simplified.tar.gz from the link above (it's about 500MB), and configure your pelias config with the path to where you put these files (it looks like you've still got it set to the default). You can see a very simple example here.

Let me know if that works, enjoy!

@harksin
Copy link
Author

harksin commented Jan 18, 2016

@orangejulius thanks! It works fine now =)!!

Just 2 quick question :

  • there is a parameter to specify the pelias.json path ?
  • did you plan to provide pelias as docker container ?

@orangejulius
Copy link
Member

Glad it all works for you!

You can specifiy PELIAS_CONFIG=/path/to/your/pelias.json as an environmental variable before any of the importer commands, or use export PELIAS_CONFIG=... in your shell (or even in a settings file like .bashrc) to make more permanent changes.

We don't have any plans for docker containers at the moment but it's probably something we will look at eventually.

P.S. Looks like we've solved your issue so I'm closing this ticket. Feel free to ask us more questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants