I telling the guys at Manifold when something isn’t working the way I think it should. On one hand, I get the satisfaction of sticking it to some guys who I know are smarter than me. On the other hand, I then get to see how quickly they move to action. Over the years it is like clockwork:
Tell Manifold their process is slower than I would like.
Manifold writes back that things are pretty good.
Then, send them timing comparisons with ArcGIS.
Sit back and wait – about a day later the issue is fixed, and Manifold is really fast for that task.
I think a big part of the above steps in #3. Whenever you can show the team at Manifold that their process is slower than ArcGIS, MapInfo, QGIS, Postgis, or anything else, they quickly move on it. Also, the nature of their builds is such that they can very quickly issue updates. It’s one of the things I really like about the product, they love making improvements.
As an example, in my last post I evaluated the contour creation in ArcGIS, Manifold, and GDAL. You’ll recall that the results were:
GDAL: 53m Manifold: 24m ArcGIS: 7m
A discussion ensued on the georeference.org forum on March 9, and a number of users validated my findings on their own. Fast forward to March 12, and a new release of the Edge builds came out to address the issue.
Now, the same process runs in 3m in Manifold 9. For those with a stop watch, it went from 1561s to 182s. That is an improvement of 8.5X. Not bad for a 3 day turn around.
If you want to learn more about Manifold and big data analytics, check out my courses at www.gisadvisor.com.