22nd March 2007, 12:47 PM
Thanks Kevin.
I've done experiments with point, polygon and polyline data. All of which work well on a Google Map. In fact, they will work well on any of the free mapping APIs (Google Maps, Yahoo Maps, MS Maps). I've demonstrated that SHP data can be served from MapServer (free) onto a Google Map either as WFS or WMS. I've also demonstrated that both spatial and non-spatial (attribute) queries and be run and the data returned.
So we know that it's all possible. The missing element of course is data.
The way I see online archaeology mapping going for the future is a series of services. This is really what Web 2.0 is all about - linking distributed datasets, in other words "mash-ups".
If others followed the lead of OA and opened up services (even if they were licenced) then a lot of archaeology data that has been so far unavailable could be shown to both researchers and the public.
Steve White
I've done experiments with point, polygon and polyline data. All of which work well on a Google Map. In fact, they will work well on any of the free mapping APIs (Google Maps, Yahoo Maps, MS Maps). I've demonstrated that SHP data can be served from MapServer (free) onto a Google Map either as WFS or WMS. I've also demonstrated that both spatial and non-spatial (attribute) queries and be run and the data returned.
So we know that it's all possible. The missing element of course is data.
The way I see online archaeology mapping going for the future is a series of services. This is really what Web 2.0 is all about - linking distributed datasets, in other words "mash-ups".
If others followed the lead of OA and opened up services (even if they were licenced) then a lot of archaeology data that has been so far unavailable could be shown to both researchers and the public.
Steve White