The STIP Map Survey Module turns a link to your agency's GIS map — for example an ArcGIS feature layer of draft STIP projects — into a public feedback map in minutes. Residents click any project on the map, tell you whether it should be a priority, and leave a comment — and every response stays tied to that specific project.
There are no survey steps to build and no email, text, or social setup to wade through. You paste a map link, we build the page, and you publish.
In your PublicInput account this module appears in the Create new menu as Map Feedback Project — that is the same thing as the STIP Map Survey Module described here.
Before you start
The STIP Map Survey Module is an add-on for transportation (DOT) accounts. If you don't see Map Feedback Project in your Create new menu (Step 1), it isn't enabled for your account yet — contact your PublicInput representative or email support@publicinput.com and we'll switch it on.
You'll also need the URL of your published GIS service — a public ArcGIS REST endpoint that hosts the projects you want feedback on (it usually ends in /MapServer or /FeatureServer). If you're not sure where to find it, your GIS team can provide it.
Step 1 — Create the project
From your dashboard, click Create new and choose Map Feedback Project.
A short window asks for only three things:
Department — which part of your agency owns this page
Name — what the project is called (for example, "2026–2035 STIP — Project Priorities")
Tags — optional, for organizing your projects
Click Create Map Feedback Project. You'll land directly in the map setup wizard.
Step 2 — Build your map
On the first screen of the wizard, paste your GIS service link into the box and click Build my page. We read the layer, pull in your projects, and generate a draft map with a live preview.
Step 3 — Make it yours (optional)
Your page works the moment it's built, but you can fine-tune the wording and look in the panel on the right. Everything updates the live preview as you go:
Wording — the page title, the corner badge (for example "STIP"), what one item is called (for example "project"), the question people answer ("Is this a priority project?"), and the "How this works" sentence.
What people see when they click an item — choose which fields from your GIS layer appear in a project's detail panel. If a field holds dollar amounts, set Dollar amounts are stored in to match your data (for STIP cost fields stored in thousands, choose thousands); a live preview shows how a value will display.
Category colors & icons — set the map color and a marker icon for each project type. Point projects appear as a colored badge with that icon so residents can spot them at a glance.
Base map — choose which base maps residents can switch between.
Step 4 — Publish and share
When you're ready, click Publish. Two things happen at once: your map goes live, and the project itself is published — so its public link now sends visitors straight to the map. Copy the public link at the top of the wizard and share it however you like.
Step 5 — Manage your map later
Open the project any time from your dashboard. A Map Feedback project shows a streamlined set of tabs — Map, Comments, Participants, and Results & Data — instead of the usual survey steps. The Map tab is your home base. From its card you can:
See whether the page is a Draft or Published at a glance
Open map settings — reopen the wizard to change wording, fields, colors, or icons (it opens your existing map — it never creates a duplicate)
Export responses (CSV) — download every priority vote and comment, tied to each project
Copy the public link to share again
What residents see
Visitors get a clean, branded map. They click any colored line or point to open its details, answer your priority question with a single tap, and add a comment. The legend lets them filter by project type, and search helps them find a specific project by name, ID, or location. The page is mobile-friendly and meets WCAG 2.1 AA accessibility standards.
Tips
It can be a child project. Add it to a Topic or engagement hub just like any other project.
Draft links are safe to share early. Until you publish, the project's public link shows your standard project page rather than the map — so nothing goes live by accident.
Responses travel with the project. Every vote and comment is recorded against the specific map project, so feedback stays meaningful as the project moves through your program.
Frequently asked questions
Who can turn on the STIP Map Survey Module?
It's a DOT add-on. If you don't see Map Feedback Project under Create new, email support@publicinput.com and we'll enable it.
What kind of map link do I need?
A public ArcGIS REST service endpoint (a MapServer or FeatureServer layer). It must be reachable on the public internet — internal-only links won't work. Your GIS team can confirm the URL.
Do residents need an account to participate?
No. Anyone with the link can view the map, mark priorities, and comment without signing in (your project's participation settings still apply).
My project costs show the wrong amount — how do I fix it?
If a cost field is stored in thousands (common for STIP data), set Dollar amounts are stored in to thousands in Step 3. The live preview confirms a sample value before you publish.
Can I change the page after publishing?
Yes. Use Open map settings on the Map tab to reopen the wizard on your existing map. Your edits apply to the live page and no duplicate is created.
How do I get the responses?
Use Export responses (CSV) on the Map tab. Each priority vote and comment is tied to its specific map project.
Will a very large GIS layer work?
Yes — the map handles thousands of projects. Extremely large services are capped for performance; if your layer is near the limit we'll help you scope it.
Are comments moderated?
Comments run through PublicInput's standard moderation, so flagged content is hidden from the public map.
Related articles
Need help?
If your map link won't load, double-check that it's a public ArcGIS REST endpoint and try again. Still stuck? Email support@publicinput.com and we'll take a look.