go2streetview v6.0
CHANGELOG v6.0 (3/4/2015
1) info layer overlay in streetview window
2) info layer overlay in bing window
3) new gui toolbar
4) location tracking improvement
5) resize issue opening view fixed
The major plugin improvement in this release is the support to markers overlay (or so called pushpins in Bing maps). Furthermore the gui has been revised with a button bar to receive plugin actions including the new infoLayer feature.
The plugin allows to select a point layer to display as marker overlay in the Google streetview and Bing bird’s Eye views. The markers can be customized with layer attributes values. Clicking the button on the right of the new buttonbar appears the infolayer dialog:
In the first field must be specified an info layer from loaded point Layers and a distance buffer from the point of view to consider the related overlay markers. It is recommended to set this parameter carefully to avoid slowdowns and plugin crashes.
The other fields (info, Icon path and Html infobox) are optional but useful for for information purposes and can be filled with the help of Expression builder.
The markers icon path, if specified, overrides the default marker styles. Icons can be easily categorized using conditions in Expression Builder.
A Yellow icon in Bing bird’s eye indicates the Google streetview Point of view.
PS. A little “easter egg”. Taking a snapshot the plugin copies in the clipboard the path to the google panorama image
Great Plugin! Love the new feature. I’m still having some issues with “Latin” characters halting the script, but I haven’t had the time to examine the code yet. Might be a Linux “thing”. Thanks again for a great plug-in!
I am very happy to know you like it!
encoding and decoding non ascii string it’s always a deal. But In this case i think the problem resides in writing javascript variables from the python plugin. non strandard chars could raise exceptions that are difficult to caught.
I would be very glad if you would submit issue on github with the blocking dataset and give any help to find the bug.
Hi Klas, I worked on the issue and I released a new plugin version with minor fixes. I submitted it to a very heavy unicode stress test and now everything is fine. You can download it from Github or Official repository. Let me know if it resolves. Thanks again for issue submission
Well, I haven’t been able to test it. The problem is that as soon as I enable the plug-in I get a Python error ( I’ll put something on GitHub), but the plug-in still starts. The real issue is that when I activate the “info layer” QGIS starts to eat up my RAM! All of it!! Sorry…
Is there something special I need to do to get the icons to show in streetview? I LOVE this plugin and it has been such a useful tool in QGIS. Just saw the latest update and can’t figure out how to get anything to show up.
Hi Z.
Could you explain better your problem?
Make me understand: you loaded a new point layer on QGis, select it as info Layer clicking the button on the right, give OK but the markers didn’t appears on streetview….
Perhaphs it’s an issue. Please provide more infos to help me undersrtand.
Anyway, as soon as possible, I will post a little video tutorial
That is correct. I have a simple point file with 3 fields. CRS is WGS84. I have the layer in the TOC and when in Go2Streetview, I select it as the info Layer, adjusted various buffer values and clicked ok. The streetview works, but no icons or labels.
Using Windows 7 machine, all plugins updated and using :
QGIS version 2.8.1-Wien QGIS code revision exported
Compiled against Qt 4.8.5 Running against Qt 4.8.5
Compiled against GDAL/OGR 1.11.2 Running against GDAL/OGR 1.11.2
Compiled against GEOS 3.4.2-CAPI-1.8.2 Running against GEOS 3.4.2-CAPI-1.8.2 r3921
PostgreSQL Client Version 9.2.4 SpatiaLite Version 4.1.1
QWT Version 5.2.3 PROJ.4 Version 480
QScintilla2 Version 2.7.2
Well Zac,
It’s the same issue reported by Klas Karlson. When using a point layer with geographic crs (latitude and longitude), distances on map must be defined in degrees. The first release of the plugin had a default distance buffer value (used to filter only points located close to the Panorama Point of view) set to 100, that is, if intentended in degrees, a huge distance value, so big to take all points of the layer as markers and cause performance and memory issues.
Yesterday I released a new version of the plugin, with new default distance buffer values, and a filter on total number of markers (max 200) so I suggest you to update plugin from repository with the v6.2 release and retry to load info layer.
If this doesn’t resolv, try to reproject layer to a projected crs (UTM are ok). Try to load info layer whitout specifying info field or html infobox to exclude malformed attribute values that could block javascript.
Apologize on slow response, but the most recent version mentioned above did the trick. Excellent improvement and has worked wonderfully in over 300 locations tested this week. Many thanks!
So, just out of curiosity, what motivated you to create this plugin?
Essentially I made tools for my everyday work needs. As urban planner I need to verify projects and plans on site on a wide region without leaving my office, so I wrote the plugin and shared it with the community to get new suggestions and acquire issues reports. Anyway I enjoy getting attention on my work.
And You, why are you asking this?
I am actually putting together a piece on the plugin for the Geographic Information Network of Alaska (GINA). I also used the plugin over the summer for my class to help with Georeferencing UAV images because our base layers were from 2009 and we needed imagery from closer to 2015.
Hi patrick, you could give a try to a new plugin I recently developed to use streetview as a “theodolite”. I will publish it as soon as I will write a brief user help. In the meanwhile you can use it collimating the same location from two different points of view and calibrating the resulting point dragging the cross in the middle view if needed. The resulting 3d point can be collected in qgis with a annotation string …
https://github.com/enricofer/stereoSurveys/archive/master.zip