Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

https://dpdd.atlassian.net/browse/MAP-3911

EVCS Stalls:

(done) Change label from EVCS Stalls to Ministry EVCS (remove underscore)

(not done - not sure we can do this) Symbolize based on attribute: Stall Type

EmVi Stall – blue colour

Fleet EV Stall – green colour

(done) Remove FID and OBJECTID from Identify Features display

(done - changed to “Building #”) Change Bldng_ID to Building # or Building ID

(partially done - using Stall Type but can only assign one attribute; see comment below) Use Stall Type and Address for identify results list

RPD Buildings:

(done) Layer name will stay as RPD Buildings with no underscore

(done) Remove FID Identify Features display

(done) Change Bldng_ID to Building #

(done) Use Building # for identify results list

(not yet done - public stations use red) Change symbol colour to red

Public Stations:

(done) Remove or hide private charging stations from Electric Charging Stations in Canada

(done) Use Station Name for identify results list

(not done - no style attribute for layer type ‘esri-feature’)Change colour to orange

(not done) Highlight which chargers are fast charges, based on DC Fast Count attribute

(also hid attribute ‘FID’ as was requested for the other layers)

In general:

(done) If possible, remove underscores from all attribute labels

Can the symbol style look more like the public stations symbol be used, which has an outline and shadow effect?

(done) Symbol drawing order should be as above (EVCS on top to Public on bottom of draw order)

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Urban Service Delivery (Social workers, B.C. Mail , Public safety): Test the application's ability to plan a route with multiple stops in an urban environment, taking into account traffic congestion, one-way streets, and parking availability which may impact route time and charger availability. Verify that the application accurately calculates the range of the EV based on expected driving conditions and traffic, and that it provides clear instructions for maneuvering in the city and accessing chargers.

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

https://dpdd.atlassian.net/browse/MAP-3842

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Lindsay and Beth to work with Andrew to specify the wording for the layer legend. Criteria to be added in this ticket.

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Extreme weather conditions(Emergency Responders, Highways officers): Test the application's ability to plan a route under extreme weather conditions including, snow, rain, flooding, and wildfires. Verify that the application considers road closures and traffic delays caused by weather when providing an optimal route and can suggest alternative routes if necessary. Additionally, test the application's ability to optimize charging stops based on the weather.

Open in MURAL
CleanBC JIRA to GH Integration- CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

As agreed at the Feb 15/23 check-in meeting, the purpose of this ticket is to list the symbolization aspects of the application that can/perhaps should be modified.

Items:

Layers (symbology and colour)
-add list of layers here

Highlighted route line (colour); marker for end of range; how should the in range line look versus the beyond range line?

Others?

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Long-distance trips (E.G. Park rangers, forestry officers, sheriffs): Test the application's ability to plan a long-distance trip through remote regions, including overnight stops and stops at multiple locations while optimizing charging and minimizing total trip time. The charging stops must be at convenient, safe and appropriate locations and that the planned route must include a reasonable range safety margin at all points in the route.

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

Open in MURAL
Untitled Mural - CITZ – BCDS – Data Systems and Services

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services

TL;DR 🏎️

Teams are encouraged to favour modern inclusive phrasing both in their communication as well as in any source checked into their repositories. You'll find a table at the end of this text with preferred phrasing to socialize with your team.

Words Matter

We're aligning our development community to favour inclusive phrasing for common technical expressions. There is a table below that outlines the phrases that are being retired along with the preferred alternatives.

During your team scrum, technical meetings, documentation, the code you write, etc. use the inclusive phrasing from the table below. That's it - it really is that easy.

For the curious mind, the Public Service Agency (PSA) has published a guide describing how Words Matter in our daily communication. Its an insightful read and a good reminder to be curious and open minded.

What about the master branch?

The word "master" is not inherently bad or non-inclusive. For example people get a masters degree; become a master of their craft; or master a skill. It's generally when the word "master" is used along side the word "slave" that it becomes non-inclusive.

Some teams choose to use the word main for the default branch of a repo as opposed to the more commonly used master branch. While it's not required or recommended, your team is empowered to do what works for them. If you do rename the master branch consider using main so that we have consistency among the repos within our organization.

Preferred Phrasing

Pro Tip 🤓

This list is not comprehensive. If you're aware of other outdated nomenclature please create an issue (PR preferred) with your suggestion.

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means it's critical that we work to make our content as discoverable as possible. Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's it, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.

Open in MURAL
CleanBC JIRA to GH Integration - CITZ – BCDS – Data Systems and Services