The Bathymetry Data Automator aggregates bathymetric data from several data stores and processes appropriate shading contours, shaded reliefs and other vector and raster-based output to visualize an area of the ocean or other waterway.  The tool is user-customizable and allows the user to pick from available processing resolutions, units, intervals and interpolation patterns.

This program can run stand-alone or integrate with ESRI ArcMap via a base-map to draw a particular AOI (Area of Interest) to process.  The coordinates of the AOI are utilized to process data across data stores and to look for the specific resolutions specified by a user that has a particular interpolation pattern in mind.

Data is output in ESRI ArcMap-capable file formats including Shaded Reliefs, Arc ASCII Grids, Contour Files, TIFF Images and 3D Coordinate Files. The Bathymetry Data Automator allows output to be imported directly into ArcMap for further processing or data viewing within additional existing map layers.

This program works with ArcMap 9.3.1 and is written in .NET.  (ArcMap v10 version coming soon)

The Metadata Manager allows for centralized storage and editing of attributes for stand-alone files and ESRI-formatted Geodatabases.  This program can point to independent data stores that contain adjustable sets of fields and groupings which can then be applied across a set of files within a file system.  The application of metadata attributes is recursive, but filterable, allowing for only the inclusion or exclusion of certain file types. 

Additionally, metadata contained within ESRI Personal and File Geodatabases can be updated directly at the source. Fields can be added or removed appropriately while being tracked within the local data store.  These features allow for maximum flexibility when applying grouping and tracking attributes across geospatial data items and related files.

The Metadata Manager tracks items within the file system and can alert the user if something has changed since the last scan or update.  The user can scan any number of local or network filesystems or directories. Data can be edited via dynamic data forms based on the fields specified for each grouping.  This program can support an unlimited number of groups of metadata.

The Geospatial Inquiry Tracker allows for metadata storage, document management and workflow logging for geospatial issues or “inquiries”.  This program centralizes data across multiple sources representing multiple Classification levels. The Tracker allows for entering and updating appropriate data for each inquiry as well as creating a new inquiry.  Data tracked includes 2D geospatial coordinates and vectors, form-based metadata, file-based attachments and database-driven workflow and event logs.

This program can run stand-alone or integrate with the mapping and shape-drawing capabilities of ESRI ArcMap.  Inquiries can be mapped and overlaid onto existing base-maps or merged with existing or new layers.  Drawing and editing of existing stored shapes, areas and boundaries can be done from within ArcDesktop and saved back to the federated data stores that the Inquiry Tracker can pull from.

Users are able to browse and edit inquiries all within the same tool based on localized permissions and data store configurations.  Workflow rules are integrated into the application, and changes and toll gates are tracked within an audit trail for each inquiry.  Inquiries can be grouped, categorized and sorted to allow for easy data access and manipulation.

The Geospatial Inquiry Tracker works with ArcMap 9.3.1 and is written in .NET.  (ArcMap v10 version coming soon)

The Geospatial Digital Asset Manager consists of data management tasks and workflow surrounding the collection, identification, annotation, storage, retrieval and distribution of spatial data and associated assets and metadata.

The use of this tool requires three components: handheld devices, phones or tablets (iOS, Android, etc.) to capture and consume the data, secure connectors between clients and endpoints to publish, retrieve and sync the data and a flexible master data store for dispersal into a Geospatial Server backend (ArcGIS, GeoServer, etc.).

Handheld devices draw, mark-up or annotate Geospatial vector/coordinate-based data and save as movable, re-usable and index-able Geospatial features within layers. Sketch and Graphics layers are able to be drawn in the form of common features such as points, multi-points, lines, multi-lines and polygons.

Feature data is coordinate-based and tied to a location identifiable by configurable and interchangeable base-maps. Feature location can be moved, adjusted, resized, redrawn or edited. Features can be grouped together within a set or layer for easy ability to categorize, tag or hide/show certain types of data. Additionally, different feature layers can contain different sets of permissions, Online or Offline to allow for only certain transactions to occur per “user” or workflow defined for that layer(s).

Additionally, other customizable metadata of any kind or type can be collected and associated with a particular feature object(s) or a defined coordinate or spatial area. Data type examples that can be collected and annotated include imagery, videos, audio, custom forms and field types within those forms and other types of digital assets including associating existing files, PDFs, Office documents, etc.

Base-map data is utilized as a point of reference and can consist of terrain data, satellite imagery, street maps or any number of types of display data. Base-maps can be loaded from an Online service (tiled or dynamic) or cached for offline use (tiled). Multiple base-maps can exist for different operations within a location.

The Geospatial digital asset management collection system is designed with the idea that there are multiple devices and one or more centralized data stores where the data is stored and retrieved from. Data such as feature services or base-maps can be pulled in from any number of sources. Additionally, clients can share or view data not centralized via a peer-to-peer ad-hoc network.

The endpoints are secure data listeners that allow for asynchronous transfer or retrieval of selected data based on your workflow and/or credentials. They are an intermediary to the client software or your Geospatial Server backend. They allow for customizable asynchronous “occasionally connected” data storage, synchronization and consumption between client and “server”. The endpoint listeners do the heavy lifting of then acting as an intermediary data store before data is finally saved or aggregated into your Geospatial data store.

The endpoints will allow for intra or inter-server communication from the intermediary data store to your Geospatial Server whether it is ArcGIS Server using ArcSDE or GeoServer utilizing PostGIS. The system is designed to interface cleanly into your existing data store without having to customize or re-configure your back-end.