View Full Version : Problem creating .emp
So, just for fun I grabbed some SRTM data and started in trying to make a map of the Pyongyang area in quadrangle lower left N38 E127. I converted the data using MicroDEM and imported it into an .xdm with no difficulties.
When I set about making the emp, I entered the following parameters, which I believe are accurate:
457200 -17
136797 24.25
3800
3200
2000 CJ DJ
2400 CH CJ
When the choose bitmap comes up, there is no selection shown, although the terrain relief is displayed more or less as expected. If I click OK, it generates nonsense into the .emp.
If I do click on the choose, it then shows the map outline, and will properly generate an .emp and the bitmaps. That won't be accurate, of course, but it does work.
Am I doing something obviously wrong?
Thanks,
--- Kevin
Pat Proctor
21 Oct 04, 10:15
If you do not see a "choose" square when the selection window comes up, it is because the area you have specified is not in, or not completely in, the area of the xdm.
The formula for the latitude and longitude is:
((((60 * degrees) + minutes) * 60) + SECONDS)
East is positive, west is negative.
North is positive, south is negative.
38 E corresponds to 136800, 167 N corresponds to 457200.
So your longitude is less than the lowest latitude on your DEM.
If you do not see a "choose" square when the selection window comes up, it is because the area you have specified is not in, or not completely in, the area of the xdm.
So your longitude is less than the lowest latitude on your DEM.
Sorry, I typed in the wrong numbers when I was posting. Those are actually the "true" lower left corner of the whole quadrangle. I was actually entering:
457739 -17
137597 24.25
3800
3200
2000 CJ DJ
2400 CH CJ
These numbers, as far as I can tell, are inside the quad.
I just did it again, to make sure I didn't brain fart the same as when I posted. Those numbers don't show a choose rectangle.
Thanks,
--- Kevin
Pat Proctor
21 Oct 04, 20:41
What version of MicroDEM are you using. It may, very well be that the lat-long coordinates are not being transfered during the translation, or that the DEM you started with is mis-labeled.
Try loading the DEM in MicroDEM and checking the LL coordinates manually. Do they show 38N, 127E?
I appologize in advance if I am insulting your intelligence, but also ensure that the bigger number is in the longitude. It is an easy mistake to make.
It might, also be that, because this is too close to one edge, the rotation angle throws a corner off of the map. You might try picking a lower-left a couple arc-minutes and/or arc-seconds closer to the middle of the map.
Barring all of that, send me a DEM or XDM and I will check it out myself.
What version of MicroDEM are you using. Try loading the DEM in MicroDEM and checking the LL coordinates manually. Do they show 38N, 127E?
Version 8.0 (latest), and yes.
I appologize in advance if I am insulting your intelligence, but also ensure that the bigger number is in the longitude. It is an easy mistake to make.
I did make that mistake at one point. But I caught it.
It might, also be that, because this is too close to one edge, the rotation angle throws a corner off of the map. You might try picking a lower-left a couple arc-minutes and/or arc-seconds closer to the middle of the map.
No, I tried a variety of corner points, but no dice.
Barring all of that, send me a DEM or XDM and I will check it out myself.
Sent via email.
Thanks,
--- Kevin
Pat Proctor
22 Oct 04, 13:34
I got it. I will check it out.
Pat Proctor
20 Nov 04, 13:41
Kevin,
Sorry it took so long to get back to you on this.
There is something wrong with the DEM converter you are using. It is not saving the DEM in USGS standard format (a common problem with this format in general).
I have recreated the XDM for Pyongyang. This one will work correctly:
http://www.prosimco.com/uploads/pyongyang2.zip
I have also uploaded Petmar's Trilobyte DEM converter (shareware).
http://www.prosimco.com/uploads/demcon.zip
This version IS compliant with the USGS standard.
There is something wrong with the DEM converter you are using. It is not saving the DEM in USGS standard format (a common problem with this format in general).
Thanks for fixing the xdm.
What exactly does ATF require that MicroDEM 8 isn't doing? Other DEM import programs don't seem to have any difficulty with its output, including the older one you uploaded just now.
I have also uploaded Petmar's Trilobyte DEM converter (shareware).
Unfortunately, that one doesn't seem to understand SRTM. Trying to load SRTM with MicroDEM, save to DEM, reload with this one and save again and then converting to XDM now results in all missing data.
--- Kevin
Pat Proctor
22 Nov 04, 18:53
I don't know. There is simply too much data for me to go through, item by item, and figure out. What I do know is that Petmar Trilobyte converter is free, and it works 100% of the time.
I am not trying to be a smart ass, but I was reluctant to create the Power Toolkit in the first place, because the map maker is buggy and fickle. It was only the overwhelming desire of ATF fans that caused me to change my mind.
Perhaps I should seek permission from Petmar to ship their converter with future ATF products...
Unfortunately, that one doesn't seem to understand SRTM. Trying to load SRTM with MicroDEM, save to DEM, reload with this one and save again and then converting to XDM now results in all missing data.
I am not sure what you mean here. I took your DEM, I assume created from an SRTM, and used "Export|DEM" from Petmare Trilobyte converter to create an ATF-friendly USGS DEM, that I then turned into the XDM I upload. It worked perfectly, the first time.
What I do know is that Petmar Trilobyte converter is free, and it works 100% of the time.
MicroDEM *is* Petmar Trilobites software. DEMConvert is merely a subset of MicroDEM. I'm just using the latest version of that software. Apparently, the ATF code has some dependency on some quirk of the specific version of DEMConvert that you happen to use. Duly noted. Sounds like a FAQ.
But I wouldn't phrase it that these other DEMs are "not USGS compliant". "Not ATF compliant" is how I'd put it.
I'm not sure what happened with the empty XDM. Perhaps I messed something else up. I'll try again later.
--- Kevin
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.