[Imports] Importing GEOnet Names Server Data of Sudan
Saeed Hubaishan سعيد حبيشان
hubaishan at outlook.sa
Mon May 3 14:06:47 UTC 2021
على ٢١/٠٩/٤٢ ٠١:٥٤ م، كتب Marc_marc:
> GNS:id : I don't see which object couldn't be matched next time without
> this reference, especially since an import must anyway conflate with
> existing objects, even if they don't have a ref, to avoid any duplication
> and it's more common to put ref into ref: namespace
Do you prefer the Key to change to "ref:GNS"?
but GNS:id is used with most GNS imports.
> GNS:dsg_code : i didn't understand the usecase to have it in osm,
> it's look like garbahe for osm user.
> GNS:dsg_name -> name key ?
GNS:dsg_code is the code of the feature and GNS:dsg_name is the name of the feature. Most of codes are hard to understand but the name is clearer.
At least one of (GNS:dsg_code and GNS:dsg_name) must be included for
1- To easy revise and fix the import if there are import tag error.
2- Some GNS features currently has not exact OSM Equivalent some one may
get more feature describe on "GNS:dsg_name" tag. In the future OSM may
have more Equivalent feature so this can be helpful.
This is summary of GNS features:
"Administrative Boundary Features" 20
"Hydrographic Features" 137
"Area Features" 47
"Populated Place Features" 15
"Road / Railroad Features" 24
"Spot Features" 251
"Hypsographic Features " 96
"Undersea Features" 72
"Vegetation Features" 18
there are some diffirent GNS features has one OSM Equivalent but with
"GNS:dsg_name" user have more information about the feature.
3- If some OSM features added after the importing make more equivalence
to GNS feature, these tag make changing to the new feature easier.
More information about the Imports