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
I import addresses for Germany (oa, osm).
I'm useing "Whosonfirst" data for the whole planet. When importing oa and osm I get hundreds of messages: debug: [wof-admin-lookup] no country lon=12.847481, lat=50.448679, ....
I have checked many of the output coordinates. They are all very close to borders or to the coast.
Unfortunately I am not yet familiar enough with the data structures to find the problem myself. Is this a problem of the importers? Or is the problem to be found in the "Whosonfirst" data? The boundaries can only be approximated with polygons, so there could be addresses in the gaps.
The text was updated successfully, but these errors were encountered:
Adding on to what @missinglink said, we don't generally consider this debug message to be a problem. Certainly if there is a particular record not being associated with a country an you expect it should, examine the record and the polygon for the country to make sure they match up (either could have invalid data).
But, in general, this any any other debug message is safe to ignore. In fact, I wonder if this is another one we want to consider removing?
I import addresses for Germany (oa, osm).
I'm useing "Whosonfirst" data for the whole planet. When importing oa and osm I get hundreds of messages: debug: [wof-admin-lookup] no country lon=12.847481, lat=50.448679, ....
I have checked many of the output coordinates. They are all very close to borders or to the coast.
Unfortunately I am not yet familiar enough with the data structures to find the problem myself. Is this a problem of the importers? Or is the problem to be found in the "Whosonfirst" data? The boundaries can only be approximated with polygons, so there could be addresses in the gaps.
The text was updated successfully, but these errors were encountered: