Google Maps + ESRI's ArcWeb Services
Categories: Google Maps
Hi all-
This is my last Google Maps post for a while! We just finished a demo application for the State of Kansas where a user can geocode a location and see that location on a Google Map client. While that is not that unique, the details of the application are pretty cool.
http://geoportal.kgs.ku.edu/googlemaps/ks_gm.cfm
Jeremy & Praveen
This is my last Google Maps post for a while! We just finished a demo application for the State of Kansas where a user can geocode a location and see that location on a Google Map client. While that is not that unique, the details of the application are pretty cool.
http://geoportal.kgs.ku.edu/googlemaps/ks_gm.cfm
- Users can geocode by city (Lawrence), address (1930 Constant Avenue, Lawrence), zipcode (66047), or the intersection of streets (9th & Iowa, Lawrence). We are using the Public Services category of ESRI's ArcWeb Services.
- The black and white imagery is coming from ESRI's ArcSDE through ArcIMS. We are using the ArcIMS cache on demand system that I mentioned here. The reason for this is the lack of quality imagery data that Google provides for most of Kansas.
- The Map client is the Google Maps ajax client.
- The Road data is from Google Maps (Teleatlas).
Jeremy & Praveen
Posted by jbartley at 4:51 PM | Link | 5 comments
Subscription Options
You are not logged in, so your subscription status for this entry is unknown. You can login or register here.
Re: Google Maps + ESRI's ArcWeb Services
once again, nice work guys. I like the integration with the free ArcWeb services for geocoding (I think I'll add that in right now ;) )
Are you running into memory problems with tile caching?
cheers
brian
Are you running into memory problems with tile caching?
cheers
brian
Posted by Brian Flood on October 28, 2005 at 8:23 AM
Re: Google Maps + ESRI's ArcWeb Services
Thanks Brian-
No memory issues. We are caching the tiles to disk. We could run into hard drive space issues. If we were to cache every tile for all Google Maps scale levels we would have to store about 500 gigabytes of tiled images. I am banking that for most of Kansas users won't look at every 300m X 300m tile (google zoom level 0).
Cheers,
Jeremy
No memory issues. We are caching the tiles to disk. We could run into hard drive space issues. If we were to cache every tile for all Google Maps scale levels we would have to store about 500 gigabytes of tiled images. I am banking that for most of Kansas users won't look at every 300m X 300m tile (google zoom level 0).
Cheers,
Jeremy
Posted by jbartley on October 28, 2005 at 8:46 AM
Re: Google Maps + ESRI's ArcWeb Services
nice, really good work.
ahh, google zoom level zero, otherwise known as the hard drive killer. I had to add checks for no features, full transparency, full background color and pixel-for-pixel comparison with existing tiles just to keep the number of tiles down during exports.
cheers
brian
ahh, google zoom level zero, otherwise known as the hard drive killer. I had to add checks for no features, full transparency, full background color and pixel-for-pixel comparison with existing tiles just to keep the number of tiles down during exports.
cheers
brian
Posted by Brian Flood on October 28, 2005 at 9:00 AM
Re: Google Maps + ESRI's ArcWeb Services
Cool app, but I'm curious...doesn't your use of ESRI's Public ArcWeb Services for the State of Kansas violate their policy of "non-governmental" use? Or is it just because you're prototyping right now?
Posted by Chris on October 28, 2005 at 9:17 AM
Re: Google Maps + ESRI's ArcWeb Services
You are right on that one. For now it is a demo/prototype. If there is an interest within the state, we will switch over to our licensed version of ArcWeb Services (something like 1 cent per geocode request).
Posted by jbartley on October 28, 2005 at 9:29 AM
Commenting has been disabled for this entry.