Frequently Asked Questions
We've tried to make this site and it's applications as easy to use as possible, but sometimes questions come up, and we will add our replies to this page.
If you have a question not covered here, please use the Contact page to ask us.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
During the High Park fire in June 2012, our Fort Collins team saw first hand how difficult it was to locate accurate, up to date, usable maps of the fire, evacuation areas, shelters and other related information. We quicly threw together a site for that specific fire, but we quickly realized that a better, long-term solution was needed, so we built WildfireMaps.com.
The application has a set of back-end tools that allow us to manage the data sources, and incident information, and so we have a secured arae of the site for dealing with that. We will also be introducing some crowd-sourcing capabilities in the near future which will require people to create an account.
