Jump to content
GMS, SMS, and WMS User Forum

jiangtao

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jiangtao

  • Rank
    Member
  1. Hi Rusty, Thanks very much for your reply. I've just contacted tech support and emailed them the files with multiple coverage in map module. The problem with scatter data could easily be reproduced so I didn't include a sample. As you stated "If two entities are at the same elevations, the object displayed last will generally win out.", I would intuitively expect that when I select whichever scatter dataset to be the active display, all points in this dataset would show up with the active display color instead of being masked out. Many thanks for your help! Regards, Jiangtao
  2. Hi, I found that if you open more than one scatter dataset, when you select the following datasets as the active scatter set, the points in following datasets that are identical to points in the first dataset will be masked out by the inactive display. I also have a problem with the active and inactive display problem in the map module. I have four coverages in the map module and one of them will never show up as inactive coverage. Anybody else had this problem? Thanks, Jiangtao
  3. Hi Rusty, Thanks for your reply. No. The coastline is the only data I have loaded into SMS. We're not trying to use that high-resolution coastline to directly generate mesh. It would be just used to define the accurate water-land interface later on. What I'm trying to do here is to convert the original shape file to map file and do the necessary cleaning (such as connecting segments, deleting false arcs etc) in SMS. I have just emailed the tech support my coastline file. Hope that can help you to figure out the speed difference between SMS10.0 and 9.2 and improve the future release. At the same time, do you know if it's technically possible for our SMS10.0 license key to also work with our SMS9.2? Many thanks for your help. Jiangtao PS. I just got the email notification saying that my email to the tech support couldn't de delivered because of its size. I'll try to figure out another way to hand them the file.
  4. Hi, As I have described in another post here: I have experienced a lot of difficulties working with a high-resolution coastline in SMS map module. It takes a long time to load the coastline and any operation, such as zoom in/out, select a node/arc also take a long time to excute. But what I discoved just now by accident was that the same procedures worked at least 10-time faster in my previous version of SMS 9.2! What's going on? I also checked to see if that's because I was running SMS9.2 in demo mode (my license key only works with SMS10.0). I tried to do the same things in SMS10.0 demo mode too but they were the same slow. Anyone else noticed the difference? Thanks, Jiangtao
  5. FYI, we just upgraded the video card in my current PC hoping that it would help with the super slow display problem when working with our high resolution coastline file. Unfortunately, I haven't observed a noticable speedup. Seems that CPU is the bottle neck here. For every single move in SMS, the cpu usage will be maxed out because SMS only run on one processor. In that case, nothing can be done on the users' end because how much faster CPU can get (I have duo 3.4Ghz now)? But I still don't quite get it, why would a simple zoom in/out, or selecting a node/arc would be so CPU demanding? Any hints?
  6. Well. I was trying to see if I can convert data between map and other formats, for example, matlab format etc. We have an old program doing that which doesn't work for writing out map file now, I guess because the map file format changed? Any lead would be appreciated.
  7. I'm also interested in getting more information on the optimal system configuration for SMS. I've had a lot of difficulties working with the coastline in map module recently. I have a high-resolution coastlline which has over 500,000 points/(vertices+nodes). It takes a long time to load the map into SMS and every single step, like zoom in/out, changing operations (from zoom to select nodes etc) can take several minutes. My current computer has dual 3.4GHz CPU, 4G RAM and 256MB ATI Video card. I wonder what resource is limiting the process more? It seems that in the mesh module I'm able to work with a grid with more than 300,000 nodes, 500,000 elements quite efficiently. I did have to work piece by piece to generate the grid though. So I'm kind of puzzled why it was so slow in the map module to deal with a 500,000-point coastline. We're currently looking into buying a new computer because of the difficulties we experienced. Would that help with both processes, i.e. working with coastline in map module and mesh generating in mesh module (hopefully working with fewer pieces)? Would dual CPU (3.4GHz) with 8G ram be sufficient for the purpose? What about vedio card?
  8. Thanks, John. I actually did what you suggested. The problem is that I didn't figure out all the fields in the file. For example: in the arcs section, I don't know what DISTNODE, NODETYPE, MERGED are and what the values following them mean. And that's only for the generic type. If it's defined as, say adcirc type, there are more fields that I don't have a clue. Is there any document on this? Thanks, Jiangtao
  9. Thanks, John. I just sent an email with the sample shape file to tech support. -Jiangtao
  10. When I tried to convert a shape file to feature objects in SMS I found that some additional lines not in the original shape file could show up. Anybody else has experienced this problem? What could have caused it? Thanks, Jiangtao
  11. Hi, I wonder if there is a way that you can select certain node/arc in map module by their IDs for problem checking? Also where can I find the format for map files? Thanks a lot, Jiangtao
×
×
  • Create New...