R4MP

RAMP - The Reusable Accessible Mapping Platform, is a Javascript based web mapping platform that provides a reusable, responsive and WCAG 2.1 AA compliant common viewer for the Government of Canada. The fourth incarnation embraces the following large-scale changes

- Updating the UI framework from Angular 1 to Vue 3
- Updating the ESRI Mapping API from v3 to v4
- An application architecture and API that is more open and adjustable
- UI re-design with mobile use in mind

The previous version (RAMP 2 / RAMP 3) can be found here. Differences between the versions are summarized in the v4.0.0 Release Notes.

> This is an unsupported product. If you require a supported version please contact applicationsdecartographieweb-webmappingapplications@ec.gc.ca for a cost estimate. The software and code samples available on this website are provided "as is" without warranty of any kind, either express or implied. Use at your own risk. Access to this GitHub repository could become unavailable at any point in time.

 

Documentation

Documentation Site with unpublished changes can be found here.

Head to the Releases page for version-specific official documentation sites.

Browser Support

RAMP supports modern versions of Google Chrome, Microsoft Edge, and Firefox on desktop, and Google Chrome, Firefox, and Safari (iOS) on mobile devices. We suggest keeping your browser up-to-date to ensure full functionality.

Internet Explorer is not supported. Use at your own discretion.

RAMP should still work on most other browsers, but we cannot promise support or fixes. However, if you notice any issues, please feel free to let us know.

Local development

$3

Use Node v22.12.0 for local development and all production builds. This version is officially supported and required for production build environments.

Developers may use any Node v22.x.x version for local work if preferred, though results may vary.
Versions below 22 or 23 and above are not tested and not recommended.

See node-compat.yml in the repo root for versions we consider production or likely supported. As we test newer Node releases, we’ll expand those ranges.

Quickstart with nvs for Windows

- Install nvs: https://github.com/jasongin/nvs#readme (winget install jasongin.nvs).
- In a new terminal:
``powershell
nvs add 22.12.0
nvs link 22.12.0
`
- Open a fresh terminal so your PATH is updated.

`sh
npm ci
`

$3

`sh
npm run dev
`
Current Samples: https://localhost:5173/demos/enhanced-samples.html.
Legacy Samples: https://localhost:5173/demos/index-samples.html.

#### Serve via http

`sh
npm run dev-http
`

$3

`sh
npm run build
`

This command runs four parallel builds, each with a different target mode and use case. This is done because Vite and Rollup do not support multiple build configurations at the same time. The modes are:

- npm run build:npm: This build generates the dist/bundler folder which contains RAMP library split into ES modules. This is the content that would be used if RAMP is installed via npm. All package.json dependencies are excluded from these files, the consuming applications npm manager and build process will handle this.

- npm run build:esDynamic: This build generates the dist/esDynamic folder which contains the RAMP library split into ES modules. This is useful for web applications that want dynamic imports to reduce the size of the initial bundle.

- npm run build:inline: This build generates the dist/ramp.browser.es.js and dist/ramp.browser.iife.js files which contain the entire RAMP library as a single file. These files don't support dynamic imports and should only be used if the consuming environment doesn't support ES modules (use iife) and/or only one RAMP file can be hosted.

- npm run build:demos: This build generates the dist/demos folder which contains the demo files. These files are the closest representation of a local develop serve.

You can also run these commands separately if you only need to build one of the modes.

$3

`sh
npm run preview
`

Open http://localhost:5050 in your browser.

$3

`sh
npx vitepress dev docs
`

$3

`sh
npm run vite-docs:generate
`

Static site generated in the vite-docs directory.




$3

`sh
npm run ts-docs:generate
`

Static site generated in the ts-docs directory. Open index.html to preview.

$3

VSCode with the recommended extensions (VSCode should bug you to install them).

#### Important:

1. Install Volar.
2. Disable/remove Vetur.
3. Type @builtin typescript in the search box on the VSCode extensions tab and disable "TypeScript and JavaScript Language Features". Volar has its own TS language server so we don't want to run two concurrently.

$3

The public folder is a static only folder. It contains the help md files and end-user demo assets and the compiled RAMP library source code. Files in this folder are not processed by vite and therefore cannot reference outside files. This is useful for testing if things are broken between the develop and production build.

To test the files in the public folder locally:

`js
npm run build
npm run preview
`

Then open http://localhost:5050/index.html in your browser.

The demos folder is processed by vite and can therefore reference any source file in the repo. This is the starting point for local development. For example, the demos/starter-scripts/main.js file imports { createInstance, geo } from '@/main'; whereas public/starter-scripts/index.js doesn't since RAMP is globally defined by the index.html file when it loads .

Run npm run dev then open http://localhost:3000/demos/index.html in your browser.

During build, the public folder contents are placed into the dist folder.

$3

When you push changes to your forked repo, a demo preview is automatically generated. The demo preview will update each time you push changes. Note that demos are deleted daily whenever the source branch or tag is deleted from your forked repo.

$3


- Branch or Tag Preview: Visit https://YOUR-GITHUB-USERNAME.github.io/ramp4-pcar4/BRANCH-OR-TAG-NAME to see a live preview of the branch or tag you've pushed.
- List of All Demos: View all your demo previews by navigating to https://github.com/YOUR-GITHUB-USERNAME/ramp4-pcar4/tree/demo-page.

$3

To enable demo previews on your forked repository, update the following settings:

1. GitHub Pages:
- Go to Settings -> Pages -> Build and deployment source and select GitHub Actions.

2. Deployment Branches and Tags:
- Navigate to Settings -> Environments -> github-pages -> Deployment branches and tags and choose No restriction.

3. Actions Permissions:
- Under Settings -> Actions -> General -> Actions permissions, set it to Allow all actions and reusable workflows.

4. Workflow Permissions:
- Go to Settings -> Actions -> General -> Workflow permissions, and select Read and write permissions.

5. Enabling Workflow:
- Go to the Actions` tab and click on I understand my workflows, go ahead and enable them.
- Note: If you've already enabled workflows in the Actions tab for your fork, this prompt won't appear again.