It seems there’s been a little more buzz about SharpMap lately and some folks have been doing some fact-checking with James offline. He deftly spun the question of “viability” into “popularity” by citing CodePlex statistics. Can’t say I blame him. The question of viability when it comes to open-source, especially smaller projects, can be tough to quantify. Say what you want about ESRI‘s licensing, tech support and whatever else; this much you can count on: they have genuine motives (profit, competiton) to keep their product line moving forward. The motives behind open-source can be a little more nebulous and they run the gamut.
A few weeks ago, I blogged about the end of the line for MapObjects. I waxed nostalgic about how fun it was to develop with MO and how, although I haven’t used it in a while, I’ll still be sad to see it go.
Well, I’m glad I’m over that! I been working with SharpMap for the last few weeks and I’m feeling that old MO vibe again. It started a few weeks ago with developing a data provider for SQLite (read here) but I’ve continued to look under the hood.
Lately, I’ve been working a project where we need to feed some spatial data into native WPF display. WPF offers high performance and great graphics quality. In addition, there are numerous other types of data involved that also need to be displayed. We didn’t want dedicated display components for each type of data so we decided to bring the spatial data into WPF.
A long time ago, on a blog-hosting site far far away, there was a blog called ArcDeveloper (not to be confused with ArcDeveloper.Net, which came later and did more). That was my first blog. It went in a few different directions. I wasn’t happy with it, so I killed it. There’s nothing to link to now.
Anyway, one of the posts I did on that blog had to do with creating derived geometry classes in .Net. The basic premise is simple: create a class that inherits from one of the ArcObjects geometry classes and then extend it to fit your needs. My application at the time had to do with writing an ArcGIS client for Common Alerting Protocol (CAP) feeds.