Service

Custom Web GIS Development.

Operational web mapping software — not a static map embedded on a page. Fast, interactive, and built to your workflow.

Talk to us ↓ SCOPED AFTER A FIT CALL
Aerial view of a coastal city, watershed, and transportation network
1730 / Geospatial Vancouver, BC · Remote
Built for

Organizations that need a genuinely interactive map or geospatial app — resources, environment, engineering, utilities, municipal.

01 / Defined scope Investor-facing project map 02 / Relevant work Interactive rare-earth project map
03 / Commercial model Senior review · fixed-price gates
The problem

Built around the hard part.

  • Off-the-shelf ArcGIS config can’t do what you need
  • You need search, filtering, custom layers, and real interactivity
  • It has to be fast and work on mobile
What you get

A clear path to production.

  1. 01
    Interactive mapping apps

    MapLibre / deck.gl front ends over your spatial data.

  2. 02
    Custom layers & queries

    Search, filter, and analysis tuned to your data.

  3. 03
    PostGIS back end

    A real spatial database, not a pile of files.

  4. 04
    Cloudflare-hosted

    Fast globally, and cheap to run.

Defined builds

Concrete scopes, typical timelines, and the work inside them. These are useful starting shapes, not packages we force onto your situation.

Explore all 50 build briefs →

Investor-facing project map

A public, interactive map of your projects and properties, embedded on your company website.

Scope
Fit after discovery
Typical time
3–6 weeks
Open build brief →

ArcGIS app or automated workflow

An Experience Builder app, Survey123/Field Maps deployment, or arcpy automation built under your existing Esri licenses — the platform you already pay for, configured around how your team actually works.

Scope
Fit after discovery
Typical time
2–6 weeks
Open build brief →

Interactive claims and project map portal

A public or investor-facing web map of your claims, projects, and targets, with searchable layers you control.

Scope
Fit after discovery
Typical time
3–6 weeks
Open build brief →

Why 1730

Senior by default

The people in the room are the people doing the work. Direct context, fewer handoffs, better decisions.

Built to be inherited

Clear architecture, maintainable systems, and practical handover are part of the product.

Real-world first

We design around imperfect data, operational constraints, human judgment, and what must still work on Monday.

Common questions

Before we begin.

What does the engagement include?+

The exact scope is shaped around the decision or workflow that matters most. Before work starts, we set out the deliverables, ownership, decision gates, implementation path, and what is explicitly out of scope.

Who will work on the engagement?+

A senior practitioner owns the work from diagnosis through delivery and reviews every deliverable. When the scope needs additional depth, we bring in vetted specialists and remain accountable for the whole engagement. If the work genuinely needs a large on-site team, we will say so before either side commits.

How quickly can we start?+

Most focused assessments and sprints can begin within two to four weeks. The first working session confirms outcomes, constraints, stakeholders, and the smallest valuable first release.

Can 1730 work with our existing team and technology?+

Yes. We work directly with internal product, engineering, operations, and domain experts. The goal is a system your team can understand, operate, and extend — not a permanent dependency.

Do you work beyond Vancouver?+

Yes. 1730 is based in Vancouver and works with organizations across Canada and the United States. Engagements can be remote, hybrid, or include on-site discovery.

Start a conversation

Bring the messy version.

Tell us what is slow, fragmented, manual, or too risky today. We will help find the highest-leverage place to start.

One sentence is enoughCurrent state · desired outcome · timing

A senior practitioner will reply directly.