Open Jamie452 opened 4 years ago
Do you need addresses? They account for about half 88 percent of the index size?
See https://pelias-dashboard.geocode.earth/pelias for an idea of what size you can expect from a full planet build, you can roughly divide that by counts per layer to estimate the disk savings.
I'd be interested to understand better what you're trying to achieve because disk is cheap and you can filter these records at query-time if you don't want to see them.
I'm a little confused about how I might achieve what I'm trying to accomplish, without importing unnecessary data or running services I don't think I'd need to have running. I was wondering if someone could possibly point me in the right direction, or tell me if what I have in mind is even possible.
Basically, for my use case, I don't need the granularity of streets or postal codes, and was wondering how I might configure
pelias.json
for a full planet build without that data? I'm also wondering what sort of savings that would make in terms of required disk space? One thing I do need though is POIs/venues.From my understanding of what the interpolation service does, I don't believe I would need that either, especially if streets are being omitted. Can that service be down without affecting other parts of Pelias?