matt on 26 Dec, 2017 09:39 PM
i only pull OSM updates once every several months, the next one should hopefully be sometime in January. There are a handful of technical reasons why I have to start from scratch and do a full import rather than using their daily/weekly incremental updates, the biggest being the distance labels I put on lines.
matt on 10 Jun, 2018 02:56 AM
I'm too busy with development work to be able to adhere to a fixed schedule. I aim for quarterly but it's generally been more like 3x/year.
I'm going to roll out a new update in the next couple days, but because I was using that dataset to create nationwide mapbuilder coverage for caltopo/sartopo offline before swapping into the production database, it's already 4-6 weeks stale. When did you make your edits?
matt on 16 Nov, 2018 09:42 PM
There is one coming shortly (as in it's done, I just need the right time to deploy it). I think I have the system down at this point, but this one was delayed due to figuring out how to load Canadian data (contours, non-OSM hydrology).
matt on 10 Jan, 2019 06:17 PM
It's all via OSM (or other government databases like the National Hydrology Dataset), I don't maintain any separate user-submitted changes.
I aim for roughly quarterly updates, but it varies depending on operational needs. Sometimes I might hold an update for code changes, other times I need to accelerate it - I'm about to do another one since I need to pull in some attributes (sidewalk, sac_scale) that aren't in the default osm2pgsql style, to support some visual changes.
Unfortunately it's a full import from scratch as I haven't figured out how to integrate weekly OSM updates with the PostGIS topology table used for trail distances.