Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map analytics #548

Open
twelch opened this issue Apr 27, 2012 · 5 comments
Open

Map analytics #548

twelch opened this issue Apr 27, 2012 · 5 comments

Comments

@twelch
Copy link
Contributor

twelch commented Apr 27, 2012

In some of our OceanMap surveys we've thought about and capturing more information about how the user interacts with the map including the zoom level they were at and such. Seems like we could use that sort of thing here. For example capturing what the users view was when they draw a feature. What layers they're using and how much, where they're looking on the map. Could be pretty useful information to planners. Could be quietly collected in the background. What do you think?

@perrygeo
Copy link
Contributor

Capturing info at feature creation would be a different technique than logging layers and general usage stats. Both would be useful. The view that the feature was draw from could be used as the KML "look at" which would be nifty.

@twelch
Copy link
Contributor Author

twelch commented Apr 27, 2012

Seems worth doing and could be made agnostic in terms of whether you are using 2D or 3D.

@perrygeo
Copy link
Contributor

View capture would need to tied directly to the API of the map client - getting the camera properties is completely different API and data structure than a bbox/zoomlevel for instance.

@twelch
Copy link
Contributor Author

twelch commented Apr 28, 2012

Yeah, I was thinking in terms of the backend and API.

@twelch
Copy link
Contributor Author

twelch commented May 4, 2012

Indeed, Google is rolling this out with their analytics for business now. http://www.webpronews.com/google-maps-analytics-for-business-opens-up-troves-of-new-site-data-2012-04.

They take it from an optimization/goal standpoint. You can see for example how much people are panning the map or what zoom levels they are accessing. You can then tune your map to reduce how much they do these things

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants