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

pbf2json to Pelias Interpolation. JSON invalid #191

Open
jvelazquez90 opened this issue Feb 27, 2019 · 6 comments
Open

pbf2json to Pelias Interpolation. JSON invalid #191

jvelazquez90 opened this issue Feb 27, 2019 · 6 comments

Comments

@jvelazquez90
Copy link

Hello,
Implement Pelias geocoder in a personal project where also with the help of ogr2osm transform an address shape file into
an OSM layer. My doubt arises when creating address.db in Pelias Interpolation. I convert the osm.pbf file into a json format with
pbf2json but when creating the base of addresses in sqlite I get json errors invalid. Some addresses can be searched
with pelias and throws the results very well but I lose information. My question is what information does Pelias Inteporlation accept?
pbf2json?

@missinglink
Copy link
Member

Yes, it is designed to take the output of pbf2json for the openstreetmap importer.

The documentation can be found here: https://github.com/pelias/interpolation/blob/master/readme.md#osm

Can you please paste some of the errors?

@jvelazquez90
Copy link
Author

Obviously I was doing wrong the execution command in the tags entered keys that did not exist.

@jvelazquez90
Copy link
Author

Hello, now my problem is when I create the street.db file I get the following error:
street has no valid names, check your 0sv file:
this file does not exist in my directory only the polylines file.

@missinglink
Copy link
Member

missinglink commented Mar 5, 2019

The file extension .0sv is the one we've given to denote a polylines file.
It's just a confusing error message.

I believe it's just a warning and not a fatal error?
What it's warning you about is that one or more of the polylines in the file do not also have a street name (it requires BOTH a shape and a name)
I wouldn't worry about it, it's possibly due to errors in the openstreetmap data, it's only a problem if you are getting thousands of them.

@jvelazquez90
Copy link
Author

Obviously it is a warning but the problem is that I am getting many of them.
Transform a shape file to osm and generate the polyline, I do the same with the heights I transform a shape file to json of directions.
When using Pelias Interpolation I generate the file street.db and when I want to generate the file addresses.db it is where I get the warning.
If I start the Interpolation service and use it with Pelias I can search for addresses but I lose the vast majority of loaded addresses.

@jvelazquez90
Copy link
Author

osm
osm1

These are my 2 osm files generated for use with Pelias Interpolation: microcentro_street and microcentro_addresses.
The 2 files were generated from the same shape.

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

No branches or pull requests

2 participants