cross-posted from: https://feddit.org/post/2989211
this post was submitted on 19 Sep 2024
310 points (100.0% liked)
Technology
37609 readers
123 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Good and all, but as somebody mentioned on the Masto comments this shouldn't be needed, this is taking an open JSON file and turning it into a proprietary Google-only format so that Organic Maps can import it, that feature should be on the app itself already.
Also as you're uploading that data to a random website you're effectively doxxing yourself as your important addresses likely will be there, your home, your workplace, etc.
Edit: Was mistaken and corrected below, the format IS a standard, not proprietary, in addition the author answered in Masto clarifying that all the conversion happens in the browser without uploading anything. That said, i do insist that the app should support uploading in this geojson format, specially since it's what Google Takeout gives you
Keyhole Markup Language
I understood it was Google-only, great to be mistaken about it. Still, the app should also support that geojson importation format too, there shouldn't be a need for external tools, SPECIALLY since it's what Google Takeout gives you, this very much should be a feature of the app.
Now that this project exists, I'm sure it'd be relatively trivial to implement in the app
I doubt the actual "feature" is much more than a single line that tells GDAL to translate it from one format to the next, so the real thing here is the convenience of having a webpage that provides this special case as a service. Geojson is easy to read in essentially every language now, so this shouldn't have been hard to do even before this website.