owned this note
owned this note
Published
Linked with GitHub
# OSMbe Camera management document - 360° put to use
###### tags: `open streetview`
## Candidates to use the camera
### Current
* **GoPro 4** C3351324926332 (still needs to be sent???)
* **Hans Vandenabeele**
* already doing a lot of stuff with cameras
* drives around a lot
* **GoPro 3** C3351321759706 "Kempen"
* DenTonny
* Has the camera since 01/06/2023
* Received Go Pro sticks for car setup
* [Stijn Claes](https://www.mapillary.com/app/user/stijn_claes?lat=51.21966465447005&lng=4.9037399987664685&z=9.48598562793459&panos=true)
* Had camera between 26/1/2023 - 01/06/2023
* Few rides (Grobbendonk-Nijlen-Geel-Vosselaar)
* [Koen vde](https://www.mapillary.com/app/?pKey=531577102198469) (December 2022 - January 2023)
* Wanted to do this within IOK-area as a proof of concept
* Region: Westerlo, Laakdal, Hulshout, Geel
* As a consequence, IOK (Koen-Stijn) has bought a GoPro for own use!
* **GoPro 2** C3351324753808 Tim Couwelier
* **GoPro 1** C3351321716556 [Rob Noort](https://www.mapillary.com/app/user/robnoort): has the camera since 10/11/2023 + new helm mount
* president of local section of Fietsersbond in Asse
* Rob already made pictures in the past for OSM BE with a Go Pro 7
* Thierry will get it back on Saturday 23 March
### Proposed
* Andy ([Der Bierpuncheur](https://www.openstreetmap.org/user/Der%20Bierpuncheur))
* lives in Sterrebeek
* works in Evere
* would like to cover area around Zaventem-Kortenberg-Vilvoorde
* [Jeroen Meirlaen](https://www.openstreetmap.org/user/carameljm) proposed himself in February 2024
* lives in Vlaamse Ardennen
* Mapillary-profile: https://www.mapillary.com/app/user/jeroenmeirlaen
* would like to cover: Vlaamse Ardennen (Oudenaarde, Maarkedal, Ronse, Horebeke, Kluisbergen, Brakel, Zwalm, Zottegem, Kruisem
* link with Trage Wegen Vlaamse Ardennen
https://www.facebook.com/groups/687104293074453
and with Natuurpunt Maarkebeekvallei (operator of Slow Ways)
https://devriendenvandemaarkebeekvallei.wordpress.com/
* Michiel Stuys
* it was more a "we asking them" thing, he's open to the idea, but didn't seem entirely convinced
* GIS coordinator at Edegem and Kontich
* marc_marc (in favour for a 2nd try)
* used it a first time during some days in Chrismas holidays 2022-2023
* would use for commute, walking, recreational trips
* based in north of Brussels
* limited engagement because of frequent travels
* Koen Roekens
* colleague of Joost @ NCCN
* would use it for MTB in winter (east of Brussels up to Meerdaalwoud)
* koen.roekens at gmail.com
### Finished
* Thibault (...- January 2024)
* handed over to Joost during meetup
* [Mizuna](https://www.mapillary.com/app/user/Mizuna) (Raf De Ryck): 20/7/2023 -> October 2023
* based in Sint-Pieters-Leeuw
* would try to do most of the municipality
* ***question from Thierry1030***: could you also take pictures of the [VolleGaas-route](https://www.openstreetmap.org/relation/12345861#map=12/50.7838/4.1343)? [Stef](https://www.openstreetmap.org/user/StefDeGreef) passed by there and took pictures in April 2022, but since June 2022 this route is also signposted
* [Thierry Jimenez](https://www.openstreetmap.org/user/Thierry1030): 17/11/2022 -> July 2023
- would like to cover the rest of Brussels region
- if time left also new infra in Brussels periphery
* [marc_marc](https://www.openstreetmap.org/user/marc__marc): 22/12/2022 -> 10/01/2023
-> during Christmas holidays in and around Brussels
* [RRRz](https://www.mapillary.com/app/user/RRRz) (Randy, randy@onepost.net): April-May 2023
* Lives in Brussels EU-quarter and teaches in a school @ Karreveld, Molenbeek twice a week
* Interested to cycle around Molenbeek
* Got in touch via newsletter Fietsersbond
* Brice Maron (eMerzh) said [on twitter](https://twitter.com/eMerzh/status/1505969471718141958) - he's interested to cover Brain l'Alleud and surroundings. We're in touch via e-mail
* received a camera May 12th 2022 and sent it in December 2022 to kvde of IOK
* Thibault Molleman
* lives and mapping Ruiselede
* will only keep for a few weeks
* a full day of cycling in Stad Antwerpen
* Peter Elderson.
* will work on hiking trails
* maybe do the Grenslandpad entirely
* connected to detailed mapping of the entire trip
* camera was sent on 29/6/2022, back by mid October 2022
* Seppe Santens. WestToer colleagues are willing to take the camera when doing prospection. They took about 10.000 pictures, sent it back end of April. And have bought their own camera!
* Jean-Christophe Lallemand
* lives close to Pierre Serpe
* also volunteer at GRACQ
* recieved a camera around mid May 2022
* [Pierre Serpe](https://www.youtube.com/watch?v=W6gpxHQL4Ns&t=51s)
* member of Gracq (= French speaking cyclist's association) doing a project for Wallonie Cyclable (Wacy) in Saint-Georges-sur-Meuse
* start: camera arrived 20/3/2022
* finished: 19/5/2022
* go pro hero sent back early May
* won a GeoChallenge project, will buy SEVERAL more [camera's](https://www.mapillary.com/app/?pKey=1419764121791494)
* camera moved straight on to Jean-Christophe Lallemand
* Dirk Dedoncker & Joost Schouppe
* Dirk has done Lierde en Pepingen
* Joost is doing Halle and uses it on trips to Brussels
* had the camera form Feb 7th till March 13th (with some interruptions when Joost mapped).
* then again after Seppe sent it back (end of April) till it was passed on to Peter Elderson at the end of June
* mobility expert working for those two municipalities with his company https://a2bmobility.be/
* interested to do more municipalities from April
* has access to the camera from early may. Joost & Dirk will share the camera for now.
* Tim Couwelier
* Would be interested to take it for a few tours around Roeselare, both by car and bike. Aiming for a fairly 'structural' coverage of certain areas.
* Claudia de Pus
* works at Provincie Oost-Vlaanderen
* interested for a project related to traffic signs on cycle highways
* HAS A 360 EVERYWHERE CAMERA Vincent Bombaerts
* lives near Rebecq
* SPW employee, well connected
* will probably receive a camera from Pierre Serpe
## More context
* [First discussion document on the topic of street level imagery](https://hackmd.io/g-ZIyBr2QgeLpKz4T6BCeg?view)
* [Project page on OSMbe](https://openstreetmap.be/en/projects/streetlevelimagery.html)
* https://wiki.openstreetmap.org/wiki/WikiProject_Belgium/open_streetlevel_imagery
* [Starter's manual](https://wiki.openstreetmap.org/wiki/WikiProject_Belgium/open_streetlevel_imagery/starters_manual) (wiki) ([original](https://docs.google.com/document/d/1mu27MJlwgXL0vBnF3Nfn2my8AIU-dOYl/edit?rtpof=true&sd=true))
* [automatic issue detection](http://osmose.openstreetmap.fr/en/map/#item=8300%2C8320&zoom=12&lat=50.751&lon=4.2334&level=1%2C2%2C3&issue_uuid=a4993876-197d-4833-1762-f86c0cfc60d4) via Mapillary objects & traffic sign detection
## Practical info for taking/processing images
### To do / to document
* horizontal horizons
* https://www.youtube.com/watch?v=HwkpGe-jlvI
* https://community.gopro.com/t5/Cameras/MAX-360-Photo-TimeLapse-Level-Horizon-EXIF-XMP-Orientation/m-p/996938#/M195623
* https://forum.mapillary.com/t/strange-horizons-of-gopro-max/4322
* automatically remove duplicates, see https://help.mapillary.com/hc/en-us/articles/115001753465-Uploading-with-Command-Line-Tools + https://community.gopro.com/t5/Cameras/MAX-360-Photo-TimeLapse-Level-Horizon-EXIF-XMP-Orientation/m-p/996938#/M195623
### Materials needed
* 360 camera
* Gopro Max (already acquired)
* Case for the Max (so the lenses dintly don't get damaged, both during shipping to the user and if the user wants to take it on location.) [This one seems good](https://www.amazon.nl/ULBTER-Opbergtas-Waterdicht-Accessoire-pro/dp/B0887YHPDM) (amazon US's reviews claim it's good)
* Extra pair of lens covers (we don't give them to the user, but we'll have them ready if user lost them, small enought to fit in an envelope and post it to them) [bol.com](https://www.bol.com/be/nl/p/gopro-max-replacement-lens-caps/9200000121302900/?Referrer=ADVNLGOO002018-G-131768302786-S-293946777986-9200000121302900&gclid=CjwKCAiAgbiQBhAHEiwAuQ6BklM8qLOerFJUn_MM-3k7ZOk5F5-LAFCwGrlxvc121r3j3yBkfTpGnBoCowwQAvD_BwE)
* Extra battery? (only buy official)
There are special 3rd party battery covers which expose the actual USB-C port so you can charge while you're using it. But this obv makes the port exposed to the elements, makes it more prone for dust and debree to get in. And bye bye waterproofness. (might also increase chance of it falling with a cable plugged in, to damage the port) And last reason why it's not a good idea to use it for this application: Overheating, multiple reports from people using their gopro's in the sun, while charging and having the camera shutting down because of the heat (charging heat). This is why a spare battery is better.
* USB 3.0 high speed sd card reader (with both sd and micro sd card slot AND that can use both at the same time (most can't do both at the same time))
* [Suggested SDCard reader](https://www.amazon.nl/UGREEN-Kaartlezer-Reader-Micro-Kaart/dp/B08CS788Q8) (it's also compatible with 2tb microsd cards as a bonus and it's cable is attached so cable can't get lost)
* A pool of micro sd cards, Gopro recommends sdcards with rating Class 10 or UHS-1, we might not need that level of performance, but UHS-1 is basically the 'standard' speed anyway. Plus a nice speed makes it quicker to do datatransfers/duplication.
* [Tweakers Microsd cards sorted by price/GB](https://tweakers.net/geheugenkaarten/vergelijken/#filter:TY7BCoMwEET_Zc-hJKma1g8QPPTksXhIk5UGopFEpCD-eze2lF52mZnHMBs8op5saxPUd8F5xehcegZuWjEu3TPMHXo0iwsT1IP2CRmEaDE2Dr2FGtKMxg3O6AP5hl2IC2U6mZ9DWEu8khWDOTqDN0eNnB0FjfMLRtqwgSir_MacguT8xKli1K-PynJnBKkMrdrTbDiX6go92VKo4s8vBPkMVMElxfv-Bg) shows that the best value is the 'Sandisk Ultra microSDXC UHS-I 400GB (SDSDQU-400G-GN6MN)' (45,90 euro)
* 1-2 micro SD card to SD card adapters (TM: I have some lying around if you need a couple)
* Assuming each 360 photo is 3.2MB. 400GB(x1024 for MB's) / 3.2MB = 128k photos on that sd card.
128k / 30 (#photos each minute) / 60 (" each hour) = 71 hours on a 400GB sd card. For 90% of people who borrow the camera, that should be enough.
* Ideally we have a couple sd cards (maybe 4)
### Risks
* Technically when we're shipping the sd cards around, definitely the one in the letter, we're hoping nothing happens with the sd card full of facial data on it..
### Logistics:
In ideal circumstances we hand off the kit to the next person in line (hence why it might be smart to have multiple pairs of sd cards in the kit).
> Just an idea, might be useful to have a map of where our trusted members live/work/go-to-frequently. That way we could see how to get the kit from one person to another just by passing it off between each other
In case we decide it's better to ship it to them:
We always create shipping labels ourselves! This was we can make sure that the package has insurance on it.
We could either
- Use 1 Bpost account we share the credentials with between trusted members so whoever has '360 cam logistics duty' can create labels. Downside: person who makes the labels has to use Bancontact/kbc/... to pay for it. So we'd need to refund via the osmbe account to them. Spreadsheet might be handy for this
- Use a platform like Sendcloud (TM: We used it in the pharmacy for a good year) where you can enable Direct debit (domiciliëring). Only downside of Sendcloud is that while they have a lower shipping fee with Bpost, there is a surcharge when you deposit the package at a 'retail location' instead of a one of their big sorting centers.
| | Bpost .be | Sendcloud (Bpost) |
| -------- | -------- | -------- |
| Shipping @home | € 5,70 | € 5,50 |
| Shipping @postpoint | € 4,40 | € 4,95 |
| Insurance €500 | € 1,20 | € 1,20 |
| Retail surcharge | | € 0,73 |
Bpost is from experience the cheapest for small parcels within Belgium. It's undecided which of these 2 options we go with. The example tracking spreadsheet will go with the more complex option of using bpost directly and tracking payments.
### Contents of the kit
This is what would be in the box/kit we send to the user:
> Everything inside the kit that's electrical should be in a waterproof plastic zipbag
> Also, everything should have (Dymo) Labels saying it's property of OSMBE.
> Ideally we put everything inside of some kind of plastic box maybe? With the assumption the cardboard box might get dirty or ripped at some point. If it's all contained in a plastic box, the user can ship it back in a different cardboard box in case the original got damaged.
* GoPro Max with the lenscovers on, inside of the fabric case
* USB-C to USB-A cable
* The SD Card reader
* 2 micro sd cards (or 4 if user really needs more storage or we plan to forward the kit to the next person after that) (Make sure the sd cards are correctly preformatted)
* Extra battery?
* helmet? or just mount(s)? different types of mounts?
* ~~Envelope (+stamp)~~ (we're assuming the user has atleast one stamp and one envelope lying around)
* Super small ziplock bag and some kind of ... hard... pouch? to put the micro sd card in. (something that can't get ripped open and is big enough if the envelope got a small hole during postal service somehow, it wouldn't slide out)
### Upload/backup strategy
We have two sd cards with the idea that we make a copy of all the files and send them trough different methods. (one with the original kit, one in an envelop to Thibault for storing on the server). Once Thibault has a couple sd cards, he can send them back to Joost or whoever manages the kit. Or we send them every time we're finished with one (does mean more stamp usage obv)
Step 1. Duplicate files/backup
**Option A:** User sends the originals via an encrypted channel to Thibault's server. Seafile/Resilio-sync/Syncthing might be ideal as it will automatically resume if the pc restarts, plus you can easily limit the bandwidth on it. But FTP or other methods would also be possible
**Option B:** User inserts the micrsd card they used for capture into the sdcard reader and inserts the empty microsd card using the microsd-to-SD adapter into the regular sd card slot.
Both will show up in their file browser, they just copy from one sd to the other. And make sure to verify that all the files were transferred by rightclicking each sd card and checking that the amount of files and filesizes are the same.
Step 2.
**Option A:** (Fully hands on)
* User knows how to use all the tools or is willing to learn to use the documentation (but isn't afraid of command lines)
**-> Upload using his own Mapillary account to the Mapillary OSMBE org**
**Option B:** (Semi hands o,n)
* User knows how to use all the tools or is willing to learn to use the documentation (but isn't afraid of command lines)
*BUT doesn't want to spend their bandwidth on uploading the data*
**-> They give us their login or use mapillary_tools to generate token - We upload to their account using their login/token under the Mapillary OSMBE org**
**Option C:** (Fully hands off)
* User wants to fully handoff all the work to us
**-> They give us their login or use mapillary_tools to generate token - We upload to their account using their login/token under the Mapillary OSMBE org
(Create generic Mapillary account for those that don't care if it's not under their name)**
* User sends one of the SD cards to Thibault as described in Step 1 and leaves the other SD card in the kit box. Then both Joost and Thibault will have a copy, gets decided who does the work afterwards.
3. Sharing with KartaView
https://osm.svimik.com/photosync/
### Proposal for tracking spreadsheet
| Column 1 | Column 2 | Column 3 |
| -------- | -------- | -------- |
| Text | Text | Text |
## Notes and thoughts
* what about "indoor view" (for public buildings)? example of a shop -> https://vtour.ovh/supermonkey/
**Opslag foto's**
**Thierry:**
- foto's die genomen worden met de GoPro van OSM BE
- alle fotomakers die momenteel in mapillary uploaden onder de groep "OSM Belgium members" + Philippe Casteleyn reken ik eigenlijk ook bij in "deze denkoefening"
**Joost:** Dan zou 't natuurlijk wel cool zijn mochten we die kunnen binnentrekken. Al zijn we dan op zich opnieuw aan het uitvinden wat OSMFR al heeft. Die hebben een server waar je tegen kan zeggen "haal via de api van mapillary al mijn foto's binnen"
maar goed, ik weet niet wat die daar mee uitsteken en er staat denk ik ook nergens veel documentatie over
Ham: full coverage november 2021
-> Thierry: kwaliteit niet optimaal (bijv. tekst onder verkeersbord): https://www.mapillary.com/app/?pKey=296527569037778
Oostrozebeke: Sept 2020 https://www.wvigisco.be/gis-coordinatie/oostrozebeke-als-eerste-volledige-gemeente-360-op-mapillary/
WEGEN
fietspaden
wegennetwerk: maxsnelheid, maxgewichten etc + inschatting verkeersborden zelf???
Allerlei POI: detailhandel, vuilbakjes, fietsenstallingen, ...
Voorbeeld:
https://mapcomplete.osm.be/waste_basket.html?z=16&lat=51.10239&lon=5.146966&language=nl&tab=1#welcome
Overzicht "easy POI": https://mapcomplete.osm.be/
voorbeeld visualisatie als fietsinfrastructuur volledig is:
https://www.cyclosm.org/#map=14/51.1021/5.1668/cyclosm
23/12/2021 Tim Couwelier:
"Qua fotobeelden wel het nadeel dat **Fluvius** een raamcontract heeft uitgeschreven voor een heel pak gemeentes
En dat is natuurlijk weer closed"
"Maar het systeem wat Vlaanderen dekte is inderdaad stopgezet
Dat gaf gemeentes de optie :
Ofwel intekenen op een contract (per gemeente) met de originele data-aanbieder
En dat was vrij stevig qua prijs
Ofwel zonder beelden verder doen
Of kijken naar derde partijen
Een aantal mogelijke private aanbieders hebben zich in die markt gezet, waaronder vansteeland
Er is vorig jaar ergens door fluvius een brief gestuurd aan alle gemeentes waar ze werkzaam zijn
Om zo een prijsvraag als soort groepsaankoop te lanceren
Dat was een vrij uitgebreide lijst, de tender daarvoor sprak denk ik van 70 gemeentes of zo
Maar alles zit achter klantlogins weg
Weet niet zeker wie het binnengehaald heeft"
26/12/2021 Thierry:
ter info in Limburg project mee ontwikkeld door **Fluvius**:
https://www.s-lim.be/nieuws/google-maps-voor-limburg-maar-dan-handiger-in-gebruik
1) "s-Lim, in 2017 opgericht door Nuhma en **Fluvius**, is de instantie van de Limburgse gemeenten die er moet voor zorgen dat Limburg mee is in het verhaal van de smart cities/regions"
2) "Er staan voorlopig vier rubrieken op de slimme kaart. In het hoofdstuk ‘mobiliteit’ kun je opzoeken waar je de auto of fiets kunt parkeren, waar je deelauto’s vindt, wanneer de bus komt en hoe druk het verkeer is."
3) "Onder de categorie ‘milieu’ kan men via de slimme kaart kijken waar de glasbollen staan. “Dit is geen lijst, maar een informaticakoppeling. Als men ergens een bak verplaatst, wordt die informatie ook meteen aangepast”, zegt Neyens."
4) "In de rubriek ‘veiligheid en welzijn’ kunnen gemeenten laten zien waar veiligheidscamera’s hangen. “Het is de autonomie van de gemeenten om te beslissen of ze dat willen laten zien of niet. In deze rubriek kun je ook ontdekken waar de **AED-toestellen** hangen."
5) "Via de stadsapp kunnen inwoners ook melding maken van sluikstorten, slechte fietspaden of zelfs van onveilige situaties in het verkeer. “Met deze input van de burgers, wat ze nu noemen, ga je de inwoners mee laten helpen om bijvoorbeeld de wegen veiliger te maken”, aldus Neyens.""
@Joost: hebt gij toegang tot dit portaal? of kunt ge dat vragen?
https://dataportaal.slim.mycsn.be/nl
# message to talk-be
https://lists.openstreetmap.org/pipermail/talk-be/2022-January/011404.html
# message to Flemish municipaliteis that already share 360
miek.sannen@ham.be,
info@ham.be,
Leen Vandenbussche <gis@oostrozebeke.be>,
gemeente@oostrozebeke.be,
ilse.vanhove@londerzeel.be,
info@londerzeel.be
Beste,
We willen jullie gemeente heel graag bedanken voor het delen van gebiedsdekkende 360° straatbeelden als open data - een Google StreetView die je ook écht mag gebruiken. Jullie zijn de eerste drie gemeenten in Vlaanderen die dat doen - en geen enkele andere overheid deed het jullie hier voor. Voor ons bij OpenStreetMap Belgium en Open Knowledge Belgium vinden we dat echt fantastisch - en we hopen dat jullie veel navolging krijgen.
Voor OpenStreetMap zijn deze gegevens zeer handig in de praktijk. We kunnen ze gebruiken om ons kaartmateriaal verder te verfijnen op jullie grondgebied. Die data kunnen jullie dan ook weer gebruiken, aangezien al onze data ook weer open is.
Meer dan enkel een dankwoord jullie richting uit te sturen, willen we vragen of er iets is dat we als dank voor jullie kunnen doen. Doordat er recente 360° beelden zijn in jullie gemeente, kunnen we bijvoorbeeld vrij eenvoudig dit doen:
- alle fietspaden in detail in kaart brengen (zie bijvoorbeeld deze kaart https://www.cyclosm.org/#map=16/50.7306/4.2430/cyclosm om de details gevisualiseerd te zien). Ook "kleine fietsinfrastructuur (zoals pompen, stallingen, winkels, ...) kunnen eenvoudig verzameld worden met jullie beelden en het tooltje https://mapcomplete.osm.be/cyclofix
- het wegnetwerk zelf verrijken: bijvoorbeeld alle wegsnelheden in kaart brengen, de maximumgewichten zodat vrachtwagens correct gerouteerd worden
- op basis van jullie beelden zijn er door Mapillary ook een hele hoop dingen automatisch gedetecteerd, denk aan verkeersborden, maar ook rioolputten, vuilbakjes etc.). Die mogen nu ook gratis hergebruikt worden. Wij kunnen helpen die data te exporteren vanuit Mapillary, maar ook ze manueel nakijken tijdens een integratie in OpenStreetMap.
- alle winkels in kaart brengen
- onze vrijwilligers houden zelf ook Mapillary up to date. We gaan met OpenStreetMap Belgium investeren in een camera om ook 360° beelden te kunnen schieten. Als er specifieke plaatsen zijn waar een update nodig is, dan kunnen we dat misschien wel regelen.
Lijkt een of meer van deze zaken jullie wat? Of inspireert het voor andere projecten? Geef gerust een seintje om er eens in videocall of telefonisch over na te denken.
Onze vrijwilligers vinden dit soort projectjes bijzonder leuk, maar we blijven een relatief kleine groep. Een communicatief duwtje in de rug op het moment dat we een project zouden aanvatten zou uiteraard zeer welkom zijn.
Met vriendelijke groet,
Joost Schouppe
voor OpenStreetMap Belgium
OpenStreetMap | Twitter | LinkedIn | Meetup
Meer info:
Over ons project 360° camera: https://lists.openstreetmap.org/pipermail/talk-be/2022-January/011404.html
Onze visie over open straatbeelden: https://openstreetmap.be/nl/2019/09/27/streetview.html