|

»

Newbie here . . .Just saying hi.

View: New views

3 Messages — Rating Filter: Alert me

	Newbie here . . .Just saying hi. by Bob Basques :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. All, Hi, just read through the WIKI and added myself as an interested party. My main interest is in using something like tilecaching to provide an emergency response platform that can stand on it's own if the network goes down. Some sort of system that would auto-cascade (to some degree) while there was anetwork, and then run on it's own if the network drops for some reason. While I'm not focusing on the specific tile scheme(a) I do think this is the approach to take with easily syncing two services (master and remote) so that the client can retrieve from either in some semi-automated fashion. More of an interest in the application aspects. I can run this all internally without the need to have a standard (yet), but for obvious reasons, it makes sense to have a standard. One thought after reading the WIKI is why not set up something along the lines of an interpreter/convertor that can feed off of existing systems to build a tilecache, then it becomes more of a Client thing vs a server thing. . . . Just musing some here to get a conversation started. . . . bobb _______________________________________________ tiling mailing list tiling@... http://lists.eogeo.org/mailman/listinfo/tiling
	Re: Newbie here . . .Just saying hi. by crschmidt :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Thu, Aug 20, 2009 at 08:48:34AM -0500, Bob Basques wrote: > All, > > Hi, just read through the WIKI and added myself as an interested party. > > My main interest is in using something like tilecaching to provide an emergency response platform that can stand on it's own if the network goes down. Some sort of system that would auto-cascade (to some degree) while there was anetwork, and then run on it's own if the network drops for some reason. > > While I'm not focusing on the specific tile scheme(a) I do think this is the approach to take with easily syncing two services (master and remote) so that the client can retrieve from either in some semi-automated fashion. > > More of an interest in the application aspects. I can run this all internally without the need to have a standard (yet), but for obvious reasons, it makes sense to have a standard. Um. We have a copule tiling standards. The WMS-C req and the TMS spec. Both are widely used. (Ther'es also WMTS; that isn't widely used.) Not sure what your thoughts are with regard to needing another spec. -- Chris > One thought after reading the WIKI is why not set up something along the lines of an interpreter/convertor that can feed off of existing systems to build a tilecache, then it becomes more of a Client thing vs a server thing. . . . Just musing some here to get a conversation started. . . . > > bobb > > _______________________________________________ > tiling mailing list > tiling@... > http://lists.eogeo.org/mailman/listinfo/tiling -- Christopher Schmidt MetaCarta _______________________________________________ tiling mailing list tiling@... http://lists.eogeo.org/mailman/listinfo/tiling
	Re: Newbie here . . .Just saying hi. by Bob Basques :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Not really interested in another spec, but am interested in which is best for ehat, why are there more than one for example, what are the pluses and minuses of each, etc. . . . bobb >>> Christopher Schmidt <crschmidt@...> wrote: On Thu, Aug 20, 2009 at 08:48:34AM -0500, Bob Basques wrote: > All, > > Hi, just read through the WIKI and added myself as an interested party. > > My main interest is in using something like tilecaching to provide an emergency response platform that can stand on it's own if the network goes down. Some sort of system that would auto-cascade (to some degree) while there was anetwork, and then run on it's own if the network drops for some reason. > > While I'm not focusing on the specific tile scheme(a) I do think this is the approach to take with easily syncing two services (master and remote) so that the client can retrieve from either in some semi-automated fashion. > > More of an interest in the application aspects. I can run this all internally without the need to have a standard (yet), but for obvious reasons, it makes sense to have a standard. Um. We have a copule tiling standards. The WMS-C req and the TMS spec. Both are widely used. (Ther'es also WMTS; that isn't widely used.) Not sure what your thoughts are with regard to needing another spec. -- Chris > One thought after reading the WIKI is why not set up something along the lines of an interpreter/convertor that can feed off of existing systems to build a tilecache, then it becomes more of a Client thing vs a server thing. . . . Just musing some here to get a conversation started. . . . > > bobb > > _______________________________________________ > tiling mailing list > tiling@... > http://lists.eogeo.org/mailman/listinfo/tiling -- Christopher Schmidt MetaCarta _______________________________________________ tiling mailing list tiling@... http://lists.eogeo.org/mailman/listinfo/tiling