Inroads Decimal Points

Hi

I'm working on a large project with multiple design packages and we are required to read in other's outputs from CAD.

My problem is that the Inroads outputs as CAD files are never more accurate the 3 decimal places which is proving problematic when using these feature strings to generate superelevation lines from other packages.

Iv tried changing it in two places and regenerated my surfaces then output my feature strings again. The only change is after the first 3 decimals it just adds zeros to the level of accuacy i specified. Is there another way to change the accuracy? This is affecting a large number of users, we would all be grateful for your help.

Chaing Microstation Setting:

Inroads Setting Change:

3 Decimals output:

3 Decimal Output (Note length has more than 3):

Version Details:

MicrostationV8i Select series 4 (08.11.09.832)

Inroads V8i Select series 2 (08.11.07.615)

Thanks

David

Parents
  • David, have you checked the precision of the Feature data itself under Feature Properties > List Points to verify whether or not the data is actually 3 places? I'm not experiencing what you are seeing.

     
    Civilly yours,
    The Zen Dude (also known as "Mark")
    Civil Software Guru & Philosopher
    InRoads User since its birth in the 80's
    OpenRoads Documentation / Training / Support
    Zen Engineering, Owner
  • Hi

    Yea iv troubleshoot those quite a bit and only seems to be Inroads V8i Select series 2 (08.11.07.615) related. If i add more decimal places to the precision it merely adds more zeros on the end.If it take a dtm from another company i can output to as many decimals as i want. If they take on my company created its limited to 3 decimals. Even if i run their preferences and IRD i get the same result.

    I thus suspect its a version flaw but am a bit hesitant to upgrade our entire company's installation

  • I just meant here is a screenshot ;-) Nope straight out of corridor modeller no filters or edits at all.

    The problem is not only me or my computer its all users within my company using the same version of Inroads. If i share the same InRoads files with a user from another file and they create a dtm directly from corridor modeller they get all the precision they require.

    Note i can get the accuracy i want from the features but only if displayed at the same time as creating the DTM from corridor modeller. If i come back later and view features they revert back to 3 decimal places.

    If i view a DTM created by someone outside my company i have no problems getting more than 3 decimal places.

  • I am seeing the same problem as you are with Power InRoads V08.11.07.615.  I've tried all the things you have mentioned and have not found a solution.  Has anyone else found a solution to this?  What I have noticed is that creating a surface with roadway modeler it rounds the features accuracy to 3 decimals.  I am able to edit the features afterwards, but all of the features have already been rounded to 3 decimals.

  • Hi

    We did not find a solution to the problem. We tried using completely different xin files and seeds. I'm not sure where the preference that overrides this precision comes from. We have just had to deal with the inaccuracy of our design.

  • Thanks for the reply.  One thing we just noted is that while creating surfaces with Roadway Designer having the settings turned on under "Densify using Chord Height Tolerance", "Horizontal Curves", and "Vertical Curves" forces the program, in our case, to round the coordinates (n,e,elev) to three decimals when it creates the surface.  Without those options clicked off the surface was created without the coordinates being rounded.  We also tried unchecking those same options and instead added horizontal and vertical event points to have transverse features placed in horizontal and vertical curves.  This way we could have more points in the model without using the densify option.  Unfortunately it worked until some point.  We eventually had to eliminate our vertical event points.  I am guessing somewhere there is a threshold (maybe file size or number of points/traingles) before it is automatically rounding the coordinates.  For now we found a semi way around it, but I am not sure how well this will work on larger models.

  • Hi Arrell

    It interesting that you highlight threshold. I picked up the same issue and tried to look at increasing the cash size for MicroStation. Thought its an internal memory issue. This also did not make difference in the number of points that we can read.

    Senior Highway Design

    ZUTARI SOUTH AFRICA & AURECON

Reply Children
No Data