Thank you for the reply and the link. I'd actually read that post, but it gave me a bit of a headache trying to reverse the process...I'm rather new to this mode of thinking (i avoided it as long as i could).
As far as the parcel number value is concerned, it needs to be a string because they are different for each county that we deal with and are typically 14-22 alphanumeric characters in length, such as '1-023B-001.000' Nick JasonBirch wrote: > > More details on this here: > > http://tinyurl.com/2rrq3e > > I'm definitely a bit rusty on this stuff, but in your initial problem > are you sure you want to be using a string value for the parcel id? > > Jason > > -----Original Message----- > From: nclayton > Subject: Re: [mapguide-users] Issues selecting a feature with custom > coding > > 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. > _______________________________________________ > 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-tp14694817s16610p14737912.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
