The Data and Engine Behind ELA Map

Photo: Patrick Hendry / Unsplash

ELA Map runs on NASA/JPL's own DE440 planetary ephemeris — the same data used to navigate spacecraft — wrapped in an engine we built specifically for mapping a chart across the whole Earth. Planetary positions agree with NASA's reference to within a tenth of an arc-second, and the engine re-checks itself against NASA's live service every hour. The interpretations on top of that come from transparent, named astrological doctrine — not a language model improvising. That combination is what we mean by Personalized Geographic Intelligence.

There's a lot of astrology software on the internet, and a fair amount of it is exactly what a skeptic assumes: a thin layer of generated text over numbers nobody checked. We built ELA Map because we wanted the opposite — a tool we'd trust with a real decision about where to live. That meant getting unglamorous about two things almost nobody asks an astrology product: where do the numbers come from, and who is writing the words. This page answers both, honestly.

Where the numbers come from

Most astrology tools compute planetary positions from Swiss Ephemeris — a good library, and a compressed derivative of older NASA data from the 2000s. ELA Map doesn't use the derivative. It uses the source: JPL DE440, the Jet Propulsion Laboratory's development ephemeris, in the same binary kernel format NASA distributes for mission work. The positions that place Mars on your map are computed from the same dataset used to point antennas at actual spacecraft.

That data covers the years 1550 to 2650 CE, which comfortably spans any birth chart and any relocation you'll ever run. It's not a model we trained or a table we typed. It's the authoritative planetary record, used directly.

This is the part we're a little stubborn about, because it's the foundation everything else stands on. If the positions are off, every line on the map is off with them, and no amount of beautiful interpretation can save a reading built on a wrong number.

Astronomy and astrology were never two trades

It's worth saying plainly, because the modern world pretends otherwise: for most of recorded history, astronomy and astrology were a single discipline, and the math was developed in service of the practice. The Babylonians kept the sky's records because the positions meant something to them. Ptolemy compiled the first great star catalog in the Almagest — as an astronomer, for astronomical needs — and then wrote the Tetrabiblos on what those positions signified; the same hand did both. Kepler refined planetary motion while casting charts for a living. The ephemeris tables that later made navigation and astronomy possible were, in their origin, tools for knowing where the planets were so a practitioner could read them.

That shared root matters here for a specific reason: improving the astronomy has never broken the astrology. As one old commentary on Ptolemy put it, his astrology "is just as applicable to modern and improved astronomy as it was to his own." Better numbers don't dissolve the tradition — they sharpen it. A line drawn from a position good to a tenth of an arc-second lands on the correct side of a mountain range; a line drawn from a rough one doesn't. The interpretive craft is centuries old. What changed is that we can finally feed it positions worthy of it.

That's why ELA Map went to the cutting edge of computation rather than settling for "close enough." Not to replace the tradition with technology, but to give an old, careful practice the precise sky it always assumed it had — and to bring it to life on a map of the whole Earth, which the people who built the tradition could only have dreamed of.

An engine that checks itself against NASA, every hour

Using good data once is easy. Knowing your software is still producing it — after a library update, a server migration, a subtle compilation change — is the part that usually gets skipped.

ELA Map's engine doesn't skip it. Running quietly in the background is a process we think of as its immune system: once an hour, it takes its own freshly-computed planetary positions and compares them against NASA's live JPL Horizons service — the public, authoritative ephemeris NASA itself runs. If our numbers ever drift from NASA's by more than a tenth of an arc-second, the system flags it before it can ever reach a chart.

A tenth of an arc-second is roughly the width of a coin seen from forty miles away. We hold ourselves to that, continuously, against NASA's own answer. Most astrology software has no idea whether it's still accurate. Ours asks, every hour, and keeps the receipt.

Why we had to build our own engine

If the data is NASA's, what did we actually build? The engine that turns it into a map.

Casting a single birth chart is a solved problem — fix a time and a place, compute a few angles, done. Casting your entire chart against every point on the surface of the Earth is a different kind of problem, and it's the one ordinary astrology libraries were never designed for. They cast one chart at a time. We needed to compute, for every body, the lines where it was rising, setting, overhead, and underfoot — sweeping the whole globe — and then the points where those lines cross, and the deeper crossings (the parans) where two bodies reach the angles together at the same latitude. That last one is solved numerically, converging on each crossing to a precision far finer than any pixel could show.

Doing all of that across a planet's worth of coordinates, fast enough to feel instant, is the work. It's also why ELA Map can do things that are genuinely hard to find elsewhere — full-globe relocation analysis, region-wide scoring, multi-chart overlays, the relationship between two people read across the Earth. Those aren't features we bolted on. They fall out of having built the right engine underneath.

One birth chart, every planet's four lines, computed against the entire surface of the Earth at once. This is the whole-globe view the engine was built to produce — the thing a one-chart-at-a-time library can't.

What "Personalized Geographic Intelligence" actually means

Precise astronomy is half of it. The other half is the writing — and here we made a deliberate choice that runs against the current.

Every interpretation in ELA Map comes from named, written astrological doctrine: a defined body of rules and meanings, authored deliberately, applied consistently. Ask the same question twice and you get the same answer, because the answer is derived, not improvised. You can disagree with the doctrine — people have argued about astrology for three thousand years and will keep arguing — but you can always see exactly which tradition produced the sentence in front of you. Nothing is being made up on the spot to sound profound.

That is the precise opposite of pointing a language model at your chart and printing whatever it free- associates. Personalized Geographic Intelligence is the join of the two halves: NASA-grade positions underneath, transparent human doctrine on top, personalized to your chart and the specific place you're asking about. Accurate, location-aware, and yours to trust — and able to show its work.

How we keep ourselves honest

A few disciplines, stated plainly, because "trust us" isn't an argument:

• Determinism. The same birth data produces the same chart, every run, on every machine. No randomness, no drift, nothing that changes between page loads.
• The hourly NASA check. Described above — continuous validation against JPL Horizons.
• Reference charts. The Human Design and astrology engines are tested against independently-published reference charts, so a regression that moved a gate or an angle gets caught before release.
• Transparent doctrine. Every interpretation is traceable to a named source rather than a generated guess.

None of this makes astrology a science. It makes ELA Map honest software — the numbers are real and checked, the logic is fixed and inspectable, and we don't pretend a machine's improvisation is insight.

What it unlocks

• Astrocartography Fundamentals — the four-angle mechanics this engine computes across the globe.
• Human Design Cartography — the same precision, applied to your HD gates and channels.
• Family Astrocartography — reading one place against a whole household.
• The Heatmap Engine — how ELA Map scores a whole region at once instead of one line at a time.

Frequently asked questions

Is ELA Map's astrology written by AI? No. Every interpretation comes from named, written astrological doctrine applied the same way every time — not a language model improvising text. The same chart always produces the same reading, and you can see which tradition each statement comes from.

What planetary data does ELA Map use? NASA/JPL's DE440 ephemeris — the development ephemeris JPL distributes for spacecraft and mission work — used directly, not via a compressed third-party derivative. It covers 1550–2650 CE.

How accurate is it, really? Planetary positions agree with NASA's own JPL Horizons service to within about a tenth of an arc-second, and the engine re-verifies that automatically every hour. (Some derived quantities, like house cusps, carry the normal slightly wider tolerances of any astrology software — we'd rather tell you that than round it up.)

How is this different from other astrocartography websites? Two ways: the data is NASA's source ephemeris rather than a derivative, continuously checked against NASA itself; and the interpretations are transparent named doctrine rather than generated text. The engine was also built specifically for whole-globe, multi-chart work, which is why it can do things single-chart tools can't.

---

Join the waitlist → and be among the first to see your birth chart drawn as a living map of the Earth.