Has any one got any advice regarding point descriptions in Magnet field. I typically describe calculated construction points for roadway work with a description that includes the station of the point; however, when importing these points into the data collector Magnet Field basically ignores anything after any punctuation mark . , + - / and the like, this makes it difficult to import points with stationing. I also can't use these characters in any field collected points which throws my whole system for coding linework in civil 3d out, because all of our figure prefixes for linework descriptors use a . to designate linework codes EP.1 BC.1 EP.2 ETC. Very frustrated...
Randy Rain, post: 392829, member: 35 wrote: Has any one got any advice regarding point descriptions in Magnet field. I typically describe calculated construction points for roadway work with a description that includes the station of the point; however, when importing these points into the data collector Magnet Field basically ignores anything after any punctuation mark . , + - / and the like, this makes it difficult to import points with stationing. I also can't use these characters in any field collected points which throws my whole system for coding linework in civil 3d out, because all of our figure prefixes for linework descriptors use a . to designate linework codes EP.1 BC.1 EP.2 ETC. Very frustrated...
When you import extended characters I suggest using trying to set them as notes.
To get your desired line work for codes EP.1 BC.1, you can set the styles in the export and be sure to use the line codes and indexing.
leegreen, post: 392844, member: 2332 wrote: When you import extended characters I suggest using trying to set them as notes.
To get your desired line work for codes EP.1 BC.1, you can set the styles in the export and be sure to use the line codes and indexing.
Thanks Lee I'll give that a try. Do I need an extra column of data in my export for that PNEZDNote?
Randy
We don't use civil 3d but we do use Magnet. Our mapping scheme might be about the same as yours for including the code and note together. Our mapping product allows us to designate a separator between the code and the note. we choose to use a (space). In Magnet we use notes instead of codes which works for us because we don't care about seeing linework in Magnet so our output format is PN,N,E,Z,Note and our note is mappingcode(space)note. It looks like you could use a . (dot) for a separator instead of a space.
i.e. 1,1000000,200000,1000,EP.1 aaaaabbbbbccccetc. Of course using notes prohibits you from using the code library in Magnet which I'm sure Lee would view as counterproductive in the data collection process but it works for us.
