bcgov / whse_2_agol Goto Github PK
View Code? Open in Web Editor NEWProject structure for managing whse_2_agol activities.
Project structure for managing whse_2_agol activities.
Currently the app is writing archive mxd files to the mpcm folder. Can this be changed to something other than the MPCM folder?
ie change
E:\sw_nt\jenkins\workspace\waops\MAXLS_build_publish>set ARCHIVE_DIR=E:\apps_data\userdata\mpcm\scripts\archive\DLVR\20201022
to
\alpheratz.dmz\e$\apps_data\ago_publish\managed_mxd or
\alpheratz.dmz\e$\apps_data\ago_publish\published_mxd
This issue is a kind reminder that your repository has been inactive for 180 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.
To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.
dormant
or retired
life cycle badge.Thank you for your help ensuring effective governance of our open-source ecosystem!
Brock has found approx 90 layers that do not have metadata records and so are not included in the mini maxls for publishing to AGO
missing_feat_classes.xlsx
Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.
It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.
I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)
https://proj.data.gov.bc.ca/jira/browse/MAP-1482
From: Hoole, Meg CITZ:EX
Sent: October 5, 2020 5:17 PM
To: 'Brock Anderson' [email protected]
Cc: Boulstridge, Marion CITZ:EX [email protected]; Tonkin, Bruce CITZ:EX [email protected]
Subject: Metadata needs for MAXL and fc2ago.py layer items in AGO
Hi Brock
There are a couple more asks for metadata changes that may not have crossed your path yet:
For the map image layer items - a 'Change Notice' that speaks to the replacement of the dynamic json service urls – it can now be removed... see https://governmentofbc.maps.arcgis.com/home/item.html?id=1923f13a74974ea48a6fdc56630703ba
If possible, can we add a note to the top of the Description section of map image layer items that drives the users to the corresponding feature layer items instead?
Something like:
NOTICE: This item will be deprecated in “the future” (we don’t have a date yet – but we can discuss). We recommend you use the feature layer item instead – see “link to feature layer item”
The AGO hosted layers replicated by the fc2ago.py script do not currently have the metadata automated like the MAXL does. Can we do the same metadata updates via script for these layers that we currently do for the MAXL layers? See for an example layer: https://governmentofbc.maps.arcgis.com/home/item.html?id=eacb5780fce3411791278b2fa31d6f07
Thank you
Meg Hoole __ | Data Administrator | DataBC | Data Systems and Services Branch | Digital Platforms and Data Division
Office of the Chief Information Officer – Ministry of Citizens’ Services
All map services that are published should be in lower case eg:
whse/bcgw_pub_REG_LAND_AND_NATURAL_RESOURCE
to match our standards and all other map services.
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!).
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.
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!!!
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.
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.
Short Code | Organization Name |
---|---|
AEST | Advanced Education, Skills & Training |
AGRI | Agriculture |
ALC | Agriculture Land Commission |
AG | Attorney General |
MCF | Children & Family Development |
CITZ | Citizens' Services |
DBC | Destination BC |
EMBC | Emergency Management BC |
EAO | Environmental Assessment Office |
EDUC | Education |
EMPR | Energy, Mines & Petroleum Resources |
ENV | Environment & Climate Change Strategy |
FIN | Finance |
FLNR | Forests, Lands, Natural Resource Operations & Rural Development |
HLTH | Health |
IRR | Indigenous Relations & Reconciliation |
JEDC | Jobs, Economic Development & Competitiveness |
LBR | Labour Policy & Legislation |
LDB | BC Liquor Distribution Branch |
MMHA | Mental Health & Addictions |
MAH | Municipal Affairs & Housing |
BCPC | Pension Corporation |
PSA | Public Service Agency |
PSSG | Public Safety and Solicitor General |
SDPR | Social Development & Poverty Reduction |
TCA | Tourism, Arts & Culture |
TRAN | Transportation & Infrastructure |
NOTE See an error or omission? Please create an issue here to get it remedied.
This file needs to have all the layers from fc2ago in it to avoid duplication when publishing layers.
Marion needs to produce config files for delivery
This issue is a kind reminder that your repository has been inactive for 181 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.
To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.
dormant
or retired
life cycle badge.Thank you for your help ensuring effective governance of our open-source ecosystem!
If the property is configured in the config file, it generates and error in the build.
"credits": "Province of British Columbia, {}".format(datetime.datetime.now().year)
This works without a problem.
"credits": "DataBC, Province of British Columbia"
Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.
It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.
I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)
When I do a publish-only with feature class: WHSE_ARCHAEOLOGY the build fails.
https://cis.apps.gov.bc.ca/int/job/waops/job/MAXLS_build_publish/54/console
I noticed other builds failed with a similar error.
Brock needs a spot other than the C: drive to place the mxd for publishing to the other environments from Alpheratz
Brock needs to modify script to add configurations
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.
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.
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.
Non-Inclusive | Inclusive | |
---|---|---|
Whitelist | => | Allowlist |
Blacklist | => | Denylist |
Master / Slave | => | Leader / Follower; Primary / Standby; etc |
Grandfathered | => | Legacy status |
Sanity check | => | Quick check; Confidence check; etc |
Dummy value | => | Placeholder value; Sample value; etc |
This list is not comprehensive. If you're aware of other outdated nomenclature please create an issue (PR preferred) with your suggestion.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.