MapDotNet UX

Pros

I endorse MapDotNet Architectural model. We have used the same pattern more than once, and always successfully. A highly technical implementation tool - the acquisition of metadata - employing high performance services based on the metadata. New layers can be added to a deployed release, or adjustments can be made as per the result of the business need.

Cons

Using a very large of layers (40 +) has adverse affect in the Console. I'm pretty sure because it's XML based. Maybe having a database version in the future will be good.

Additional Comments

We have just finished the implementation of a Nationwide Property Spatial Application based on a comprehensive database that covers 95%+ of the US Properties. ( going live these coming holidays ) With several layers (Parcels, Properties for Sale, Foreclosures, Delinquencies, Flood Hazard, REO Sales, access to documents and more). We offer a very complete GIS feature set (drawing tools, selection tools, searching, farming, exporting, labelings, etc), and the overall system performance of both the client (using Silverlight 5 on top of MapDotNet API) and the MapDotNet Servers (currently backed up by a cluster SQL Server 2008 R2) surpasses all our competitors largely, and rivals the big GIS space players with defiance. The user experience is a solid, responsive map interface that resembles the feel of a local fast desktop application. Five stars all the way! Adriano Freire Director, Research & Development First American DataTree Santa Ana, CA

• Price: 5
• Deployment Time: 5
• Needs Met: 4.5
• Compatibility: 5
• Performance: 5

0% of 0 people found the following review helpful. Did you? Yes or No | Report this review

Pros

The ease and speed at which you can go from creating a mapfile to creating a map to deploying the mapping solution on the Internet is a huge plus. The entire map service is self contained which makes it easy to configure and deploy. The suite is built on the latest Microsoft stack and keeps up-to-date with the latest and greatest in technology (HTML5 maps, for instance). Reads data from wide varierty of data source - SQL server, shapefiles, etc

Cons

The inability to create a data layer from anything else but tables and views in SQL server. Dont like the way it stores connection strings for the individual layers and lack of a reliable tool to change this between environments other than physical find-replace.

• Price: 3.5
• Deployment Time: 5
• Needs Met: 4
• Compatibility: 3.5
• Performance: 4.5

0% of 0 people found the following review helpful. Did you? Yes or No | Report this review