This repository has been archived by the owner on Nov 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: add extra info on importer/updater plans
- Loading branch information
1 parent
fe1170e
commit 1d28344
Showing
2 changed files
with
54 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,47 @@ | ||
# OSM Importer Service | ||
|
||
Import data into a fresh OSM Sanbox instance. | ||
Import data into a fresh OSM Sandbox instance. | ||
|
||
Uses Geofabrik country data, then filters down to the users required BBOX. | ||
Method: | ||
1. User provides BBOX to download data for. | ||
- First we do a simple calculation to get centroid from BBOX. | ||
- https://nominatim.org/release-docs/latest/api/Reverse | ||
2. (Optional) reverse geocode the country name from BBOX area. | ||
3. Download latest country data using GeoFabrik. | ||
4. Filter data using `osmium` BBOX functionality. | ||
5. Import the BBOX data into the sandbox db using `osmosis`. | ||
|
||
> [!NOTE] | ||
> While `osmium` is the most performant and best maintained tool | ||
> for dealing with OSM data, it does not support importing into | ||
> an OSM-type database (dbapi). | ||
> | ||
> It's primary purpose is for importing into an alternative | ||
> PostGIS database for data analysis, using PostGIS representations | ||
> of each geometry (the OSM db does not use PostGIS). | ||
> | ||
> As a result, the only available tool for importing into dbapi | ||
> format is `osmosis`, a now deprecated Java tool. | ||
## Work Modes | ||
|
||
### Option 1: Startup | ||
|
||
- Each osm-sandbox instance is throwaway. | ||
- The user starts sandbox with a bbox, the data is populated. | ||
- The mapping concludes, data is extracted, and the sandbox deleted. | ||
|
||
### Option 2: Triggered | ||
|
||
- We run one osm-sandbox instance. | ||
- The user triggers import for an AOI. | ||
- The data is imported using the workflow above. | ||
|
||
## Updating Data | ||
|
||
See the `updater` section of this repo. | ||
|
||
## Future | ||
|
||
- This is a test service to demo different approaches. | ||
- The end goal is to contribute to developmentseed/osm-seed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters