Capability Reference
Purpose: Check format, role, device, and workflow requirements.
Before you start: The application version, workspace, and intended task.
Expected result: You know which prerequisites to confirm before deploying the workflow.
This module summarizes what Mapplex can do in the current application. Use it as a practical boundary guide when planning a deployment, training a team, or deciding which workflow belongs in Mapplex.
1. How to Read This Reference
Mapplex capabilities depend on four things:
| Factor | What It Controls |
|---|---|
| Workspace plan / entitlement | Whether premium tools such as Geova AI, GeoPackage and GDB exchange, Smart Logic, CAD, SHP, slope tools, and team features are available |
| Project role | Whether a user can create features, manage forms/layers, import reference data, or run administrative actions |
| App settings | Whether optional map tools such as GPS recording, Advanced Edit, Sketch Mode, Quick Capture, or Slope Profiler are visible |
| Device and network context | Whether GPS, offline tiles, native local sync, cloud sync, and AI services are available |
If a tool is unavailable, the app normally shows a lock state, a disabled control, or a role/permission message.
2. Offline, Online, and Local Network Behavior
| Capability | Offline | Requires Internet | Notes |
|---|---|---|---|
| Local projects | Yes | No | Stored on the current device |
| Hosted projects | Limited | Yes for sync | Data can be viewed locally after loading, but cloud updates need connectivity |
| Drawing and forms | Yes | No | Works with locally available project data |
| GPS capture and tracking | Yes | No | Requires device location permission |
| Offline basemaps | Yes after download | Yes to download | Cached tiles remain available until cleared |
| Local GIS import/export | Yes for supported local formats | No for local processing | Required data and attachments must be on the device; large files depend on available memory |
| File Geodatabase conversion | No | Yes | Sign-in and Geova conversion-service access are required for both import and export |
| Local P2P sync | Local network only | No internet required | Requires supported native/local-network capability and same Wi-Fi or hotspot |
| Team collaboration | No | Yes | Requires authenticated cloud workspace |
| Generative Geova AI questions | No | Yes | Requires sign-in, workspace credits, and network access |
| AI field intelligence | Local evidence may be available | Use online for the supported answer workflow | A validated technical answer costs one workspace AI credit, including deterministic checks |
| Cloud audit/history | No | Yes | Availability depends on plan and retention policy |
3. Account, Workspace, and Role Boundaries
Account Model
- Users can sign in with an account or continue in Guest mode for local-only work.
- New accounts may require admin approval before accessing a workspace.
- Each account supports up to two trusted devices.
- Workspaces isolate projects, layers, forms, members, and cloud data.
Typical Role Capabilities
| Role | Typical Use | Practical Boundary |
|---|---|---|
| Owner | Workspace and project lead | Full project and member administration |
| Admin | Operational administrator | Manages users, data, imports, and most project settings |
| Editor | GIS or data lead | Edits data and manages imports, but some advanced map tools remain Owner/Admin-only |
| Collector | Field data entry | Adds records to existing layers and completes forms; does not manage schema or reference data |
| Viewer | Review-only access | Views and exports where allowed; does not create or edit records |
Advanced polygon split/merge is limited to Owner/Admin access in the map code. CAD import, SHP import, and reference-layer import require Owner, Admin, or Editor access.
4. Feature Requirements Matrix
Use this table when a user asks why a tool is locked, hidden, or unavailable. Availability can still vary by workspace configuration, but these are the practical requirements reflected by the current app.
| Feature | Plan / Entitlement | Role | Setting | Network / Device |
|---|---|---|---|---|
| Create local project | Core | Any signed-in user or Guest | None | No internet after app loads |
| Create hosted project | Free retains its existing limit; Pro 5 / Teams 10 / Enterprise 20 per workspace | Signed-in user with workspace access | None | Internet required |
| Create features | Core | Owner, Admin, Editor, Collector | Active layer selected | GPS optional unless capturing location |
| Edit feature attributes | Core | Owner, Admin, Editor; Collector for own records where allowed | None | No internet for local data |
| Manage layers and forms | Core | Owner, Admin, Editor | None | No internet for local projects |
| GeoJSON / KMZ / CSV export | Core | Any project member with export access | None | No internet for local export |
| GeoPackage export | GeoPackage entitlement | Any project member with export access | None | No internet for local export |
| File Geodatabase import/export | GeoPackage export access for export; authorized import access | Owner/Admin/Editor to create layers; Collector can import into an existing layer | Signed-in session | Internet and Geova conversion service required |
| PDF map export | PDF export entitlement | Any project member with export access | None | No internet after map data and tiles are available |
| Spreadsheet import | Spreadsheet import entitlement | Owner, Admin, Editor, Collector | Target Point layer selected | No internet for local files |
| Reference zone import | Reference import entitlement | Owner, Admin, Editor | None | No internet for local files |
| Spatial Auto-Fill | Reference import / form entitlement | Form manager to configure; collector to use | Reference polygon layer and field mapping configured | No internet after data is loaded |
| Smart Logic | Smart Logic entitlement | Owner, Admin, Editor to configure | Form rule configured | AI-assisted setup needs internet and credits |
| Lexicon picklists | Lexicon entitlement | Owner, Admin, Editor to manage; collectors can use | Field linked to Lexicon | No internet after values are loaded |
| Quick Capture | Quick Capture entitlement | Owner, Admin, Editor, Collector | Quick Capture ON | GPS permission required |
| Fill by voice | Voice-entry entitlement and enabled workspace access on an eligible paid plan | Signed-in user with permission to create the record | Quick Capture ON; read Privacy & processing | Internet, AI points and workspace AI/sharing permission; Android speech service and microphone permission for recording; typed description fallback |
| GPS recording tools | Core / enabled workspace feature | Owner, Admin, Editor, Collector | GPS Recording Tools ON | GPS permission required |
| Advanced split / merge | Core / enabled workspace feature | Owner, Admin | Advanced Edit ON for side panel; radial controls for contextual polygon actions | No internet |
| Sketch Mode | Core / enabled workspace feature | Owner, Admin, Editor, Collector | Sketch Mode ON | Local project annotations on this device |
| Slope Profiler | Slope Profiler entitlement | Field user with project access | Slope Profiler ON | Device sensor support recommended |
| Offline map tiles | Core | Any project member | None | Internet required to download tiles |
| Local P2P sync | Core / native support | Project members with sync access | None | Same Wi-Fi or hotspot; native local-network support |
| Cloud sync / team collaboration | Team or cloud entitlement | Signed-in workspace member | Hosted project | Internet required |
| Audit history | Team / audit entitlement | Project member with access | None | Internet required for cloud history |
| Geova Project Planner | Teams/Enterprise and enabled workspace | Creation: Owner/Admin; design/review and execution availability can differ | Resolve questions and assumptions, check capacity, review and confirm | Online; design/revision and successful creation use separate credits |
| Work schedule / My work | Teams/Enterprise and enabled Work access | Owner/Admin assign; Editor plans/updates; Collector progresses assigned work; Viewer reads permitted work | Optional Work map icon | Hosted changes require server confirmation; in-app reminders only |
| Geova AI generative questions | Geova AI entitlement and credits | Signed-in workspace user | None | Internet required |
| AI field intelligence | AI access; one credit per validated technical answer | Authorized project user | Intended project/layer/selection | Use online; local computation does not remove billing or access requirements |
| AI dashboard query generation | Geova AI entitlement and credits | Signed-in workspace user | None | Internet required |
| CAD import | CAD Manager entitlement | Owner, Admin, Editor | None | No internet for local file import |
| CAD export | CAD Manager entitlement | Any project member with export access | Target CRS selected | No internet for local export |
| SHP import | SHP Manager entitlement | Owner, Admin, Editor | None | No internet for local file import |
| SHP export | SHP Manager entitlement | Any project member with export access | None | No internet for local export |
Contextual Drawing and Precision
The default Use radial drawing controls setting hides the drawing toolbar. Long-press or right-click opens actions for the selected map context. The menu respects feature permissions; it does not grant additional access.
Add Point / Precision Crosshair provides controlled placement at the map center. Snap to Features helps align with visible edges. Neither is an accuracy certification or a replacement for geometry review. See the worked drawing guide.
5. Project and Dashboard Capabilities
Mapplex supports:
- Hosted cloud projects for collaboration and sync
- Local offline projects for guest work, field-only collection, and disconnected use
- Initial project import from KMZ, KML, or GeoJSON
- Uploading a local project to hosted storage when collaboration is needed
- Project deletion with typed confirmation
- Project statistics: feature counts, completion percentage, length, and area
- Guided dashboard filters for non-technical users
- Raw filter expressions for users who know the layer schema
- AI-assisted dashboard query generation when Geova AI is available
- File Geodatabase conversion with supported feature attributes and attachments; consult the format preservation limits for separate related tables
Dashboard raw SQL is a filter-expression tool, not a full database console. Enter conditions such as status = 'Open' AND priority = 'High', without SELECT, WHERE, joins, ordering, grouping, or database functions.
6. Map and Field Collection Capabilities
The Map View supports:
- Point, line, and polygon collection
- Geometry drawing with layer-aware tools
- Snapping to nearby vertices and edges
- GPS point capture
- GPS path recording and silent tracking when GPS tools are enabled
- Quick Capture for faster point collection when enabled and entitled
- Manual coordinate entry
- Precision crosshair placement
- Distance, multi-segment, perimeter, and area measurement
- Offline tile download and cache management
- Satellite/street basemap switching
- Layer visibility controls
- Feature popups with form values, photos, geometry details, edit/delete actions, and history where available
- Advanced polygon split and merge for Owner/Admin users when Advanced Edit is enabled
- Sketch Mode when enabled
- Temporal playback when date/time fields exist
- Geova AI preview and previous-result overlay pills
GPS accuracy depends on the device sensor, sky visibility, and operating-system permissions. Mapplex can display accuracy indicators, but it cannot make phone GPS equivalent to survey-grade equipment.
7. Layers, Styling, and Data Dictionary
Layer tools support:
- Point, LineString, and Polygon layers
- Marker colors and marker icons
- Polygon fill/hollow display
- Label display from selected fields
- Feature clustering for dense point layers
- Green/red completion for all eligible visible fields, including optional fields, where entitled; this overrides classification colors
- Categorical and graduated symbology where entitled
- Classification methods including quantile, equal interval, and Jenks
- Color ramps such as blues, reds, greens, yellow-orange-red, and red-yellow-green
- Data Dictionary aliases, units, type hints, and semantic field roles
Use the Data Dictionary for human-readable field names, units, and roles. It improves maps, exports, forms, and AI query quality.
8. Forms and Data Quality
Forms can include:
| Field Type | Typical Use |
|---|---|
| Text | Names, notes, identifiers |
| Number | Counts, ratings, dimensions, readings |
| Dropdown / manual select | Controlled choices |
| Lexicon picklist | Shared standardized terms where entitled |
| Date | Inspection dates, install dates, visit dates |
| Date and time | Visit start times and other observations that need both a day and time |
| Checkbox | Yes/no or completion flags |
| Photo | Single image capture |
| Gallery | Multiple photos where entitled |
| Attachment | Supporting files and documents |
| Auto geometry | Coordinates, length, area, or perimeter values |
Additional form capabilities include:
- Schema import from supported data files
- Spatial Auto-Fill from reference polygon layers using point-in-polygon or centroid-in-polygon lookup
- Needs attention indicators for saved spatial mappings whose source layer or property is unavailable
- Non-blocking manual-entry guidance during Quick Capture and standard Map capture when a configured spatial value cannot be resolved
- Smart Logic for conditional visibility, required inputs, fixed/copied values, and calculations where entitled
- AI-assisted Smart Logic generation where Geova AI credits are available
- Lexicon linking, matching, and value cleanup where entitled
- Photo, gallery, and file attachments for field evidence
- Related-record workflows for linking inspections, work orders, or visits to a parent asset where enabled for the workspace; each operation has its own access requirements
For reliable field data, keep field names clear, avoid duplicate meanings, and use Lexicons or dropdowns for values that must be consistent.
9. Import and Export Matrix
| Format / Tool | Import | Export | Important Notes |
|---|---|---|---|
| GeoJSON | Yes | Yes | General-purpose GIS/web format |
| KML / KMZ | Yes | KMZ export | Useful for Google Earth-style handoff |
| GeoPackage (GPKG) | Yes | Entitled feature | Large files may show warnings before processing |
| File Geodatabase (GDB) | Zipped GDB via online conversion | GeoPackage export access and online conversion | Project package can preserve supported related data and embedded files; ordinary import is not a full-project restore |
| CSV | Yes for point import | Yes | Spreadsheet import requires coordinate columns |
| Excel (.xlsx / .xls) | Yes for point import | No native Excel export | Export CSV for spreadsheet review |
| Reference zones | KMZ, KML, GeoJSON | Managed in app | Polygon background layers for Spatial Auto-Fill |
| DXF | Entitled CAD Manager | Entitled CAD Manager | 2D drawing and matching PRJ delivered in a ZIP; polygon holes become separate closed outlines, not CAD hole relationships |
| SHP | Entitled SHP Manager | Entitled SHP Manager | Supports ZIP archives or loose shapefile component files |
| PDF map | No | Entitled feature | Print-ready map layout and legend output |
| Engineering drawing PDF | No | Yes where export tool is available | Schematic drawing output, not a legal survey plat |
Spreadsheet import is intended for point layers because it creates geometry from latitude/longitude or projected coordinate columns.
What an Export Preserves
Use this table to choose a handoff format. “Supported” means the source content and selected workflow meet the format’s requirements; verify a representative export in the receiving application.
| Content | GeoJSON / CSV | GeoPackage | GDB conversion |
|---|---|---|---|
| Feature geometry | GeoJSON retains geometry; CSV provides a table with coordinate columns | Feature geometry is included | Converted feature geometry is included |
| Feature attributes | Included, subject to the format’s value representation | Supported typed fields are included | Supported converted fields are included |
| Mapplex forms, rules, styles, and choice lists | Not a complete project setup backup | Supported Mapplex metadata is included; other applications may ignore it | Preservation depends on conversion and the receiving application |
| Feature photos and files | Do not assume a self-contained media archive | Supported embedded attachments are included; verify the files open | Verify converted attachment content and links in the receiving application |
| Separate related tables and their relationships | Not a complete relationship backup | Included for supported structures through Project package, not ordinary layer-only export | Project package → FileGDB ZIP preserves supported relationships and embedded files, and includes the original GeoPackage |
For related data, follow Export a project package. Hosted packages use cloud data and exclude unsynced edits. Forms and rules remain metadata in other GIS applications; the package does not recreate the complete app workflow or its permissions.
Keep the original project and source files until you have verified the handoff. Do not infer a complete project backup from a successful geometry export.
10. CAD, SHP, and CRS Handling
CAD Manager
CAD Manager imports DXF entities into Mapplex layers and exports collected features back to DXF. Import supports common entities such as points, lines, polylines, circles, arcs, ellipses, splines, solids, and 3D faces. Block inserts are not expanded as editable feature geometry.
CAD and SHP Manager offer a worldwide coordinate-system catalogue. Confirm the source system from the accompanying PRJ file, search by name or EPSG code, or review the suggestions for your project area. For export, choose WGS84 or a suitable supported projected system agreed with the recipient. A suggested system is not proof of survey accuracy.
Use Prepare DXF ZIP, complete the save/share action, then extract the drawing and matching PRJ into the same folder. Confirm the coordinate system and units in the receiving application. This route exports 2D geometry, not forms, attributes, attachments or related records; polygon holes become separate closed outlines and heights are not retained. See CAD delivery steps.
SHP Manager
SHP Manager imports and exports ESRI Shapefiles. It can read ZIP archives containing one or more shapefiles, or loose component files selected together. A .prj file allows automatic CRS detection; without one, confirm the source CRS before importing.
11. Geova AI Capabilities and Boundaries
Geova AI can help with:
- Counting, filtering, sorting, grouping, and summarizing records
- Drafting dashboard filter expressions
- Finding nearest features and building buffers
- Joining points to zones or comparing layers
- Running supported spatial workflows such as gap analysis, catchment analysis, suitability ranking, clustering, density, interpolation, and scenario comparison where available
- Running deterministic, read-only field-quality, completeness, conflict, selected-feature intersection, and inspection-handover checks; a validated technical answer uses one workspace AI credit
- Showing Decision-grade, Review required, or Advisory only evidence labels so users can distinguish exact evidence from warnings, samples, or fallbacks
- Suggesting one controlled form value from the current Lexicon or fixed options, with a review card, explicit confirmation, guarded Apply, and safe Undo where role and record state permit
- Proposing asset work creation or assignment, with explicit confirmation and the same role permissions as Work Schedule
- Previewing result layers on the map
- Exporting AI results to formats such as GeoJSON, CSV, KML, or PDF
- Saving AI results as permanent Mapplex layers after review
Important boundaries:
- Use Geova AI with a signed-in session, network access, and workspace credits. A validated technical answer costs one credit whether it uses deterministic checks, a spatial template, or model assistance. Clarifications, failed operations, welcome-screen suggestions, and conversational replies are not billed as technical answers. A verified answer of zero can be billable. See AI credits.
- Ordinary analysis uses complete referenced layers by default. The current map extent or selected features become the scope only when the request explicitly asks for them.
- Controlled field suggestions affect one feature and one field. They cannot bypass form rules, Lexicons/domains, role/ownership checks, explicit confirmation, or hosted sync authorization.
- The model works best when layers, fields, aliases, units, and roles are configured clearly.
- AI requests may include layer schema, field samples, and relevant location context.
- Project-data chat displays record lists locally. Full records and geometries are not sent to Geova AI as result rows; question text and limited field samples may still contain information you need to protect. See Privacy & Data Safety.
- Review generated SQL, previews, and exports before using them in operational decisions.
- Do not treat AI output as certified engineering, legal, safety, or regulatory advice.
12. Offline Field Readiness Checklist
Use this checklist before sending a team into the field, especially when the work area has weak or no connectivity.
Before Leaving the Office
- Open the correct workspace and project on each device.
- Confirm the active layers, forms, dropdowns, Lexicons, Smart Logic rules, and required related-record structures are loaded.
- Download offline tiles for the work area and verify the map still displays after disabling internet.
- Confirm GPS permission is granted and the blue location dot appears on the map.
- Check the correct field tools are enabled in Settings: GPS Recording Tools, Quick Capture, Sketch Mode, Advanced Edit, or Slope Profiler as needed.
- Confirm each user has the right role for the job: Collector for entry, Editor for imports and corrections, Owner/Admin for advanced editing.
- Check available device storage, especially when collecting photos, attachments, or large imported layers.
- Confirm the sync plan: cloud sync if internet is expected, local P2P sync if the team will use the same Wi-Fi or hotspot.
At the Site
- Select the correct project and active layer before collecting the first feature.
- Wait for GPS accuracy to stabilize before capturing important locations.
- Use controlled fields, Lexicons, or dropdowns instead of free text when consistency matters.
- Add photos and notes while still at the location, not later from memory.
- If GPS is poor, use manual coordinates or crosshair placement only when you have reliable source coordinates.
Before Leaving the Site
- Review the collected features table for missing required values, obvious duplicates, and empty photo fields.
- Use local P2P sync if multiple devices need to consolidate records without internet.
- Export a quick CSV or GeoJSON backup when the workflow requires a local handoff.
- If cloud sync is expected, open the Dashboard once connectivity returns and confirm pending syncs have cleared.
13. Practical Deployment Checklist
Before rolling Mapplex out to a team:
- Create the workspace and confirm the plan includes the tools you need.
- Define user roles before inviting the team.
- Create layers with clear geometry types.
- Build forms with consistent field names and controlled values.
- Configure Data Dictionary aliases, units, and semantic roles.
- Import reference zones if Spatial Auto-Fill is part of the workflow.
- Test the required import/export formats with a representative client file. For GDB, confirm connection requirements and compare the returned fields and attachments with the source.
- Download offline tiles for the field area before travel.
- Confirm GPS permissions on each device.
- Run one end-to-end pilot: collect, edit, sync, export, and review.
Previous: Module 14: SHP ManagerNext: Module 16: Sample Project - Municipal Asset Inspection