Surveying, Mapping and GIS

Exploring all aspects of mapping and geography, from field data collection, to mapping and analysis, to integration, applications development and enterprise architecture...

  • Geospatial Technology, End to End...

    Exploring all aspects of mapping and geography, from field data collection, to mapping and analysis, to integration, applications development, enterprise architecture and policy
Showing posts with label data management. Show all posts
Showing posts with label data management. Show all posts

U.S. Environmental Protection Agency...

Posted by Dave Smith On 4/05/2010 05:52:00 PM 4 comments


My big news to report:  After 6 years at Synergist Technology Group, Inc., I am changing directions.  I have accepted a position at the U.S. Environmental Protection Agency's Office of Environmental Information.  I will be starting at USEPA the week of April 26th, 2010.

I greatly enjoyed the work I was doing at Synergist, having been involved in everything from business development to writing code and everything in between, supporting geospatial, mapping and integration efforts to support diverse business areas from environmental protection to emergency response to transportation to military and intelligence applications.  I enjoyed the diversity.

I have worked in private sector, consulting for over 20 years, but all throughout this, have always been solutions-focused, and have always had a keen interest in supporting the core mission of the agencies that I worked with - though, the downside of private sector consulting is always in the vagaries of its' occasionally fragmentary nature, with competetive bidding and teaming arrangements often dynamic and changing.

So, coming into Federal service brings a whole gamut of new things.  In some ways, I will get to dig deep into some of my core passions of environmental protection, geospatial technology and integration - and I look forward to this. However, it will surely bring many other challenges along with it - but I am up for any challenge.

My new role will, among other things, involve support to EPA's Facility Registry System (FRS), which is a repository for facilities data for 2.5 million unique facilities regulated under a variety of environmental laws and statutes. Herein, I see opportunity for further geo-enablement of Agency business processes, along with continued integration potential, to put hooks and eyes into a variety of other processes for ever-improving analytical, reporting and querying capabilities, cross-media, cross-agency, cross-domain, cross-dimension, as well as facilitating further partnership-building, between local, state, and federal government, tribes, academia, industry and the public, and supporting data publishing, OGI and transparency initiatives.

I anticipate I will also be pulled into a variety of other geospatial efforts across EPA as well... In many ways, I will essentially continue to do many of the things I already did - only, from the other side of the fence. In terms of physical logistics, I have already essentially been commuting to Washington DC for 6 years - though, now having a permanent duty station there, I can now consider getting a place to stay, as opposed to living out of hotels and bouncing between various locales as I have been.

So - mixed emotions - I will certainly miss working with Synergist, but likewise, there is a great team at EPA, and I am sure I will have a great time there.

National Environmental Information Exchange Network

Posted by Dave Smith On 4/11/2009 06:54:00 PM 2 comments

Here's another exiting bit of news - my firm is teamed with CGI Federal on USEPA's Software Engineering & Specialized Scientific Support (SES3) Contract, and we just got word that our team has won EPA's Central Data Exchange (CDX) task. This is very exciting news, CDX and the Exchange Network serve the community via facilitating exchange of a wide variety of environmental data between federal, state, tribal and other partnerships - it is a partnership that has proven itself to be tremendously effective and a great model for other types of data exchanges as well.

What I am particularly excited about is in leveraging the infrastructure that has already been built toward more robustly supporting geodata services, and ultimately toward enhanced reporting, metrics, analytical capabilities, and other capabilities to support feds, states, tribes and others in informed decisionmaking toward environmental policy and stewardship.

As such - we also anticipate we will be looking to grow as a company, and will be looking to hire additional technical gurus with capabilities in data exchange, data management and data flows, particularly if you have prior capabilities and knowledge of EPA's Exchange Network and CDX, and/or geospatial technology.

If you are interested, drop me a line at dsmith (at) synergist.tech.com

FGDC Metadata Rant Du Jour

Posted by Dave Smith On 4/23/2007 10:06:00 AM 1 comments

I have been doing some work developing metadata records and automated processes for generating and updating metadata as part of data refresh and ETL processes lately. In the course of doing this, we are trying to develop means of providing very rich and well-documented, FGDC and Agency-profile metadata.

However, when it comes to attributes... Seems FGDC and ESRI both have put some disincentives in the way of capturing attribute data and documenting them painlessly.

http://www.fgdc.gov/metadata/csdgm/05.html

One could take the easy way out, and just put in an overview description and citation, and completely ignore any detailed description of the individual attributes.

Or, one could use ArcCatalog and extract a quick listing of attributes as <attr> elements - but.... ArcCatalog only captures and stores the <attrlabl> elements within this. In the infinite wisdom of the folks at FGDC and the folks that developed MetaParser, they then further require attribute domain <attrdomv> (and in my experience, 99.99% of most attribute data is either never validated against a domain, or validated outside of the GIS system, in the database, data capture or ETL process) and attribute value accuracy description <attrvai><attrvae> which I agree is valuable where applicable, but in many instances is not applicable, such as feature name, FID or other types of fields.

It tends to make providing detailed attribute information a disincentive, and steers folks toward taking the cop-out approach of just providing the overview description. Seems like an opportunity lost.

Search