A Family Weekend with Google Maps, My Maps and Earth

The family, town, landmarks and route in this story are fictional. The mapping steps are real. Do not search for these invented destinations or upload invented addresses to a real map; use verified places from your own trip when trying the instructions.

On Friday evening, Nell put a notebook beside the family laptop. On its cover she had written: Things we must not drive past.

Her older brother, Kit, had one suggestion: somewhere to eat. Their parents, Mara and Dev, wanted a short weekend away without spending most of it in the car.

Their imaginary journey runs from Brackenmere through the Reedwater valley to Lantern Ridge, with a riverside museum, a picnic meadow and an optional lookout along the way. Google Maps will handle directions, My Maps will hold the shared itinerary, and Google Earth will help them understand the landscape. By Monday, Nell will have a different use for the same weekend: a school map project.

Plan your own weekend with an AI assistant

Want to plan a trip like this one? Copy this prompt into ChatGPT, Claude or Gemini and fill in the brackets. It points the assistant to the guide for each step, so you can check its suggestions yourself.

I'm planning a weekend trip from [START] to [END] on [DATES] with my family.
Stops we don't want to miss: [STOPS].
Anything else that matters to us: [e.g. short drives for the kids, no night driving, or leave blank].

Help me plan it with Google Maps, My Maps and Google Earth:
1. A sensible order for our stops, and how to add them:
   https://themapsguide.com/guides/google-maps-multiple-stops/
2. Route options worth switching on, such as avoiding tolls,
   highways or ferries where they exist:
   https://themapsguide.com/guides/google-maps-avoid-tolls-highways-ferries/
3. A shared map of our stops the family can open:
   https://themapsguide.com/guides/google-maps-vs-my-maps-vs-earth/
4. What to download for offline use:
   https://themapsguide.com/guides/google-maps-offline/
5. Who to share our live location with, and what to keep private:
   https://themapsguide.com/guides/google-maps-privacy-checklist/
6. After the trip, a simple plan to turn it into a school map project:
   https://themapsguide.com/guides/student-map-projects/

If you can open web pages, use the linked guide for each step. If you
can't, tell me which guide to open. Ask me if anything important is
missing. Don't make up road closures, opening hours or prices, and
don't ask for our home address.

1. Friday evening: give each map one job

Dev opened Google Maps and started adding destinations. Mara opened My Maps. Nell wanted the globe.

“Are we planning three trips?” Kit asked.

They agreed on three jobs instead. Maps would answer how to reach the next stop. My Maps would preserve their choices, notes and alternatives. Earth would help explain the valley and ridge, not tell them which junction to take.

They did not need to enter everything three times. The itinerary would be their shared reference; driving directions could be checked separately each day. Earth only needed the places relevant to the landscape question.

Mara also checked which Earth version suited the laptop. Web, mobile and the installed Earth Pro do not offer identical controls. Pro is the desktop application, not another name for a paid cloud plan. They would use the web for exploration and consult version-specific instructions if a control differed.

Nell wrote three headings in her notebook: Get there. Keep the plan. Understand the place.

Try it yourself: Choose with Google Maps vs My Maps vs Google Earth and Google Earth Web vs Pro vs Mobile.

2. Friday night: make room for the stops

The first route looked efficient until Nell asked when they would actually visit the museum.

Dev had treated the driving estimate as the whole morning. He added time for parking, lunch and getting everyone back into the car. They kept the museum and picnic meadow as commitments, with the lookout optional. Sunday would have its own return route.

In Maps, the practical sequence is to enter a start and destination, choose driving, then look for the controls to add and reorder stops. Arrange the visits yourself: calculating directions is not the same as optimizing your sightseeing order.

Mara compared the available roads rather than choosing by arrival time alone. Avoiding highways might produce a less suitable road; avoiding ferries would matter only where a crossing was relevant. Preferences were not promises about scenery or road quality.

Their fictional valley also gave them a reason to check weather along the journey, not just at the destination. For a real trip, they would match forecasts and official road notices to the places and times of travel, then recheck before leaving.

Kit crossed the lookout off the must-do list. Lunch stayed.

Try it yourself: Start with the road-trip planning guide, then use multiple stops, route avoidance options and weather along your route.

3. Still Friday: turn the shortlist into a shared My Map

Nell’s notebook now contained two kinds of places: agreed stops and things someone had merely suggested. Mixing them made the weekend look busier than it was.

A custom Maps list would have been enough for a simple shortlist. But Mara wanted a map with categories, arrival notes and alternatives, so she prepared a spreadsheet for My Maps.

Her headings were Name, Location, Day, Status and Notes. On a real trip, Location would contain verified addresses or coordinates—not the invented names in this story. Booking references and private family details stayed out.

On a computer, she would create a My Map, name a layer, look for Import and select the spreadsheet. The import prompts identify the location fields and the column to use for marker titles. Each important pin needs checking afterward; a matching name does not guarantee the right place.

They separated agreed stops from alternatives and used words as well as colors. Mara and Dev would edit; other relatives only needed to view. They checked the intended recipient’s access rather than making the map public.

Updating the spreadsheet would not automatically update the imported map. They kept the source table and would review any reimport options before replacing existing information.

Try it yourself: Compare labels, lists and Starred places, follow spreadsheet import into My Maps, or check My Maps import problems if the upload fails.

4. Before bed: see why the valley road bends

From above, Nell thought the museum and lookout looked close together. Tilting Earth made the ridge between them more obvious.

She tried drawing a straight line across it. Dev stopped her from calling that their walking route. A line measures the geometry they choose; it does not establish a public path, a safe crossing or a driveable road.

They explored how an elevation profile could show terrain rising and falling along a chosen line. Web Earth and Pro have different workflows. The chart’s distance axis follows the line; its elevation axis estimates ground height. It is not a promise about walking difficulty or total ascent.

Then Nell asked whether the riverside had always looked the same. They looked for historical imagery, compared the dates available and kept the view centered on the same area. Missing imagery would remain a gap, not evidence that nothing had changed.

Even within this imagined scene, the lesson mattered: satellite imagery is not live. A visible difference needs investigation, and the date belongs beside the observation. Nell saved a question for later rather than inventing an explanation for every patch of bare ground.

Try it yourself: Explore distance and area measurement, elevation profiles, historical imagery and Earth imagery dates and updates.

5. Saturday morning: pack a map that needs no signal

Dev reached for the car keys. Mara asked him to open their plan without the home Wi-Fi.

That exposed a mistaken assumption: a saved custom map was not an offline navigation download.

For a real journey, they would open the Maps phone app while connected, look for Offline maps and download an area covering the whole driving corridor, including sensible detours. They would check completion and any update or expiry notice, not just see whether the destination appeared on screen. Downloads are unavailable in some regions.

Offline driving cannot supply live traffic or alternative routes. Offline walking, cycling and transit directions are unavailable. Their My Map and saved lists were separate from that coverage.

Mara also prepared a printed overview, directions and numbered stop notes. A PDF on the phone was useful, but paper would still work with a flat battery. Neither could warn them about a new closure.

Nell took charge of checking that the page showed the final approach, not just a tiny line across the valley. Dev packed a charging cable. They restored connectivity after their stationary offline check.

Try it yourself: Prepare Google Maps offline and print directions or save a PDF. If you want a separate offline app, compare the workflow in Organic Maps offline before relying on it.

6. On the road: a new route and a different voice

At a wooded fork, the mobile signal dropped. Dev followed the road signs while Mara checked their paper overview; nobody tried to open a new online map at the junction. It was the first time Nell’s numbered stop notes had felt more useful than the screen.

Later, with connectivity restored, Maps proposed another route. Dev kept driving; Mara, in the passenger seat, checked what had changed.

They did not assume every reroute meant something was broken. Traffic, a missed turn or an inaccurate position could produce different situations. A previously selected route was not permanently locked. If repeated changes became distracting, they would stop somewhere safe to inspect settings and positioning rather than wrestle with the phone at a junction.

Then the navigation voice spoke, and Kit looked up.

“That’s not the usual one.”

At their next parked stop, Mara checked the navigation language and available sound options. Android and iPhone handle these differently, so she followed the instructions for their phone rather than assuming every device offered the same controls. They did not assume there was a switch to restore an exact previous voice.

They cared more about understanding the instructions than finding a familiar sound. A sample could check audibility, but spoken street names needed checking in real guidance. Mara would listen as a passenger; Dev would not operate the phone while moving.

Nell added another notebook heading: Things the map changes while we travel.

Try it yourself: Use the rerouting checks and navigation voice and language guide. Keep changes for a parked stop.

7. Near the museum: share progress, then find the entrance

The grandparents sent a message asking how far away the family was. Mara chose to share her own live location for a limited period, with their agreement, rather than ask Nell to share anything from a child’s account.

She checked the recipients and duration. Location Sharing was different from sending the itinerary: it could reveal her current position and other account or device information. It also needed connectivity; a stale location was not proof the family had stopped there. They agreed to send an arrival message too.

At the fictional museum, the destination marker pointed toward the building, but the visitor entrance lay around the other side. The family followed access signs rather than trying to drive through a pedestrian approach.

For a real destination, inspect the arrival point, confirm the entrance with the venue and save an exact pin when useful. Street View can help recognize an approach, but its capture date matters. Missing coverage does not mean an entrance does not exist.

If coordinates are needed, preserve latitude-longitude order and minus signs, then check the result. A precise point still cannot grant access across private land.

Try it yourself: Read Location Sharing, dropping an exact pin, wrong-address and entrance checks, Street View dates and Maps coordinates.

8. Saturday evening: decide what stays in the family

After the picnic, Nell wanted to send the entire map to her class. Mara opened it beside her instead.

The useful school material was the relationship between river, road and ridge. Their overnight arrangements, starting point and relatives’ movements added nothing to that question.

They planned a separate classroom version with only the necessary public places and research notes. Hiding a layer would not be their privacy method; sensitive material would be absent from the shared version. They would also inspect descriptions and photographs for personal information.

Mara checked her outgoing location share and stopped it when it was no longer needed. She did not confuse stopping a share with deleting search activity or Timeline. Those were different controls, with different effects. A privacy review did not mean switching everything off without understanding it.

Nell suggested using a picture of the picnic. They chose a landscape image without identifiable children instead, with a description of what it showed. Their class map would not carry the family’s real-time whereabouts or travel schedule.

The grandparents received the arrival message. The class would receive an explanation of a landscape.

Try it yourself: Follow the Google Maps privacy checklist, with separate instructions for search history and Location History and Timeline.

9. Sunday homecoming: turn a diary into a question

Back home, Nell arranged her notes in order. First the museum, then lunch, then the lookout they had skipped. It was a trip diary, but not yet a research project.

Her new question was narrower: How did the river and ridge shape the route between the weekend’s stops?

Because Brackenmere is fictional, this story’s school project is illustrative too. In a real classroom, the teacher could choose a verified public study area or clearly labelled synthetic exercise. Invented places would never be presented as documentary evidence about real geography.

Nell’s imagined teacher approved the scope and sharing arrangement before map-building began. The equivalent real preparation includes checking school service access, age restrictions and required consent. A blocked school account is not an invitation to use an unapproved personal one.

They agreed that the hand-in would contain a small map, a source table and a conclusion. The teacher would have viewing access through the approved account, tested before submission. A failed opening attempt would prompt an account and permissions check, not a public-sharing shortcut.

Nell removed the lunch recommendation. It had mattered to the trip, but it did not help answer her question.

Try it yourself: Begin with Google Maps for Teachers, Student Map Projects and sharing a My Map with students.

10. Sunday afternoon: make every marker explain something

Nell’s first caption said only, We went this way. Her second draft explained what the bend in the road helped her notice and what evidence she still needed.

For a real project, she would keep a source row for each feature: title, author or institution, URL or page, publication date when supplied, consultation date and location precision. Her own dated observation would stay separate from an official record, a map label or an interpretation.

Older imagery would need its capture date, not just the day she opened it. A terrain measurement would need the tool, units and definition of the line. An approximate location would say so. No missing date or unsupported historical claim would be filled in for neatness.

Her parents could help with controls, but the question, explanations and revisions would remain hers. Together they checked a simple assessment list: Does each place help answer the question? Can a reader trace the evidence? Do the symbols make sense without color? Is there a text version? Is the audience appropriate?

The conclusion would explain a relationship and acknowledge a limit, not merely repeat the stops. Attractive pins could not substitute for that answer.

Try it yourself: Use mapping research resources, adapt mapping lesson ideas, or compare student map project examples without copying their conclusions.

11. Monday’s hand-in: save more than a link

Before the imagined presentation, Nell rehearsed with the map closed. Could she explain the question from her companion table?

She could. The table repeated the captions, sources and legend; the conclusion worked without hovering over markers or following globe animation. She changed one color-only category into a written label.

Then they preserved the work. In My Maps, look for the map menu’s KML/KMZ export for a geographic copy, or a layer’s CSV export for tabular information. CSV is not a complete replacement for map styling and geometry. A downloaded file is a separate copy, not the live shared map.

If taking KML/KMZ into Earth, choose the appropriate import workflow and inspect the result. Check the important markers, descriptions and media instead of assuming everything survived. Keep the source spreadsheet, bibliography and text explanation too.

Nell’s hand-in would therefore include the restricted map link, accessible companion document, conclusion and any export the teacher requested. None required publishing the family’s private itinerary.

On Friday, she had wanted a map of everything they might do. By Monday, she wanted a map that helped someone understand one thing. The skipped lookout still appeared in her notebook, but it no longer needed a marker.

Try it yourself: Choose a format with the map-files overview, follow My Maps export instructions and use KML/KMZ import into Earth when the globe adds something useful.