Remote sources are contacted directly by your browser; EditPolygon does not proxy them.
Understand the remote-data boundary
Local files and remote services follow different network paths. Local GIS files remain inside the browser. When you deliberately add a remote source, your browser contacts that provider directly to discover, import or display the requested data. EditPolygon does not proxy the request through its own geoprocessing server.
A local layer can be edited without uploading it. A remote ArcGIS, GeoJSON, WMS or tile source necessarily reveals a normal browser request to that source provider when you use it.
Open Advanced GIS → Add data
Switch to Advanced GIS and choose Add data. The panel separates local browser files from web sources and raster/tile services.
Use Open GIS files for local GeoJSON, KML/KMZ, GML, GeoPackage, Shapefile ZIP, zipped File Geodatabase, CSV, WKT, TopoJSON and project files. Use the remote sections only when the source is a web address or service.
Discover ArcGIS REST sources
EditPolygon understands common ArcGIS URLs rather than requiring you to manually construct a /query request. You can paste a services directory, FeatureServer/MapServer service, individual layer, query URL or supported ArcGIS item link.
The discovery flow can step through:
- Paste the ArcGIS link.
EditPolygon classifies the address and requests metadata directly from the provider.
- Choose a service or folder.
A REST services directory can contain many services.
- Choose one or more layers.
A FeatureServer/MapServer can expose several feature layers.
- Preview a selected layer where useful.
Review layer name, geometry family, feature count and source CRS metadata.
- Import selected data.
The feature data becomes normal project geometry when imported as editable data.
ArcGIS query requests use browser-compatible REST behaviour and handle pagination/object-ID workflows as needed by the current importer.
Remote GeoJSON
A direct .geojson or .json data URL can be discovered and imported when the provider allows browser access. The response must actually be JSON/GeoJSON rather than an HTML webpage.
If a pasted URL opens a normal webpage instead of spatial data, EditPolygon reports that distinction rather than treating the HTML as malformed GeoJSON.
WMS
Add a WMS when you need a server-rendered map image as contextual/reference data. Configure the service URL and layer information in the Add data workflow. WMS is presentation/reference imagery; it is not automatically editable vector geometry.
Because the browser talks directly to the WMS provider, the service must support requests compatible with your browser/network environment.
XYZ, TMS and TileJSON
Custom tile sources can be added as a basemap or reference overlay. Provide a name, source type and URL template/service information. Opacity can be adjusted for overlays so editable vectors remain readable above the source.
Tile sources provide map imagery/tiles rather than editable feature attributes. Use a FeatureServer/GeoJSON source when you need actual vector records for selection, joins or Processing.
Manage remote layers alongside local data
The Advanced GIS Layers tab shows editable data, local reference/image layers, remote service layers and basemaps in one list. Remote layers can be shown/hidden, reordered, grouped and adjusted for opacity where supported.
A remote layer's presence on the map does not automatically make it an editable Processing input. Processing forms list the compatible editable/project inputs that the selected tool can actually use.
Troubleshoot browser access and CORS
The service works in a desktop GIS but EditPolygon cannot reach it
The provider may not allow cross-origin browser requests, may require authentication/cookies, or may be accessible only from a particular network. Because EditPolygon does not proxy the request, browser-access rules matter.
The URL returns HTML instead of GIS data
Check that you copied the REST/data endpoint rather than a human-facing portal page. ArcGIS links can often be resolved automatically, but a generic website cannot be converted into a feature service without an actual data endpoint.
An ArcGIS service contains many layers
Use the discovery chooser to select one, several or all exposed layers rather than importing an arbitrary first layer.
The source is slow
The remote provider controls response speed and service limits. Import only the layers needed for the task and use the provider's appropriate feature layer rather than a broad services directory once you know the target.
Project recovery and remote definitions
Remote source configuration is project context rather than a copy of every external server resource. Keep source URLs/documentation available when a project needs to be reproduced later, and verify that remote services still exist and return compatible data when reopening a workflow.
- The source is genuinely remote data rather than a local file that should stay browser-local.
- An ArcGIS REST/service/layer URL is used instead of an unrelated web page.
- The chosen service layer has the expected geometry type and feature count.
- Reference imagery/tiles are not being mistaken for editable vectors.
- The provider permits direct browser access from the current network.
- Source CRS metadata was reviewed after editable vector import.