Open GoogleCodeExporter opened 9 years ago
Original comment by jus...@gmail.com
on 18 Jun 2013 at 4:03
https://github.com/camptocamp/cgxp/tree/master/openlayers.addins/GoogleEarthView
may be something to look at...
Original comment by jus...@gmail.com
on 4 Jul 2013 at 9:45
Or this
https://github.com/camptocamp/cgxp/tree/master/geoext.ux/ux/StreetViewPanel
Original comment by jus...@gmail.com
on 4 Jul 2013 at 9:47
> https://github.com/camptocamp/cgxp/tree/master/geoext.ux/ux/StreetViewPanel
This falls under the same thing as my "future development potential". It
requires a google Maps key which we don't have/want (we're trying to cut costs
;-) ). Also for whatever reason they don't seem to have an example of it on
their website, despite it being in git:
http://dev.geoext.org/geoext/extensions/geoext.ux/ux/
>
https://github.com/camptocamp/cgxp/tree/master/openlayers.addins/GoogleEarthView
This is the Google Earth browser-plugin version; not sure if it requires a
license but we don't have that plugin installed corporately. OpenGeo's
GeoExplorer features an example of it -
http://suite.opengeo.org/geoexplorer/composer/
I also used it as part of my Masters Dissertation.
My problem isn't the core logic, that's done. It's integrating it with Heron.
Either of those two may be desired by other users, but they're outside of my
remit and I don't have the facilities available to implement them anyway (lack
of plugin and key).
Original comment by jonathan...@warwickshire.gov.uk
on 4 Jul 2013 at 10:06
Attention http://trac.geoext.org/wiki/ux/StreetViewPanel isn't compatible with
V3 API. Better use GXP as I wrote in mailing list
https://groups.google.com/forum/#!topic/geoext-viewer-devel/foUlL5i_5rI
Original comment by martin.k...@gmail.com
on 4 Jul 2013 at 3:15
Original comment by jus...@gmail.com
on 8 Sep 2013 at 8:02
And another example:
https://github.com/teamgeo/ZaanAtlas/blob/master/app/static/script/app/plugins/S
treetview.js
from
http://geo.zaanstad.nl/zaanatlas/composer (GeoExplorer app).
Original comment by jus...@gmail.com
on 25 Nov 2013 at 3:58
Moving to 1.0.1
Original comment by jus...@gmail.com
on 22 Dec 2013 at 3:53
I did some further investigation: best to base on GXP version: is compatible
with V3 and doesn't require an Google API key. If the interaction like in this
example:
http://gxp.opengeo.org/master/examples/google-streetview-panel.html is ok, than
we can take that as starting point for integration in Heron. My suggestion is a
toggle button in the map toolbar to enable/disable StreetView popups when
clicking on map.
Original comment by jus...@gmail.com
on 23 Feb 2015 at 9:15
The use of a popup to provide the StreetView is definitely the best way to
establish the relationship between the map location and the view. I think this
approach works particularly well when a simple directional icon is added to the
map, showing the direction from which the StreetView is taken (as in this QGIS
plugin: go2streetview example).
https://geogear.wordpress.com/2014/11/04/go2streetview-v5-0/
Original comment by paullarc...@warwickshire.gov.uk
on 24 Feb 2015 at 3:16
Yes, I see. That would be powerful.
Following StreetView location and direction (POV) on the map will require extra
effort off course. We need to observe "StreetViewEvents", move a rotating
"Sprite" on the map etc. Also the interaction with the popup will need some
care: as a popup may interfere/cover the Sprite when moving in StreetView.
Shall we split this up:
- first a basic version as in
http://gxp.opengeo.org/master/examples/google-streetview-panel.html with
additional enable/disable button in the Toolbar.
-then a "map-follows-streetview" version
Can give estimates here or offline.
Note for future: https://www.mapillary.com a friendly Open Data alternative...
Original comment by jus...@gmail.com
on 24 Feb 2015 at 4:31
Original issue reported on code.google.com by
jonathan...@warwickshire.gov.uk
on 13 Jun 2013 at 12:39Attachments: