This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We have a client that ships from multiple warehouses using zones to determine | |
pricing. They maintain the zones in a Goole Maps document. We are creating a | |
front end that clients can enter their address and we'll show them what their | |
shipping options are. We will have the client export their zones as a KML | |
file and we'll import it into a MySQL database and use ST_Contains to find | |
the shipping zone(s) customers are in. (They can only be in one zone for any | |
given warehouse but may be within range of multiple warehouses.) | |
One thing to point out is there is confusion about the order of latitude and | |
longitude. Mathematically, it is naturally ordered "longitude, latitude" but |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<input pattern="/^(?:(\d+\/[1-9]\d*)|(\d*(?:(\s\d+\/[1-9]\d*)|\.\d+)?))$/"> | |
<!-- | |
(?: => non-capturing group, EITHER | |
(\d+\/[1-9]\d*) => any number of digits followed by a slash then any number of digits not beginning with 0 (fraction) | |
| => OR | |
(\d*(?: => zero or more digits followed by non-capturing group, EITHER | |
( | |
\s => a space | |
\d+ => any number of digits | |
\/ => a slash |
OlderNewer