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

OSM records with 'constructor' tag result in invalid Pelias documents #557

Closed
orangejulius opened this issue Aug 10, 2021 · 2 comments · Fixed by #558
Closed

OSM records with 'constructor' tag result in invalid Pelias documents #557

orangejulius opened this issue Aug 10, 2021 · 2 comments · Fixed by #558
Labels

Comments

@orangejulius
Copy link
Member

Back in pelias/pelias#867 we noticed that our name.* dynamic mapping had a strange entry:

In addition to expected fields like name.default, name.en, etc there was a dynamic name field with the key function Object() { [native code] }.

I was looking into language related data today and spent an extra moment to track down what was going on here.

It appears that OSM records with the non-standard constructor tag are the ultimate cause of this odd data.

The good news is there are only 60 records in all of OSM with this tag, and only 32 records ended up with the function Object() { [native code] } property in the planet build I was examining.

Still, we probably want to skip the constructor tag when importing :)

@orangejulius
Copy link
Member Author

@orangejulius orangejulius changed the title OSM Records with 'constructor' tag result in invalid Pelias documents OSM records with 'constructor' tag result in invalid Pelias documents Aug 10, 2021
@missinglink
Copy link
Member

Funny, nice catch

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

Successfully merging a pull request may close this issue.

2 participants