It depends on the CAD program that you’re running. Most CAD programs can support Intermap’s Web Services.
Web service data will be slower to access than data sitting on a local server. Speed accessing Web service data is
a direct result of the connection to the Internet. If a user is connected via a T3 line it will be quicker than
a T1 ->ISDN ->DSL-> Cable->Wi-Fi in that order.
Having said that, users familiar with other Web services have been impressed with the access speeds of Intermap’s connection.
Users accessing via Wi-Fi, and even 3G connections have not been disappointed with the ability to access and work with data in
locations where they had previously had no access at all.
Yes. All of the tools normally used -through any OGC compatible GIS software- will perform in a similar manner as if the data were sitting locally.
We have done extensive testing using ArcGIS/ArcMap and Global Mapper tools, and although we can't promise that every possible test was performed, the results showed no discernable difference between the Intermap Web Service and an original file format delivered from Intermap and sitting locally.
No. Any time you over manipulate data you have the potential to introduce artifacts that were not in the original data. Web service data are no different.
We have performed extensive analysis to compare physical formats - .bil, jpeg2000 etc, with Web service – WCS and WMS- formats. In all cases there was potential to introduce errors in the data.
The Proxy is necessary only when using ArcGIS software. Currently Arc can only create a secure connection to an instance of ArcServer.
Intermap plans to have an instance of ArcServer by the end of Q4 2011. This will allow ArcGIS users to access the ArcServer which will point directly to Intermap’s Web service database making the proxy unnecessary.
Intemap's proxy can be downloaded here.
Yes. Intermap has a simple Application Programming Interface (API) with files which can access our Web service database. This interface has resulted in several common tools (GetHeight, GetProfile, GetViewshed, GetMLP, etc). Our SDKs include sample code and documentation to help clarify how the tools can be used by third party applications.
The Web service SDK includes all the components necessary to work with the Intermap API. Partners can develop using Java, Microsoft .NET or PHP to create new applications. As development support is limited, partners and users must understand Web services programming concepts when using our SDK.
- Change the file extension from .bil to .flt.
- Open Arc Toolbox (in ArcMap or Arc Catalog) → Data Conversion Tools → To Raster.
- Select “Float to RASTER”, (“floatGrid” if using ArcInfo).
- Import the file.
- After importing, define the projection to geographic coordinate system NAD83.
- Open Arc Toolbox (in ArcMap or Arc Catalog → Data Management Tools → Projections and Transformations → Define Projection.
If you want to create ASCII file in Arc, you first need to have grid file then use Raster to ASCII tool.