osm-oscar/oscar-web

A simple search engine for OpenStreetMap data

oscar-web's Issues

On lowest zoom level all regions in the viewport should be expanded

Add option to draw geometry instead of markers

Currently markers are drawn. But sometimes it is better to draw the geometry instead of the markers.
We should add an option to do that. Maybe add this to the query as well (as configuration option) so that users can customize their search shortcuts

Add geoJSON download option

Items that are not in a leaf node of the dag are not drawn

Currently items that are not in a leaf node of the dag are not draw. This is unfortunately not so easy to fix since there may be many items that are not in a leaf node. Consider an island with few cities. The cities are leaf nodes but all the other stuff on the island is not in a leaf node.

Get rid of tokenfield

This solves numerous problems.

Init search on defocus

cppscms dead, switch to other framework

Cppcms has no commits since April 2016. We may need to change our framework. Crow seems to be a promising alternative. Need to look into websockets as well.

Transparancy in dag visualization

The background of the visualization of the dag should have a opacity less than 1

Improve build architecture

Currently there is none. Hence most files are large, with bad code quality, no way to easily see what's in a file. This should be fixed.

mpa.js: mapViewChanged takes too long

Currently updating the map is not very asynchronous. It takes way too long to compute a new view. Unfortunately this not going to be easy to turn into an async function. This may only be possible after a larger refactor of the whole code.

Zoom on chromium broken

On chromium zooming skips some levels. Firefox is ok.

Add ability to tell the client that the request was too large

Currently server and client need to have matching configs to ensure correct processing of requests. There should be some way to tell the server that it should generate smaller requests. Maybe a capabilities api would be good aswell.

Region cluster drawn that should not be drawn

Query: barfußpark
Zoom to Hallwangen -> Württemberg cluster with 12 hits stays on the map although items are visible. This should not be the case

Full cqr and simple cqr should be made compatible again

Tracker bug. There are likely many things that need to be done to support this (if this is useful at all)

Add pagination to result tabs

Currently there is no way to load more results into the result list. There should be some way to do this. Though there is the problem of changing result list since the result list depends on the map view. This might create strange paginations.

$geo query has out of bounds coords

Some part of the website produces out of bounds coordinates in the region of 500 lat/lon

@tourism:hotel "new york"

from https://github.com/dbahrdt/oscar-web/blob/4d54325b627203669f38e09aba20b4f0e62266c5/website/template/help.html#L166

 @tourism:hotel "new york"
 List all hotels in New York

but @shop:clothes "Москва" will return 812 results in Russia but also this node in Kazachstan too, something is inaccurate here.

Inaccurate docs?

Click on details item marker should remove item from details view

Limit number of drawn clusters

A human can only process a small number of things at once. For oscar-web the things are the clusters on the map. As a consequence there should be no more than about 5 clusters on the map.

Show children in dag

The "Show children" link should only be visible if no children have been loaded yet

Add option to download all results in zip archive

Using ItemIndex with native encoding results in crashes

There seems to be something wrong with ItemIndexPrivateNative though the good looks correct.

Improve calculation of cluster centers

Maybe we should calculate the center of clusters by using cluster centers of their children. This should improve zoom-consistency since the parent cluster center may be closer to the cluster center of the children.

Dag: One pass is currently no possible if all regions are loaded

Result view broken in Firefox

Clicking on an Item in the results view does not open the detailed information. Tested with FF46

Add point location to be able to add items close to a point to the result

Inspection tab: Add extra detail close button, click on name should zoom to item on map

Mouse over item markers

Dag: Expanding a node should keep that node at the same place

If one clicks on "OnePath" then the whole dag ist refreshed and any translation is discarded. Instead we should translate/scale the new dag such that the old node is at the same coordinates

Polygon creation is broken for triangle

And it should also work if only accept is pressed without finish before

Add clear button to clear current search input

Display problems of large elements

If a large item is highlighted and the map viewport changes considerably it may and does happen that to view returns to a cluster view hence removing the item. That is something that needs to be avoided.

The question is how? Somehow we need know if the use just browses the map or wants to inspect a single element.

Disable clustering for small results

Add routing engine

We currently do not have any kind of routing engine. This might be a nice addition. As a first step it should be possible to do normal routing but at a later stage we may want to do advanced routing taking heights, surrounding and so on into account.

Tagsearch should be part of search input field

Speed-up result list updates

Currently the map and result list updates are quite slow. About 1 msec per item. This is way to slow. This also make the website unusable on older hardware.

Add inspection mode

Add a new display "mode" that allows one to inspect multiple elements at once.
In this mode we want to keep inspected elements on the map.
Maybe we want to disable clustering.

Broken query in tenerife

Broken query: % $item:53357456

Improve marker styles

Use sigma-geosistemas/Leaflet.awesome-markers for markers?

Highlight on click

Clicking on an object on the map does not highlight the item in the result list and vice versa. This seems to be a problem on Firefox.

Tokenfield does a defocus on createtoken which currently iniates a search

Improve cluster icon and item marker selection

Currently it may be the case that in a given cell items are drawn but a cluster icon of a region spanning that cell is drawn as well. This is the case if the cell is part of a region without children and one with children. This should be fixed in favor of the cluster icon. In order to do this the client needs to understand the concept of cells.

Add cluster markers for cells

For regions with many cells that overlap other regions it might be useful to have cluster markers for cells. Consider the region A = {1, 2,3}, B = {1}, C={3}. For regions B and C get cluster markers. Hence we can't add a cluster marker for region A. But there are still items in cell 2.

Top-k tags for query

Replace current usage of taginfo with our own version to retrieve top-k tags in our database

Counts of cluster icons are wrong

The counts of cluster icons that result from clustering of regions are wrong. It's not a good idea to just sum them together

Map objects and result list are not in sync

Sometimes map objects and the result list are not in sync. Clicking on a map object then results in an exception since the result list entry does not exist. Need to investigate when this happens.

Aalen Döner has a lot of results in NRW

The query Aalen Döner has a lot of results in NRW in oscardev. But Aalen is in BW.

No results information for queries without results

Broken query @amenity:post_office vaihingen

On oscardev the following query results in 100% cpu usage:
@ amenity:post_office vaihingen

Link: http://oscardev.fmi.uni-stuttgart.de/?q=%40amenity%3Apost_office%20vaihingen

You have to zoom in to Stuttgart. Then the loading animation appears and never goes away.

Denial of service problems

There are currently many possibilities for denial of service attacks by issuing queries that take very long to compute. We need some way to first filter these queries and at a later stage stop processing queries if they take too long.