Syndicate content
Monday, March 19, 2012

Previous posts have touched the problems that traditionally face those wanting some geospatial consistency in data collection, data presentation, and data understanding.  These issues drive much of the continual interest and push for increased Metadata and many of the "Use Liability" clauses that are attached to current datasets.  After all, if you don't really know what the feature is, or what many of the attributes really mean, geospatial data is of considerably reduced value.

Wednesday, February 1, 2012

WeoGeo Tools for ArcGIS is an extension and toolbar designed by Zekiah Technologies for use with ArcGIS for Desktop. The current version allows users to browse the WeoGeo Market or hosted libraries and order data sets for use within ArcGIS. If you are not familiar with WeoGeo Market, it contains thousands of data sets, both for-purchase and free-of-charge, from numerous data providers. WeoGeo allows a user to customize an order to suit his or her needs. For example, a user is able to extract a subset of features from a national data set if only features in a specific area of interest are needed.

Friday, January 13, 2012

Background:  While many organizations see the clear advantages of establishing and using geospatial data standards, obtaining compliance from constituents continues to be a frustrating, and costly, problem.  Users are frequently reluctant to adopt a new standard given the potential cost of modifying applications that use an existing, custom schema or simply having a 'not invented here' mentality.  This was true within the Department of Defense (DoD) Installation Geospatial Information and Services (IGI&S) community, even though a standard had existed from more than 10 years.  As a part of 2006 Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) initiative, Zekiah developed a data standardization concept intended to provide flexibility in schema naming conventions and organization without compromising ease of data sharing, conversion, and information understanding.

Tuesday, October 11, 2011

On my current project I was tasked with exporting our map layers to Google Earth.  This was simple for the ESRI ArcGIS Server layers, since Server has out-of-the-box support for KML.  However, as would be the case, we don't use ArcGIS Server for all of our layers.  We also use ESRI Graphic Layers for rendering user markup and data from various data sources.  This presented a challenge to export these layers to Google Earth.  Specifically, we wanted to maintain the same rendering and symbology that we used on our Silverlight maps in Google Earth.

Wednesday, August 3, 2011

Zekiah supports many organizations, especially in the federal government, that have a need to run ArcGIS Server on networks that are not connected to the internet. Oftentimes, these organizations use tiled basemaps that are built from data or services that are available (whether free or by subscription) from the internet. While ArcGIS Server can produce these tile caches, organizations with production servers on disconnected networks can find it impractical to do so. Although the cost of running two ArcGIS Servers is sometimes a factor, we find more often that IT and information security policies make it difficult for these organizations to stand up servers on internet-connected networks. In such situations, a desktop solution is preferable.