Currently, we import all data within a radius. This can be a problem if we don't want some objects inside this radius to be shown and they have no city/municipality names in the data. Two options:
1) import all municipalities/cities and save the names in the db for each point. Filter in the UI (like Lipas points work currently)
or
2) limit import by municipality/city. This should be doable in overpass (OSM has the geometries), not so in the case of arcgis objects?
It is not feasible to do the filtering in the tile server call. The polygon in the call would be huge and would make zero sense to transfer all that data in each call.
Currently, we import all data within a radius. This can be a problem if we don't want some objects inside this radius to be shown and they have no city/municipality names in the data. Two options:
1) import all municipalities/cities and save the names in the db for each point. Filter in the UI (like Lipas points work currently) or 2) limit import by municipality/city. This should be doable in overpass (OSM has the geometries), not so in the case of arcgis objects?
It is not feasible to do the filtering in the tile server call. The polygon in the call would be huge and would make zero sense to transfer all that data in each call.