Hi Stephen, I made that feed myself as a learning exercise using a KML file of State Boundary Polygons (which I sourced from the google Take 10 Census map mentioned above).
The steps to create the feed were: 1. Include attribute data in each KML Placemark as <ExtendedData> with the standard State abbreviations as an identifier for each State. 2. Break any <MultiGeometry> into separate <Polygon> Placemarks, because the Maps Data API only allows a single geometric feature. For example Hawaii has multiple Polygons. 3. Use the Maps Data API to create a new blank map (which by default will has api_visible set to true) and record the map id for future reference. 4. Use "My Maps" at maps.google.com to load the KML into the map, using the Import KML function. If you use "My Maps" to upload the KML data, then attribute data should be held as <ExtendedData> in the Placemarks, but if you use the Maps Data API to upload the data, the attribute data should be held as <gd:customProperty> on the <atom:entry> The feed identifier has two parts: the first identifies the user (standard google account) and the second identifies the map. The next step for me is to upload County and State boundaries with the FIPS codes as the search criteria. ... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
