@BitSound @openstreetmap
There is no real reason to break things up block by block unless the blocks have unique names or something. It's also a pain to edit when the areas have been glued to the roads.
So yeah, leave them big.
@BitSound @openstreetmap
There is no real reason to break things up block by block unless the blocks have unique names or something. It's also a pain to edit when the areas have been glued to the roads.
So yeah, leave them big.
Breaking up roads for turn restrictions, changes in the number of lanes etc is perfectly fine.
I've always found it a bit silly to break up roundabouts for route relations, but not everything supports leaving them intact.
Don't copy from maps you don't have permission to use.
https://wiki.openstreetmap.org/wiki/Copyright#Proprietary_data
@jaxxed @vatlark @openstreetmap
Very slim. But their privacy policies are online if you're concerned.
You free labour all goes to the OpenStreetMap database licensed under the Open DataBase License.
@RealFknNito @vatlark @openstreetmap
It caused a lot of fake stuff to be added to OSM even though its update frequency was slow enough that very little of the fake stuff actually made it into Pokemon Go.
I think it did bring in a few good mappers too though so it wasn't all bad.
@Danitos @AngryCommieKender @openstreetmap
IIRC that was pulled out of the app into a separate companion app (StreetMeasure) ages ago.
F-Droid is complaining about "non-changeable or non-free network service".
It doesn't seem to say _which_ network service this is, which I think is quite scummy behaviour TBH.
@stiephelando @vatlark @openstreetmap
If a question type gets tedious you can disable that "quest" in the settings.
@possiblylinux127 Well no, it's entertainment. You don't get many FOSS novels either, not that are worth reading at least.
@MigratingtoLemmy @101 @openstreetmap
No, this is against Google TOS and OpenStreetMap policy on data sources and the Data Working Group will step in and block any accounts doing this to protect the project as a whole.