# GeoGraphics

Since Version 10.0 of the Wolfram Language, GeoGraphics allows a simple and general way of constructing maps of the surface of the Earth and other celestial bodies. GeoGraphics combines the powerful Graphics functionality with fast and highly precise geodetic computations and also direct access to the Wolfram Knowledgebase through the Entity framework.
The fundamental new ingredient in GeoGraphics with respect to standard 2D Graphics is the fact that the surface of the Earth is curved and therefore must be distorted to produce a flat map (on a piece of paper or the computer screen). This always requires a choice of a cartographic projection, a function that determines how points on the curved surface are mapped to points on the flat map. The GeoProjectionData paclet provides a large collection of projections.
GeoGraphics also introduces new graphical primitives like GeoPath, GeoDisk, and GeoHemisphere, adapted to the Earth's curvature, and even time-dependent geo primitives like DayHemisphere and DayNightTerminator.
The GeoGraphics functionality can easily access the Wolfram Knowledgebase to obtain geographical information using the Entity framework, providing homogeneous access to a large number of properties about dozens of types of objects, from countries and cities to bridges, earthquakes, and artificial satellites.
GeoGraphics is also fully integrated with the geodesy functionality of the Wolfram Language, extensively updated for Version 10.0. This functionality is now much faster and precise to millimeters on the surface of the ellipsoidal Earth. GeoPosition allows specification of any position on the Earth, in any of the large collection of ellipsoids of GeodesyDatafor example, the WGS84 reference used by GPS satellites.
This tutorial provides an introduction to GeoGraphics and its associated functions. The tutorial starts by showing how to easily construct maps of arbitrary regions or geographical entities, letting GeoGraphics choose appropriate coordinate ranges, projections, etc. for you. Then it explains how you can choose all those options to fine-tune the maps to your needs.
Basic Mapping
The simplest and most important operation is obtaining a map of a given region of interest. The Entity framework provides a fast and homogeneous way to obtain the required positional information. GeoGraphics will then choose an adequate projection, generally the "Mercator" projection for small to medium scales (under 2000 km diagonally, approximately).
 GeoGraphics[primitives,options] draw a map
Main mapping command.
A map of France. Type CTRL= and then the word "France" to get the entity:
A map of New York City:
With no argument specification, GeoGraphics gives by default a map of your local area, as determined by \$GeoLocation, with a radius of around 10 miles.
The current \$GeoLocation, returned as a GeoPosition[{lat,lon}] object:
A map around that geo location:
Maps of the whole world are obtained by using the option value GeoRange"World". Such maps are given by default using the so-called "Equirectangular" projection, in which the horizontal axis is exactly longitude and the vertical axis is exactly latitude. Similarly, GeoRange"Country" gives a map of your country, and GeoGraphics will choose a projection that minimizes distortion of the map.
A map of the world:
A map of your country, again as determined by \$GeoLocation:
Discover which projection was used:
Or which ranges of latitude and longitude (in degrees) were selected:
The options GeoRange, GeoRangePadding, GeoCenter, and GeoZoomLevel allow multiple ways of specifying the regions of interest. They will be studied in detail later on in this tutorial.
Give explicitly the ranges of latitude and longitude:
Specify a center and a zoom level:
You can also change the zoom level of an image without changing its geo range. This results in increasingly more detail:
But then maps are increasingly larger in size:
So far maps have been produced showing the geo background image corresponding to a given region. The GeoGraphics language provides a variety of objects, called geo primitives, that can be placed on the map. These geo primitives can be point-like (Point or GeoMarker), line-like (GeoPath, GeoCircle, Line, ...), or area-like (GeoDisk, GeoHemisphere, Polygon, ...).
Place markers at the capitals of South America:
The geodesic curve from Santiago de Chile to Madrid. It is not a straight line in this projection:
A disk of 60 miles around Chicago, by default with low opacity so that it can be seen through:
A polygon covering the United States, again with default low opacity:
There are multiple ways to stylize a map. You can add parallels and meridians, a scale bar, or change the geo background to depict a relief map of elevation data or a contour plot. You can change colors and opacities, or even place images inside 2D geo primitives like geo disks or polygonsand many more options.
A map of Spain and Portugal with latitude and longitude lines separated 1 degree and a scale bar in kilometers:
A relief map of the same area showing geo elevation data:
Place the Spanish flag over the country:
Maps of other celestial bodies (planets and moons) are also possible.
The near side of the Moon (longitude 0 is defined to be oriented toward Earth):
A map of the area around Olympus Mons on Mars:
Geographical Locations and Computations

### GeoPosition and Geo Entities

Specific locations on the Earth are given as GeoPosition[{lat,lon}] objects, with latitude and longitude coordinates given in degrees, with standard conventions. GeoPosition can also convert other forms of input into that notation for convenience, including geographical Entity and EntityClass objects.
 GeoPosition[{lat,lon}] position on the surface of the Earth Entity["type",name] entity of a given type EntityClass["type",name] class of entities of a given type, equivalent to a list of entities
Location specification.
The coordinates of the North Pole:
They can also be obtained as follows:
Coordinates can also be provided in degree-minute-second (DMS) string form:
Give angles as Quantity objects, in any unit:
Convert geographical Entity data into numeric coordinates:
Internally, GeoPosition calls EntityValue to get that information:
GeoPosition can also handle arrays of coordinates. This is useful for working efficiently with many points at the same time. Points of the array can be given in different notations, and GeoPosition will convert them all to numeric coordinates.
Convert a list of entities:
An EntityClass object is interpreted as representing the list of its members:
Extract geo location EXIF information from a picture:
Convert different types of objects simultaneously:

### Distances and Bearings (Angles)

Together with the coordinate positions of given locations, it is generally important to know distances between any two of them, as well as the compass direction you need to follow to go from one to another. Distances are computed along geodesics, i.e. basically the shortest curve between two positions. Angles are given as bearings, namely the angle from the north to that geodesic line, measured clockwise in degrees. In the Wolfram Language, distances on the surface of the Earth are measured with GeoDistance, and bearings are computed with GeoDirection.
 GeoDistance[loc1,loc2] geodesic distance between two locations GeoDirection[loc1,loc2] angle from north at loc1 of the geodesic from loc1 to loc2 GeoDisplacement[loc1,loc2] distance and angle at loc1 of the geodesic from loc1 to loc2 GeoDestination[loc1,displ] end position of the geodesic given by displ starting at loc1
Geodesic displacements.
Take the approximate center positions of two cities:
This is the geodesic between those points:
Distance between them:
The result is given as a Quantity object with units determined by your \$UnitSystem:
To change to any other unit, use UnitConvert:
You can also modify the unit system required in the GeoDistance call itself:
You can use the Entity objects directly to compute distances, but then the Wolfram Language functions try to use polygonal information, when available, rather than purely point-like positions. That means that GeoDistance will return the smallest possible distance when considering all points of the polygons.
Distance between the borders of New York and Paris:
It is smaller than the distance obtained before from center to center:
The distance between centers can also be computed using the DistanceFunction option of GeoDistance:
This map shows the position of the center with respect to the polygon of the city:
Bearings are computed with GeoDirection. Currently this function does not handle polygonal information, only positional information. A warning message is issued when appropriate.
This is the bearing of the geodesic from New York to Paris, measured at New York:
Express the result in DMS form:
GeoDirection always uses center positions; hence, the previous result equals the following:
This is the bearing of the same geodesic, but now from Paris to New York:
GeoDisplacement reports both distance (in meters) and bearing (in degrees):
Knowing the geo displacement and the initial position, it is possible to recover the final position:

### Relational Positioning

Given a location, it is frequently important to know instances of a particular type of entity that are at a short distance from it. This is the role of the function GeoNearest. If the locations or entities are extended, you may also be interested in inclusion relations.
 GeoNearest[enttype,loc] entities of type enttype closest to loc GeoIdentify[enttype,loc] entities of type enttype that contain loc GeoEntities[reg,enttype] entities of type enttype contained in the region reg GeoWithinQ[reg,loc] check whether loc is contained in the region reg
Distance relations among entities and locations.
Find the nearest ocean or sea to your current location:
Find the four nearest countries to a given location, sorted by distance to the border:
Find all cities within 10 miles around Bath, UK, also sorted by distance:
Other relations are essentially derivates of GeoNearest. For example, GeoIdentify returns all entities containing a given location, by default your current geo location.
All available entities containing the current geo location:
They are entities of various types:
Vice versa, GeoEntities lists the entities contained in a given extended entity.
Famous buildings in Dallas:
The function GeoWithinQ checks inclusion of a geographical location (extended or not) inside a geographical region.
Check that Chicago is inside the state of Illinois:
The island of Tenerife is in the Atlantic Ocean, not in the Mediterranean Sea:
All these computations are sent to the Wolfram geo server, and results are then downloaded from it. In some cases it is possible to perform the operations locally using Nearest.
This variable reports your current country:
Take the points of the boundary of its polygon:
Find out which of those points is closest to your current location:
Draw the geodesic as an arrow:

### Geo Entity Variants

Sometimes you want a map of the main area of a country, without including smaller islands or dependencies that may be very far away. Or you may need a map including all territories. In those cases, the Wolfram Language specifies the additional information using the head GeoVariant.
 GeoVariant[entity,variant] a geographical variant of an entity
Geo entity variants.
The default map of the US only includes the conterminous states:
This map includes all areas:
Something intermediate is given by the variant "PrincipalArea" and its downsampled form "SimplifiedArea". In this case the US map includes Alaska and Hawaii:
The variant used by default in the maps is called "DefaultMapArea":
Other geo functions can also handle geo entity variants. However, the defaults are not necessarily the same. For example, the default variants for GeoNearest are sometimes larger than the corresponding defaults in GeoGraphics.
The default geo variant in GeoNearest is "PrincipalArea":
Therefore, the result may be different when you change the variant:

### \$GeoLocation and FindGeoLocation

The Wolfram Language can determine your approximate location using GeoIP information. This is done with FindGeoLocation, and the result is stored in the global variable \$GeoLocation. The variable Here is an alternative way of accessing the current geo location. Many of the functions related to GeoGraphics will default to that position when location information is not provided. You can manually set \$GeoLocation to any other position you want, and then your Wolfram Language session will behave as if you were at that position. When the value of \$GeoLocation is set, the variables \$GeoLocationCity and \$GeoLocationCountry are automatically assigned to the city and country containing \$GeoLocation, or the nearest possible city and country. Note that changing your \$GeoLocation does not automatically change \$TimeZone.
 \$GeoLocation resettable variable containing your current geo location Here a simpler way to obtain your current geo location \$GeoLocationCity nearest city to your current geo location \$GeoLocationCountry nearest country to your current geo location FindGeoLocation[] find your current geo location using GeoIP information
Current location.
The current \$GeoLocation:
This is an equivalent object:
Therefore:
Change \$GeoLocation to some other position:
Now local maps are maps of New York:
Change back to your current location:
Use FindGeoLocation to find approximate locations for addresses.
Ranges of Coordinates and Projections

### Latitude and Longitude: GeoRange

The most general way of specifying the region covered by a map in latitude and longitude coordinates is using the option GeoRange{{latmin,latmax},{lonmin,lonmax}}. As usual, the angles are given in degrees, with standard conventions. Any other specification of a geo region is eventually converted internally into one such range specification, perhaps extended as determined by the GeoRangePadding option.
 GeoRange option of GeoGraphics that specifies the ranges of the map
Geo range specification.
GeoBounds computes the latitude and longitude ranges of any geographical region:
A map using the "Equirectangular" projection will show that region with axes corresponding to those coordinate ranges. When using a specific numerical geo range, there is no padding added:
The "World" geo range corresponds to the whole world, by default {{-90,90},{-180,180}}:
The two halves of the world:
Longitudes {lonmin,lonmax} can be given in any determination. lonmax is adjusted modulo 360 to be larger than lonmin:
The determination used in the longitude range is preserved in the result, though only for cylindrical projections (see types of projections below):

### GeoCenter

An alternative way to provide a geo range is to give a center point and a distance radius, defining a geo disk on the Earth's surface. The geo range is then the rectangle in {lat,lon} coordinates that fully encloses that geo disk. This is done by using the options GeoCenter and GeoRange, the latter now containing only the distance radius.
 GeoCenter option of GeoGraphics that specifies the center of the map
Geo center specification.
A map of the area 100 miles around Dublin:
The GeoCenter option can also be used to select the center point of a map whose GeoRange was automatically obtained from the input. If the option GeoRange explicitly specifies a region, it will always override any other information provided by GeoCenter.
A map of Germany centered at Munich:
If the GeoRange option is explicit, then GeoCenter will be ignored:
GeoCenter also allows you to choose the center longitude for the "World" geo range:

### Other Specifications of the Map Region

GeoGraphics accepts location information in input, not inside geo primitives. That information contributes to the specification of the ranges of the map, but nothing is rendered on the map associated to it. Again, when only center information is available, the default scale of the map is approximately 10 miles in radius.
A map around a given position. Nothing is drawn on the map:
This shows the scale of the map:
You can change the default range to anything you want:
When using an Entity object, GeoGraphics consults with EntityValue about whether position and polygon information exists. If a geo polygon can be obtained, then that means there is also a clear sense of scale. If a polygon cannot be obtained, then you proceed with the center position and the default scale as before.
This is the polygon surrounding San Francisco. It contains a GeoPosition object with multiple {lat,lon} pairs inside:
This map is scaled to contain that polygon:
But this other map has the standard scale of about 10 miles:
Currently there is no polygon information for Rome, and hence these two maps cover identical ranges:

### Projected Coordinates

For large areas of the world, the default projection is "Equirectangular", in which the map coordinates are directly longitude and latitude. However, for smaller areas of the world it is more convenient to choose other projections, to decrease distortion. The map coordinates do not then have immediate angular meaning. For example, for low scales (approximately under 2000 km diagonally) the default projection is "Mercator", which preserves shapes. In this case, the horizontal axis still represents longitude, but the vertical axis is not latitude anymore.
The Mercator projection is frequently used in map services on the internet. However, it highly distorts distances and areas near the poles. In fact, the poles are mapped at infinite distance along the vertical axes, and therefore the Mercator projection cannot show the whole world in a map. GeoGraphics allows you to choose the projection needed, and the paclet GeoProjectionData provides one of the most extensive collections of projections available. When no explicit projection is indicated, GeoGraphics will choose an appropriate projection for you, based on the scale and center of the map.
 GeoProjection option of GeoGraphics that specifies the cartographic projection
Geo projection specification.
These are the latitude and longitude coordinates of Berlin:
However, a map of Germany in the Mercator projection shows Berlin with different coordinates:
This is the projection used in the map, a Mercator projection, with adapted "Centering" and "GridOrigin" parameters so that the horizontal axis still represents true longitude:
GeoGridPosition will give you the exact coordinates in the projection chosen:
You can now force that projection in the same map, obtaining the same result:
Or in another map, whose default projection would be quite different:
For intermediate-scale maps, the default projection is "LambertAzimuthal". The coordinate values do not then have an immediate meaning in terms of latitude or longitude angles.
A map of the United States. Note how the northern boundary (approximately parallel 49) is curved:
In that projection, neither parallels nor meridians are straight lines:
Compare to a Mercator map of the United States, displaying the same parallels and meridians:

### Introduction to Geo Projections

There are many functions and parameters to control cartographic projections and projected coordinates in the Wolfram Language. This subsection gives a brief summary of them. See the documentation of GeoProjection and GeoProjectionData for more detailed information.
Cartographic projections are functions of points on the surface of the Earth onto points on the surface of a flat map, a process that always involves some form of distortion. There are many possible choices of such functions, and the actual choice must be determined by the practical and aesthetic properties of the result, like minimizing distortion in some sense. This leads to several possible classifications of projections.
Many projections are defined using geometric methods of mapping points on a sphere to points on a tangent plane ("azimuthal" projections), a tangent cylinder ("cylindrical" projections), or a tangent cone ("conic" projections). Formulas can be easily generalized for the respective secant cases. In their basic cases, the axes of cylinders and cones are aligned with the polar axis of the sphere.
Cartographic projections are relevant at all scales, but their differences are clearer when using world maps. This subsection will only use examples of world maps.
Available cylindrical projections:
In cylindrical projections, parallels and meridians are straight orthogonal lines:
Available conic projections:
In conic projections, meridians are straight lines and parallels are circle arcs:
Available azimuthal projections:
Examples of azimuthal projections, centered at various points by default:
There are multiple variations of those basic types of projections. For example, if parallels are kept as horizontal straight lines but meridians are allowed to be arbitrary curves, the result is the family of "pseudo-cylindrical" projections. Projections that do not naturally have a particular type are usually classified as "miscellaneous".
Available pseudo-cylindrical projections:
An example of a miscellaneous projection:
Another important way of classifying projections is by using the geometric properties they preserve, mainly angles ("conformal" projections), distances ("equidistant" projections), or areas ("equal-area" or "equivalent" or "eumorphic" projections). No projection can preserve everything simultaneously.
The Mercator projection is the only cylindrical and conformal projection:
The Albers projection is conic and equal area:
The stereographic projection is azimuthal and conformal and is also constructed via perspective mapping:
Geo projections have parameters. GeoProjectionData[projname] gives the default values of the projection parameters.
Choose the centering point of a projection:
Choose the secant parallels in a conic projection:
Change the default map scale to use kilometers (true distance only on the equator for the Mercator projection):

The GeoRange option with explicit numeric values of latitude and longitude ranges returns a map of exactly the region requested. If the projection is not cylindrical, then the borders of the map will be curved lines, corresponding to the specified parallels and meridians.
These are the latitude and longitude limits of the mainland United States:
Use GeoRangePaddingNone to restrict to the actual geo range of the US:
A map specified by a geographical Entity or EntityClass object is constructed by first computing the latitude and longitude bounds of the object with GeoBounds, adding a small amount of padding, and finally completing the rectangular plot range, effectively using .
The map of Australia:
This is the geo range chosen by GeoGraphics:
The latitude and longitude limits of Australia are actually smaller:
To obtain the limits above, you need to extend by 5%:
Finally, to obtain the original map, combine the padding specification with Full:
The GeoRangePadding option is very flexible. It allows you to specify independent paddings for the four different sides of the map, and also allows different ways of specifying the actual padding: distances, angles, or scaled fractions of the total map. Click the link on its name to explore all the possibilities.

### GeoZoomLevel and ImageSize

Yet another way of providing a geo range is by selecting a point (for example, using GeoCenter or giving a point-like object in the first argument of GeoGraphics) and a zoom level. GeoGraphics will then choose a geo range radius so that the geo background image is constructed with a small number (generally around 10) tiles of 256×256 pixels. It is possible to get larger geo ranges by increasing the ImageSize option of the map.
 GeoZoomLevel option of GeoGraphics that specifies the zoom level ImageSize option that specifies the size in pixels of the final map
Zoom and image size specification.
A map around Paris at zoom level 5:
This was the associated geo range selected:
You can get larger images of the same area (also with correspondingly increased zooms) as follows:
Geo Primitives

### Points and Markers

The simplest primitive to use is Point. It will represent a point on the map, with the standard flexibility in Graphics to control its size, color, opacity, etc.
 GeoMarker[loc,icon] marker primitive at location loc using the given icon Point[loc] point primitive at location loc
Zero-dimensional geo primitives.
Take the list of supervolcanos:
These are their respective positions:
Draw a point at each position:
Draw larger points, with a different color. Note that you can also use Point without mapping it over the list of positions:
The use of GeoPosition inside Point guarantees that the points will be properly placed in the map for any projection:
You can also use the list of entities directly. GeoGraphics will internally use EntityValue to get their positions:
You can even use the EntityClass object itself, because it represents the list of its members:
The GeoMarker primitive adds the flexibility of placing anything at the given position.
This is the default geo marker:
Take this image of a volcano:
Use it at each location. You could have used the image itself instead of the icon Entity object:

### Paths

The GeoPath primitive represents any line on the surface of the Earth before it is projected onto the flat map. That is, a GeoPath object is a trajectory that has geometric meaning on the curved surface of the Earth. Currently three types of such lines are supported: "Geodesic" (shortest path between any two given points), "Loxodrome" (curve that crosses all meridians with the same bearing or angle), and "GreatCircle" (curve obtained by cutting the Earth by a plane through its center). Meridians are always both loxodromes and great circles. Parallels are always loxodromes but not necessarily great circles. The equator is the only parallel that is also a great circle.
 GeoPath[locs,pathtype] primitive joining the given locations with a path of type pathtype
One-dimensional geo primitives.
The default type of a GeoPath object is "Geodesic". This is a geodesic:
The Lambert azimuthal projection represents the geodesic as nearly straight. Compare to the equirectangular and Mercator projections for the same region:
This is the loxodrome curve, or rhumb line, from Buenos Aires to Lisbon:
It crosses all meridians with this angle, measured on the surface of the Earth, not on the map:
Compare the three types of GeoPath between two given points:
The geodesic and the great circle are nearly identical, but not exactly, due to the Earth being ellipsoidal. Zoom in near Iceland:
It may seem strange that the red curve above is shorter than the green curve. The orthographic projection explains the difference:
You have seen examples of geo paths between pairs of points. GeoPath[{p1,p2,,pn},type] gives a continuous line formed by segments of the given type between consecutive points pi, but the complete line is not of that type in general.
Draw the shortest route between several cities. The whole line is not a geodesic between the initial and final points:
Join the final point to the initial point with an additional segment of the same type:
There are named types of geo paths, including {"Parallel",lat}, {"Meridian",lon}, and particular cases like "Equator", "PrimeMeridian", or "DateLineMeridian".
Draw several parallels:
Draw parts of parallels, from west to east or from east to west. Use Arrow to add the arrowhead to a geo path:
Important named geo lines:
Draw the international date line:

### Circles and Disks

A geo circle with center p and radius r is a closed line surrounding p whose points are all at geo distance r from p. Due to the curvature of the Earth, the total length of the geo circle will be smaller than 2π r, and in fact if r keeps growing, the geo circle will start decreasing in size and focus around the antipode of p.
 GeoDisk[loc,r] geodesic disk centered at loc, with radius r GeoCircle[loc,r] geodesic circle centered at loc, with radius r
Disk-like geo primitives.
A geo circle of 500 kilometers of radius around Chicago:
A geo circle of 5000 kilometers around the same place. It does not look circular in the equirectangular projection:
If the geo circle crosses the pole, it will look like this:
And if it gets even bigger, it will start focusing around the antipodal point:
All together, in steps of 1000 kilometers:
Due to the Earth being ellipsoidal, the last geo circle in that sequence is as follows:
A geo disk is the 2D interior of a geo circle. A geo circle (like any closed curve) separates the surface of the Earth into two finite parts. The interior is the part containing the center point, not necessarily smaller in area than the exterior.
A geo disk of 500 kilometers of radius around Chicago:
A geo disk of 5000 kilometers around the same place:
If the geo disk crosses the pole, it will look like this:
And if it gets even bigger, it will cover most of the Earth, except for a small region around the antipodal point:

### Hemispheres

A hemisphere covers exactly half of the Earth's surface, as divided by a plane passing through the Earth's center. Hence the boundary of a hemisphere is a great circle (actually a great ellipse because an ellipsoidal model of the Earth is being used). The Wolfram Language provides two types of geo primitives to work with hemispheres: on the one hand is the hemisphere around a point p of the surface, and on the other hand are the especially important hemispheres DayHemisphere[date] and NightHemisphere[date], determined by the position of the Sun at the given date. The boundary of is the line . The boundary of the day and night hemispheres is DayNightTerminator[date].
 GeoHemisphere[loc] hemisphere centered at loc DayHemisphere[date] daylight hemisphere at the given date NightHemisphere[date] night hemisphere at the given date GeoHemisphereBoundary[loc] boundary of the hemisphere centered at loc DayNightTerminator[date] terminator line between the day and night hemisphere on date
Hemisphere-related geo primitives.
The hemisphere around Tokyo:
Superimpose its boundary line:
Use an azimuthal projection centered at Tokyo:
The Northern Hemisphere:
The day and night hemispheres are just an application of GeoHemisphere for the projection of the position of the Sun on the Earth's surface, or its antipodal point. To avoid ambiguities, dates must be specified with explicit TimeZone specifications.
The daylight and night parts of the Earth at a northern winter solstice:
The daylight and night parts of the Earth at a spring equinox:

### Region of Visibility from a Height

A geo hemisphere can be considered the part of the Earth that would be visible from very far (actually infinite distance) along some direction. Here the generalization of that concept when the viewing point is at finite height over the surface of the ellipsoidal Earth is introduced. The region obtained is then always smaller than a hemisphere. The geometric construction is very similar though: the region of visibility is also determined by a secant plane, but now it does not pass through the center of the Earth.
 GeoVisibleRegion[loc] visible region from the elevated position loc GeoVisibleRegionBoundary[loc] boundary of the visible region from the elevated position loc
Regions of visibility.
The region currently viewable from the International Space Station:
The boundary of the visible region from geostationary orbit over the point {0,0}:

### Line, Polygon, and Other Standard Graphics Primitives

The standard, non-geo graphical primitives, like Line, Polygon, Circle, etc. can also be used in GeoGraphics, but are interpreted as primitives on the flat map, not on the surface of the Earth as their geo counterparts are. They have the same standard properties they have in Graphics; in particular, the segments in Line and Polygon between any two consecutive points are straight lines.
Take four geo positions:
The Line primitive connecting those four points always has straight sides, in every projection, but the GeoPath connecting them has generically curved sides:
On the other hand, the points of the geodesics are uniquely defined, while the Line points are not. For some projections, the black line passes through Brazil, but not for others:
In all cases, one geodesic segment passes between Mozambique and Madagascar, but the corresponding Line segment crosses different countries of Africa for different projections:
It is possible to use directly projected coordinates in the standard non-geo primitives, but this requires taking into account which projection is being used. This is useful for adding additional graphical elements to the map, not directly related to elements existing on the surface of the Earth. In fact, you can use coordinates that do not even correspond to any point on the surface of the Earth. When this is done, it is highly recommended that the projection being used be made explicit in the input, to avoid GeoGraphics selecting a different projection when more primitives are added.
Add arrows and texts to a map in the "Bonne" projection. Note how GeoPosition specifications are mixed with projected coordinates in some Line primitives:
Using a different projection will automatically modify the positions specified with GeoGraphics, but not the positions given with projected coordinates:
PlotRange and GeoRange are completely independent options. Typically GeoRange is specified and GeoGraphics is allowed to choose an appropriate PlotRange, but you can always specify both. GridLines and GeoGridLines are also independent:

### Advanced: The Structure of a GeoGraphics Result

The output of a GeoGraphics input expression also has head GeoGraphics, but its first argument is now a Graphics object, the actual graphics object that is displayed as the map. This output GeoGraphics also contains a sequence of options with absolute values, both options that were given in input and options that were decided by GeoGraphics.
Analyze the structure of GeoGraphics in output:
The output still has head GeoGraphics:
The first argument is a Graphics object, and then there is a sequence of options:
In particular, there is information about the projection:
The zoom level selected:
Or the geo range and center chosen:
You also see the ellipsoidal model chosen for the Earth, the default "ITRF00":
An important option contained in the Graphics object itself is PlotRange:
To extract the images in the result (in this case the background image and some road shields), use the following:

### Advanced: Geo Evaluation of Geo Primitives

The geo primitives are converted into standard primitives in the "Equirectangular" projection so that they can be easily displayed using Graphics.
Use Geographics`GeoEvaluate on a GeoCircle, converting it into a Line object containing a list of {lon,lat} pairs:
A second argument of GeoGraphics`GeoEvaluate specifies the model of the spheroid being used, either a number in meters or a Quantity distance representing a sphere of that radius, or a pair {a,b} of semiaxes of an ellipsoid of revolution, also given as numbers in meters or Quantity lengths. The result is now different.
The same geo circle but now on a sphere of 2000 kilometers of radius. The result is different:
A third argument of GeoGraphics`GeoEvaluate specifies the resolution distance required, in meters. When this number is smaller, then the geo primitives are resolved with more points, to guarantee that neighbors are closer than that distance.
Use a resolution of only 1000 meters. The same geo circle is now resolved with many more points:
Geo Styling

### Map Stylings

GeoGraphics inherits from Graphics a large variety of directives that can be used to stylize a map, including colors, opacities, textures, and many more. It also adds new elements that are characteristic of maps, which automatically respond to the projection being used. The most important new element is GeoStyling[mapstyle,directive], which specifies how to stylize an arbitrary area of the map; that could be in particular the geo background.
GeoGraphics provides several predefined map styles, like "StreetMap", "ReliefMap", or "ContourMap", and only allows you to place arbitrary images on a polygon.
 GeoStyling[mapstyle] stylize the interior of 2D geo primitives using mapstyle GeoBackground option of GeoGraphics that specifies the background map style
Map styling.
The default style map is "StreetMap":
Show the same area, but without labels:
Show a relief map of elevations:
Or the corresponding contour map. Use options to control the result:
Show a satellite image:
Show an outline map with country borders:
GeoStyling effectively works like Texture, specifying what to place inside the following 2D primitives, like geo disks or polygons. In that sense, the GeoBackground option can be considered as the particular case of specifying what to place in the whole map.
A relief map of Peru over a map with default style:
GeoStyling can be used to show a map confined to the borders of a given area:
There are two flexible map styles that allow you to place arbitrary images and graphics on a map, namely {"Image",image} and {"GeoImage",image}. The difference is that in the first case the image will be placed in the given area with no transformation (perhaps only a change in aspect ratio), while in the latter case the image will be projected along the map area. Therefore "GeoImage" is adapted to place pieces of maps over other maps.
Take a picture of Gauss:
Place it over Germany, in the default "Mercator" projection:
With the "Image" map style, the image will preserve its orientation in any projection:
Take this nice old map of Brazil and cut its borders:
Using the "GeoImage" map style, it will be projected appropriately in any map:

### Opacity and Color

The Graphics 2D primitives are opaque by default because the background is typically empty, so it can be covered. However, GeoGraphics usually contains a map image as geo background, which should not be fully covered by the primitives over it. Therefore, the default opacity of 2D primitives is small: 0.2. This throws in a slight twist in how opacities are handled in GeoGraphics, because the opacities of the 2D primitives need to be distinguished from the opacities of the rest of the primitives (points and lines), which are still opaque by default. This can be done by using GeoStyling again.
A geo disk around Ottawa, with a thick blue border. The geo circle is opaque, but the disk is not:
Standard opacity specifications will affect all primitives except for the 2D primitives:
To change the opacity of the disk, use GeoStyling[opacity], which will not affect the thick geo circle:
Colors will affect all primitives normally:
But colors placed inside GeoStyling take precedence for 2D primitives, even over colors that are given afterward:
undoes the action of any previous GeoStyling specification and recovers the defaults:

### Geo Grid Lines and Scale Bar

Drawing parallels and meridians is always very useful for understanding the orientation of the elements on a map, even more so when using a noncylindrical projection. The option GeoGridLines and its styling counterpart GeoGridLinesStyle provide a flexible interface to drawing the so-called graticule of lines.
 GeoScaleBar option of GeoGraphics that turns on the use of a scale bar GeoGridLines option of GeoGraphics that turns on the use of a lines graticule GeoGridLinesStyle option of GeoGraphics that specifies the style of geo grid lines
Other map styling options.
In the "Equirectangular" projection, the parallels and meridians are straight lines (as in all cylindrical projections) and are equally spaced. Let the system choose the lines:
These are the latitude and longitude lines used, multiples of "nice" integer angles:
Specify respective approximate numbers of lines to use, in any projection:
Specify the graticule subdivision size as Quantity angles:
To read scale in a map, you can use the GeoScaleBar option. For large-scale maps, the distance scale factor may vary from point to point, and therefore the scale bar will only represent an average.
Use a scale bar with metric units in a map of France:
Other Celestial Bodies
All of the above has been presented for the Earth, but can be applied to other celestial bodies for which satellite images exist, like Mars, Pluto, or the Moon. GeoGraphics uses appropriate background tiles as determined by the value of the option GeoModel.
 GeoModel option of GeoGraphics that specifies a datum or celestial globe
Geo model specification.
A map of the Moon in the Mollweide projection:
A shallow valley on the Moon:
The Copernicus crater:
A map of Mars in the Bonne projection:
Show the landing position of a space probe:
Another interesting area on Mars:
A view of Pluto using the orthographic projection: