Here are the results of both the mgos base64 value and the php base64_encode value:
Actual FeatId: 33181 MGOS Value: nYEAAA== base64_encode Value: MzMxODE= I found code for writing a base64 function in javascript, and it gives the same result as the php function. Kenneth, GEOGRAF A/S wrote: > > If you select the feature, you can read the WKT or BoundingBox for the > object. > With this info, you can calculate the Center X,Y + Scale, and manually > zoom to it. > > I have not worked enough with the selection to understand it completely. > However, I think you are mistaken about the Base64 functions not being > compatible. > What appears to be different about the two encodings? > > If they truly are different, it is very easy to write your own base64 > encoding/decoding functions. > > Regards, Kenneth, GEOGRAF A/S > > > > nclayton skrev: >> Hi everyone, >> Here is my situation: >> >> I am hacking up the mapviewerphp files to fit the needs of the company I >> work for. One piece of functionality that is requried is that after a >> user >> queries our database for owner information, it is displayed in a new >> frame. >> Along with this information, there is a 'Zoom to Parcel' link. When the >> user >> clicks this, it should zoom to that parcel and select it without >> affecting >> the owner data list. >> >> My issue right now is in the selection of the parcel. I'm folling the >> code >> given in the dev guide, but my $selection->ToXml() always comes out as: >> >> <?xml version="1.0" encoding="UTF-8"?><FeatureSet >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xsi:noNamespaceSchemaLocation="FeatureSet-1.0.0.xsd"></FeatureSet> >> >> I am creating and passing in a query filter of "PARCEL_ID_ = '12345'" >> (with >> the appropriate parcel number supplied of course). I know that this >> PARCEL_ID_ value exists. >> >> I have tried manually creating the featureset query, since I can get the >> feature id of the selected parcel. The problem with that is that mgos >> uses a >> base64 encoding that doesn't match php's base64_encode() output, so >> that's a >> no-go as well. >> >> Any help and suggestions are appreciated >> >> -- >> Nick >> > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- View this message in context: http://www.nabble.com/Issues-selecting-a-feature-with-custom-coding-tp14694817s16610p14733863.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
