Personally I think Dekho should be entitled for 100% width and height of your browser, so that you have maximum screen space to allow your users to work their magic. However, for some situations you may want to nest Dekho within another website – perhaps make it look consistent with the rest of your site, retaining the header & footer for example. Read more >>
Esri Australia are pleased to announce the launch of our first Dev Meet Up group, which is to be established in Melbourne. Read more >>
With some minor tweaks to the existing ArcPy print sample for Dekho, you can point the script at your source data as opposed to the map services that have references to the source data.
This not only improves the quality (as the map services ‘rasterise’ the raw data), but also dramatically speeds up the process.
For a 600DPI print at A1 using the standard ArcPy print sample for Dekho (via map services) = 1 minute
I hope most of our Dekho users are aware of what can be done with Layer Description Tags; things like hiding a layer or legend, or making layers un-selectable. If this concept is new to you – I will give you a quick explanation of how they are applied. Read more >>
For ArcGIS Server 9, The WKID for the coordinate system, ‘WGS 1984 Web Mercator (Auxiliary Sphere)’ was 102100. It is then changed to 3857 at ArcGIS Server 10.
The background behind this is:
The EPSG assigned the 3857 code in March 2008, to signify the spherical Mercator projection that has become widespread with web mapping services, as Google, Bing and OpenStreetMap began to use this projected coordinate system.
To be in sync, Esri changed their WKID to match this EPSG code, and this happened at the v10 release. Read more >>
Flex has come a long way since its beginnings with v1 back in 2004. Adobe acquired Flex from Macromedia and in 2007 the Flex 3 SDK was released as open source under the Mozilla Public License. This enabled IDEs such as Eclipse to compile Flex code, but the roadmap and release cycle was still dictated by Adobe.
Back in November 2011, Adobe announced that they would be passing the Flex project over to the Apache Software Foundation. Flex has already been accepted into the Apache incubator stage, and mailing lists are already booming with support from the Apache developer community.
However, this announcement, along with the swell in interest for HTML5, has caused a number of questions to be asked about the future of Flex. Read more >>
This post includes steps to resolve a data insertion problem that we found with one of our Dekho client recently. Dekho insertions were failing with following exception.
“SQLServerException: A result set was generated for update”
To resolve this you need to turn off “no count” from your MS SqlServer options. Apparently this setting’s default behavior is inconsistence among SqlServer versions.
You can change it using following steps.
- Shout down Dekho and stop all connections to MS SqlServer
- Go into the SQL Server management console
- Right-click on the server and select “properties”.
- Select “connections”
- Under “Default Connection Options”, turn off “no count”.
In my previous post on Diagnostics, I mentioned how we can view the server logs from within Dekho Admin. At version 3.2.2 of Dekho we added another feature in the same area by which you can change server logging level from within Dekho Admin. It makes life easier because now you don’t have to go into the server directory, modify the logging.propeties file and restart tomcat service. It is more handy especially when the Dekho is on a different machine than you are accessing it from. Here is a brief note on how we do this: Read more >>
If you have Dekho maps that have a large number of layers and as a result you require large legends for your prints, it can often be a challenge trying to insert these legends into your layout templates.
This video looks at an alternative approach that modifies the existing ArcPy generic print sample to append a separate page with a previously created static Legend, to the exports from Dekho.
This is the fifth part of blog series on integrating Dekho with SQL Server Reporting Services. In case you missed the first four parts you can access them from here;
In the previous part of this series we now used a second Dekho servlet to display information from a feature info query from selection in the users Dekho session. Let’s have a look at the data flows from the last part.
At this stage we have only used Dekho to retrieve data and while this is useful we haven’t moved beyond what is already displayed on the selection review panel within Dekho. In this part we are going to delve out of the Dekho comfort zone and start querying the database directly via SQL. Read more >>