development-application-portal
Community Welcome to the development application guide for our city. This page offers the resources, guidelines, and tools to start your application. We aim to make the process easy to understand and efficient. Scroll down to learn more about the Development Applications Process. To Begin the Development Application Process A Pre-Application is the initial step in the development application process; it allows the applicant and the City to engage in a preliminary discussion about a development proposal before the application is submitted. It helps identify key considerations and potential challenges of the proposed development before significant investment is made in a full application. Since every property and development proposal is unique, application requirements may vary. Before submitting a pre-application, please review the required information here. City Planning staff will review the pre-application submission and may contact you to schedule a pre-application meeting. Depending on the complexity of the proposal, not all applications will require a pre-application meeting. Staff will guide you through the application process and discuss any potential constraints with your proposed development. How do I know what to do? Property development in the City can vary greatly in scale, from small projects like standalone garages to extensive undertakings such as multi-family residential complexes. To determine whether you need to submit a development application related to Planning and Development, you can use our interactive
Public Data Viewer to check your property’s land use designations in relation to our Zoning, Official Community Plan (OCP) and Subdivision Development and Servicing (schedules) bylaws. Additionally, you can verify if your development is within a Development Permit Area and may need a Development Permit. You can also answer the questions on the Development Approvals Required Checklist graphic on this page. If you are unsure or know that an application is required, you can then use our Pre-Application Submission tool (below). To avoid confusion about the role of City Staff (Staff) in the development process, and to make it clear that Staff do not make decisions about whether a project is feasible, here are some simple points outlining the Staff’s role: Pre-Application Consultation: Staff meet with applicants to discuss their proposals, provide guidance on the necessary steps, and outline the required documentation and studies, as per City bylaws and processes. Application Review: Staff review submitted applications to ensure they comply with local bylaws and policies, as well as provincial legislation. This includes checking for completeness and accuracy. Coordination: Staff coordinate with city departments and external agencies to gather feedback and ensure all aspects of the development are considered. Public Engagement: If needed (i.e., provincially legislated or by City Bylaw) for an application, Staff facilitate public meetings and consultations to gather input from the community and address any concerns. Report Preparation: Staff prepare detailed reports and recommendations for decision-makers (Council). The reports and recommendations are based on the Applicant’s submission, City bylaws, policies, and legislation, as well as planning principles and potential impacts of the proposal as determined by feedback from internal departments, external agencies, and the public. Decision Implementation: Once a decision is made, Staff ensure that all conditions of approval are met and that the development proceeds according to the approved plans. Ongoing Support: Throughout the development process, Staff provide ongoing support and guidance to applicants, helping to resolve any issues that arise. Ready to submit your Pre-Application? If you are comfortable using online tools, launch the web-based application to submit electronically. Alternatively, you may email the required Pre-Application submission materials to
[email protected]
. For details on submission requirements and the Pre-Application process,
click here
. Following the Pre-Application process you may be asked to proceed with a full application. Learn more about Development Permits, Variances and more applications below:
Datasets available for download
This dataset has no data
Additional Info
| Field | Value |
|---|---|
| Last Updated | September 10, 2026, 07:09 (UTC) |
| Created | March 24, 2026, 21:08 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
development-application-portal |
|
Description
A description of the dataset.
|
Community Welcome to the development application guide for our city. This page offers the resources, guidelines, and tools to start your application. We aim to make the process easy to understand and efficient. Scroll down to learn more about the Development Applications Process. To Begin the Development Application Process A Pre-Application is the initial step in the development application process; it allows the applicant and the City to engage in a preliminary discussion about a development proposal before the application is submitted. It helps identify key considerations and potential challenges of the proposed development before significant investment is made in a full application. Since every property and development proposal is unique, application requirements may vary. Before submitting a pre-application, please review the required information here. City Planning staff will review the pre-application submission and may contact you to schedule a pre-application meeting. Depending on the complexity of the proposal, not all applications will require a pre-application meeting. Staff will guide you through the application process and discuss any potential constraints with your proposed development. How do I know what to do? Property development in the City can vary greatly in scale, from small projects like standalone garages to extensive undertakings such as multi-family residential complexes. To determine whether you need to submit a development application related to Planning and Development, you can use our interactive Public Data Viewer to check your property’s land use designations in relation to our Zoning, Official Community Plan (OCP) and Subdivision Development and Servicing (schedules) bylaws. Additionally, you can verify if your development is within a Development Permit Area and may need a Development Permit. You can also answer the questions on the Development Approvals Required Checklist graphic on this page. If you are unsure or know that an application is required, you can then use our Pre-Application Submission tool (below). To avoid confusion about the role of City Staff (Staff) in the development process, and to make it clear that Staff do not make decisions about whether a project is feasible, here are some simple points outlining the Staff’s role: Pre-Application Consultation: Staff meet with applicants to discuss their proposals, provide guidance on the necessary steps, and outline the required documentation and studies, as per City bylaws and processes. Application Review: Staff review submitted applications to ensure they comply with local bylaws and policies, as well as provincial legislation. This includes checking for completeness and accuracy. Coordination: Staff coordinate with city departments and external agencies to gather feedback and ensure all aspects of the development are considered. Public Engagement: If needed (i.e., provincially legislated or by City Bylaw) for an application, Staff facilitate public meetings and consultations to gather input from the community and address any concerns. Report Preparation: Staff prepare detailed reports and recommendations for decision-makers (Council). The reports and recommendations are based on the Applicant’s submission, City bylaws, policies, and legislation, as well as planning principles and potential impacts of the proposal as determined by feedback from internal departments, external agencies, and the public. Decision Implementation: Once a decision is made, Staff ensure that all conditions of approval are met and that the development proceeds according to the approved plans. Ongoing Support: Throughout the development process, Staff provide ongoing support and guidance to applicants, helping to resolve any issues that arise. Ready to submit your Pre-Application? If you are comfortable using online tools, launch the web-based application to submit electronically. Alternatively, you may email the required Pre-Application submission materials to
. For details on submission requirements and the Pre-Application process,
. Following the Pre-Application process you may be asked to proceed with a full application. Learn more about Development Permits, Variances and more applications below: |
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
9704.25 |
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2024-04-09 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
public |
|
License
License used to access the dataset.
|
License not specified |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://opendata.grandforks.ca/datasets/4c33882c60b4464091667c731a683292 |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
mycity_admin |
|
Contact Point
Who to contact regarding access?
|
|
|
Contact Point Email
The email to contact regarding access?
|
|
|
Publisher
Publisher of the dataset.
|
|
|
Publisher Email
Email of the publisher.
|
|
|
Author
Author of the dataset.
|
mycity_admin |
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
2026-09-04 |
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
4c33882c60b4464091667c731a683292 |
|
Language
Language(s) of the dataset
|
English |
|
Link to dataset description
A URL to an external document describing the dataset.
|
https://opendata.grandforks.ca/datasets/4c33882c60b4464091667c731a683292 |
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
|
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
|
|
Number of data columns
If tabular dataset, total number of unique columns.
|
|
|
Number of data cells
If tabular dataset, total number of cells with data.
|
|
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments