Thanks for the clarification William. I also struck the issue of the polygon node limitation. I used FME software to generalise the polygons prior to construting the KML file, which seemed to do the trick.
On Jun 8, 7:51 am, William <[email protected]> wrote: > >If you do the later, am I correct in saying > > that you still have to use the Maps Data API to obtain the feed > > identifier? i.e. the user and map id. > > these are visible in My Maps when you click the "Link" button, the > "msid" is included in the url. > > There are two tasks: > 1. Creating a Map, and > 2. Creating Features in a Map. > > You create an empty map then import data (features) into into it. > > I found it easier to create an empty map with the API because the > property "api_visible" is automatically set to true. If you create > the map with My Maps, then you need to use the API to change the > "api_visible" property afterwards and I couldn't get that to work. > > Also I found it easier to import data into the map using My Maps > because it automatically reduces the number of points in polygons. > There seems to be an upper limit on the number of points in a polygon > (500 points) and this prevented me loading some polygons using the API > (for example Texas boundary). This limit requires further > investigation. -- 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.
