Darren, That was delightfully dense. Do you think you could unpack it a bit more? Possibly some sample (pseudo) queries?
Upayavira On Wed, Aug 26, 2015, at 03:02 PM, Darren Spehr wrote: > If you wanted to try a spatial approach that blended times like above, > you > could try a polygon of minimum width that spans the globe - this is > literally using spatial search (geocodes) against time. So in this > scenario > you logically subdivide the polygon into 7 distinct regions (for days) > and > then within this you can defined, like a timeline, what open and closed > means. The problem of 3AM is taken care of because of it's continuous > nature - ie one day is adjacent to the next, with Sunday and Monday > backing > up to each other. Just a thought. > > On Wed, Aug 26, 2015 at 5:38 AM, Upayavira <u...@odoko.co.uk> wrote: > > > > > > > On Wed, Aug 26, 2015, at 10:17 AM, O. Klein wrote: > > > Those options don't fix my problem with closing times the next morning, > > > or is > > > there a way to do this? > > > > Use the spatial model, and a time window of a week. There are 10,080 > > minutes in a week, so you could use that as your scale. > > > > Assuming the week starts at 00:00 Monday morning, you might index Monday > > 9:00-23:00 as 540:1380 > > > > Tuesday 9am-Wednesday 1am would be 1980:2940 > > > > You convert your NOW time into a "minutes since Monday 00:00" and do a > > spatial search within that time. > > > > If it is now Monday, 11:23am, that would be 11*60+23=683, so you would > > do a search for 683:683. > > > > If you have a shop that is open over Sunday night to Monday, you just > > list it as open until Sunday 23:59 and open again Monday 00:00. > > > > Would that do it? > > > > Upayavira > > > > > > -- > Darren
