Opened 10 years ago
Last modified 9 years ago
#1151 new defect/bug
PlanetExtractor with multiple BBoxes
Reported by: | usul | Owned by: | usul |
---|---|---|---|
Priority: | major | Milestone: | version 0.6.0 |
Component: | tools | Version: | git master |
Severity: | Keywords: | map, osm, extractor, area, www | |
Cc: |
Description (last modified by usul)
Hi, the PlanetExtractor is a essential service in the Navit universe, as it offers the compiled OpenStreetMap? areas for download. It also offers packages for compagnion areas of multiple countries, examples are D-A-CH or Benelux.
As it currently only supports one single BBOX for selection, the returned packages contain a lot of information, that aren't covered by the desired countries. To get some smaller packages that can be faster transfered and that save space on the embedded devices, I suggest to offer cuts with multiple bounding boxes, that touch each other:
Attachments (2)
Change History (8)
Changed 10 years ago by usul
Changed 10 years ago by usul
comment:1 Changed 10 years ago by usul
- Description modified (diff)
- Keywords extractor added; extract removed
comment:2 Changed 10 years ago by usul
- Keywords www added
comment:3 Changed 10 years ago by tryagain
comment:4 Changed 10 years ago by ah be
if you have overlapping boxes each saved as a single osm_XY_Z_.bin file being part of the active mapset, would navit then still be able to calculate a full route?
r
comment:5 Changed 10 years ago by tryagain
Currently, you will have troubles with search and navigation instructions if you have overlapping maps. Routing will work, but would require more resources, compared with the case of one binfile.
This ticket suggests to let user to describe the map region needed, as a set of boxes.
tryagain
comment:6 Changed 9 years ago by ah be
as there are examples of overlapping regions (D-A-CH or Benelux), how are these produced? maybe one can offer some kind of script or so as a first workaround where one adds the top left and bottom right coordinates manually to overcome the issue?
I would suggest to remove requirement to have touching bboxes. They can be overlapping, touching or have no common points at all.
And it would be nice to have planet extractor interface working on default android browser. Maybe switch user-side engine to leaflet?
Update: OpenLayers? drawing samples seem to work pretty well on my mobile. So engine change is not necessary, upgrade to current version of OpenLayers? should be enough.
tryagain.