Just as a test, do you get the same problem if you disable the
bUseNativeServices flag in the checkNativeServiceSupport() function in
MapGuide.js?
That disables use of v2.6.0 QUERYMAPFEATURES and falls back to the existing
PHP scripts
- Jackie
--
View this message in context:
Ok, I think it's because you failed to specify SELECTIONFORMAT.
- Jackie
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/QUERYMAPFEATURES-and-requestdata-3-throws-NpE-tp5145379p5146212.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Hi,
I try to use MgCooker (v5 or v6) with a destination shared directory on another
server that the mapguide server.
In Windows Credential panel, i set EveryOne and I can create directories and
files to the destination server from the mapguide server by explorer.
I change TileCachePath to
Really Sorry...I misread the Problem...I thought you were trying to select
a point feature and Zoom out by a percentage (which doesn't work)...also
in a Lat/Long Psuedomercator even adding units instead of percent is hard
becuase a single unit can be a large Area.
S+I thought that is what you were
I tried that and it did not have any effect. Here's a way to easily see this
problem in Fusion 2.6:
With the Sheboygan dataset, create a new layer from the Trees SDF data
connection. Copy the Sheboygan map to a new map, assign WGS84
PseudoMercator, add the Trees layer to it, and also make the
Ok, does this appear to only be affecting point layers? Because it's starting
to sound like a ticket I filed 7 weeks ago:
http://trac.osgeo.org/mapguide/ticket/2441
- Jackie
--
View this message in context:
I don't think they're the same issue. When I select a feature on a tree
layer, the ID and other property values are properly retrieved.
In my prior message I also mentioned testing it with the Roads (lines)
layer. They both have problems that are manifested differently. Looking
more closely at
I think the problem is that the QueryFeatureProperties() API which v2.6
QUERYMAPFEATURES currently uses to assemble the response does not seem to
produce the same expected set of data as QueryFeatures() even though we pass
the same set of parameters to both.
I've been testing on the Sheboygan map
