You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :)
The text was updated successfully, but these errors were encountered:
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
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 keyfunction 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 :)The text was updated successfully, but these errors were encountered: