This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
admin:features:geo:indexing [2012/02/22 23:47] doc |
admin:features:geo:indexing [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 34: | Line 34: | ||
| **Example** | **Example** | ||
| - | <code sql> | + | <code> |
| create table "ZIPCODES" | create table "ZIPCODES" | ||
| physical "dat/zipcodes.dat" | physical "dat/zipcodes.dat" | ||
| Line 57: | Line 57: | ||
| Geographic coordinates are indexed in a multi-column Omnidex index containing first the **longitude and then the latitude**. This index will then be available for use in optimizing the [[dev:sql:functions:distance|$DISTANCE function]] in SQL SELECT statements. | Geographic coordinates are indexed in a multi-column Omnidex index containing first the **longitude and then the latitude**. This index will then be available for use in optimizing the [[dev:sql:functions:distance|$DISTANCE function]] in SQL SELECT statements. | ||
| - | <code sql> | + | <code> |
| create table "ZIPCODES" | create table "ZIPCODES" | ||
| physical "dat/zipcodes.dat" | physical "dat/zipcodes.dat" | ||