<div dir="ltr">Hello, <br>I'm a GIS developer and I've started recently using the OpenLayers API and found it as an excellent tool.<br>I've succeeded using Google maps and OSM as my background maps but I want to cache these tiles on my server,<br>
in order to get them faster but I didn't find the way to do it. <br>I tried to use TileCache.org and it is great for my Mapinfo server but not for the OSM or Google.<br>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!<br>
I'd very appreciate your help.<br><br>I must add that OpenLayers is the best project I've seen. all the best for you, the developers!<br><br>Best regards,<br><br>Moshe Shpitz<br>Beit-El ,Israel<br><br><div class="gmail_quote">
2009/3/28 <span dir="ltr"><<a href="mailto:dev-request@openlayers.org">dev-request@openlayers.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Send Dev mailing list submissions to<br>
<a href="mailto:dev@openlayers.org">dev@openlayers.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://openlayers.org/mailman/listinfo/dev" target="_blank">http://openlayers.org/mailman/listinfo/dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:dev-request@openlayers.org">dev-request@openlayers.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:dev-owner@openlayers.org">dev-owner@openlayers.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Transition From Google's API to OL (Arnie Shore)<br>
2. Re: Transition From Google's API to OL - Correction! (Arnie Shore)<br>
3. Re: Transition From Google's API to OL (Stephen Woodbridge)<br>
4. Re: Triage Meeting, Round #2 (Eric Lemoine)<br>
5. maps with all "overlays" (Tim Schaub)<br>
6. Re: Transition From Google's API to OL (Schuyler Erle)<br>
7. Re: Transition From Google's API to OL (Arnie Shore)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 27 Mar 2009 15:16:50 -0500<br>
From: Arnie Shore <<a href="mailto:ashore3@verizon.net">ashore3@verizon.net</a>><br>
Subject: [OpenLayers-Dev] Transition From Google's API to OL<br>
To: "dev@openlayers" <<a href="mailto:dev@openlayers.org">dev@openlayers.org</a>><br>
Message-ID: <<a href="mailto:49CD3432.60709@verizon.net">49CD3432.60709@verizon.net</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Folks, hello, and I wonder if anyone can share experiences doing such a<br>
transition. (I've tried this question with the users group but with no<br>
responses. It was suggested that I try this august group, so here 'tis.)<br>
<br>
Background: I've written a free, Open Source application targeted to<br>
the public safety community, notably ham radio groups who kick into gear<br>
during emergency/crisis conditions. It relies on their mapping API,<br>
currently.<br>
<br>
But under emergency conditions that comprise the reasons for this<br>
community's existence, internet connectivity to Google may not exist of<br>
course. Accordingly, I'm planning a version of the app in which the<br>
tile sets and API are resident at a local server. Hence my strong<br>
interest in OL.<br>
<br>
I can't imagine I'm the only one here doing anything like that, so I'll<br>
appreciate hearing re experiences doing this, plus, especially, thoughts<br>
on the tile sets available. Thanks, all.<br>
<br>
Arnold Shore<br>
Annapolis, MD<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 27 Mar 2009 15:41:33 -0500<br>
From: Arnie Shore <<a href="mailto:ashore3@verizon.net">ashore3@verizon.net</a>><br>
Subject: Re: [OpenLayers-Dev] Transition From Google's API to OL -<br>
Correction!<br>
To: "dev@openlayers" <<a href="mailto:dev@openlayers.org">dev@openlayers.org</a>><br>
Message-ID: <<a href="mailto:49CD39FD.9010507@verizon.net">49CD39FD.9010507@verizon.net</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Sorry, "Google's" for "their" below; DUH!<br>
> 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.)<br>
><br>
> 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,<br>
> currently.<br>
><br>
> 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.<br>
><br>
> 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<br>
> on the tile sets available. Thanks, all.<br>
><br>
> Arnold Shore<br>
> Annapolis, MD<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 27 Mar 2009 16:46:10 -0500<br>
From: Stephen Woodbridge <<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>><br>
Subject: Re: [OpenLayers-Dev] Transition From Google's API to OL<br>
To: Arnie Shore <<a href="mailto:ashore3@verizon.net">ashore3@verizon.net</a>><br>
Cc: "dev@openlayers" <<a href="mailto:dev@openlayers.org">dev@openlayers.org</a>><br>
Message-ID: <<a href="mailto:49CD4922.9030109@swoodbridge.com">49CD4922.9030109@swoodbridge.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Arnie Shore wrote:<br>
> Folks, hello, and I wonder if anyone can share experiences doing such a<br>
> transition. (I've tried this question with the users group but with no<br>
> responses. It was suggested that I try this august group, so here 'tis.)<br>
><br>
> Background: I've written a free, Open Source application targeted to<br>
> the public safety community, notably ham radio groups who kick into gear<br>
> during emergency/crisis conditions. It relies on their mapping API,<br>
> currently.<br>
><br>
> But under emergency conditions that comprise the reasons for this<br>
> community's existence, internet connectivity to Google may not exist of<br>
> course. Accordingly, I'm planning a version of the app in which the<br>
> tile sets and API are resident at a local server. Hence my strong<br>
> interest in OL.<br>
><br>
> I can't imagine I'm the only one here doing anything like that, so I'll<br>
> appreciate hearing re experiences doing this, plus, especially, thoughts<br>
> on the tile sets available. Thanks, all.<br>
<br>
Arnie,<br>
<br>
There is not magic to doing what you want, just a lot of work.<br>
<br>
OpenLayers is a good way to go. I have client that had originally built<br>
application on Google and have since migrated to OpenLayers. You will<br>
need to get something like the Tiger Shapefiles and process them into<br>
something suitable for you purposes to work with UMN Mapserver which can<br>
serve map images to OpenLayers or can be used to generate tiles.<br>
<br>
You can start by rebuilding your application using OpenLayers and<br>
continue using Google for the time being. Then when you have it rehosted<br>
into the OpenLayers API, you can turn your attention to getting the maps<br>
working. Once you have Mapserver generating maps, you can change a few<br>
lines of OpenLayers to switch it between Mapserver and Google. Another<br>
option might be to use OSM and Tilecache to cache a copy of the OSM<br>
tiles locally.<br>
<br>
When you are ready to focus on the Mapserver side of things, join the<br>
mapserver list and I'm sure we will be glad to help you.<br>
<br>
-Steve<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 27 Mar 2009 22:43:33 +0100<br>
From: Eric Lemoine <<a href="mailto:eric.c2c@gmail.com">eric.c2c@gmail.com</a>><br>
Subject: Re: [OpenLayers-Dev] Triage Meeting, Round #2<br>
To: Christopher Schmidt <<a href="mailto:crschmidt@metacarta.com">crschmidt@metacarta.com</a>><br>
Cc: <a href="mailto:dev@openlayers.org">dev@openlayers.org</a><br>
Message-ID:<br>
<<a href="mailto:5ec103de0903271443j3f0a967cw5c5ab295b3b3629@mail.gmail.com">5ec103de0903271443j3f0a967cw5c5ab295b3b3629@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
I hope to be able to attend this time, my agenda being a bit uncertain<br>
these days.<br>
<br>
Thx,<br>
<br>
--<br>
Eric<br>
<br>
<br>
<br>
On Tue, Mar 24, 2009 at 8:09 PM, Christopher Schmidt<br>
<<a href="mailto:crschmidt@metacarta.com">crschmidt@metacarta.com</a>> wrote:<br>
> In order to finalize what will not be going into the 2.8 release, I<br>
> propose we have another meeting on April 1st, at the same time as<br>
> before, if there are no serious conflicts:<br>
><br>
> ?<a href="http://bit.ly/yeFwo" target="_blank">http://bit.ly/yeFwo</a><br>
> ?Time: April 1st, 16:00 UTC<br>
><br>
> It is my intention that after this meeting, no new non-regression bugs<br>
> will be included in 2.8, and any bug that is unlikely to have a patch in<br>
> trunk over the following 2-3 days will not be included in 2.8. This<br>
> should allow us to plan for an RC1 on April 6th.<br>
><br>
> I should note that it appears that London, and possibly other European<br>
> countries, observe Daylight Savings Time starting this weekend, which<br>
> may push this meeting one hour *later* than the previous one for you<br>
> folks.<br>
><br>
> If anyone has serious conflicts with this time, and has other<br>
> suggestions, please try to have them in within the next 24 hours, and<br>
> I'll try to come up with a plan that works as well as possible. I'm<br>
> especially interested in anyone who currently has a ticket assigned to<br>
> them<br>
> (<a href="http://trac.openlayers.org/query?status=new&status=assigned&status=reopened&milestone=2.8+Release&order=priority&group=owner" target="_blank">http://trac.openlayers.org/query?status=new&status=assigned&status=reopened&milestone=2.8+Release&order=priority&group=owner</a>)<br>
> being able to attend.<br>
><br>
> Thanks!<br>
><br>
> Best Regards,<br>
> Christopher Schmidt<br>
> OpenLayers 2.8 Release Manager<br>
> _______________________________________________<br>
> Dev mailing list<br>
> <a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br>
> <a href="http://openlayers.org/mailman/listinfo/dev" target="_blank">http://openlayers.org/mailman/listinfo/dev</a><br>
><br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 27 Mar 2009 17:18:27 -0600<br>
From: Tim Schaub <<a href="mailto:tschaub@opengeo.org">tschaub@opengeo.org</a>><br>
Subject: [OpenLayers-Dev] maps with all "overlays"<br>
To: openlayers <<a href="mailto:dev@openlayers.org">dev@openlayers.org</a>><br>
Message-ID: <<a href="mailto:49CD5EC3.3070101@opengeo.org">49CD5EC3.3070101@opengeo.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hey-<br>
<br>
I've put together a pretty simple patch [1] that allows a map to be<br>
configured so that the lowest layer in the draw order is always treated<br>
as the base layer.<br>
<br>
With this patch, if you configure your map with allOverlays: true and<br>
configure every layer with isBaseLayer: false, you can have a map with<br>
any number (including zero) of layers visible or invisible.<br>
<br>
The patch is marked for commit, and I'm happy to commit it. If anybody<br>
has any comments about *not* wanting this, please speak up.<br>
<br>
Tim<br>
<br>
[1] see <a href="http://trac.openlayers.org/ticket/2004" target="_blank">http://trac.openlayers.org/ticket/2004</a><br>
<br>
--<br>
Tim Schaub<br>
OpenGeo - <a href="http://opengeo.org" target="_blank">http://opengeo.org</a><br>
Expert service straight from the developers.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Sat, 28 Mar 2009 05:22:36 -0700<br>
From: Schuyler Erle <<a href="mailto:schuyler@nocat.net">schuyler@nocat.net</a>><br>
Subject: Re: [OpenLayers-Dev] Transition From Google's API to OL<br>
To: Stephen Woodbridge <<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>><br>
Cc: "dev@openlayers" <<a href="mailto:dev@openlayers.org">dev@openlayers.org</a>><br>
Message-ID: <<a href="mailto:20090328122236.GA3056@vishnu.tridity.org">20090328122236.GA3056@vishnu.tridity.org</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
* On 27-Mar-2009 at 1:44PM PDT, Stephen Woodbridge said:<br>
> Another option might be to use OSM and Tilecache to cache a copy of<br>
> the OSM tiles locally.<br>
<br>
I was going to recommend this option as well -- it has the advantage<br>
that you won't need to deal with getting a whole bunch of vector data<br>
and then figuring out how to render it, although it would require more<br>
disk space than rendering vectors on the fly. I estimate that<br>
rendering the US down to zoom level 16 would require about 130 million<br>
tiles, or about 40 GB of cache.<br>
<br>
Arnie, if you're in Annapolis in June, you might be interested in<br>
this:<br>
<br>
<a href="http://barcamp.org/CrisisCamp" target="_blank">http://barcamp.org/CrisisCamp</a><br>
<br>
SDE<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Sat, 28 Mar 2009 09:29:36 -0500<br>
From: Arnie Shore <<a href="mailto:ashore3@verizon.net">ashore3@verizon.net</a>><br>
Subject: Re: [OpenLayers-Dev] Transition From Google's API to OL<br>
To: "dev@openlayers" <<a href="mailto:dev@openlayers.org">dev@openlayers.org</a>><br>
Cc: Bob Austin <<a href="mailto:mandolinpicker@verizon.net">mandolinpicker@verizon.net</a>><br>
Message-ID: <<a href="mailto:49CE3450.9030502@verizon.net">49CE3450.9030502@verizon.net</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hmmm. (I was hoping quietly to myself that nuth'n wd pan out, cuz if it<br>
did - and it does - I got a heap of work staring right at me.)<br>
<br>
Taking a harder look at OSM than I'd taken earlier tells me that it<br>
ain't half bad, given the kind of usage I'm addressing. I'd been<br>
concerned that the folks out in South Succotash wd have little<br>
available, but not so. I did a pair of test cases, and while OSM wont<br>
get to the lowest zoom that GMaps does, I think that's quite live-able<br>
with, with the added plus of local editing.<br>
<br>
I'd need to provide the kind of repository SDE notes, plus some<br>
convenient tools - Tilecache sound right - to allow a user to collect<br>
tiles for the areas of interest. And then there's the CAD application!<br>
<br>
Thanks, guys - you've helped a lot! I have a feasible direction now.<br>
<br>
AS<br>
<br>
PS re BarCamp: Yep, I'm in Annapolis in June. And July. And ... Will<br>
look hard at that - first peek comes up positive.<br>
<br>
~~~_/)~~~~~~~~_/)~~~~~~~~_/)~~~~~~~~_/)~~~~~~~~_/)~~~~~~~~_/)~~~~~~~~_/)~<br>
<br>
Schuyler Erle wrote:<br>
> * On 27-Mar-2009 at 1:44PM PDT, Stephen Woodbridge said:<br>
><br>
>> Another option might be to use OSM and Tilecache to cache a copy of<br>
>> the OSM tiles locally.<br>
>><br>
><br>
> I was going to recommend this option as well -- it has the advantage<br>
> that you won't need to deal with getting a whole bunch of vector data<br>
> and then figuring out how to render it, although it would require more<br>
> disk space than rendering vectors on the fly. I estimate that<br>
> rendering the US down to zoom level 16 would require about 130 million<br>
> tiles, or about 40 GB of cache.<br>
><br>
> Arnie, if you're in Annapolis in June, you might be interested in<br>
> this:<br>
><br>
> <a href="http://barcamp.org/CrisisCamp" target="_blank">http://barcamp.org/CrisisCamp</a><br>
><br>
> SDE<br>
><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Dev mailing list<br>
<a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br>
<a href="http://openlayers.org/mailman/listinfo/dev" target="_blank">http://openlayers.org/mailman/listinfo/dev</a><br>
<br>
<br>
End of Dev Digest, Vol 30, Issue 43<br>
***********************************<br>
</blockquote></div></div>