GIS Labs

Product

300+ quality checks, each one tested against real data.

Geometry, topology, attributes, networks, coordinate systems, metadata, CAD drawings, 3D city and building models, and vector tiles. Checked against OGC, ISO 19157 and the industry models (LADM, INSPIRE, CityGML, IFC).

Most run as soon as your layers are mapped; the rest are templates you set to your own layers, fields or limits.

What it catches

A few of the problems it finds, drawn the way GeoDoctor shows them on the map.

claimed twice
Polygon overlapTwo parties hold registered title to the same ground.
unclaimed sliver
Gap between parcelsLand belongs to nobody, and appears in no register.
4 210 m²0.9 m²sliver
Sliver polygonA digitising offcut that inflates counts and breaks area totals.
0.02 m gap
Dangling edgeA network trace stops at a gap the map does not show.
ring crosses itself
Self-intersecting ringThe geometry is invalid, so most spatial operations refuse it outright.
2 vertices, 0.004 m apart
Duplicate vertexZero-length segments that crash simplification and buffering.

The checks, by field

Every check comes with a severity and a note on how to fix what it finds.

  • CoreEvery licence144 checks
  • Cadastre & Real Estate42 checks
  • Electric & Telecom26 checks
  • 3D & Buildings28 checks
  • Utilities34 checks
  • Environmental & Hydro25 checks
  • Transportation31 checks
  • Municipal27 checks

What each pack covers

Rule packs, their rules and industry checks, and what each one covers
PackRules and checksWhat it covers
CoreEvery licence144 checksCross-industry checks included with every licence: geometry, topology, attributes, schema and coordinate systems.For example: invalid geometry, empty geometry and coordinates at the origin.
See every check in this pack
  • Mandatory field is empty (null or blank)
  • Value not in the field's coded-value domain
  • Identifier value repeated within a layer
  • Numeric value outside its allowed range (declared domain, role range or configured bounds)
  • Value does not match its required format (pattern, e-mail, phone, URL)
  • Cross-field condition violated (WHEN condition THEN requirement)
  • Value does not fit the declared field (text longer than the width, more decimals than the scale)
  • Text has leading/trailing, doubled, tab, zero-width or non-breaking whitespace
  • Date value is not a valid calendar date or lies outside [min_date, max_date]
  • Description field disagrees with its code's description
  • Start date later than end date (validity/lifecycle interval reversed)
  • Stored coordinate attributes disagree with the feature's position by more than tolerance_m
  • Placeholder stored instead of a value ('N/A', 'TBD', 'unknown', -9999 ...)
  • Field name is a reserved word in SQL or common GIS formats
  • Text contains markup or script (HTML tags, javascript:, event handlers)
  • Same coded value written in different letter cases within a field
  • Text corrupted by encoding errors (mojibake, U+FFFD, control characters, presentation forms, non-NFC)
  • Language-tagged text field holds text in another script (field suffix _xx, ISO 639-1)
  • Stored area or length attribute disagrees with the measured geometry by more than tolerance_pct
  • Numeric value is a statistical outlier within its layer or group (robust z-score above k)
  • Feature has a name in one language and none in the other (English/Arabic name pair)
  • The same Arabic name is written two ways in a layer (alef forms, alef maqsura and ya, ta marbuta and ha, tatweel or diacritics)
  • Identifier mixes Arabic-Indic and Western digits, in one value or across the layer
  • Reference feature has no counterpart in the delivered layer (omission)
  • Area not covered by the coverage layer (area of interest, jurisdiction or parent unit)
  • Layer feature count outside the expected range
  • Share of empty values in a field above max_empty_pct
  • Expected category value absent from the layer
  • Area-of-interest grid cell holds fewer than min_features_per_cell features
  • Feature cut at a delivery-tile edge has no matching continuation in the neighbouring tile (edge-match)
  • Feature not updated within max_age_days (stale)
  • Delivered feature has no counterpart in the reference dataset (commission)
  • Classification disagrees with reference/control data above max_misclassification_pct
  • Attribute value disagrees with the matched reference feature (number beyond the tolerance, or text after normalisation)
  • Change against the previous delivery above the limit (share of features removed, added or changed)
  • Layer has no coordinate reference system
  • Layer CRS not in the project's allowed list (horizontal and vertical)
  • Coordinates outside the area of use of the layer's CRS
  • Feature outside the area of interest
  • Layers of one dataset use different coordinate reference systems
  • 3D layer has no vertical reference system
  • Positional accuracy against control points: horizontal RMSE or systematic offset above limit
  • Layer CRS cannot be identified (custom or unknown definition without an authority code)
  • Vertical accuracy against control points: RMSEz or systematic vertical offset above the limit
  • CAD entity on layer "0" or "Defpoints"
  • Closed shape drawn as an open polyline (start and end within tolerance but not closed)
  • Drawing units or scale implausible (sizes suggest millimetres, centimetres or feet instead of metres)
  • Text or annotation entity not associated with any feature (orphan label)
  • CAD entities not converted to GIS features (blocks, proxies, 3D solids, hatches), listed by type
  • 3D model file does not conform to its format (schema errors, or internal references that do not resolve)
  • Geometry is not OGC-valid (ST_IsValid false; GEOS reason reported: self-intersection, ring self-intersection, hole outside shell, nested holes, interior disconnected, too few points)
  • Feature of a spatial layer has no geometry (null, empty or unparseable)
  • Geometry type differs from the layer's expected type (role geometry, declared type, or dominant type of a mixed layer)
  • Coordinate is NaN or infinite
  • Consecutive duplicate vertices (zero-length segment)
  • Line crosses or retraces itself (non-simple line)
  • Polygon ring not closed or with fewer than 4 positions in the source file
  • Spike: interior angle at a vertex below max_angle_deg (geometry folds back on itself)
  • Non-zero segment shorter than min_segment_length_m (micro-segment)
  • Polygon area below min_area_m2
  • Line length below min_length_m
  • Multipart geometry in a layer whose model requires single-part features
  • Hole larger than max_hole_area_pct of its polygon's outer ring
  • Vertex coordinates not on the delivery precision grid grid_size_m
  • Feature has more than max_vertices vertices
  • Z coordinate missing, NaN or placeholder in a layer that declares or requires Z
  • Z value outside the plausible range [min_z_m, max_z_m]
  • M (measure) values missing where the model requires them
  • Sliver polygon: mean width 2A/P below max_width_m and thinness 4piA/P2 below max_thinness
  • Segment longer than max_segment_length_m (densify before reprojection or along curved boundaries)
  • Vertical spike: height changes between consecutive vertices by more than max_dz_m or max_slope_pct
  • Polygon narrower than min_width_m somewhere (a narrow neck or strip), though not a sliver as a whole
  • Curve segments (arcs, circles, splines, ellipses) where the model requires straight segments
  • M (measure) values not monotonic along a line
  • Polygon ring orientation differs from the format or model convention
  • Metadata missing required elements (ISO 19115-1 mandatory, quality, lineage, or the customer's list)
  • Reference system in the metadata missing or different from the data's CRS
  • Metadata bounding box does not contain the data extent
  • Attribute changes along connected network lines without a node or device that allows it
  • Attribute changes in the wrong direction downstream (e.g. diameter or conductor size decreasing away from the source)
  • Network line does not reach an outlet or source (sink or loop)
  • Line drawn against its flow or fall (start lower than end)
  • Feature not inside a feature of the reference layer (contained, inside, or centroid within)
  • Feature of layer A intersects no feature of layer B
  • Feature of layer A overlaps or crosses a feature of layer B where the model forbids it
  • Point of layer A not on a line of layer B within tolerance_m
  • Feature of layer A closer than min_distance_m to a feature of layer B
  • No feature of layer B within max_distance_m of a feature of layer A
  • Feature lies far from the rest of its layer (robust spatial outlier)
  • Duplicate or near-duplicate features (identical geometry, or within tolerance_m)
  • Feature outside the land reference polygons (off land)
  • Feature in the opposite hemisphere from >= 90 % of its layer (coordinate sign error)
  • Vertex at the coordinate origin: (0,0) in the source CRS or lon/lat (0,0) within 1 m (Null Island)
  • Coordinates transposed (X and Y swapped)
  • Foreign-key value has no matching record in the referenced layer
  • Feature not within the feature it references
  • Line end not covered by a point of the required layer
  • Point does not coincide with a point of the required layer
  • Polygon contains no point, or more than one point, of the required layer
  • Line leaves the corridor of the reference lines it must follow
  • Attribute disagrees with the feature it lies in (e.g. label and parcel identifier, address locality and administrative unit)
  • Feature straddles the boundary of a polygon of the reference layer
  • Layers that must cover each other do not (part of one lies outside the other)
  • Polygon not covered by the union of the reference layer's polygons
  • Polygon boundary not covered by lines of the reference layer
  • Line not on the boundary of a polygon of the reference layer
  • Point not on the boundary of a polygon of the reference layer
  • Required layer missing or empty
  • Required field missing from the layer schema
  • Field definition differs from the model (type, width, nullability) or text values do not parse as the model type
  • Layer or field name violates the naming convention
  • Layer has no persistent unique feature identifier (no mapped ID and no non-system field that is filled and unique)
  • Delivered layer contains no features
  • Delivered layer is not part of the target model (unmapped extra layer)
  • Polygons of the same layer overlap (shared interior area >= min_overlap_area_m2)
  • Gap inside a coverage layer: hole in the union of its polygons with area >= min_gap_area_m2
  • Dangling line end: end touches no other line and no line lies within snap_tolerance_m
  • Lines intersect or touch away from a shared node (crossing or T-junction without a split)
  • Pseudo-node: exactly two lines with identical attributes meet end to end
  • Neighbouring polygons' boundaries do not match: edge within tolerance_m of a neighbour without coinciding (near-miss gap/overlap, unmatched vertex)
  • Lines of the same layer share a collinear stretch (double-digitised segment)
  • Line end within snap_tolerance_m of another line without touching it (undershoot or overshoot)
  • Polygon boundary not covered by the boundaries of the reference layer
  • Line not connected to the network (isolated component, or not connected to a source)
  • Lines cross or touch where the model forbids any contact
  • Number of lines meeting at a node outside the allowed range (valency)
  • Adjacent polygons with identical attributes not merged (unnecessary boundary)
  • Lines intersect at different Z values without a declared grade separation
  • Line closes on itself (forms a loop) where the model forbids loops
  • Lines meet at a node at an angle below min_angle_deg (acute junction)
  • Vector tile over its size or feature budget (max_tile_kb, max_features_per_tile)
  • Vector tile not valid under the Mapbox Vector Tile 2.1 specification (geometry commands, ring winding, zero-area rings, extent, layer and key tables)
  • Vector tiles missing inside the declared bounds and zoom range where the parent tile has data, or present outside them
  • Vector tile layer or attribute schema differs between zoom levels (layer missing inside its zoom range, fields appearing or disappearing)
  • Feature present at the maximum zoom is dropped at a lower zoom of its layer's range although larger than min_pixel_size
  • Tileset metadata missing or inconsistent with the tiles (bounds, zoom range, vector_layers, attribution in TileJSON, MBTiles or PMTiles)
  • E-mail field value is not a syntactically valid address
  • Phone field value is not a plausible international number (7-15 digits, optional + and extension)
  • URL field value is not an absolute http(s) URL
  • Numeric value outside the plausible range (user bounds or robust outlier)
  • Metadata has no data quality information (ISO 19157 report or quality statement)
  • Metadata has no lineage statement (ISO 19115-1 LI_Lineage statement, sources or process steps)
  • Recommended metadata elements absent (customer-selected list)
  • Two features of the same layer have identical geometry
Cadastre & Real Estate42 checksParcels, rights and their sources: overlaps, identifiers, references between records, and areas.For example: current parcels that overlap.
See every check in this pack
  • Retired parcel has no recorded successor
  • Strata participation shares of a scheme do not total 100%
  • Active right on a retired parcel
  • Current parcels overlap each other
  • Narrow gaps between parcels
  • Duplicate parcel identifier among current parcels
  • Right record references a parcel that does not exist
  • Parcel corner not on a surveyed boundary point
  • Parcel overlaps road right-of-way
  • Easement extends outside its servient parcel
  • Child parcels do not exactly cover the parcels they replaced
  • Building footprint straddles a parcel boundary
  • Parcel land-use code not in the code list
  • Parcel survey reference does not exist among the survey sources
  • Boundary point accuracy worse than required
  • Strata units on the same floor overlap
  • Title reference does not match the configured format
  • Parcel lies outside its cadastral block
  • Right, restriction or responsibility without an administrative source
  • Parcel status inconsistent with its validity end date
  • Parcel has no frontage on a road or right-of-way
  • Duplicate right record identifier
  • Parcel without a survey source reference
  • Parcel identifier does not match the configured format
  • Parcel references a cadastral block that does not exist
  • Validity start date later than end date
  • Easement narrower than the minimum width
  • Parcel contains no label point or more than one
  • Label text differs from the identifier of the parcel containing it
  • Strata unit extends outside its building footprint
  • Sliver parcel
  • Recorded parcel area differs from drawn area
  • Surveyed boundary point not on any parcel boundary
  • Building not on any parcel
  • Current parcel without an ownership right
  • Parcel status not in the status domain
  • Ownership shares of a parcel do not total one
  • Parcel identifier empty
  • Right record references a party that does not exist
  • Right, restriction or responsibility type not in the LADM code list
  • Easement references a parcel that does not exist
  • Boundary line does not run along a parcel boundary
Electric & Telecom26 checksAssets and their code lists, transformer references, corridors and recorded lengths.For example: service points that reference a transformer that does not exist.
See every check in this pack
  • Conductor carries a phase not present on the conductor feeding it (phase continuity from the source)
  • Transformer's feeder differs from the feeder of the conductor it is on
  • Loop in a radial distribution feeder (with normally-open points open)
  • More cables assigned to a duct than it has ways
  • Overhead span longer than the maximum without a support structure (supports missing)
  • Conductor size increases away from the source
  • Overhead conductor end not at a pole, tower or substation
  • Duct end not at a chamber, cabinet, substation or another duct
  • Connected conductors of different voltage with no transformer between them
  • Splice closure joins fewer than two cable ends
  • Switching device normal status not 'open' or 'closed'
  • Service point references a transformer that does not exist
  • Fibre count changes along one cable
  • Line outside its right-of-way corridor
  • Recorded cable or conductor length differs from the drawn length by more than 10%
  • Mandatory electric or telecom attribute empty
  • Duplicate asset identifier within an electric or telecom layer
  • Conductor or cable not connected to any source (isolated network component)
  • Line end within 0.5 m of another line of its network but not connected
  • Line end connects to nothing and has no device, support, termination or service point
  • Device or telecom node not on a conductor or cable
  • Voltage outside the plausible range (0.05-1200 kV)
  • Network classification code not in its code list (phase, vertical position, cable type, device, structure and node types)
  • Connected conductors carry different feeder ids without an open point or source between them
  • Fibre count is not a standard cable count
  • Asset status not in the condition-of-facility code list
3D & Buildings28 checksFootprints, identifiers, building parts, heights and Z values.For example: building footprints that overlap.
See every check in this pack
  • Declared LoD does not match the geometry
  • Building shell not closed (watertight)
  • Building surfaces lack a roof or ground surface
  • Shell faces not consistently oriented outward
  • Building base not at its recorded ground elevation
  • 3D model footprint does not match the 2D building footprint
  • Shell volume implausible for its footprint and height
  • Thematic surface type inconsistent with its orientation
  • Building shell self-intersects
  • Degenerate face (fewer than 3 distinct vertices or near-zero area)
  • Face not planar
  • Parts of the same building intersect in 3D
  • Building corner deviates from a right angle by more than the tolerance (footprint not squared)
  • Building height inconsistent with its storey count
  • Building function code not in the code list
  • Building part references a building that does not exist
  • Condition of construction not in the CityGML code list
  • Year of construction outside the plausible range
  • Building footprints overlap
  • 3D building geometry has no Z values
  • Building height outside the plausible range
  • Recorded height differs from the 3D geometry's height
  • Building part outside its building footprint
  • Duplicate building identifier
  • Building identifier empty
  • Building footprint smaller than 2 m2
  • Building shell has non-manifold edges
  • Building solid consists of disconnected parts
Utilities34 checksAssets and their code lists, pipe node references, diameters, depths and lengths.For example: pipes whose upstream or downstream node does not exist.
See every check in this pack
  • Pipe end invert below the invert of its manhole, or above its cover level
  • Water isolation segment longer than the maximum (valves missing)
  • Crossing pipes closer vertically than the minimum clearance
  • Main crosses a pressure-zone or DMA boundary without a boundary valve or meter
  • Pipe's recorded upstream or downstream node is not at the pipe's start or end
  • Gravity pipe slope below 0.1% or above 25%
  • Pipe not connected to any network source (isolated network component)
  • Gravity pipe drawn against its fall (start invert lower than end invert)
  • Pipe material not in the material code list
  • Gravity pipe diameter decreases downstream
  • Utility facility not connected to any pipe
  • Pressure-zone or DMA polygons of the same type overlap
  • Gravity pipe does not drain to an outfall or treatment facility (flow sink or flow loop)
  • Meter not on a service line or main
  • Recorded pipe depth of cover outside the allowed range
  • Pipe end not connected and not closed by an end cap, device or facility
  • Duplicate asset identifier within a utility layer
  • Asset status not in the condition-of-facility code list
  • Valve type or normal position not in its code list
  • Installation date in the future or before 1850
  • Pipe's upstream or downstream node reference names no existing structure
  • Recorded pipe length differs from the drawn length by more than 1%
  • Mandatory utility attribute empty
  • Pipe diameter outside the plausible range (10-4000 mm)
  • Valve not on a pipe
  • Hydrant not connected to a water pipe
  • Manhole not at a pipe end (orphan manhole, or pipe not split at the manhole)
  • Manhole invert level not below its cover level
  • Pipe end within 0.5 m of another pipe of its system but not connected (undershoot or overshoot)
  • Pipes of the same system cross without a junction
  • Potable water pipe connected to non-potable pipe without a closed valve or backflow device (cross-connection)
  • Gas pipes of different pressure class connected without a regulator or closed valve
  • Separate sanitary and storm sewers connected (illicit connection)
  • Network classification code not in its code list (water type, sewer water type, flow type, delivery type, product type)
Environmental & Hydro25 checksHydrography and protected areas: code lists, basin coverage, watercourse continuity and contours.For example: gaps inside a coverage of basins or thematic units.
See every check in this pack
  • Recorded Strahler stream order differs from the order computed from the network
  • Watercourse drawn against its flow (start lower than end)
  • Watercourse does not reach an outlet (flow sink or flow loop)
  • Drainage basins of the same order overlap
  • Watercourse area polygon with no centreline through it (network broken at a wide river)
  • Wetland type not in the Ramsar classification
  • Sub-basin not within its recorded parent basin
  • Water area polygons overlap (standing water and watercourse areas)
  • Monitoring station not on a watercourse or water body
  • Dam or weir not on a watercourse or standing water
  • Thematic coverage polygons overlap (soil, land cover, vegetation, habitat maps)
  • Contour lines cross or touch each other
  • Coverage class code not in the configured classification
  • Mandatory hydrography or environmental attribute empty
  • Duplicate identifier within a hydrography or environmental layer
  • Watercourse not split at a confluence (link end touches another link's interior)
  • Watercourse end within 1 m of another link but not connected
  • Hydrography code not in the INSPIRE code list (flow direction, persistence, origin, node category)
  • Gap inside a coverage of basins or thematic units
  • Recorded area or length differs from the drawn geometry by more than 1%
  • Basin reference names no existing basin
  • Hydro node category disagrees with the links meeting it (or node touches no link)
  • Contour elevation not a multiple of the contour interval
  • Protected area IUCN management category not in the IUCN list
  • Watercourse lies outside the basin it records
Transportation31 checksRoad network topology, crossings and road attributes.For example: road segments not connected to the main network.
See every check in this pack
  • Node with only inbound or only outbound one-way traffic
  • Segments meeting at a node have different z-levels at that node
  • Roundabout segments do not form a closed ring
  • Lines of one group (route or street) are not connected
  • Address ranges overlap on the same side of the same street
  • Road gradient exceeds the maximum
  • Turn restriction does not match the network
  • At-grade road-rail crossing without a level crossing
  • Segments of one street carry different names
  • Measures of a route are not continuous between consecutive segments (gap or overlap in M)
  • Road segment not connected to the main road network
  • Road segments cross at the same grade without a junction node
  • Road class not in the code list
  • Speed limit outside the range allowed for its road class
  • Lane count outside the plausible range
  • Pedestrian crossing not on a road centreline
  • Road surface type not in the code list
  • Road centreline runs outside the road polygon
  • Traffic sign farther than 30 m from any road
  • Road segment ends just short of another segment (undershoot)
  • Segments sharing a route number are not connected
  • Recorded road length differs from drawn length
  • Duplicate road segment identifier
  • Road segment shorter than 0.5 m
  • Road segments overlap along their length
  • Traffic direction code not in the code list
  • Road segment overshoots a junction by a short stub (overshoot)
  • Transit route leaves the road network
  • Transit stop farther than 30 m from its route
  • Road of a named class without a name
  • Pseudo-node between segments with identical attributes
Municipal27 checksAddresses, administrative units, land use and zoning.For example: address street names not found in the road network.
See every check in this pack
  • Land-use polygons do not cover the jurisdiction
  • Administrative units of the same level overlap
  • Point-of-interest category not in the code list
  • Building without an address point
  • Zoning districts do not cover the jurisdiction
  • Address street name not found in the road network
  • Administrative unit extends outside its parent unit
  • Statistical units do not cover the jurisdiction
  • Duplicate address identifier
  • Address point missing house number or street
  • Same address recorded more than once
  • Address point away from its referenced building
  • Address street name differs from every road within 150 m
  • Address locality differs from the administrative unit containing it
  • Child administrative units do not cover their parent
  • Administrative level outside the configured range
  • Duplicate administrative unit name within the same parent
  • Zoning districts overlap
  • Zoning code not in the code list
  • Land-use polygons overlap
  • Land-use code not in the code list
  • Adjacent land-use polygons with the same code are not merged
  • Duplicate point of interest
  • Point of interest without a name
  • Building footprint overlaps a road polygon
  • Statistical units overlap
  • Administrative unit name empty

What the core library checks

144 checks, included with every licence whichever packs you add.

Categories of check in the core library, with what each one looks for
CategoryRules and checksChecks
Attribute integrity20+Nulls in mandatory fields, values outside a domain, pattern and range failures.
Spatial relationship10+Containment, adjacency, coincidence and must-cover constraints between layers.
Topology15+Overlaps, gaps, dangles, disconnected networks and unintended holes.
Geometry integrity15+Self-intersections, slivers, duplicate vertices and zero-area features.
Schema15+Field presence, types, naming conventions and key uniqueness.
Completeness5+Population rates per field and layer, and coverage gaps against an area of interest.
Metadata (ISO 19115)5+Discovery and lineage elements required to publish into a data infrastructure.
Coordinate systems5+Projection and datum correctness across every layer in a submission.

Beyond the checks

Finding problems is half the job. These are the tools for the other half.

Validation engine

Within a validation, runs your selected rules in parallel with live per-rule progress, and reports what it could not read rather than reporting success regardless. One validation runs at a time on an installation.

Dataset intake

Shapefile, GeoPackage, File Geodatabase, CAD drawings and more. Every layer is profiled on arrival with its geometry type, coordinate system, feature count and field list.

Violation triage

Filter by severity, rule and layer. Assign owners, track resolution, and mark false positives with a recorded reason.

Reports

PDF, Excel, HTML, Word and PowerPoint from one run, with your branding, ready to hand to a supplier or a reviewer.

Schema mapping

Match incoming field names to a target schema so rules apply to unfamiliar data. Save a template per supplier.

Professional+

Scheduled runs

Validate a folder or a live connection on a schedule, so a bad delivery is caught before it reaches production.

Professional+

Custom rules

Author your own from parameterised templates, then govern them through draft, review and publish. No scripting.

Professional+

Map viewer

Inspect violations spatially with clustering and heatmaps, annotate the data, and save a workspace to resume a review.

Live connections

Read PostgreSQL/PostGIS tables, and WFS, OGC API Features or Esri REST layers, straight from where they live: no export step. SQL Server, Oracle, MySQL and enterprise geodatabases on request.

Professional+

Quality intelligence

Schema profiling, completeness scoring against a target, and quality trend per supplier over time.

Professional+

Auto and assisted fixes

Safe fixes in one click, proposals for the rest, each a new dataset version with the original kept. Every change recorded.

Professional+

Schema transformation

Turn a supplier schema into your standard, including reprojection and geometry conversion.

Enterprise

Enterprise identity

Single sign-on with your identity provider (OIDC), including its multi-factor authentication, and session governance across every role.

Reads the formats your suppliers actually send

GeoDoctor reads vector data, CAD and 3D models. It does not read imagery, elevation rasters or point clouds.

Upload a file

Drop in the files a supplier sends.

  • Shapefile
  • Shapefile (ZIP)
  • File Geodatabase
  • GeoPackage
  • GeoJSON
  • KML
  • KMZ
  • CSV
  • Excel
  • GeoParquet
  • AutoCAD DXF
  • AutoCAD DWG
  • GML
  • FlatGeobuf
  • MapInfo TAB / MIF
  • GPX
  • SQLite / SpatiaLite
  • CityGML
  • CityJSON
  • IFC
  • glTF / GLB
  • OBJ
  • 3D Tiles
  • I3S scene layer package
  • MBTiles
  • PMTiles
  • Vector tile folder (z/x/y)
  • File Geodatabase multipatch

Compare with a reference

Lay a base layer over the delivery.

  • GeoJSON overlay
  • KML overlay

Connect to a database

Check the data where it already lives.

  • PostgreSQL / PostGIS
  • WFS
  • Esri ArcSDE
  • SQL Server
  • MySQL / MariaDB
  • Esri REST / OGC API Features
  • Oracle Spatial

Dashed: available on request for your installation.

Try it on your own data.

Run the checks for your field on a real layer of your own. You’ll know within an afternoon whether it’s worth it.