Scoping the workflow is probably the single most important activity of the Geospatial workflow. It establishes the foundation on which the rest of the workflow rests. For the student, it is where you, in your own words, explain what you see as the focus of a given task. For the consultant, it is an activity that focuses on ensuring alignment with the client, and for the researcher, it is where we establish what the task is all about: does it generate new knowledge or has someone else already done something similar?
Deconstructing the Brief: Taming “Semantic Noise”
Every Geospatial workflow begins with a Wild Brief. This is the raw, unrefined request from a client or stakeholder. It is usually full of “Semantic Noise”—vague terms like “hotspots,” “suitable areas,” or “impact zones” that have no inherent mathematical meaning. Your job is to act as a translator, moving from the client’s “Wild Intent” to an “Actionable Question.”
Defining Core Questions & Semantic Analysis
Your first task is to translate the Wild Brief into a Actionable Geospatial Question. This requires a “First-Pass” semantic analysis: identifying the Entities (the actors in your spatial play).
Copenhagen Case Study:
The Wild Brief: “We have a growing problem with noise and litter in the city centre during weekends. We need to identify ‘Party Zones’ so we can better coordinate our street-cleaning teams and noise-monitoring officers. We have access to the business register (CVR), but it doesn’t seem to tell the whole story. Can you provide a data-driven map of these hotspots?”
The Semantic Analysis: What is a “Party Zone”? It isn’t a physical object you can find in a database. It is a Composite Entity made of Venues (Bars/Clubs), Friction (Noise), and Movement (Transit).
By defining these entities now, you establish a Semantic Anchor. This is your first and best guard against Technical Drift
Addressing Spatial Omission and Bias (The “Unseen”)
A map is a rhetorical argument. When mapping “Party Zones,” we must document the potential for bias in our Design Rationale. We must ask: Does our focus on formal, registered establishments ignore the informal “vibrancy” of the city?
-
Informal Activity Hubs: Many intense social zones—such as the harbour-front (Islands Brygge) or public parks (Fælledparken)—do not appear in any business register. If your project only uses “Formal” data, it risks being biased toward established, commercial interests.
-
The Allotment Paradox: Areas like kolonihavehuse (allotment gardens) may experience high social intensity, yet they are semantically classified as “Residential,” masking their role as party zones.
-
The Mobile Economy: Food trucks and pop-up bars represent a Semantic Mismatch. Their legal registration (the Extent) is often far removed from their actual point of business (the Intent).
Stewardship Note: Documenting and informing the client about these omissions is a hallmark of professional practice. These might be acceptable omissions, or they might be oversights that require a renegotiation of project resources.
Defining the Universe of Discourse
“Whatever may be the extent of the field within which all the objects of our discourse are found, that field may properly be termed the universe of discourse”. (Boole, 1854) We use it here in its original, unconstrained sense—the ideal conceptual ontology required to answer the Spatial Intent. We call each element in this ontology a concept. In simple situations, the “Universe of Discourse” can be constructed from a semantic analysis of the spatial intent and the GIS professional’s a priori knowledge; in other cases, it can help to include an expert panel and perhaps conduct preliminary field studies.
This phase focuses on defining the “concepts” (Cast of Characters) for our project and establishing the rules governing their existence. Note that in the spatial context there are two fundamental types of “concepts”: namely, “entities,” which are discrete (countable) things like venues, food trucks, etc., and “gradients”, which represent non-discrete, i.e., continuous, phenomena like vibrancy, salinity, air temperature, etc.
As part of the semantic analysis and discussion with the client, in the “workflow scoping” we arrived at:
The Refined Question: “What is the spatial intensity of nightlife activity in Copenhagen, and how does this correlate with reported urban friction (noise)?”
Semantic Analysis (The Intent): To answer this, we must define the “Party Zone” not as a legal boundary, but as a Vibrancy Gradient.
- Primary Entity: “The Venue” (Bars, Clubs, Pubs).
- Proxy Entity: “The Friction Point” (Noise complaints).
- Gateway Entity: “The Transit Node” (Metro/Bus stops).
So we already have some clear candidates for our “Cast of Characters”:
- “Vibrancy Gradient”
- “Venue”
- “Friction Point”
- “Transit Node” We also have that the “Vibrancy Gradient” is some form of gradient derived from or related to the entities, i.e. the more Venues, the more Vibrancy.
In the “Addressing Spatial Omission and Bias” section of the “workflow scoping”, we identified that
- “Official business registers (CVR) miss informal socialisation. We must include polygons for “Public Social Space”
- “The Seasonal Mask: Kolonihavehuse (allotments) and pop-up bars are “Semantic Chameleons”—their legal address rarely matches their spatial impact.”
- Mobile Entities: Food trucks will be treated as “Temporal Points” rather than static venues
From this, we decide that the “Vibrancy Gradient” also need input from polygons for “Public Social Space” We also conclude that we need to address areas of more impromptu parties and pop-up bars; finally, we have identified food trucks as moving objects not related to their legal address.
Our “Cast of Characters”: must therefore also include
- “Public Social Space”
- Areas with seasonally higher party activity (allotments and areas with pop-up bars
- “Mobile objects” (Food trucks)
This illustrates that the “universe of discourse” is derived as a compilation of the “spatial components” identified and documentation of the “workflow scoping”
Mapping the Operational Context
While the Question defines your Intent, the Operational Context defines your Extent—the hard boundaries of the physical, legal, and technological world.
Stakeholders: The Human Ontology
A project is a social system. You must map the roles to ensure the project remains legible to whoever picks it up later:
-
The Client: The source of the “Wild Intent.”
-
The Gatekeeper: The IT or Legal officer who controls access to tools and data.
-
The End-Users: The person who must act on your results. If they cannot read your map, your science has failed.
This need to be extended it is not so much for o whoever picks it up later: but to be clear about the intreste of the projevt both formal and informal Eskecialy endusers play a roal in the design of the deliverbuls. But even though the clicant migh t seam obvius the planning department of municipality so and so. this is often just the formal front for a political system, the intrests of which might or might not be of relevance for your work.
The Politics of Data Sources
In professional practice, you are often forbidden from using certain data for reasons of “Official Liability.”
-
The Case Against Google/OSM: A client might ban Google Maps because it is proprietary and biased toward internet-active businesses. They might ban OpenStreetMap (OSM) because it lacks “Official Liability”—there is no government body to stand behind its accuracy.
-
Data Delivery: Document what the client provides. Is it a clean database or a “Wild CSV” full of spelling errors? This dictates how much cleaning and reconciliation are required to establish the Data Frame.
Copenhagen Case Study: The City Council provides data from the Københavner-vink system (public complaints). Business Rule: They forbid OSM data because they require “Authoritative Government Data” to justify tax-funded resource allocation.
Governance, Ethics, and the “Moral Intent”
In the geospatial workflow as presented in semanticGIS, privacy is “Baked In” (Privacy by Design).
- Aggregation: Instead of mapping a specific house that complained, we map a 100m grid. This protects the resident (GDPR compliance) while preserving the Scientific Intent of identifying a “Friction Zone.”
Summary: The SemanticGIS Deliverables
By the end of the workflow scoping, you can provided the client with a strategic blueprint of your understanding of what the workflow is to deliver. This is, in practice, extremely important. In a consultancy situation, you should always perform this operation before committing the workflow; it is your best guarantee that your understanding of the task and the client’s are aligned and that the resource allocation is sufficient. When that is said, many resource problems are first discovered when establishing the Data Framewrk