Archive for the ‘weogeo’ Category

WeoGeo Is Content Management

Tuesday, March 9th, 2010

Talking about Content Management

OK, lets be honest, talking about content management is about exciting as talking about metadata, or XML, or Canadian fiscal policy. I mean really, who cares about managing your information in ways that make it discoverable, usable and most importantly sharable.

Oh right, maybe this stuff isn’t as boring at we thought. I’ll tell you what is the most boring thing in the world. Watching your desktop search strain to find data on your local drives with wacky search strings like water.*. Think about how you find GIS data on your hard drives? Search or browse. Heck, you might even go back to an old project and try and find the dataset that was stored in my MXD or other map document.

Now this doesn’t mean that using search tools to find data isn’t valuable. I know many folks that use Google Desktop Search to index their GIS files. It just isn’t efficient and it sure as heck doesn’t allow you to share it with multiple users. Using these private search indexes is just like putting the data on your desktop, sure you can find it, but no one else can. It gets to the core why content management of geospatial data is so important and why it is actually really fun to talk about.

WeoGeo’s approach to content discoverability is to use the one thing that makes finding maps simple. A map! If I want to find hydrography layers in Wisconsin, I pan/zoom to Wisconsin and then search for hydro tags. If I want a worldwide country boundary layer, I zoom to the world and search tags for country. If I want to find demographic data from Arizona, I geocode that in my WeoGeo search and zoom right to that area.

WeoGeo manages content using maps

Textual based search is horrible at finding spatial data. Does “washington” mean the state, which of 31 counties, which of almost 50 cities and the countless lakes, islands, streets, neighborhoods and other place-names? A map allows you to narrow that down to the Washington that you are interested in and not have to parse though hundreds of records for other “Washingtons”.

Sharing Your Geo-Data

OK, so we’ve all got these issues finding data on your hard drives. That is part of the problem though. Sharing this data amongst your peers is hard as well. Not everyone has that GIS data hard drive mapped, the VPN is problematic and slow causing off-site users to not have access and it is too large to email to your clients who want to see it. This makes it very hard to get the most value out of this dataset because you are fighting to share it as much as you are fighting to find it.

What a content management system such as WeoGeo brings into play with our web-based front end is a simple way for many people to access the same dataset from many different places. Across the hall, across the building, across the state and across the world. With user access controls, you can set which datasets are available to which users. Grant rights for your clients to gain access to your geodata, but see only those datasets that they are supposed to see. No worries about them rummaging through your FTP site looking for proprietary information that shouldn’t be seen.

Add users and give them access to datasets

Geo-Formats In and Out

One of the greatest fears I always had with archiving data was will it be usable in the future. I just found a CD the other day with a ton of Corel Draw documents on it. Nothing I had on my laptop could read those old .cdr files despite claims from the software package that it could. What about GIS data? I’m pretty sure that your shapefiles and GeoTIFFs will be readable in the future, but what about more obscure data formats? Will you be able to read that vector or raster format in 10 years? Who knows right? But WeoGeo has the industry standard on reading proprietary data files under our hood. Safe Software FME drives all our data format transformations. Safe FME allows WeoGeo to transform data stored in our Library to any format they support. So if you need to get your data out of Integraph MGE, because your company no longer supports it, into Autodesk SDF format, you can do that with FME and WeoGeo. Protecting your archival, system of record, datasets from obsolescence is just as important as making sure that you can find it.

Content Management Within Your Workflows

There are tons of content management systems out there and for good reason. Companies want to keep control of their data because they can get more value out of it than they would storing it on DVDs in your desk drawer or on a DLT tape at Iron Mountain. Neither of those methods is a form of content management and neither makes your data discoverable or shareable.

What sets WeoGeo apart from most content management systems is that we are first and foremost a GEO content management system. We are designed from the ground up to allow you to manage all your geo-content; whether it be shapefiles, ERDAS or anything that has a reference to place (PDF, Word documents, video). We’ve also worked hard to integrate WeoGeo into your workflows with our new WeoGeo Tools for ArcGIS and our WeoApp which runs on Windows, Mac OS X or Linux. Using content management shouldn’t be hard or require lots of training. We’ve made it as simple as “upload to WeoGeo” and “browse WeoGeo” to get data in and out of our content management system.

WeoGeo Tools for ArcGIS in action

Your return on investment putting your data in WeoGeo will be realized quickly when you no longer have to spend hours finding your data or invest in expensive, closed, proprietary content management systems. You can start using WeoGeo for Content Management today for free and see how it can change how you manage your geodata.

Introducing WeoGeo Tools for ArcGIS

Tuesday, February 16th, 2010

Workflows Drive Everything

One thing about using a “cloud based” data store is that you have to leave your tools to start using it. This means that you break any work-flows you are in and lets be honest, the last thing you want to happen when you are being productive is to head to the internet.

Seriously though, being able to stay in your content creation tools and work with SaaS based content management is a great idea. The reality of the situation is that there hasn’t been any good tools to accomplish this yet.

Enter WeoGeo Tools

Today we are releasing the first of our planned content creation tools that bring the SaaS WeoGeo Library and WeoGeo Market as well as any WeoGeo Library Appliances to ArcGIS Desktop users. With WeoGeo Tools for ArcGIS you can connect to these libraries and discover datasets in your area of interest. Inside ArcMap this area of interest is defined by your view window. So if you’ve got a project you are working on and want to see what is available in your work area, WeoGeo Tools takes your extents and returns only datasets in that region.

WeoGeo Tools for ArcGIS

Text-based Search is Wrong for Geo-Content

WeoGeo has worked hard at changing the way we search for geospatial datasets. Rather than requiring users to type in keywords or other text search terms into a search query, we allow users to discover data via maps. You can see this in our WeoGeo Market. What is natural though about content creation tools like ArcGIS Desktop is that your canvas is a map. Why not take that bounding box extent and return data in that area? Our MapRank technology also returns datasets that best match your zoom level (if you are zoomed into a neighborhood you’ll get those datasets listed first and likewise if you are at the country level, you’ll get those datasets before neighborhood ones.

WeoGeo Tools for ArcGIS Browse

Uploading From Inside ArcGIS Desktop

Getting your content up to your Library or the Market should be just as easy. Why do you have to save out your data and then open your web browser and then proceed to fill out data forms and finally upload? Yep, that is what we call a workflow killer. With WeoGeo Tools for ArcGIS, ESRI users can easily upload datasets from within ArcMap with just a click of a button. Everything is handled for you. Just highlight the dataset in your layers list and click the upload to WeoGeo button.

WeoGeo Tools for ArcGIS Upload

Download WeoGeo Tools for ArcGIS

I encourage everyone to download WeoGeo Tools for ArcGIS and give it a shot. You can browse the WeoGeo Market without having to have an account so you can see how easy it is to bring data in. If you want to try out our Library, we offer free Library tiers and 30 day trials for the rest. Just use signup code: weogeolib5769. Lastly if you need any help, don’t hesitate to contact us.

This is our first release of WeoGeo Tools for ArcGIS and we will continue to work hard on improving it, so any feedback is welcomed. We are also working at more WeoGeo Tools for other GIS software packages. You can also create your own versions of WeoGeo Tools for your own software packages by using our open APIs.

Visit Us at the FedUC

If you are at the 2010 ESRI Federal User Conference, feel free to drop by out booth (#141) and get a full demo of WeoGeo Tools for ArcGIS as well as all our SaaS and appliance products.

Fluid Icon for WeoGeo

Sunday, February 14th, 2010

With Fluid you make web apps appear as applications on OS X. These Side Specific Browsers (SSB) enable you to work with web apps just as they were actual applications. If you don’t run Mac OS X, you can use Prism to do the same thing on Windows or Linux. I run just about all my web apps this way because it gets them out of tabs in my browser and into my Dock which means that they are always available to me, no matter how many times Flash crashes my browser.

WeoGeo Web App

Here is a high resolution WeoGeo icon to use with Fluid. (Just click to download)

WeoGeo Fluid Icon

Check Out the Latest From WeoGeo at the ESRI Federal User Conference

Friday, February 12th, 2010

If you are going to be at the 2010 ESRI Federal User Conference next week in Washington D.C. we’d like to encourage you to come by our booth (#141) and see our latest features, get a demo, and see how WeoGeo is bringing the cloud to ArcGIS.  We will be showcasing our new ArcGIS integration where we bring the power of WeoGeo’s SaaS cloud or appliance tools directly into ArcGIS Desktop.

Paul, Dan and James will all be there on the floor and even if you aren’t going to the FedUC, we’d be happy to meet with you in the area to talk about WeoGeo Library and Market.  The exhibit floor is open Wednesday, February 17 from 3:00 – 6:00 PM and Thursday, February 18, from 10:00AM – 4:00 PM.

Worried about the weather?  ESRI says don’t let that stop you.  It isn’t going to stop us from showing up.

Vector Datasets in WeoGeo

Wednesday, February 10th, 2010

Now that WeoGeo supports vector datasets, it opens up the content management capabilities for lots of new geo-content.  Not only can we support vectors (ESRI Shapefile and MapInfo TAB), but also we can transform them into new formats, warp the data’s datum/projection and clip out the area you are interested in.  We also support layers inside datasets, so if your project contains both counties and highways, you can store both those layers in one dataset and select either one (or both) to download.

Let us look at this dataset I uploaded with cultural data layers.  I downloaded the data from Natural Earth which if you don’t know about, you should.  I brought the layers into my ESRI ArcGIS Desktop and created some cartography to better visualize the layers.  Because I’m in ArcMap, I have all the rich cartographic tools available to me to work with to generate previews of the data.  But that isn’t all I can do with ArcMap (or any other desktop GIS system), I can include my symbology with my dataset on WeoGeo allowing those who download the data to see it how I see it.  I can also include multiple symbology types if I want (ESRI LYR, MapInfo WOR, MapFile, SLD) that are delivered along with the downloaded dataset.

After creating the cartography, I export out the preview images and use our WeoApp to upload them.  The WeoApp is our graphical upload tool that can handle terabytes of data and runs natively on Windows, Mac OS X and Linux.  Once the WeoApp finishes uploading the data, one can now view it in your WeoGeo Library.  This is our access control content management system; so feel free to securely share your data with your friends and colleges.  The Library is available as SaaS or as an appliance.  Because I want to share this data with people outside my private library (and let you guys see it), I pushed it to our WeoGeo Market.

While I could set a price to this dataset, I decided to give it away free.  Now you might be thinking that why would someone want to sell public domain data on WeoGeo Market.  Well you probably wouldn’t make much money doing that because people would quickly realize that you were charging them for free data and rate your products poorly.  BUT, if you added value to that data by creating a complex cartographic styleset and spent weeks creating it, why wouldn’t you want to charge money for that?  People should value the hard work you put into your symbology even if the data is free.  Plus with our WeoGeo License, derivative works are supported so others can remix your work and resell it as well, but you’d get a cut of the sale yourself.

Now that this dataset is freely available on the WeoGeo Market, you may now try our customization features yourself.  You could subscribe to a GeoRSS feed that would keep you up to date on any public domain datasets that become available on the WeoGeo Market.  You can share the preview KML with others so they can see the dataset in Google Earth (and then get to WeoGeo Market to download it).  You can even use our Datasets API to get the details of the entry in JSON.

Now I’m a vector guy a heart, so vector support in WeoGeo is just about the most exciting thing I’ve been a part of.  With WeoGeo’s ability to perform server side transformations, users can get what data they want in formats and projects they want.  No more worries about users wanting data in everything from Old Hawaiian to EPSG:4326.  And best of all if you don’t like our UI, you can roll your own with our APIs.  Build your own front end to our SaaS and Appliance Library to meet the needs of your clients and users.

Best of all, stay tuned next week to hear about a great new product we will be releasing to take your geo-content management beyond where you thought it could go.

Next week my friends!

New WeoGeo Release: 2.0.10

Monday, January 11th, 2010

This week we released an update to the WeoGeo Library and Market services. 2.0.10 is now up and running and you can find the details on our change log.

One of the biggest features is the new free tier to WeoGeo Library. Yep, we now have free WeoGeo Library accounts. You can now start using WeoGeo for free, the only limitations are number of users and storage size. You can of course easily upgrade to paid tiers when you need to. So try out our WeoGeo Library for free (no credit card needed) and see what it can do for you.  When signing up use the invite code: freeweogeolib

WeoGeo 2.0.9 Release

Monday, December 21st, 2009

Last week our 2.0.9 release went live enabling a couple of new features and cleaning up a few stragglers from the last release.  You can always read the details at our wiki page, but I’ll highlight a couple here that are worth noting.

  • Human Readable URLs: Prior to this release, a dataset had a token in the URL such as “4a7df1a5-af77-ab5a-a0b9-59a97b6d03d4″.   This token was a unique identifier to the dataset, but you couldn’t tell what the token was unless you clicked on it.  Now URLs are based on the name of the dataset.  Thus if I have a dataset called “City Roads”, the URL will now use that in the URL.
    http://mylibrary.weogeo.com/#/original_data_map/mylibrary_city_roads
    You can still use the tokens as before, but the URLs will default to the name of the dataset.
  • CSV (comma separated values): You can now convert vector datasets into CSV files.  This means that users that don’t have access to GIS software can get at the data values behind the shapefiles.
  • GeoRSS Feeds Improved: Our last release introduced GeoRSS files.  Now at 2.0.9 the RSS feed gives you updated datasets in your area of interest defined by the bounding box you set either in the the WeoGeo website or by customizing the URL yourself.
  • Performance improvements: Added caching to improve the performance of the web app.
  • Improved user activity stats for administrators:  Library administrators can get better analytics to determine how datasets are being downloaded and used.

If you are interested in taking the WeoGeo Library or Market for a test spin, please contact us and let us know you’d like to try it out.  Also please let us know if there are any enhancements or features you’d like to see enabled into our Library/Market or APIs.

The GeoMonkey is already working with the WeoGeo APIs to convert MapInfo TAB to CSV.

Keep Up to Date on Your Geo-Searches With GeoRSS

Monday, November 23rd, 2009

We’ve gone ahead and added GeoRSS support for our listings in both the private Library and the open Market.  On the top of Panel 3 you’ll see a RSS icon which leads to a GeoRSS feed that gives updates to whatever search criteria you have set including the bounding box (your area of interest), any keywords search, modified dates, file type (vector/raster/other) or price (on Market).

Panel 3 now has a GeoRSS Link

Panel 3 now has a GeoRSS Link

By zooming into the state of California, you can see the GeoRSS feed includes only datasets in that area of interest. Any time a new dataset is loaded, you’ll know about it because it will appear in your RSS aggregator or even in your GIS applications. Or how about this feed for ATLIS Geomatics which shows all their datasets in Calgary, Alberta.  Providers of data on WeoGeo can give their users GeoRSS feeds to keep them updated on new uploads.

Licensing Derivative Works or How to Have Your Cake and Eat It Too

Tuesday, November 17th, 2009

The OpenGeoData Blog had a very interesting post last week on what they called the cake test.  From the blog:

“What is the Cake Test? Easy: A set of geodata, or a map, is libre only if somebody can give you a cake with that map on top, as a present.”

I actually like this test.  It is simple and easy to see.  Can you download geodata and have your local baker reproduce it with icing.  But there is a little problem with their definition; it is way too narrow.  Most of the data in the world is not libre or free.  It is either locked up at one of the various stages of local and federal government, or it can be owned by a company/individual who doesn’t want to give it away for free.  The cake test does work in this aspect, if you can take a dataset and put it on a map without signing anything or paying for anything, it is most likely libre.  But the reality of the situation is that most data isn’t free and probably won’t be in the near term.  This means we need another way to license geodata on top of that cake.

Derivative Work from geodata is very liberating

Derivative Work from geodata is very liberating

We at WeoGeo have been thinking about this for a long time.  In fact we realize that without a good license for allowing users to create derivative products from geodata, that information is probably going to stay locked up behind restrictive licensing and cause people to create their own datasets without them.  Our WeoGeo License Agreements for Providers and Users both oversee how content can be licensed to allow derivative works to be created.  If you’d like to use this aerial image of download Calgary, you will get a license that allows you to create the single use from this aerial which would include putting it on a cake for a (yummy) mapping party.

Now of course this aerial isn’t libre, and you are still bound by the license agreement. However this license also explicitly states that you could sell this cake as a derivative product to others and a potion of that sale would go back to ATLIS Geo.  But what it does do is give users of geodata a clear and consistent way to actually use content to create derivative products and still give the original rights holder a cut of future sales.  So if you list data on the WeoGeo Market, you can give buyers of your geodata the rights to create derivative work based upon it and gain an additional revenues from those downstream sales.  Remember EVS-Islands and DigitalGlobe from a while back?  All he wanted to do is license derivative work off of the imagery.  Because DigitalGlobe has no such license, we can’t enjoy his hard work and DigitalGlobe gives up some revenue that they wouldn’t have had otherwise.

The cake test as proposed by the OpenGeoData blog is an all or nothing test that results in the many users gaining little benefit.  Sure it is nice that OpenStreetMap, TIGER and other datasets can be thrown on top of a cake, but most data available to users is not libre.  If the owners of this data were to enable derivative works using the WeoGeo Content License Agreement or similar type licenses, you can only imagine some of the really great derivative products people would be able to create and help to continue funding further development of these datasets.  Don’t we all want our geodata to pass the cake test and ensure that you have something tasty to celebrate on Geography Awareness Week?

Discovering and Customizing Your Geo-Data on the GeoWeb

Monday, October 19th, 2009

Downloading spatial datasets these days is really no different than it was 10 years ago.  Rather than taking advantage of new technologies, these data sharing sites are really just HTML wrappers to FTP sites.  You navigate them like you navigate the folder structure on any computer.  This makes downloading datasets very difficult because you may have to drill down to get one GIS file and then jump back up and drill down again.

A couple years ago I needed to download some DEMs in California from their GIS data website.  These DEM’s were organized, as expected, like the DRGs.  So they have that wonderful folder structure that none of us can remember.

Since my area was small, I just wanted to grab the 7.5 minute quad map DEMs for my area.  So navigating to the 7.5_minute_series_albers_nad83_trimmed folder you get this:

Years ago I had access to a wonderful printed index to all the USGS Quad Maps in the USA.  Of course I no longer have this so trying to remember what Quad map number I need is almost impossible.  Now there are websites that will tell you this and you can download an index, but it is a huge pain in the rear and time consuming.  You can start seeing the problem though.  If all my DEMs I need are under one folder, I can just grab them all.  But the world never works that way and I had to grab DEMs from 4 folders for my area of interest.

So as I described above, I started to drill down into each folder and download the data I needed.  But because this was all HTML, I had to right click on every file and download it.  The story of course ended with my just writing a Perl script to scrape all the DEMs for California into my local directory and off I went.

The problem of course with this is that I grabbed way more than I would ever need.  Because the process was so painful, I just assumed to download everything locally and if I ever needed a new area, I had it available.  California (thanks guys) paid for bandwidth that I used up with my Perl script that just downloaded everything in its path.  The inefficiency of this process is totally clear.  I just wanted to get DEMs in my little area, but because the organization of this data was so archaic, I had to result to brutal measures to get what I needed.

Now what would have been better?  Well first off, I would have loved to just crop out the dataset I needed and then get only that as a download.  When you think about it, it is really just a simple GIS clip function.  We do it all the time, but why don’t we allow our users on the web to do it themselves?

Lets take this example in Florida in my WeoGeo Library:

If we look at the right panel we can see that the dataset has a huge size, almost 900 MB.

If I’m only interested in a little section of this data, why would I either pay for the whole thing or deal with a huge ENVI file when I really only want a small jpeg?  So as you can see below, by zooming into the small section I want and changing some setting to match what I want my output to be, I can reduce the file size from 835 MB to 8 K.  This means that rather than downloading a huge file and causing a lot of bandwidth costs, I was able to quickly get the file that I needed, for the area I needed in the format I needed.

Also this means that I as an organization wouldn’t have to have multiple versions of the same dataset on my web server.  I can keep the data in GeoTIFF and let people transform them into other formats.  Because we leverage Safe FME on the backend, we can transform to and from hundreds of data formats.  If you have users that need that in Swedish KF85, WeoGeo can enable that even if you don’t have any software on your own that can read or write it KF85, just upload any supported vector format and WeoGeo supports it.

Discovering data is only part of the story on the GeoWeb.  Getting this data in formats you can consume and use is really where the value happens to sharing data.  People are using data in so many different ways that trying to figure out how to support all these needs is becoming very difficult.  Because WeoGeo gives you the ability to allow your users to extract only the data they wish from your geodatabases and into one of the hundreds of formats that WeoGeo supports, you’ll have much happier customers, save money on your IT infrastructure and know that no matter what happens down the road you’ll be able to address those needs quickly and without worry.