OpenSeaMap Forum

For new registrations: Please create and activate an account. Afterwards send an email to forum.openseamap@gmail.com including a short message and your username to get write access to this forum. Thanks!
Für neue Registrierungen: Bitte erstelle einen neuen Account und schalte ihn frei. Anschließend sende eine kurze Mail mit deinem Nutzernamen an forum.openseamap@gmail.com um Schreibzugriff für dieses Forum zu bekommen. Danke!

You are not logged in.

#1 2017-06-14 12:09:27

mikes
Member
Registered: 2017-03-27
Posts: 2

NGA LoL import

Hi, I saw that the original import of files like
http://msi.nga.mil/MSISiteContent/Stati … b110bk.pdf

(or better yet, http://msi.nga.mil/MSISiteContent/Stati … 110bk.pdf)

I'm not looking to import, rather, I'm looking at the step where "First of all a OSM file is being generated out of PDF data." mentioned on this page

http://wiki.openstreetmap.org/wiki/Open … hts_Import

How does one do this? I don't see any code or executable.

Offline

#2 2017-06-14 13:39:12

malcolmh
Member
From: Hull, UK
Registered: 2012-09-05
Posts: 188

Re: NGA LoL import

This project was abandoned several years ago. It had two major problems: The data extracted from the NGA documents is very inaccurate, which made merging it extremely difficult. Also the import did not comply with the OSM import requirements, which earned OpenSeaMap a bad name.


Malcolm Herring, Developer

Offline

#3 2019-08-27 10:04:59

alta_schwede
Member
Registered: 2017-11-02
Posts: 18

Re: NGA LoL import

Hello malcolmh,

malcolmh wrote:

This project was abandoned several years ago. It had two major problems: The data extracted from the NGA documents is very inaccurate, which made merging it extremely difficult. Also the import did not comply with the OSM import requirements, which earned OpenSeaMap a bad name.

I observed that NGA documents are available as xml files now.
https://msi.nga.mil/MSISiteContent/Stat … Pub110.xml
https://msi.nga.mil/MSISiteContent/Stat … Pub111.xml
https://msi.nga.mil/MSISiteContent/Stat … Pub112.xml
https://msi.nga.mil/MSISiteContent/Stat … Pub113.xml
https://msi.nga.mil/MSISiteContent/Stat … Pub114.xml
https://msi.nga.mil/MSISiteContent/Stat … Pub115.xml
https://msi.nga.mil/MSISiteContent/Stat … Pub116.xml

Data based on this documents seems to be more accurate now.

Sample from LoL 115, name "Megra.", ref=L7048
Position lol: 66.1718055894557, 41.6172222900225
Position osm: 66.1500000,41.6333000 (taken from id-1208588673 / version 1, changeset 20930372)

Sample from LoL 115, name "Nes', on N. entrance point of river.", ref=L7100
Position lol: 66.6737223035826, 44.4855278591381
Position osm: 66.6667000, 44.4833000 (taken from id-1208588734 / version 1, changeset 20930372)

From my point of view we can use the documents:
- for the automated identification of lights which are missing in osm (in minimum to find candidates for manual import)
- for automated detection of lights that which are still present in osm and lol
- for automated detection of lights witch are present in osm but where removed from lol.

Can you make assessment of the xml data and give some feedback?

Offline

Board footer

Powered by FluxBB