Thanks Jonathan! I need to scale up to eventually tens of thousands of points across the entire U.S. At any given time thousands of points in a major metro area. I just found the following:
http://code.google.com/apis/maps/documentation/mapsdata/developers_guide_protocol.html#Search which is exactly what I need, access to Google's very fast and robust spatial search capabilities, since I do NOT want to have to maintain spatial search myself on my own server, it's too specialized a product. So then now as I think I'm converging closer to a sense of how this would be put together, my question would be this: how could I get access to the Atom-based searching capabilities via the Flash API? Or would I have to write my own ActionScript or use some ActionScript HTTP library to do that? Thanks! On Dec 29, 1:49 pm, Jonathan Wagner <[email protected]> wrote: > I think it really depends on how much data you're talking about for > each point. 20,000 points actually isn't that much, you could load all > those locations and store them in flash and it wouldn't have to big of > a memory foot print. If you're talking about even more then that, you > might need to grab data for a particular region. I think you're going > the right way, keeping the Meta data and position data separate. If > you have a lot of data per point, it might even be worth it to poll > for the particular data for each node specifically. > > Jonathan > Scribblemaps.com > > On Dec 29, 7:45 am, Gaudi <[email protected]> wrote: > > > Hi, I'm researching the use of Google Maps and Flex for a project. I > > am architecting a solution and have a basic question about the storage > > of point data for my app. For the sake of simplicity, let's say I'm > > building an app that tracks all the fire hydrants in a city, and > > stores a bunch of metadata about each hydrant, e.g. when it was last > > serviced. So imagine there are 20,000 of them in NYC. If I zoom out > > to a broad view and even only display a few hundred points, it's still > > a lot of data. I don't want to have to send all those lat/longs to > > the Google server each time. Ideally Google would store the id of > > each hydrant and its location, and then I would key on that id and > > store my metadata in my own database (maybe that database is also > > stored in some Google data storage repository?). > > > Is this the right approach to storing my data? If Google stores the > > position data for each object, can I then add arbitrary columns of > > metadata either in the Maps storage or in some other Google database > > of some kind? I sense that I want Google to store all my location > > data so that as I add features like geo-fencing I can let Google > > handle spatial queries like that so that I don't have to have that > > kind of capability on my own server. > > > Thanks! -- 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.
