Closed Joxit closed 5 years ago
This is the by-product of an indexing bug that should be fixed later today. Once all the code has been updated we will rebuild all the SQLite distributions.
Apologies for the inconvenience.
Related: https://github.com/whosonfirst/go-whosonfirst-geojson-v2/issues/4
Okay, this is being caused by a logic error in the go-whosonfirst-sqlite-features-index
package that was introduced as part of the work to include "alt" files in distributions:
https://github.com/whosonfirst/go-whosonfirst-sqlite-features-index/blob/master/index.go#L33-L35
I will disable this for the time-being and explicitly disable indexing alt files in this package until suitable LoadWOFFeature
methods can be updated to accomodate alt files (or equivalent)
OK, thanks :-)
Be careful with LoadWOFFeatureFromReader
, I tried this in my PR and I got some troubles on a full export... See: https://github.com/whosonfirst/go-whosonfirst-sqlite-features-index/pull/2#issuecomment-523538815
This should be fixed as of release 0.1.4
but I will leave this issue open until we produce a new batch of SQLite distributions.
$> ./bin/wof-dist-build -workdir ./ whosonfirst-data-postalcode-it
$> bunzip2 whosonfirst-data-postalcode-it-latest.db.bz2
$> sqlite3 whosonfirst-data-postalcode-it-latest.db
SQLite version 3.24.0 2018-06-04 14:10:15
Enter ".help" for usage hints.
sqlite> SELECT id,name,parent_id,placetype FROM spr WHERE id=504792239;
504792239|66045|-1|postalcode
Okay, thank you @thisisaaronland :smiley: I will build my SQLite tomorrow then
It seems to work on a full planet build ! :+1: thanks again :smile:
Excellent, thanks for the report. I will kick off a rebuild of postalcodes shortly.
I have the same issue as this one https://github.com/whosonfirst/go-whosonfirst-geojson-v2/pull/3 but now for SQLite exports.
In the spr table I have this kind of entries:
names, placetypes, country... looks wrong