osm-search / nominatim-data-analyser-frontend Goto Github PK

One of Polish mappers (heavily involved in address fixing) mentioned that "edit to JOSM" button would be welcomed

The usual zoom controls for zooming in and out would be nice to have. Also I often wish for a button that brings you back to world view.

Layers like 'place nodes close' always have groups of features that belong together. It would be nice to have a visual hint where the other feature is instead of the simple object ID.

https://nominatim.org/qa/#map=2.91/0.00/0.00 links https://github.com/AntoJvlt/Nominatim-Data-Analyser/issues that redirects to https://github.com/AntoJvlt/Nominatim-Data-Analyser/pulls

please come to the "Issues" section of the github repository to discuss this.

Linking issues and mentioning issues in repo with disabled issues seem not intentional

When I zoom into the map by pressing the Shift key and drawing a rectangle on the map with a mouse, the vector layers often don't get loaded correctly. Tore produce

• Start for example with this view: https://nominatim.org/qa/#map=8.71/49.74/15.04&layer=addr_place_and_street
• Press shift and draw a tiny rectangle around the "P" of Praha. The map will zoom in but there are no items displayed.
• Go back to the original page and zoom in by repeatedly clicking at clusters. You will see that there should indeed be items.

I suspect that it happens when I hit a zoom level for which there are no vector tiles defined. Instead of loading the ones for the next lower level, it simply does nothing.

Osmoscope adds URL fragments with current map position and zoom whenever one moves the map, e.g. #map=17.991666666666667/6.8867/52.24745 This makes it easy to share the current view with other users.

I think we need to do something about zooming in when clicking on clusters. I get really odd behaviour at times. Sometimes it zooms out instead of in, sometiles it doesn't zoom at all.

Example of not zooming at all: https://nominatim.org/qa/#map=10.00/35.32/139.91&layer=same_wikidata (try clicking on the large 3-digit number, "172" as of today)

I can't provide an example where it zooms out. I think what happens is that there is a place where there is no tile at the current zoom level, so the cluster item of a lower zoom level is shown instead.

This appears to be a very helpful tool to improve OSM, and catch issues. Is there a way to export data we can use with micro-tasking tools, so local communities/users can review, and hopefully fix them in a more systematic manner?

related to #16

Open https://nominatim.org/qa/#map=18.16/53.70/18.98&layer=addr_street_wrong_name - nothing shown

Open https://nominatim.org/qa/#map=10.89/53.74/19.23&layer=addr_street_wrong_name or zoom out - entry shown

When editing just in my city it would be nice to show all errors at once.

More variety.
No need to check several layers.
No pointless opening of empty layers.
Easier to edit things in area known to me.

It would be nice if the UI allows relative URL names in the global layers.json and each layer.json file. These URLs should then be interpreted as relative to the position of each configuration file.

With this change there would no longer be a need for the Nominatim-Data-Analyser to know about where the data is served when generating its layers.json file. Makes development deployments a tiny bit easier.

Clicking on a cluster to zoom in is a cool feature. Frequently it works well but just as often it doesn't zoom in enough. If I understand the code right, then it zooms in to the zoom level given by the cluster. I wonder if it would work better if the cluster would communicate the bounding box for of the features it contains. The map could then zoom directly to this extent.

The info box has to be closed again every time I visit the site. It would be nice, if it remembered the state, preferably using local storage and not cookies.

The site fails to load when one of the layer description files cannot be found. It would be nice, if it just shows a warning and loads the other layers anyways.

You might encounter some performance issues with some layers if you are using the Firefox browser. Please switch to another browser if this is the case.

What is going on? I see no open issue for that - is it a Firefox bug? Upstream bug? It would be nice to link it so I can at least go there and upvote the issue.

When going to the page, it sometimes shows text place holders at the place of the arrow and cross icons and the layer list has the wrong format. This looks like a race condition when some of the resources takes to long to read. The behaviour is unfortunately not reproducable but I've seen it a couple of times now.

I was about to suggested to add a link to the Nominatim details page for each feature but then I realised that we have a nice JSON API for the details, so we could pull in the information and show it directly in site. This should only be done after an explicit request for the details, not simply when a feature is clicked to save the Nominatim server some bandwidth.

Osmoscope has a direct link to loading an OSM object directly in JSOM or ID. I think that would be useful too have here too.