📝 Overview
Resident/non-resident pricing is controlled by a boundary. This boundary can be any arbitrary shape and can even include donut holes, which are zones within a boundary that are not part of the boundary. This can happen in some municipalities for various reasons. Even complex boundaries can be represented.
💡 Interested in other data import services? Learn more about the full range of data import options available for your organization.
🔑 What is Needed
Click the arrow to learn more about GIS boundary file requirements
Click the arrow to learn more about GIS boundary file requirements
A Google Earth boundary file (KML or KMZ format) is required in order to import the boundary for your organization. Typically, these can be provided by Public Works departments using software called Arc GIS. If you are having difficulty locating a Google Earth boundary file for your organization, you can reach out to our support team and one of our developers may be able to help locate a file. Once this file is provided, our team will import this boundary into the platform and your organization can enable the GIS Mapping feature in the application. Resident/non-resident pricing will then be available.
✍️ Note: A KMZ file is simply a compressed version of a KML formatted file. Compressed files are smaller and easier to copy, so Arc GIS and other tools often create this format.
🧩 Examples
Click the arrow to view boundary examples
Click the arrow to view boundary examples
Below are some example boundary images and KML/KMZ files. The boundary for your organization may be simpler than these, but it does not have to be. As long as the boundary file is provided in Google Earth KML or KMZ format, it can be imported.
Post Falls, ID - The yellow areas are within the city while the gray areas are not (exclusion zones).
Evendale, OH - The blue area is within the boundary. This boundary has no donut holes (exclusion zones).
💡 We are happy to provide an example KML/KMZ file upon request by emailing [email protected].