The tools that read something you have and answer at once — a File Geodatabase's schema, coordinates between systems, what a shapefile or GeoPackage holds, what an outside service serves — each with a page of its own in the Tools catalog.
Open Inspect and exploreInspect and explore is a category of the Tools catalog in Hyz Portal, under Tools: the tools that read something you have — a file, a service — and answer at once. None of them is metered, and each has a page of its own, found with every other tool in the catalog. More arrive as people ask for them. (They were a page of their own, Mini apps, until 2026-10-21; its old addresses forward.)
The first of them reads what a File Geodatabase holds — the folder ArcGIS keeps a database in — or an Esri XML Workspace Document, the file ArcGIS writes with Export › XML Workspace Document. No ArcGIS is needed on your side.
Drop one of these anywhere on the page, or choose it with the file or folder picker:
| You drop | What happens |
|---|---|
A zipped geodatabase (a .zip holding a .gdb folder), or the .gdb folder itself |
Your browser picks the geodatabase's own catalogue out of it — a few hundred kilobytes for any size of geodatabase — and sends only that to Haiyz, which reads it and keeps nothing. The schema opens in a second. |
| An XML workspace document | It is read in your browser and never uploaded. |
From Export: the PDF report in your language, the tables as CSV (in a zip) or one Excel workbook, the schema as JSON, a Markdown data dictionary for a wiki or a repository, and the workspace document itself as XML.
Upload as a data item takes the geodatabase you dropped to the create popup with the file already chosen.
A point, a pasted list, a shape or a whole file from one coordinate system to another — Ain el Abd 1970 (the older Saudi datum much municipal data is still in), KSA-GRF17 (the national frame), WGS 84, their UTM zones, and any system in the EPSG registry. Haiyz's engine does the conversion with the transformation the EPSG registry gives for where your data lies, and tells you its accuracy: Ain el Abd to WGS 84 is ±18 m in Saudi Arabia, to KSA-GRF17 ±2 m; a change of zone or of degrees to metres is exact.
| You give | What happens |
|---|---|
| A point — latitude and longitude, or easting and northing, written any way (24.7136, 24°42′48.96″N, 24 42 48.96 N) | Converted as you type: the result large, in DMS too when it is degrees, and the same point in the other Saudi systems. |
| A list — one place a line, a name in a third cell if you like | Read and converted as a table, input beside output. |
A shape — WKT (POLYGON ((…))) or GeoJSON |
Converted, drawn on the map, its WKT ready to copy. |
| A file — a zipped shapefile, GeoPackage, KML, KMZ, GML, GPX, GeoJSON or a CSV with coordinate columns | A file that says its system is read in it; one that does not asks you to choose it under From. The result is on the map and downloads in the format you choose. |
From and To are the picker every tool uses — the Saudi systems first, then the registry by name or code — and under each, chips for WGS 84, KSA-GRF17 and Ain el Abd whose UTM zone follows your input. The page opens on Ain el Abd / UTM zone 38N → WGS 84.
Export: the coordinates as CSV or Excel, the shape as GeoJSON or WKT, or a shapefile, GeoPackage, GML or FlatGeobuf in the To system (GeoJSON, KML and KMZ are WGS 84 by their own standards).
Before you upload a shapefile or a GeoPackage, see what is in it and what will break. Drop a zipped shapefile (one or several), the loose .shp, .dbf, .shx and .prj together, or a GeoPackage.
| It shows | And it checks |
|---|---|
| Every layer: geometry type, feature count, coordinate system, extent, the fields as the file declares them with their empties and a few values, the first rows, geometry health, a map | A missing .prj (and whether the numbers read as degrees or metres), a text encoding nothing declares or a .cpg that lies, field names cut at ten characters, duplicate or unsafe names, invalid or empty geometries, mixed types |
| A shapefile's text encoding, read from the DBF's own bytes — UTF-8, or Windows-1256 as older tools wrote Arabic — so the Arabic reads right here | Whether a tool that trusts the file will show garbage |
| A GeoPackage's version, extensions, spatial indexes, defined systems and attribute tables | A layer without a spatial index, an undefined coordinate system, a table the GeoPackage does not list |
Each check says how serious it is — will break, will surprise, a note — and what to do.
Repair and download writes the file back with what was missing: a .cpg naming the encoding, a .prj for the coordinate system you choose, every other byte kept; or the whole as a GeoPackage in UTF-8 with the system set on each layer. Export gives the PDF report, the fields as CSV or Excel and the inspection as JSON. Upload as a data item takes the file to the create popup.
Paste the address of an outside service — an ArcGIS REST catalog, service or layer, a WMS or WFS endpoint, an OGC API Features page or collection, or a GeoJSON file — or choose one of your saved sources, and see what it serves before you link it.
| It shows | And it checks |
|---|---|
| The service: its title, publisher, version, capabilities, formats, coordinate systems, extent and copyright, and what it lists — folders and services to open, layers, tables, feature types, collections | What breaks a link: a WMS (pictures, no features), a WFS with no JSON output, an ArcGIS layer larger than one answer that cannot page, a raster |
| A layer: its fields with their aliases, types and coded values, its geometry, systems and extent, how many features it holds, its symbology, subtypes and relationships, a sample drawn on the map (a WMS layer's own picture and legend), the first rows | What will surprise: a very large layer, no count, no coordinate system; and notes — editable, attachments, coded domains |
Link as a data item makes a live data item that reads the layer from the service — a saved source is made for a pasted address first, in your name. Export gives a layer's fields as CSV or Excel and the service as JSON.
Haiyz's engine fetches the address through its guard: HTTPS only, public addresses only, nothing stored. A service that wants a credential is read through a saved source that holds it.