South Bay Streets (SBS) – User’s Guide for Maps
© 2025 McQuillin & Associates Inc. -- Company Confidential
Guide Ver 0.7 – 2025-03-14 – For South Bay Streets Ver 0.8 – R. McQuillin
1. NOTE: ROUGH DRAFT – PARTIALLY COMPLETED – WORK IN PROGRESS
2. NOTE: This document is COMPANY CONFIDENTIAL with limited distribution. It has been provided to you for early review. Please do not forward, copy, or otherwise distribute it without prior authorization.
3. WARNING: This guide may be updated often. Avoid using outdated copies. Please note the version number above. A version history is shown at the end of this guide.
Contents
1.1 Who is this for (the Audience)?
1.2 What is South Bay Streets (Streets) and Why Use It?
1.4 Use This Guide alongside the Application
2 Terms and Abbreviations (Application-Specific)
3.1 View and Use a Map (Guest or Member)
3.2 Manage a Map (MapOwner and MapAuthor)
3.3 Find and Use a MapSet or Map
3.8.1 View and Use a Map (Guest or Member)
3.8.2 Manage a Map (MapOwner and MapAuthor)
3.8.3 Find and Use a MapSet or Map
3.8.5 Clone a Model Map and Modify it.
4 Appendix: Use Case Template (Author)
|
Version |
Date |
Primary Author |
Change Summary |
|
0.8 |
2025-03-14 |
R.McQuillin |
Original |
|
|
|
|
|
|
|
|
|
|
This document is for users who will create accounts in Streets and use the mapping capabilities. You may simply ‘follow’ others’ maps, or you may create your own map sets and maps for more capability.
(This section provides a quick recap. See the SouthBayStreets Introduction for a better introduction.)
(South Bay Streets (“Streets”) is a also web application that you use to create and manage a database of your goals and needs. Those capabilities are covered in the general South Bay Streets User Guide. )
1. The SouthBayStreets Introduction
This guide has some screen shots, but not for all topics. If you can, we recommend that you open this guide on-screen next to the Streets screen(s) you want to work with and follow the instructions step-by-step using the live screen. Or you could print out the guide.
NOTE: See also Terms and Abbreviations (General) in the Streets Introduction document. Those terms are also needed to understand this document. This is a list of additional terms for actually interacting with the application.
|
Term |
Meaning |
|
Actor |
|
|
Use Case |
A Use Case is a “How To”: It is a task performed by an actor (a user in a role) using the application to complete an operation. |
|
Page |
|
The Maps capability will develop in stages:
1. The first phase, the simplest, allows anyone (not signed in) to view the pre-created maps. Also, designated MapOwners and MapAuthors will be able to manage (build and maintain) the pre-created Maps. This will be enough capability to allow us to provide SeeArtesia, our flagship map, and SeeTheGalleria, its companion. To view a map, simply navigate to the map’s page and use the basic features (view, filter, find, tc.) .Here are the steps to be able to manage a map:
a. Create an account (Client only)
b. Tell the Admin the email you used to create the account with.
c. The Admin will add you as a MapAuthor to the map.
d. When a MapAuthor visits the map, they will be able to edit it, especially adding, updating, and removing locations on the map.
2. In later phases, users will be able to perform several functions with maps, including:
a. Pinning maps (this is actually available at first release)
Locations. Maps are built from Locations. A location is normally a street address, but it can be a street or a place (e.g. a geolocation) without an address. The Locations use cases are provided within the Modify a Map use case since that’s where they are used.
MapSets. Before diving into the use cases for Maps, let’s just note that you’ll encounter MapSets mixed in with Maps in some lists and other pages. A MapSet is just a collection of Maps. We’ll talk about Maps first since they are more “core”. The MapSet use cases are shown after the Map use cases.
Using.
vs.
Following.
1. Clone a Model Map and Modify it.
2. Create “from Scratch”.
Include Linking Maps.
CURRENT PROBLEM WITH LOCATIONS: Location Name vs. Occupant Name: Non-addresses need a Location Name which is not required by the UI/app, and it’s not provided on the Add Location page. For now, when adding a new non-Address location, just use the Occupant Name, then open the Edit Location page and enter the Location Name (can remove the occupant name?).
NOTE: Both Location SubType and Occupant SubArea may normally have a single entry, but both can both have multiple entries (prefer the use of CDLs).
(See the description of MapSets in the SouthBayStreets Introduction)
Except for the detailed building part, managing MapSets is like managing Maps, and sometimes they are in the same lists.
(This document author may use this template to create new Use Case topics.
· Trigger.
· Preconditions.
· Procedure.
· Results.
· WARNING(S): Things to be cautious of when performing this task.
NOTE(S): Other important aspects or implications of this task.
(THIS DOCUMENT IS STILL IN EARLY DEVELOPMENT)