In closing, the dataset I've been using contains a few parcels with holes, and these features were not rendering correctly using my original approach, which expected and handled only a single array of coordinates. Below, in the asText for an offending polygon, notice a second and third set of coordinate pair arrays appear---look for the pattern ),( in the st_asText below. So I changed my approach to create a different XML format that returns a single feature with a number of "poly" objects (most often only one "poly" object), and each "poly" has its own encode points string. Then, on the client side, I can build a polygon with holes by creating an array of encoded point strings (i.e. one for each poly). This fixed the whole problem. "POLYGON((-93.4944295871593 39.3827400749619,-93.4944252697337 39.380534356737,-93.4944195616267 39.3796043923341,-93.5006246650925 39.3796930973912,-93.500600797483 39.3801231879668,-93.501129008109 39.3801425105256,-93.5016673549857 39.3801537889061,-93.501759717126 39.3801609491456,-93.5018317516393 39.3801802183681,-93.5018987170303 39.3802035080036,-93.5019554327586 39.380226885865,-93.5020071374219 39.3802582631708,-93.5020640807351 39.3802975507531,-93.5021060206441 39.3803373557511,-93.5021362923111 39.3803704966064,-93.5021633277051 39.3804088059037,-93.5021837411725 39.3804471713312,-93.5022008448625 39.3804855661645,-93.5022112910323 39.3805214485033,-93.5022251205161 39.3805624404718,-93.5022273905851 39.3806064117042,-93.5022232274212 39.3810320704301,-93.5022189504934 39.3814497746905,-93.5022117724054 39.3816646372314,-93.5022133083096 39.3817720239037,-93.5022246959717 39.3818514817616,-93.5022160388449 39.3819629348391,-93.5022238375011 39.3821498235045,-93.5022305553381 39.3822611432382,-93.5027789978061 39.3822603954159,-93.5027681240955 39.3818587326111,-93.5027673296966 39.3814450497874,-93.5027614673624 39.3810353883205,-93.5027703548871 39.3805818440157,-93.5027766368413 39.3797562604686,-93.5028186025768 39.3797243824661,-93.5034916022112 39.3797339702573,-93.5035694352849 39.3841445066105,-93.50268352755 39.3841213732924,-93.4979567276564 39.3840668645335,-93.4946080897406 39.3840167644376,-93.4944096929057 39.3838747970935,-93.4944102184807 39.3838448471989,-93.4944295871593 39.3827400749619),(-93.5020540775657 39.3824655308315,-93.5020480485485 39.3820439367943,-93.5020399091296 39.3818331848022,-93.5020376907368 39.3816780535006,-93.501412377412 39.3816794756631,-93.5014227874078 39.3820493200709,-93.5014273347527 39.3823675038206,-93.5014596764599 39.3824786039527,-93.5020540775657 39.3824655308315),(-93.5011273068992 39.380288607776,-93.500054877801 39.3802528640443,-93.5000090283246 39.3811001236366,-93.5010810410109 39.3811058934829,-93.5011273068992 39.380288607776))"
-- You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api-for-flash?hl=en.
