How often are online LoPoints updated?
Need Answer
Hey guys,
how often are LoPoints updated? I do a lot of mapping in the openstreetmap community. While changes to e.g. streets and pathes are updated very quickly in the online LoMap (2-3 days), changes to POIs aren't reflected in LoPoints (even after one month). I cleaned the cache by the way.
Best regards, Steffen
The same question
In my experience, it actually takes quite a long time, often 3-4 weeks or even longer. At the moment, LoPoints from POIS that I entered into OSM in mid-November are missing.
In my experience, it actually takes quite a long time, often 3-4 weeks or even longer. At the moment, LoPoints from POIS that I entered into OSM in mid-November are missing.
Hello Steffen,
Usually the database update runs approx. once a week, or more exactly 4-5 times a month. Sometimes we disable the updates because of some migration e.t.c. And sometimes updates break. This is actually happening right now. I have fixed the updating mechanism. Public database should be updated in a couple of days. Sorry for this inconvenience, gap so long is not a norm.
Hello Steffen,
Usually the database update runs approx. once a week, or more exactly 4-5 times a month. Sometimes we disable the updates because of some migration e.t.c. And sometimes updates break. This is actually happening right now. I have fixed the updating mechanism. Public database should be updated in a couple of days. Sorry for this inconvenience, gap so long is not a norm.
Thanks Radim, there's no hurry, I was just curious.
Thanks Radim, there's no hurry, I was just curious.
"... once a week, or more exactly 4-5 times a month ..." does not seem to be the norm. The last update was also about 4 weeks ago... But there are worse things. ;)
"... once a week, or more exactly 4-5 times a month ..." does not seem to be the norm. The last update was also about 4 weeks ago... But there are worse things. ;)
So I will be doing a bunch of schoolboy excuses here. There used to be a powerful server machine in datacenter A. That datacenter had cooling leak. That was bad! That affected many other servers and miles of cables. Large outage! Luckily, our powerful server machine survived. Datacenter A claims they have fixed all hardware and cables. Life goes back to normal. Until it doesn't. Powerful server machine starts to exhibit weird, random errors. So we run tests. We try to examine. There must be solution! All in vain, decision to migrate all functionality to datacenter B has been made. From now, new powerful server machine runs updates in Cycle, Eat, Sleep, Repeat style. There should be regular updates for both routing and POIs from now.
So I will be doing a bunch of schoolboy excuses here. There used to be a powerful server machine in datacenter A. That datacenter had cooling leak. That was bad! That affected many other servers and miles of cables. Large outage! Luckily, our powerful server machine survived. Datacenter A claims they have fixed all hardware and cables. Life goes back to normal. Until it doesn't. Powerful server machine starts to exhibit weird, random errors. So we run tests. We try to examine. There must be solution! All in vain, decision to migrate all functionality to datacenter B has been made. From now, new powerful server machine runs updates in Cycle, Eat, Sleep, Repeat style. There should be regular updates for both routing and POIs from now.
Replies have been locked on this page!