error: invalid character 'v' looking for beginning of value about go-whosonfirst-pip-v2

[thisisaaronland]

Thanks, I will investigate. That suggests that one of the underlying GeoJSON records was improperly encoded.

[HIRANO-Satoshi]

Thanks for your reply.

Sorry, I should do something related to git in ~/whosonfirst-data.

git lfs fetch
git lfs checkout

[thisisaaronland]

Ugh... yes, "git lfs". This is a perennial problem and one we're not entirely sure how to deal with, outside of better (more prominent) documentation. The issue is two-fold:

1. GitHub (or any other hosted service provider) will always have a ceiling on file sizes, at least for the foreseeable future
2. Any given WOF record will have a "ground truth" geometry (in addition to any other simplified versions, etc.) which, like Mandel's map of England, will only grow in size as measuring instruments get precise.

Currently this is only a problem for New Zealand (and the meta files, discussed below) which has a > 100MB geometry but since it could potentially happen for any country we have chosen to force the issue now. I apologize that you've gotten caught up in the ongoing work to make this easier than it is. You're not the only one... :-P

So in the meantime, yes: You need to remember to do the git lfs dance. If you can suggest or recommend some place in the documentation where it would be useful for us to bring this to people's attention that would be very helpful.

As mentioned "meta" files are being phased out of the core (Git) distributions in favour of cross-platform binary tools for generating them on demand or when a repo is updated, via Git hooks. This has been rolled out for all the repos except whosonfirst-data which does both for now:

https://github.com/whosonfirst-data/whosonfirst-data/blob/master/meta/README.md