|
| v4.0.6 Upgrade Notes | Discussion Forum |
| IMF Developer's Guide » What's New » Upgrade Notes |
This page discusses important differences between IMF release 4.0.6 and the previous version, particularly things that have changed and require action on your part in order to run your existing IMF sites under the new release.
| Projections |
The <projection> element has been eliminated. You need to change your site configuration to use the new elements instead.
Albers Equal Area Conic:
<projection name="AlbersEqualAreaConic"
alias="BC Albers"
ellipsoid="GRS80"
central-meridian="-126.0"
reference-latitude="45.0"
standard-parallel-1="50.0"
standard-parallel-2="58.5"
false-easting="1000000.0"
false-northing="0.0"/>
... is now:
<projection-albers-equal-area-conic alias="BC Albers"
ellipsoid="GRS80"
central-meridian="-126.0"
reference-latitude="45.0"
standard-parallel-1="50.0"
standard-parallel-2="58.5"
false-easting="1000000.0"
false-northing="0.0"/>
Geographic:
<projection name="Geographic"/>... is now:
<projection-geographic/>
Lambert Conformal Conic:
<projection name="LambertConformalConic"
alias="WA South NAD27"
ellipsoid="CLARK1866"
central-meridian="-120.5"
reference-latitude="45.33333333333334"
standard-parallel-1="45.83333333333334"
standard-parallel-2="47.33333333333334"
false-easting="2000000"
false-northing="0.0"
units="feet"/>
... is now:
<projection-lambert-conformal-conic alias="WA South NAD27"
ellipsoid="CLARK1866"
central-meridian="-120.5"
reference-latitude="45.33333333333334"
standard-parallel-1="45.83333333333334"
standard-parallel-2="47.33333333333334"
false-easting="2000000"
false-northing="0.0"
units="feet"/>
Transverse Mercator:
<projection name="TransverseMercator"
alias="RI State Plane"
ellipsoid="GRS80"
central-meridian="-71.5"
reference-latitude="41.08333333333334"
scale-factor="0.99999375"
false-easting="328083.3333333333"
false-northing="0.0"
units="feet"/>
... is now:
<projection-transverse-mercator alias="RI State Plane"
ellipsoid="GRS80"
central-meridian="-71.5"
reference-latitude="41.08333333333334"
scale-factor="0.99999375"
false-easting="328083.3333333333"
false-northing="0.0"
units="feet"/>
Auto Calculated UTM:
<projection name="TransverseMercatorCalculatedZone"/>... is now:
<projection-utm-auto/>
| Tools, buttons & spaces |
In previous releases, buttons, tools and spaces were all defined in the site configuration XML as <tool> elements with a type attribute. Now, these different objects are defined with their own elements:
Button Example:
<tool name="Print"
type="button"
url="$FRAMEWORK/imfPrintScaledMapForm.jsp"
target="dataFrame"
hint="Print to PDF"
status="Prepares a scaled map in PDF format."
graphic="$FRAMEWORK/tools/print_1.gif"
width="16" height="16"/>
... is now:
<button name="Print"
url="$FRAMEWORK/imfPrintScaledMapForm.jsp"
target="dataFrame"
hint="Print to PDF"
help="$FRAMEWORK/help/printMapButton.txt"
status="Prepares a scaled map in PDF format."
graphic="$FRAMEWORK/tools/print_1.gif"
width="16" height="16"/>
Tool Example:
<tool name="Identify"
type="tool"
hint="Identify"
help="$FRAMEWORK/help/identifyTool.txt"
status="Display information about the features that you can click the map."
graphic="$FRAMEWORK/tools/identify_1.gif"
active-graphic="$FRAMEWORK/tools/identify_2.gif"
width="16" height="16"/>
... is now:
<tool name="Identify"
hint="Identify"
help="$FRAMEWORK/help/identifyTool.txt"
status="Display information about the features that you can click the map."
help="$FRAMEWORK/help/identifyTool.txt"
graphic="$FRAMEWORK/tools/identify_1.gif"
active-graphic="$FRAMEWORK/tools/identify_2.gif"
width="16" height="16"/>
Space Example:
<tool type="space"/>... is now:
<space/>Refer to the <tools> page for more information about this.
| Help System - Tab Names |
In order to be properly displayed on the automatically generated help page, <tab> elements should now contain a name attribute.
Example:
<tab url="$FRAMEWORK/imfLayers.jsp"
target="dataFrame"
hint="Set Layers"
status="Set which layers display, and choose an identify layer."
graphic="$FRAMEWORK/tabs/bc/layers53x27.gif"
width="53" height="27"/>
... should now be:
<tab name="Layers"
url="$FRAMEWORK/imfLayers.jsp"
target="dataFrame"
hint="Set Layers"
status="Set which layers display, and choose an identify layer."
help="$FRAMEWORK/help/layersTab.txt"
graphic="$FRAMEWORK/tabs/bc/layers53x27.gif"
width="53" height="27"/>
| Custom tools |
The format of the parameters passed to your custom tool handler has changed. In the past, the coordinates have been passed in a parameter called "pts" which is a text string that had a comma between the x and y value, and a semicolon between points. It now uses commas between all x, y, and tuple values (e.g. 20,30,50,60 instead of 20,30;50,60).
You must change your handler scripts accordingly. For example, you may have previously had a parsing routine something like:
AimsPoints pts = new AimsPoints();
String ptsArg = request.getParameter("pts");
if (ptsArg != null) {
StringTokenizer pTok = new StringTokenizer(ptsArg,";");
while (pTok.hasMoreTokens()) {
pts.addPoint(new AimsPoint(pTok.nextToken()));
}
}
... which created an AimsPoints object with the points. A new AimsPoints
constructor has been created to accept a string in the comma separated
format, so the parsing now can be done with one line of code as follows:
AimsPoints pts = new AimsPoints(request.getParameter("pts"));
All custom handler scripts that you have created must be modified
per the example above in order to continue to work with v4.0.6. Please
refer to the page titled,
"Custom Tools" for more
information about this.
| XML Schemas |
Schemas are now available for each of the XML configuration file formats. Using the schemas with an XML editor / validator such as XMLSpy is highly recommended, but if you do, you may need to reorder the elements in your site configuration file and make other changes in order to successfully validate your XML.
| Geocoding |
For naming convention purposes, the geocoding form script names have been changed.