OpeningHoursEvaluator VS opening_hours.js

This year we had a GSOC student.work on a campanion evaluator to https://github.com/simonpoole/OpeningHoursParser (which BTW.is plenty fast enough, not quite sure while you felt the need to do something new), it hadn't been integrated in to anything yet, but I'll be working on that sometime this.month. See https://github.com/goodudetheboy/OpeningHoursEvaluator

Yeah, the country location is a requirement to show the opening hours. The library (https://github.com/opening-hours/opening_hours.js) is aware of holidays in many countries, but for that it needs to know what country a POI is in.

The country awareness source code is here: https://github.com/pietervdvn/latlon2country

The idea: I've taken all the country boundaries from OSM (via nominatim); I slice them in four parts. If the resulting geojson is too big, I slice this again until I have small geojsons, suitable to download. If you know the zoomlevel and location, one can use the standard slippy-tile-index to fetch the correct tile. (Alternatively, if the entire tile is within a country, it'll just return the country code)

However, the client also needs to know what zoomlevel there is. For that, I built a search tree.

It's been a while though, so I've forgotten some of the details ;)

In the mean time the JS library already provides a powerful tool that should fit your needs : https://openingh.ypid.de/evaluation_tool/. This library is more permissive than my implementation compared to the specification, I'm not sure if it is a good or a bad thing.

Currently it is not possible to specify this, see https://github.com/opening-hours/opening_hours.js/issues/252