topic Re: Flex Viewer 2.2 released! in ArcGIS Viewer for Flex Questions

Flex Viewer 2.2 released!

BjornSvensson — Fri, 10 Dec 2010 20:52:21 GMT

Today we released version 2.2 of both ArcGIS API for Flex and ArcGIS Viewer for Flex.

Among the highlights to both Flex API and Flex Viewer:
�?� Support for arcgis.com web maps
�?� Legend Component in the API and Legend Widget in the Viewer
�?� Undo/redo while editing

API 2.2 What�??s New
http://help.arcgis.com/en/webapi/flex/help/index.html#whats_new.htm

Viewer 2.2 What�??s New
http://help.arcgis.com/en/webapps/flexviewer/help/index.html#whats_new.htm

Re: Flex Viewer 2.2 released!

RobertScheitlin__GISP — Fri, 10 Dec 2010 22:37:14 GMT

Team,

Sorry to report a possible bug on the first day of release but I was wonder why the draw widget does not give any scale handles for extents when clicked?
If I add:

if (editGraphic.geometry is Polyline || editGraphic.geometry is Polygon || editGraphic.geometry is Extent)

it seems to work fine, was this left out for some reason?

Next I would like to rant a little. I have been spending the last week or more working on adding move and rotate handles to my Enhanced draw widget and was extremely close to releasing it... The fact to you guys came out with the functionality but better implemented is great except that it would have save me a week or more of development time if I knew you guys had any intention of doing this...

So as it has been stated a couple of times on this forum can the team be team players and release a list of intended widgets and enhancements? Even if the teams says it is looking at doing this and you determine that it has to be removed from the list, that would be better than developers like my self wasting time developing something just to turn around and throw it away because a BETTER alternative was produced by you guys. So to recap the Viewer team could publish a list of widgets and enhancement that are intended to be released in the FlexViewer 2.3 that can be a living document that has things added and removed from the list at the teams discretion.

How about it?

Re: Flex Viewer 2.2 released!

Anonymous User — Sat, 11 Dec 2010 20:22:49 GMT

Robert,
I fully concur. I put off developing an enhanced print widget in hopes that the next release of the viewer would have addressed this issue. It hasn't! If you look at ideas.arcgis.com this issue has been 'Under Consideration' for some time and currently has 3,020 votes. I must field at least 15-20 phone calls from the public a week on printing issues.
The new draw widget is a step in the right direction, however it has issues. I was hoping to move, rotate and edit (size, color, contents, etc.) annotation by clicking on annotation that was added to the map (reference Mark Hoyland's redlining graphics tool). Instead this error occurs:

TypeError: Error #1034: Type Coercion failed: cannot convert mx.core::FTETextField@22a91101 to com.esri.ags.Graphic.
at widgets.Draw::DrawWidget/graphicClickHandler()

As a long time consultant of ours has stated, "Esri has always treated annotation as a wart on a toad's butt".

Also where are the resize handles for an added rectangle?

Re: Flex Viewer 2.2 released!

BjornSvensson — Sun, 12 Dec 2010 19:09:43 GMT

Robert, thanks for being first to report that no-extent-editing bug.
Chris, this is why you don't see the resize handles for rectangles.

Chris, while there are plans for a more complete print solution with ArcGIS Server, it will probably be released post-2.3.

As for general 2.3 plans, we will be working on the detailed plans next week. We've added an entry to our FAQ called "What about the next version (2.3)?" to share an initial list of some of the items we are considering for the next version.
http://help.arcgis.com/en/webapps/flexviewer/help/index.html#faq.htm

Re: Flex Viewer 2.2 released!

RobertScheitlin__GISP — Sun, 12 Dec 2010 19:47:37 GMT

Bjorn,

That's what I am talking about. I knew you guys were team players.

Keep Up the Good Work.

P.S.

This is probably a REST enhancement request but... I would love the ability to specify the legend image size from the Rest endpoint. I sometimes need bigger swatches when working with picture fill symbols.

Re: Flex Viewer 2.2 released!

RobertScheitlin__GISP — Sun, 12 Dec 2010 19:59:10 GMT

Next enhancement request:

In the DrawWidget be able to change the measurement font color, weight, size, etc. This is basic needed functionality when dealing with maps with dark backgrounds.

Re: Flex Viewer 2.2 released!

AdrianComan1 — Mon, 13 Dec 2010 19:15:39 GMT

Hi,

Please teach me how to connect to a WMS service or what i have to change in flexviewer-2.2-src to add/work;

Thanks in advance

Re: Flex Viewer 2.2 released!

DasaPaddock — Mon, 13 Dec 2010 19:26:58 GMT

Here's an example:

<layer
    label="US"
    type="wms"
    visible="true"
    visiblelayers="0,2"
    url="http://sampleserver1.arcgisonline.com/arcgis/services/Specialty/ESRI_StatesCitiesRivers_USA/MapServer/WMSServer"/>

There's more options available. See:
http://help.arcgis.com/en/webapps/flexviewer/help/layer_tag.htm

Re: Flex Viewer 2.2 released!

StephenLuzny — Sat, 11 Dec 2021 23:22:00 GMT

Dasa,

Could you elaborate on including a WMS layer in the Operational Layers section of the config.xml file for Flex Viewer 2.2? The documentation does not have much detail.

Specifically, I am attempting to add the hypsography layer from the Toporama Web Map Service (Toporama WMS) of the Earth Sciences Sector (ESS) at Natural Resources Canada (NRCan). See http://geogratis.cgdi.gc.ca/geogratis/en/service/toporama.html for information about this service.

<Layer queryable="0" opaque="0" cascaded="0">
<Name>hypsography</Name>
<Title>Hypsography</Title>
-
<Abstract>
The Hypsography layer represents elevation points and continuous lines formed by peaks of equal altitude used to describe the topography. Elevation of points and lines is always calculated from mean sea level.
</Abstract>
<SRS>EPSG:4269</SRS>

The layer line I have included in my config.xml is as follows:
<layer label="Contours" type="wms" visible="true" visiblelayers="hypsography" url="http://wms.ess-ws.nrcan.gc.ca/wms/toporama_en"/>

Is there an option to set the WMS version in the layer line? An error message I get seems to indicate that FlexViewer defaults to version 1.3.0, but Toporama supports the OGC WMS standard, version 1.1.1.

SecurityError: Error #2048: Security sandbox violation: http://465793h/FlexViewer2.2/index.swf cannot load data from http://wms.ess-ws.nrcan.gc.ca/wms/toporama_en?VERSION=1%2E3%2E0&REQUEST=GetCapabilities&SERVICE=WMS.
 at Function/com.esri.ags.layers:WMSLayer/private:loadCapabilities/com.esri.ags.layers:myFaultFunction()
 at mx.rpc::AsyncResponder/fault()
 at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyFault()
 at mx.rpc.events::FaultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()
 at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
 at HTTPOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
 at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()
 at mx.rpc::Responder/fault()
 at mx.rpc::AsyncRequest/fault()
 at DirectHTTPMessageResponder/securityErrorHandler()
 at flash.events::EventDispatcher/dispatchEventFunction()
 at flash.events::EventDispatcher/dispatchEvent()
 at flash.net::URLLoader/redirectEvent()

Additionally, is there a way to specify the EPSG code for the WMS in the layer line? This is not mentioned in the documentation. I suppose that "EPSG:900913 - Google Spheric Mercator", which is supported by Toporama, would match the ArcGIS Online cached services.

Re: Flex Viewer 2.2 released!

DasaPaddock — Mon, 13 Dec 2010 21:37:25 GMT

The Security error is being thrown because they don't have a crossdomain.xml file on their server. You can either configure the layer to use a proxy or have it skip getting the capabilities.

e.g.

<layer label="Contours" type="wms" visible="true" visiblelayers="hypsography"
url="http://wms.ess-ws.nrcan.gc.ca/wms/toporama_en" skipgetcapabilities="true" version="1.1.1"/>

The skipgetcapabilities and version attributes have been added to the layer tag doc. The WMSLayer uses the map's SpatialRefernce so you can set wkid="900913" on the map tag.

Re: Flex Viewer 2.2 released!

AdrianComan1 — Tue, 14 Dec 2010 09:58:39 GMT

Hi dpaddock,

I made the change in config.xml on basemaps:

<layer
label="axa"
type="wms"
visible="true"
visiblelayers="0,2"
wkid="EPSG:31600"
url="http://localhost:8080/geoserver/wms"/>

and i received a blank page..ESRI logo si loaded and staying on Transferring data from localhost..

i have a crossdomain.xml if help.

Re: Flex Viewer 2.2 released!

PedroGarcia — Tue, 14 Dec 2010 12:03:45 GMT

Hi,

I would like to know if there is a problem with the print widget in that new version. Because of margin cuts the images displayed. Note: That doesn't happen in previous version.

Thanks.

Re: Flex Viewer 2.2 released!

CynthiaMatney — Tue, 14 Dec 2010 15:16:56 GMT

Hello. I'm new to Flex. I have been working with Flex Viewer 2.1 for the past couple of months and have changed a lot of the xml files and some of the mxml files as well. What do I need to do in order to migrate to Flex Viewer 2.2 in order to get the updates & fixes and not lose the stuff I've already done?

Thanks!
Cynthia

Re: Flex Viewer 2.2 released!

DasaPaddock — Tue, 14 Dec 2010 15:35:47 GMT

Hi dpaddock,

I made the change in config.xml on basemaps:

<layer
label="axa"
type="wms"
visible="true"
visiblelayers="0,2"
wkid="EPSG:31600"
url="http://localhost:8080/geoserver/wms"/>

and i received a blank page..ESRI logo si loaded and staying on Transferring data from localhost..

i have a crossdomain.xml if help.

The wkid goes on the map tag, but it may not be needed. Make sure the visiblelayers match the available layer names. You may need to use a tool like HttpFox to see what the request/responses are.

Re: Flex Viewer 2.2 released!

BjornSvensson — Tue, 14 Dec 2010 16:37:43 GMT

Pedro, about the Print Widget:
The only changes to the Print Widget between 2.2. and 2.1 was related to localization. The actual printing should be the same for both versions.

Maybe the print differences you are seeing is based on the size of your browser at the time of printing. For example, if you're browser is "tall", you will get get a different printout than if you resize to be "wide".

Re: Flex Viewer 2.2 released!

BjornSvensson — Tue, 14 Dec 2010 16:53:02 GMT

Cynthia (and others), to migrate your 2.1 viewers:

A) If working with the compiled version:

Download the new viewer.

Copy your modified xml's file over to the new viewer.

Review What's new to see if there's something new you want to take advantage of.

B) If working with the source code:

Download the new viewer.

Copy your modified xml's file over to the new viewer.

Review What's new to see if there's something new you want to take advantage of.

For changes made in the mxml files ... depends. If it was something that was fixed, then do nothing. For fixes that you want to migrate over, the best way is probably to compare that specific mxml and integrate your changes with ours.

Re: Flex Viewer 2.2 released!

AdrianComan1 — Tue, 14 Dec 2010 18:19:22 GMT

The wkid goes on the map tag, but it may not be needed. Make sure the visiblelayers match the available layer names. You may need to use a tool like HttpFox to see what the request/responses are.

Worked, Thank U; I wrote in config.xml:

<layer
label="axa"
type="wms"
visible="true"
visiblelayers="axa"
url="http://localhost:8080/geoserver/wms"/>

and it's work; Now, it is a way to overlay this data with bing maps, I suppose i have to put to basemap ..bing map and to operationallayers my wms, it will work? and how i do this.

Thank again.

Re: Flex Viewer 2.2 released!

BrianCrumpler — Wed, 15 Dec 2010 03:07:25 GMT

The wkid goes on the map tag, but it may not be needed. Make sure the visiblelayers match the available layer names. You may need to use a tool like HttpFox to see what the request/responses are.

Here's another example using the 2.2 viewer and the WMS feed - one that works and one that doesn't... It does look like this is a projection definition issue...

<layer label="NOAA Infrared Satellite"
type="wms"
visible="false"
visiblelayers="RAS_GOES_I4"
url="http://nowcoast.noaa.gov/wms/com.esri.wms.Esrimap/obs?service=wms"/>

<layer label="Nexrad Radar"
type="wms"
visible="true"
visiblelayers="nexrad-n0r"
url="http://mesonet.agron.iastate.edu/cgi-bin/wms/nexrad/n0r.cgi?"/>

The Iowa State link works but the Nowcoast one doesn't. Iowa State has their service publishing in 102100 but Nowcoast only has the following (http://nowcoast.noaa.gov/help/mapservices.shtml):

SRS Identifier Projection Name
EPSG:4267 North American Datum of 1927 (NAD 27)
EPSG:4269 North American Datum of 1983 (NAD 83)
EPSG:4326 World Geodetic System 1984 (WGS 84)
EPSG:102113 Web Mercator (ESRI Identifier)
EPSG:900913 Web Mercator (Google Identifier)

I have also tried adding in variables for SRS or WKID and they haven't worked, but removing them alltogether makes Iowa State work.

What would be helpful in the next go around would be to have the option to specify the SRS/WKID of the WMS layer since SRS is required by WMS (see http://help.arcgis.com/en/arcims/10.0/mainhelp/mergedprojects/wms_connect/wms_connector/get_map.htm). While it is optimal for the WMS layer to be in the same projection, this is not always possible. This is especially the case when using regional data (ie. national or multi-state like weather) and applying it to local or regional areas where the projections will be different.

Additionally, for cross-jurisdictional interoperability, there is a requirement to be able to leverage multiple projections either automatically or programmatically. Much of your local, regional, federal and multi-state data will be in different projections and the ability to use WMS layers with other ArcGIS server layers should be simple to solve by adding a variable for WKID for the map layer.

If this isn't possible, then while WMS is added, it really doesn't work unless the WMS service provided has an option to output in the same projection as your other map layers which isn't always possible.

Thoughts?

Brian Crumpler - GIS Manager
Virginia Department of Emergency Management

Re: Flex Viewer 2.2 released!

PedroGarcia — Wed, 15 Dec 2010 06:10:35 GMT

Hi,

Could somebody explain how to integrate the esri geoportal extension widget to this new version (both compiled and source code)? All documentation I've found in forums and webhelp refers to previous versions.

Thanks.

Re: Flex Viewer 2.2 released!

TimMcKinney — Wed, 15 Dec 2010 16:05:46 GMT

Bjorn and others -
Is there a preferred strategy for copying the 'modified xml's' to the new viewer while leaving enhancements to the new viewer intact? In other words, is there a better/easier way to sync the old and new viewers rather than looking through all of the widgets and comparing code? If I've modified a 2.1 widget, and the widget is improved a 2.2, I don't want to just copy my widget and replace the newer version, I want to merge the two.

thanks

Tim