search

OSMLatvija / Osmalyzer

Parsing OSM data in Latvia against various data sources
https://osmlatvija.github.io/Osmalyzer/
GNU General Public License v3.0
2 stars 1 forks source link

Manually tag problems as resolved #5

Open HellMapGoesCoding opened 7 months ago

HellMapGoesCoding commented 7 months ago

Let user manually mark a problem as resolved when they know it's not actually a problem with OSM, but with data or data interpretation. This way confirmed "problems" don't report as problems on the map and clutter the view.

For storage, current plan is something like Google Spreadsheets.

UI will have to be JavaScript (github.io is static pages, so cannot do anything in backend).

markalex2209 commented 2 weeks ago

I started working on this here: https://github.com/markalex2209/Osmalyzer/tree/manual-resolution-of-issues For now everything is in very primitive stage, but I think something should get out of it in a couple days. My vision is to have this all completely in JS (basically overriding error points on map with alternative status)

But I have some issues with the vision for storage: I don't imagine working with google spreadsheets very pleasant from API standpoint. Have you considered any alternatives for storage? Maybe something capable of storing (and allowing editing) JSON file? Or maybe OsmLatvija has somewhere S3 for some similar needs?

HellMapGoesCoding commented 2 weeks ago

Hmm. Yeah, I have no idea how you will handle storage. That is basically the biggest problem here. OSM Latvia is just some repos, it's not like an official organization or anything. We don't have any dedicated hosting or paid plan anywhere. Google Spreadsheets was just an example of what could be used (I actually have no idea what their TOS says). I don't imagine it being nice to work with either. So alternatives are fine. The issue might be giving JS free access to it - after all, how are you going to ensure it's not just storing some API keys or whatever in JS code? There is not backend for github.io, so there's no way to "hide" anything. This means the user has to log in if we don't want this to be easily abusable. But now it's a massive can of worms... I really don't know. This hasn't been a priority for me, because it's a lot of work and unanswered questions.