WikiMapping pricing is based on one year projects.  You’ll see that the plans we offer are based on input from people using WikiMapping.  State governments tend to use WikiMapping through their on-call contractors.


$449 per project

As of October 2022, the price per project is $449. This price reflects increased costs of providing the service. 

This one year price makes it easy for planners to use WikiMapping in their proposals. If your project reaches 3000 comments, then we review the project and you get an email.  The project continues to collect data. Typically, we just increase the limits.

When the project is complete, you still have full access to the results.  New entries are limited.  The status of the project is noted in the upper right part of the map.

Free Project

By default a project is limited to 10 users and 10 comments until it is activated.  There’s a “Draft Project” text. We are happy to increase these limits by request.  The project will remain in draft form until activated.

Project Setup – $400

We encourage people to set up their own projects. That said, it may be faster and more convenient for your organization if we set up your project for you. This is an additional $400 fee above the project price. This includes up to two hours of work. Above and beyond this, the rate is $200/hour. The additional fees reflect times when an organization needs repetitive changes due to uncertainty in what is desired in the first place.

The added benefit is that we will also help you download the results into GIS and provide a summary pdf if requested. 

Typical setup time can vary because you may want to review the project with your clients and make changes. We can get you up in running pretty quickly, typically within a week.


Depending on the need, we may be able to customize WikiMapping beyond its current status. There is an hourly rate, and we can provide a rough but not final estimate for changes. Changes made for one project may be available for others. 

We need ample time to do such customization. And we can decline to implement customization if it doesn’t serve our core audience.