OK, the S2map presentation linked does a pretty good job of explaining things, but it lacks a good visualisation of the whole earth.
IITC now has a scoring cells plugin that'll give you a nice interactive map of all the cells, and http://ingress-cells.appspot.com/ will let you search individual cells and click to find out the names without touching IITC if you're wary of the Niantic TOS.
It's worth noting that the cells are only numbered along the hilbert curve at the lowest level, i.e. the final two digits - AM01 through AM16 are 'rows' reaching across the AM face (numbered north to south), and AM**-ALPHA through AM**-SIERRA are 'columns' reaching down the AM face, numbered west to east (n.b. this orientation changes for each face!). Therefore each face isn't really a complete Hilbert Curve
With that in mind:
- Where does the region s2 / hilbert curve start for the Americas face (AM)?
- The curve 'starts' with AM01-ALPHA-00 approximately 800 miles West of the coast of california.
- Where does it end?
- The highest numbered cell is AM16-SIERRA-15, approximately 500 miles ESE of Buenos Aires - note that this is NOT the SE corner of the Americas face (which is AM16-SIERRA-10) (see note earlier about cell numbering)
- How do the 6 faces line up?
- Is there a good argument for a well-defined start to the whole curve? On which face?
- As discussed above the cell numbering ISN'T really a complete curve. Not even along an entire face.
As for listing portals in 'cell order' - well that would be scraping the intel map and definitely a breach of the Niantic TOS ;-)
Postscript: Not all the NATO Phonetic Alphabet labels are used in 'column' names, here's the list:
ALPHA, BRAVO, CHARLIE, DELTA, ECHO, FOXTROT, GOLF, HOTEL, JULIET, KILO, LIMA, MIKE, NOVEMBER, PAPA, ROMEO, SIERRA
Excluded: Indigo, Oscar, Quebec - draw your own conclusions as to why!
The formulas in this post on glyph hacking are based on extensive field testing.
Relevant part from the post:
+------------+--------------------+------------+
| Portal lvl | Perfect hack bonus | Time limit |
+------------+--------------------+------------+
| 1 | +28% | 20s |
| 2 | +40% | 20s |
| 3 | +55% | 20s |
| 4 | +55% | 19s |
| 5 | +55% | 18s |
| 6 | +80% | 17s |
| 7 | +80% | 16s |
| 8 | +112% | 15s |
+------------+--------------------+------------+
Hack bonus:
Bhack = 10 ×
Gcorrect +
P ×
Bperfect
Speed bonus:
Bspeed =
P × ⌊100 ×
Tleft ÷
Tlimit⌋
AP:
APbase = 50 ×
Gcorrect
APbonus = 20 × P × 20.5×Gcorrect
AP = APbase + APbonus + Bspeed
where:
- P is 1 if all glyphs were drawn correctly and 0 otherwise (P = ⌊Gcorrect ÷ Gtotal⌋),
- Bhack is the hacking bonus,
- Gcorrect is the number of glyphs you got correct,
- Gtotal is the total number of glyphs in the sequence,
- Bperfect is the perfect hack bonus corresponding to the number of glyphs in the sequence, as shown in the table above,
- Bspeed is the speed bonus,
- Tleft is the time remaining on the clock,
- Tlimit is the total time you were given to draw the sequence, as shown in the table above,
- APbase is the amount of AP earned for correctly-drawn glyphs,
- APbonus is bonus AP earned for drawing all glyphs correctly,
- AP is the total amount of AP earned from the glyph hack. (Note: Does not include AP from hacking enemy portals.)
Example: Suppose you perform a perfect glyph hack on a L7 portal with 5 seconds left. Your hacking bonus would be 10% × 4 + 1 × 80% = 120% (4 correct glyphs and perfect hack bonus). Your speed bonus would be 1 × ⌊100 × 5 ÷ 16⌋ = 31% (5 out of 16 seconds left). Finally, you would earn 8 glyph hacking points and 50 × 4 + 20 × 1 × 20.5×4 + 31 = 311 AP.
Best Answer
At each checkpoint, all currently-standing fields in the region are measured. The region's team score is then averaged with any previous checkpoints in the cycle.
It's possible to use one very big field at one checkpoint to inflate that average for a while. (This is moderately common in my region, where one side is significantly outnumbered -- they can't keep lots of smaller fields up for an extended period of time because of lack of manpower, so they make up for it with planning and coordination to have short-lived but very large fields at least once per cycle.)
Fields need to be standing at checkpoint to count. If I make that two million MU field and it is taken down before checkpoint, it isn't measured or recorded in the scores -- just in my agent profile.