Why not a Web-based ModelBuilder ?

modelbuilder
From ArcGIS 9.3 Desktop Help – imagine it in a web browser.

Yet another refrain of : Web2.0 means anyone can be a publisher.

Right now Modelbuilder is part of ArcGIS Desktop. Modelers create and test models, then publish them by creating a new geoprocssing service on ArcGIS Server.

Why not provide a thin client version of model builder, allowing people from outside the firewall a way to create and edit models?

That way, a cool geoprocessing task like this could be developed by a 3rd party.

Gory Details
Note that IGpFunction doesn’t need to be exposed to COM interop – just IGpFunctionFactory.

This means it should be possible to implement IGpFunctionFactory such that it returns GpFunctions hydrated from assemblies stored in a database as blobs. Using reflection, the assemblies would be scanned, each class implementing IGpFunction would be returned for GetFunctionNames(). This would allow (trusted) developers to publish custom GpTools for use by the web-based modelbuilder simply by uploading assemblies.

For geoprocessing models, a method would be provided that allows the IMdModel of a particular tool in the database to be edited. Note that IMdModels can be serialized/deserialized as xml, so XSLT templates could also be provided, allowing transformation from any client side model representation – not just the one used by modelbuilder. This would allow domain-specific modelbuilder variants to be developed by 3rd parties.

It seems like a generic geoprocessing service could be written that takes a model as an argument and runs it. That way each model wouldn’t need to have its own service. The model could be attributed so that usage statistics are tracked.

Advertisements

5 comments so far

  1. Sean Gillies on

    Yes, like Yahoo Pipes, but a pipe that has a generic XML representation. Built around the operations of the OGC simple features spec maybe?

  2. Kirk Kuykendall on

    Similar, but the models built by modelbuilder contain processes that run on a cluster where they have fast access to things like the geodatabase. For an OGC spec, it seems like the important one would be Web Processing Service (WPS). http://en.wikipedia.org/wiki/Web_Processing_Service

    If published models could also be exposed to the web in a WPS compliant manner, I guess they’d be more accessible – assuming the standard catches on.

  3. Sean Gillies on

    WPS, the protocol, isn’t something to pursue. What the OGC does get right in this domain is the enumeration of geometry types and operations (union, buffer, etc) and that’s the basis for interoperable models.

  4. […] ESRI could also web-enable model builder (as I’ve describe here) the solver could also be exposed as a geoprocessing […]

  5. Aaron Gilliland on

    See geo-model at http://code.google.com/p/geo-model/. I started a similar GUI to model-builder that is backended by WPS running on in geoserver.

    I haven’t completed the project but its getting close.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: