[OpenLayers-Dev] About Caching copy of OSM on a local server
מוישי שפיץ
mos at vmail.co.il
Sat Mar 28 14:46:27 EDT 2009
Hello,
I'm a GIS developer and I've started recently using the OpenLayers API and
found it as an excellent tool.
I've succeeded using Google maps and OSM as my background maps but I want to
cache these tiles on my server,
in order to get them faster but I didn't find the way to do it.
I tried to use TileCache.org and it is great for my Mapinfo server but not
for the OSM or Google.
How am I suppose to do it? I didn't find the correct place to ask on
tilecache and because i've seen mention to this subject in the last digest,
i'm asking it here!
I'd very appreciate your help.
I must add that OpenLayers is the best project I've seen. all the best for
you, the developers!
Best regards,
Moshe Shpitz
Beit-El ,Israel
2009/3/28 <dev-request at openlayers.org>
> Send Dev mailing list submissions to
> dev at openlayers.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://openlayers.org/mailman/listinfo/dev
> or, via email, send a message with subject or body 'help' to
> dev-request at openlayers.org
>
> You can reach the person managing the list at
> dev-owner at openlayers.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dev digest..."
>
>
> Today's Topics:
>
> 1. Transition From Google's API to OL (Arnie Shore)
> 2. Re: Transition From Google's API to OL - Correction! (Arnie Shore)
> 3. Re: Transition From Google's API to OL (Stephen Woodbridge)
> 4. Re: Triage Meeting, Round #2 (Eric Lemoine)
> 5. maps with all "overlays" (Tim Schaub)
> 6. Re: Transition From Google's API to OL (Schuyler Erle)
> 7. Re: Transition From Google's API to OL (Arnie Shore)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 27 Mar 2009 15:16:50 -0500
> From: Arnie Shore <ashore3 at verizon.net>
> Subject: [OpenLayers-Dev] Transition From Google's API to OL
> To: "dev at openlayers" <dev at openlayers.org>
> Message-ID: <49CD3432.60709 at verizon.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Folks, hello, and I wonder if anyone can share experiences doing such a
> transition. (I've tried this question with the users group but with no
> responses. It was suggested that I try this august group, so here 'tis.)
>
> Background: I've written a free, Open Source application targeted to
> the public safety community, notably ham radio groups who kick into gear
> during emergency/crisis conditions. It relies on their mapping API,
> currently.
>
> But under emergency conditions that comprise the reasons for this
> community's existence, internet connectivity to Google may not exist of
> course. Accordingly, I'm planning a version of the app in which the
> tile sets and API are resident at a local server. Hence my strong
> interest in OL.
>
> I can't imagine I'm the only one here doing anything like that, so I'll
> appreciate hearing re experiences doing this, plus, especially, thoughts
> on the tile sets available. Thanks, all.
>
> Arnold Shore
> Annapolis, MD
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 27 Mar 2009 15:41:33 -0500
> From: Arnie Shore <ashore3 at verizon.net>
> Subject: Re: [OpenLayers-Dev] Transition From Google's API to OL -
> Correction!
> To: "dev at openlayers" <dev at openlayers.org>
> Message-ID: <49CD39FD.9010507 at verizon.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Sorry, "Google's" for "their" below; DUH!
> > Folks, hello, and I wonder if anyone can share experiences doing such a
> transition. (I've tried this question with the users group but with no
> responses. It was suggested that I try this august group, so here 'tis.)
> >
> > Background: I've written a free, Open Source application targeted to the
> public safety community, notably ham radio groups who kick into gear during
> emergency/crisis conditions. It relies on Google's mapping API,
> > currently.
> >
> > But under emergency conditions that comprise the reasons for this
> community's existence, internet connectivity to Google may not exist of
> course. Accordingly, I'm planning a version of the app in which the tile
> sets and API are resident at a local server. Hence my strong interest in
> OL.
> >
> > I can't imagine I'm the only one here doing anything like that, so I'll
> appreciate hearing re experiences doing this, plus, especially, thoughts
> > on the tile sets available. Thanks, all.
> >
> > Arnold Shore
> > Annapolis, MD
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 27 Mar 2009 16:46:10 -0500
> From: Stephen Woodbridge <woodbri at swoodbridge.com>
> Subject: Re: [OpenLayers-Dev] Transition From Google's API to OL
> To: Arnie Shore <ashore3 at verizon.net>
> Cc: "dev at openlayers" <dev at openlayers.org>
> Message-ID: <49CD4922.9030109 at swoodbridge.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Arnie Shore wrote:
> > Folks, hello, and I wonder if anyone can share experiences doing such a
> > transition. (I've tried this question with the users group but with no
> > responses. It was suggested that I try this august group, so here 'tis.)
> >
> > Background: I've written a free, Open Source application targeted to
> > the public safety community, notably ham radio groups who kick into gear
> > during emergency/crisis conditions. It relies on their mapping API,
> > currently.
> >
> > But under emergency conditions that comprise the reasons for this
> > community's existence, internet connectivity to Google may not exist of
> > course. Accordingly, I'm planning a version of the app in which the
> > tile sets and API are resident at a local server. Hence my strong
> > interest in OL.
> >
> > I can't imagine I'm the only one here doing anything like that, so I'll
> > appreciate hearing re experiences doing this, plus, especially, thoughts
> > on the tile sets available. Thanks, all.
>
> Arnie,
>
> There is not magic to doing what you want, just a lot of work.
>
> OpenLayers is a good way to go. I have client that had originally built
> application on Google and have since migrated to OpenLayers. You will
> need to get something like the Tiger Shapefiles and process them into
> something suitable for you purposes to work with UMN Mapserver which can
> serve map images to OpenLayers or can be used to generate tiles.
>
> You can start by rebuilding your application using OpenLayers and
> continue using Google for the time being. Then when you have it rehosted
> into the OpenLayers API, you can turn your attention to getting the maps
> working. Once you have Mapserver generating maps, you can change a few
> lines of OpenLayers to switch it between Mapserver and Google. Another
> option might be to use OSM and Tilecache to cache a copy of the OSM
> tiles locally.
>
> When you are ready to focus on the Mapserver side of things, join the
> mapserver list and I'm sure we will be glad to help you.
>
> -Steve
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 27 Mar 2009 22:43:33 +0100
> From: Eric Lemoine <eric.c2c at gmail.com>
> Subject: Re: [OpenLayers-Dev] Triage Meeting, Round #2
> To: Christopher Schmidt <crschmidt at metacarta.com>
> Cc: dev at openlayers.org
> Message-ID:
> <5ec103de0903271443j3f0a967cw5c5ab295b3b3629 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> I hope to be able to attend this time, my agenda being a bit uncertain
> these days.
>
> Thx,
>
> --
> Eric
>
>
>
> On Tue, Mar 24, 2009 at 8:09 PM, Christopher Schmidt
> <crschmidt at metacarta.com> wrote:
> > In order to finalize what will not be going into the 2.8 release, I
> > propose we have another meeting on April 1st, at the same time as
> > before, if there are no serious conflicts:
> >
> > ?http://bit.ly/yeFwo
> > ?Time: April 1st, 16:00 UTC
> >
> > It is my intention that after this meeting, no new non-regression bugs
> > will be included in 2.8, and any bug that is unlikely to have a patch in
> > trunk over the following 2-3 days will not be included in 2.8. This
> > should allow us to plan for an RC1 on April 6th.
> >
> > I should note that it appears that London, and possibly other European
> > countries, observe Daylight Savings Time starting this weekend, which
> > may push this meeting one hour *later* than the previous one for you
> > folks.
> >
> > If anyone has serious conflicts with this time, and has other
> > suggestions, please try to have them in within the next 24 hours, and
> > I'll try to come up with a plan that works as well as possible. I'm
> > especially interested in anyone who currently has a ticket assigned to
> > them
> > (
> http://trac.openlayers.org/query?status=new&status=assigned&status=reopened&milestone=2.8+Release&order=priority&group=owner
> )
> > being able to attend.
> >
> > Thanks!
> >
> > Best Regards,
> > Christopher Schmidt
> > OpenLayers 2.8 Release Manager
> > _______________________________________________
> > Dev mailing list
> > Dev at openlayers.org
> > http://openlayers.org/mailman/listinfo/dev
> >
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 27 Mar 2009 17:18:27 -0600
> From: Tim Schaub <tschaub at opengeo.org>
> Subject: [OpenLayers-Dev] maps with all "overlays"
> To: openlayers <dev at openlayers.org>
> Message-ID: <49CD5EC3.3070101 at opengeo.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hey-
>
> I've put together a pretty simple patch [1] that allows a map to be
> configured so that the lowest layer in the draw order is always treated
> as the base layer.
>
> With this patch, if you configure your map with allOverlays: true and
> configure every layer with isBaseLayer: false, you can have a map with
> any number (including zero) of layers visible or invisible.
>
> The patch is marked for commit, and I'm happy to commit it. If anybody
> has any comments about *not* wanting this, please speak up.
>
> Tim
>
> [1] see http://trac.openlayers.org/ticket/2004
>
> --
> Tim Schaub
> OpenGeo - http://opengeo.org
> Expert service straight from the developers.
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 28 Mar 2009 05:22:36 -0700
> From: Schuyler Erle <schuyler at nocat.net>
> Subject: Re: [OpenLayers-Dev] Transition From Google's API to OL
> To: Stephen Woodbridge <woodbri at swoodbridge.com>
> Cc: "dev at openlayers" <dev at openlayers.org>
> Message-ID: <20090328122236.GA3056 at vishnu.tridity.org>
> Content-Type: text/plain; charset=us-ascii
>
> * 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
>
>
> ------------------------------
>
> Message: 7
> Date: Sat, 28 Mar 2009 09:29:36 -0500
> From: Arnie Shore <ashore3 at verizon.net>
> Subject: Re: [OpenLayers-Dev] Transition From Google's API to OL
> To: "dev at openlayers" <dev at openlayers.org>
> Cc: Bob Austin <mandolinpicker at verizon.net>
> Message-ID: <49CE3450.9030502 at verizon.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> 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
> >
> >
>
>
>
> ------------------------------
>
> _______________________________________________
> Dev mailing list
> Dev at openlayers.org
> http://openlayers.org/mailman/listinfo/dev
>
>
> End of Dev Digest, Vol 30, Issue 43
> ***********************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20090328/a5c99e57/attachment.html
More information about the Dev
mailing list