Re: [mapguide-users] mapguide rest - bbox parameter with map?

[Jackie Ng]

I think you might be misunderstanding the purpose of the image representation
in restcfg.json

Features will *always* be selected in the image representation. This is by
design. The intention behind the image representation is to show where your
feature(s) are in relation to the map specified in restcfg.json, and we do
that by showing such features as selected on the map. GeoREST follows this
same idea. Your feature(s) are the centre of attention, not the map.

If you are just after an image of a map at a certain view, then you can just
use the image representation of the map definition:

eg.
http://localhost/mapguide/rest/library/Testing/report/AV_Vorlage.MapDefinition/image.png?x=YOUR_CENTER_Xy=YOUR_CENTER_Yscale=YOUR_SCALEwidth=YOUR_IMAGE_WIDTHheight=YOUR_IMAGE_HEIGHT

- Jackie



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/mapguide-rest-bbox-parameter-with-map-tp5187340p5188279.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users

[mapguide-users] GML Parsing in WFS Provider

[kship...@juno.com]

Hello,

In setting up a WFS Feature Source for NFHL (National Flood Hazard Layer) data 
in Mapguide 2.6 and Maestro 6.0.0.8244 I am having trouble with any Feature 
class namespace which is not a POINT geometry. Here is the FeatureServer link 
for FEMA's WFS Feature Source:

https://hazards.fema.gov/gis/nfhl/services/public/NFHL/MapServer/WFSServer

This connects fine. I create a Layer Definition from this data source, and all 
30+ Feature Class namespaces are listed. BUT, only the following seven Feature 
Class choices actually populate the Geometry Property field with the correct 
value 'SHAPE':

Datum_Conversion_Points, Station_Start_Points, Gages, River_Mile_Markers, 
LOMAs, High_Water_Marks, Nodes

There are 20+ other namespaces that, when selected, leave the Geometry Property 
value blank, and consequently these layers will not work to display any 
features. Using manual WFS requests, I can see that these non-Point namespaces 
have a 'MultiSurfacePropertyType' for their geometry property. For example, for 
the namespace FIRM_Panels:


http://hazards.fema.gov/gis/nfhl/services/public/NFHL/MapServer/WFSServer?service=wfsversion=1.1.0request=DescribeFeatureTypetypeNames=public_NFHL%3AFIRM_Panels

The above DescribeFeatures request shows MultiSurfacePropertyType in 
xs:element minOccurs=0 name=SHAPE type=gml:MultiSurfacePropertyType/


If I use WFS version 1.0.0 in my manual WFS request, this comes in as 
MultiPolygonPropertyType instead:

http://hazards.fema.gov/gis/nfhl/services/public/NFHL/MapServer/WFSServer?service=wfsversion=1.0.0request=DescribeFeatureTypetypeNames=public_NFHL%3AFIRM_Panels

xs:element minOccurs=0 name=SHAPE type=gml:MultiPolygonPropertyType/


I have a feeling Mapguide would process this older version request and properly 
read the MultiPolygonPropertyType if it used the 1.0.0 parameter in its URL 
request. However I do not see a way to force 1.0.0 requests in either the 
FeatureSource or LayerDefinition xml in Mapguide Maestro. I further see this 
RFC on the WFS FDO Provider system which indicates full upgrades to GML 3 have 
not been completed:

http://trac.osgeo.org/fdo/wiki/FDORfc51

Has this problem occurred elsewhere and a solution is already available, or is 
the recent change in GML 3 from MultiPolygon to MultiSurface not yet supported?


Thank you,

Kyel Shippey


How Old Men Tighten Skin
63 Year Old Man Shares DIY Skin Tightening Method You Can Do From Home
http://thirdpartyoffers.juno.com/TGL3131/54e3fad0a2d007ad073b0st04duc
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users