osmlatvija / osmalyzer Goto Github PK

I am parsing this from website maps, since all banks prominently mark this, but I'm not using to check if OSM elements have the correct tag(s) set.

Explain the icons found on the map in a legend, especially correlator stuff.

Stretch goal would be to allow the legend to toggle issue layers, although not sure how that would work with clusters.

Instead of having a hard-coded file/list - NSI index

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.

• Skeleton
• Wiring
• UI
• Storage

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).

Basically, all the tags and whatnot plus links to common stuff. Currently, you have to open the link to see. This will really bloat the report page though, possibly needing a JS call. Or filter to relevant tags - but then it's a lot of manual hard-coding work.

https://www.rigassatiksme.lv/lv/biletes/bilesu-tirdzniecibas-vietas/bilesu-automati/

Currently, public transport issues are really hard to parse and understand. The problem is that there are so many issues with so many routes and it's all on the same map, but then each issue type is its own map. It's all really complicated though, so not sure what the best approach would be. Perhaps map per route with all issues combined for that route? It needs to get converted to correlator too.

Stuff in data\ folder.

• Embed
• Add container class

Treat like analysis data, i.e. local data?

• Apotheka
• BENU
• Mana Aptieka
• Mēness aptieka
• Euro aptieka
• aptieka 1
• Latvijas aptieka - these are also numbered, which can be used as ref
• Aptieku Aliance - group/brand franchise, seems to list independent ones

Full government list at https://www.zva.gov.lv/aptieku-karte/ although the site is dead at this time - last archived Jan 2022

Open data at https://data.gov.lv/dati/lv/dataset/farmaceitiskas-darbibas-uznemumu-registrs , although it's hosted at https://dati.zva.gov.lv so it's still dead right now...

May be full data is more usable without needing individual lists, although I still probably want per-brand reports or it might be too many. Not sure if it includes irrelevant locations.

Besides regular links, https://relatify.monicz.dev would be useful for missing stops, broken connections, ambiguity and such - really nice visualization and editing. Of course, those issue checks still need to be implemented.

Banks with (wide) physical presence:

• Swedbank
• SEB
• Luminor
• Citadele

Not including: LPB (1 location), RIB (1 location), Signet (1 location), BlueOr (2 locations), Rietumu Banka (1 location), Industra (8 locations)

Data includes their branches and ATMs.

• Virši
• Circle K
• Neste
• Latvijas Propāna gāze
• Gotika auto
• KOOL
• Viada

https://www.tiesas.lv/tiesas/saraksts

• Latvijas Pasts (also has mail boxes)
• Omniva
• DPD
• Venipak
• Itella / Smartpost (also have pickup points, like at Narvessen/petrol stations)

Latvijas Pasts mail boxes have this validation tool https://mapillaryby.github.io/PostboxValidator/latvia_index.html

LP Express in the future planning to install lockers.

Find ways that don't interconnect because they terminate at the edge of an area - parking lot, pedestrian area, etc. This is not really Latvia-specific though. There probably are QA tools for this already. No sure if it's worth it.

Shop websites generally list their individual shop opening hours, which presumably are more or less up to date.

Would need to parse them - I did not parse any when doing #3.

https://www.depozitapunkts.lv/

Problem is not all are actual separate POIs - a rural shop may accept them manually.

Grocery shop networks with many shops:

• Rimi
• Maxima
• Elvi
• LaTS - many are franchised
• top!
• Lidl - unparsable map, remote API with auth
• Mego
• Citro
• Aibe - most are franchised; excluding bars and fuel stations
• Spar
• Vesko

Shops that have many locations, but no website/map - Beta

Currently, all reports are in English. I imagine they could have 2 language version - Latvian and English. Explaining things, especially to new editors, would be clearer. This is a lot of extra work though, given that I haven't even written most stuff in English. I don't think automated tools would help, since the primary reason to explain is accuracy for fairly technical stuff.

https://www.rigaspieminekli.lv

The icon used for multiple issues at the same location is the icon for the first issue and not the combined icon variant - probably need to reuse clustered icons. Would also make sense to just show them as "clustered" if actually just one marker.

I wonder if I can clustered at lower zooms only cluster issues on top of each other - then I can just use that logic. The problem is how do I see popups for the clustered marker like that.

There are a bunch of related ones like shops and banks and transport that can be shown in subgroups.

There is a list at Valsts izglītības informācijas sistēma (VIIS) https://www.viis.gov.lv/registri/iestades

Searching without criteria brings up the full list, paged.

They provide a CSV export, but it doesn't have coordinates/location or IDs.

I can get the "searched" list as JSON from https://www.viis.gov.lv/registri/iestades?search=true&json=true, which gives me nearest page links (basically for UI), which then provide something like https://www.viis.gov.lv/registri/iestades?search=true&json=true&page=3 that I can keep iterating with full data on each page in chunks of 20, which means 110 pages at this time.

I can also get an individual record JSON from an ID at https://www.viis.gov.lv/registri/iestades/25. This is what the website loads when clicking an entry.

Some details:
data._rows has actual "full" data
data._rows.total for count
data._rows.hits are the "search" results
data._rows.hits[0]._source is then the data of each record
notable immediate fields are Name and InstitutionTypeName
each also has data._rows.hits[0]._source.locations
notably these have LAddressType and LStreet and some others but no actual street number, like it will have "LĒDURGAS IELA" and "JŪRMALA" but no number.
I have to get the individual record, which then has data.pamatdati.papildinfo_telpas[0].AddressFullText with usable address. But this means I have to get each record for all 2182 records as of now... which is not feasible.

• Location map correlation
• Handle multi-point objects (e.g. robežzīmes RĪGA)
• Web-scraped map data - current
• API Map data - currently, impossible
• Wikidata items ID list
• Verify tags - heritage, wikidata
• Filter out monuments with known/ignorable names - partly done

Match data to OSM elements based on how well they match and report accordingly. Two main reasons.

UI can show more matches without more false positives. For example, a data item with an address could match an ATM with that address exactly even if it's like 500 meters away. But normally, it would only match that ATM without further data close nearby.

Another example is when a better matching element is further away than some closer but weaker matching element. For example, a cultural monument ID would be a perfect match, while having operator only a good match and only being tagged with heritage a poor match. It should then pick a stronger match rather than closer match.

• Post code analyzing
• Post offices from OSM
• Post offices from LP
• Compare OSM to LP post offices
• Post codes from OSM
• Post codes from LP
• Compare OSM to LP post codes occurrences
• Post code regions from OSM
• Post code regions from LP
• Compare expected to actual regions

Non-grocery shops. Currently, not parsing any yet. Logic would be pretty much identical to #3. Need to compile a list of potentials.

• Pepco

Difficult or no map:

• Drogas - no map, but semi-well-formed address that could be matched

• Fetching a basic list of items based on having some property, like having a known ID, e.g. for cultural monuments
• Expand this list...