#Orbital and #Suborbital Launch Sites of the World 2025 https://brycetech.com/reports/report-documents/Bryce_Launch_Sites_2025.pdf by #BryceTech https://brycetech.com/reports
In #OpenStreetMap* 
https://taginfo.openstreetmap.org/search?q=spaceport#values
*data used by #OsmAnd https://f-droid.org/en/packages/net.osmand.plus/index.html, https://industry.openmaps.space or #Marble https://marble.kde.org (and many others)
@Nagaram on #fdroid there is #SherpaTTS. I use it with #OsmAnd .
I never had the need for other usecases.
Hvilken skattekiste det er at kigge på kort. Jeg så nogle farveforskelle på naboens mark i luftfoto i #osmand som viste at uanset hvor meget landmændene gør for at dræne og slette alle forskelle, så findes vandløb og moser stadig lige under overfladen. Her er to ortofotos og et højt og et lavt målebordsblad (ca. 1865 og fra starten af 1900). Gå selv på opdagelse i https://dataforsyningen.dk/map/3577 og https://dataforsyningen.dk/map/4519 og alle de andre.
@colinstu no, the #Enshittificaton is on purpose, as #Google microtargets you specifically to trigger you into doing unpaid labour for them!
@VTDARKSIM
maybe you want to give #osmand a chance?
Let's make #FOSSfriday a weekly thing!
I'm currently excited about #OSMAnd which is an #OpenStreetMap Android app that is great for #bicycling navigation - way better than let's say Google Maps!
@trailspotting
We'll see. I've never used #OrganicMaps because I was using #OsmAnd~ and then I directly switched to #CoMaps.
Do #OrganicMaps and #CoMaps have the same features? Or they are independent one from the other now?
I don't know much about this topic, so pls tell me if you do.
#Waydroid could be a stopgap.
What's funny is that android is so bloated (12gb of system files), that running waydroid within pmOS takes less storage space.
#OSMand seemed impressively responsive on waydroid.
But the RAM usage of all the android components is huge. Still useable, but huge. I saw memory usage shoot from 0.8GB to 2.5GB
Did you know? #Denmark has over 3,700 shelters (shelter_type=lean_to) mapped in #OpenStreetMap!
Many of these are found in peaceful, scenic spots. Together with numerous primitive campsites, they make up for the fact that we don’t have the same Allemandsret (Freedom to roam) as our Nordic neighbors.
Want to find them while out and about? Apps like #OsmAnd (using OpenStreetMap-data) make it super easy to explore and navigate to these (usually free) shelters and tent spots.
The routing profile is not built-in, but #OsmAnd is capable of importing custom routing profiles.
Check this out, to get you started: https://github.com/LorenzoStucchi/Wheelchair-OsmAnd
Do you know that with #OpenStreetMap data, #wheelchair navigation is possible in the #OsmAnd app?
Another tool that can help enrich wheelchair access data. is https://wheelmap.org, which is an easy-to-use thematic editor, though you can use always use your favorite editor.
@iwmm Grundsätzlich finde ich die Funktion von OsmAnd ganz gut und relativ fortgeschritten, man muss sich aber mit den Einstellungen & Co. deutlich mehr beschäftigen als bei Komoot. Auch das Preismodell ist fair. Was mich stört, sind eine ganze Reihe Bugs bei der Routenplanung, zum Beispiel wird die Anzeige manchmal erst aktualisiert, wenn man die App beendet und wieder startet. Absolutes No-Go sind aber die unfassbar dämlichen und falschen Antworten von deren KI auf sorgfältige Reports #OsmAnd
Guide on how to create a quick action in #OsmAnd
https://bf5.eu/post/osm/how-to-quick-map-with-osmand/
This may save time between hot-swapping among StreetComplete and iD.
And just the ALPRs with orientation info from deflock.me/map, showing pretty extensive coverage of all the ways into the region via 24 ALPRs, most of which are Flock devices (a few Axis ALPRs are there, too).
Aaaand now I've fleshed out the data in the map with proper tags.
Overpass-turbo query here: https://overpass-turbo.eu/s/26uS
@barefootstache @philip For mapping out the surveillance items specifically, I've been working with DeFlock, which unfortunately only does its work inside of Discord :( The tagging schema is evolving, but has largely coalesced around something like this for Flock devices:
```
camera:mount=pole
camera:type=fixed
direction=150
electricity=solar
man_made=surveillance
manufacturer=Flock Safety
manufacturer:wikidata=Q108485435
surveillance=outdoor
surveillance:type=ALPR
surveillance:zone=traffic
```
The `electricity` key can take either `solar` or `grid` as values. `surveillance:type` key's value is either `ALPR` or `gunshot_detector`, depending on the device. `surveillance:zone` key's value is typically either `traffic` or `parking`, though `entrance` can sometimes be relevant (e.g., ALPRs pointed at the gated entrances to apartment complexes).
Additional tags that are sometimes included are the `operator` and `operator:wikidata` tags. Typically, if a public info request is successfully made, it'll say who leases the cameras and other devices from Flock, and that becomes the `operator` (typically a police department). Or, if a particular entity is known to use Flock devices, such as Home Depot --- they use them across at least some of their stores' parking lots --- then that would become the operator. Ultimately though, most operators end up sharing their data with others, so who the specific operator is isn't that pertinent IMHO.
I don't think anything has been added to the OSM wiki though. Maybe I should get this info on there, since there, it will outlast any ephemeral chatter in a Discord server.
Actually, there is some guidance for Flock in Richmond, Virginia:
https://wiki.openstreetmap.org/wiki/Richmond,_Virginia/Tags#Flock_Safety
Might introduce a dedicated page to the wiki though, to get/keep everyone on the same page.
As for workflow:
1. Pick an area to survey. I do #GigWork #DoorDash, so I drive all over the place regularly. When I see a Flock device, I note the area down for follow-up survey.
2. Drive around the area, recording path with #OsmAnd (for GPX files).
3. Upon seeing a device, find a safe place to pull over.
4. Use #StreetComplete to add an initial `surveillance` (shot spotters) or `surveillance camera` (ALPRs) thing.
5. Add a note via StreetComplete with more info on the device, including orientation, and a picture if possible.
6. Go home.
7. Pull up iD, and go through my notes, fleshing out the tags on all the surveillance nodes I added early via StreetComplete.
It all depends on the level of details you want to add.
I start off with #ArmChairMapping and once have grabbed most major objects like buildings and landcover. Then I go to the streets to add more details like the values of the buildings and/or addresses.
#StreetComplete permits notes, though prefer to use #OsmAnd instead where I have created a set of quick actions to speed up the process. #EveryDoor in another favorite under #MicroMapping.
Ho Lee Crap this region is crawling with surveillance. I mean, I kinda figured. It has a reputation as being a "bad" part of town. But damn. Dozens of Flock shot spotters, and at least a dozen ALPRs. Working on adding details to the map now. Used #StreetComplete for initial survey. Been using it often enough that I might try out adding a flow for Surveillance Things specifically rather than having to tack on notes and go back in via iD to flesh things out.
re 
