Who maintains EditPolygon
The application and its documentation are maintained together under the EditPolygon project. Published guides identify EditPolygon as their maintainer and link back to this page so readers can see the product scope, verification approach, privacy model and limitations behind the instructions.
Questions, corrections and workflow feedback can be sent to feedback@editpolygon.com.
What EditPolygon does
EditPolygon supports editable point, line, Polygon and MultiPolygon workflows, including direct map editing, attributes, styling, selection, Geometry Health, coordinate reference system tools and a browser-local Processing Toolbox. Processing includes operations such as buffer, dissolve, union, intersection, difference, clip, geometry conversion and spatial analysis.
Supported local-data workflows include GeoJSON, KML, KMZ, GML, GeoPackage, TopoJSON, zipped ESRI Shapefile, zipped File Geodatabase, WKT, CSV and EditPolygon project files. Remote sources can also be added deliberately through supported web-service and tile workflows.
Privacy and network requests
Imported local geometry files are processed in your browser and are not uploaded to or stored by EditPolygon. Project work is browser-local unless you deliberately use a remote data source or another web service.
The application makes normal network requests when it loads basemaps, map tiles, place-search results or remote GIS services. Those third-party providers may receive normal request information such as your IP address, browser details and the requested URL. Remote services are contacted directly by the browser rather than being treated as local files.
Technical basis
The current map interface is built on OpenLayers. Geometry and GIS work runs in browser JavaScript and Web Workers, with WebAssembly/GEOS used for robust topology in relevant Processing and Geometry Health operations. The application is designed as a static browser GIS rather than a server-side file-processing service.
Exact behaviour is documented in the current guides, including dedicated pages for Processing, Geometry Health, CRS, local data and remote sources.
How the documentation is produced and checked
Guide pages are maintained with the application source and generated from reviewed guide content. Automated repository checks verify canonical URLs, metadata, structured data, internal links, screenshots, sitemap state and stale generated output. Browser smoke tests exercise the current documentation at desktop and mobile widths alongside the application test suite.
Documentation may be drafted or revised with automated assistance. Automation is not treated as a source of truth: published product behaviour is checked against the current application, repository contracts and automated tests before changes are accepted.
Corrections and update policy
Guide dates are changed when the page or its documented workflow changes materially; dates are not advanced merely to make old content appear new. If a guide conflicts with current product behaviour, report it through feedback@editpolygon.com so the documentation and tests can be corrected together.
The site deliberately avoids fabricated ratings, testimonials, certifications, personal bylines or external affiliations. Structured data describes only entities and relationships that are represented by the published site.
Limitations and responsibility
EditPolygon is a general-purpose GIS editing and analysis tool. It does not replace authoritative source data, professional surveying, cadastral or legal boundary advice, specialist desktop GIS review, or domain-specific safety assessment.
A geometrically valid result can still be wrong for its intended real-world purpose. Check coordinate reference assumptions, source data, processing scope, attributes, topology and exported results before operational, legal or safety-critical use.