Jump to content
GMS, SMS, and WMS User Forum

Kai Li

Members
  • Content Count

    7
  • Joined

  • Last visited

Posts posted by Kai Li

  1. There are two ways to increase resolution when using paving.

    The first applies to regular paving (no scalar size function). To use this add a feature point or arc in the area you want the increased resolution and specify the desired resolution by assigning the refine attribute to the feature point or redistribute the feature arc.

    The second applies to scalar paving. In this method you specify a size function in the form of a scattered data set. When using this method, you can just create a new scatter vertex in the area where resolution is being lost and specify the size in that area to be smaller.

    Sorry for misunderstanding, I'm currently using scalar paving density mode, but the mesh result is not the same as I expected.

    I mean in the picture I attached, the red area should have higher resolution than blue area, but it's not that.

    By the way, I've tried sms 11.0.12 and 11.1.5, and I got the same result.

  2. Issue: When I trying to make a big mesh with paving density mode, some of the regions does not meshed with enough resolution. As you can see the colored background is the contour of scatter value. There is an obvious area where the mesh lose resolution.

    So how can I avoid this? Is it caused by some kind of insufficient iteration or something else? Is there a simple option to correct this issue? Thanks!

    post-12823-0-17121800-1371126590_thumb.p

  3. I have removed the hardwired tolerance for converting CAD data to feature objects. That change is available in the next update (or nightly build).

    We have been working on the projections for version 11.1. If you have steps that cause problems, I would love to get them reported so that you can work with the correct projection specified. This would allow you to use dynamic images and the project on the fly features. I understand that reporting such issues can be a nuisance. We are testing the system ourselves but we appreciate feedback from the community.

    If you can send me a sample shapefile that is not read correctly, we will investigate this issue right away.

    Thank you for your support!

    I'm using geographic wgs84 coordination in projection settings. I'm sorry that the stability problem related to projection is not easy to reproduce, it happend randomly for my understanding until now. I will report it when I found an easy way to reproduce it. I'm just starting to evaluate the new version of SMS v11.1.5. It works much better than before until now.

    For the shapefile which is not displayed correctly, which email should I send the shape file to? I've send it to support@aquaveo.com. I hope you can get it.

  4. You have raised a good question. When I look at this, it appears that objects less than 1.0e-3 are being merged. I will investigate where this tolerance is coming from.

    What projection are you working in?

    I did not use any projection. I can understand that if I use projection, this precision issue may not affect me. But when I set the projection to geographic, SMS does not work well for me, it's easier to crash than no projection is specified.

    By the way, I'm using SMS 10.1.11, and work with scalar paving density mode on large scale.

    I just checked the code and there is a hard coded tolerance for coincident nodes set to 0.0001. As I said, it does not seem to impact feature nodes (ends of arcs), but it will impact stand alone feature points and probably feature vertices on an arc.

    We will have to discuss this to determine if we need to expose this tolerance so the user can set it, remove it, or compute it in some way to be automatic.

    Thank you for identifying this issue.

    You are welcome! Anyway, I passed this issue by converting dxf to shapefile. But another problem is that when I working with shapefile, it is not correctly read sometimes. The current state of shapefile overlayed with previous shapefile edit history. I have to convert it to mapinfo tab file then convert back to avoid this issue. I'm using Quantium Gis Desktop 1.9 to generate shapefile, I have not checked whether it's the same with Arcgis Desktop.

  5. Kai,

    If you are using paving, just point feature points inside the polygon and SMS will create mesh nodes at the feature points. If you make those feature points "refine points" you specify an element size for the elements attached to the point. The resulting mesh tends to be a smoother transition if they are refine points.

    Alan

    Hi Alan,

    Sorry for misunderstanding. I'm not using "paving" mode, I'm using "scalar paving density" mode. But I've tried what you say and it also works for me.

    Thanks!

×
×
  • Create New...