[OpenLayers-Dev] Transition From Google's API to OL

[Arnie Shore]

Hmmm.  (I was hoping quietly to myself that nuth'n wd pan out, cuz if it 
did - and it does - I got a heap of work staring right at me.)

Taking  a  harder look at OSM than I'd taken earlier tells me that it 
ain't half bad, given the kind of usage I'm addressing.  I'd been 
concerned that the folks out in South Succotash wd have little 
available, but not so.  I did a pair of test cases, and while OSM wont 
get to the lowest zoom that GMaps does, I think that's quite live-able 
with, with the added plus of local editing.

I'd need to provide the kind of repository SDE notes, plus some 
convenient tools - Tilecache sound right - to allow a user to collect 
tiles for the areas of interest.  And then there's the CAD application!

Thanks, guys - you've helped a lot!  I have a feasible direction now.

AS

PS re BarCamp:  Yep, I'm in Annapolis in June.  And July.  And ...  Will 
look hard at that - first peek comes up positive.

~~~_/)~~~~~~~~_/)~~~~~~~~_/)~~~~~~~~_/)~~~~~~~~_/)~~~~~~~~_/)~~~~~~~~_/)~

Schuyler Erle wrote:
> * On 27-Mar-2009 at  1:44PM PDT, Stephen Woodbridge said:
>   
>> Another option might be to use OSM and Tilecache to cache a copy of
>> the OSM tiles locally.
>>     
>
> I was going to recommend this option as well -- it has the advantage
> that you won't need to deal with getting a whole bunch of vector data
> and then figuring out how to render it, although it would require more
> disk space than rendering vectors on the fly. I estimate that
> rendering the US down to zoom level 16 would require about 130 million
> tiles, or about 40 GB of cache.
>
> Arnie, if you're in Annapolis in June, you might be interested in
> this:
>
>   http://barcamp.org/CrisisCamp
>
> SDE
>
>