Add many places at once

1. Step by step

1. Make the sheet. Start from the template or your own: one row per place, column names in the first row. In Google Sheets or Excel, save it as CSV.
2. Open the importer: on the map, Lists → 📄 Import (or this link). You need a LeelaMaps account; it's free. Then either:
   • Choose the file;
   • paste the CSV ("Or paste the CSV"): handy when the sheet is open somewhere else, or an assistant is doing it for you; or
   • give a link ("Or from a link"): a .csv address, or a Google Sheet shared as "Anyone with the link". Each tab is its own link: open the tab and copy the address.
3. Check the columns. Each column's job is guessed from its name; change any guess that's wrong.
4. Review. Each row shows where it will go and what it carries (📅 an event, 🖼️ photos, 🔗 a link, ⚠️ something similar already nearby). Untick any row to skip it.
   • Where are these places? Type the town (e.g. Gainesville, FL) when your rows name venues rather than street addresses.
   • Privacy: everyone, friends, or just you, for rows that don't say.
   • Events: a row with a date becomes an event in the place's library, with its times and venue. Rows with the same title at the same place become one place with several dates (untick "Combine rows" to keep them apart). Tick Take RSVPs for events that don't say, and use Repeats (weekly, weekly: Tue, Thu, monthly) for a regular event instead of a row per date. A Ticket price ($15, $10-25 sliding scale, pay what you can, free) lets people request a ticket; you arrange payment, or turn on card payment for that event in the app.
   • Timing: Publish on holds a place back until a date; Archive after takes it off the map after one (or never); Reposts brings it back weekly, monthly or yearly; Season (Mar 15 - Jun 30) dims it, or hides it, the rest of the year. Status puts a live status on the pin (🟢 Open now), for as long as Status for says.
   • Readers can add to these: who else may add photos, links and words to each place (anyone, friends, people there, or no one), and whether it waits for your OK first. A row's own Readers can add / Approve additions wins.
   • Pins for these: a colour and a style for every pin, unless a row has its own Pin colour / Pin style.
   • Save as drafts to check them on the map before anyone else sees them; publish later.
   • A list description: everything lands in one list named after the file.
5. Import. A big sheet takes a few minutes; keep the window open. The report says what was made, which rows were skipped and why, and which places may already be on the map. Undo removes the whole import.

2. Columns it understands

Column names are matched loosely: case, spaces, _ and - don't matter. Each place needs a where: Latitude + Longitude, an Address, or a Venue.

3. How places are found

• Latitude and longitude are used exactly.
• A full street address (401 E University Ave, Gainesville, FL) is found anywhere.
• A venue name (Bo Diddley Plaza) is found when the cell also says the town, or when you fill in Where are these places?.
• We never guess. A row we can't place for sure is skipped and named in the report ("venue name only", "only matched a town", "too far from the area you gave"); fix it and import that row again.

4. Limits and house rules

• Up to 500 rows a file, 5 imports an hour, and 3,000 rows a day.
• Imported places earn no Loops and send no notifications; they're on the map for whoever looks.
• Everything follows the Posting Guidelines.
• For something that changes every week, the API can update the same notes again and again instead of making new ones.