Latest Contributions by AdamRepsher

‎01-28-2021

That's okay Bruce. Thank you for the extra input.. We already do line-of-sight analysis with a local projected coordinate system for our assessment of future microwave shots - one at a time as they are requested. Right now, I have a little over 350 lines I have to produce from this CSV dataset with coordinates given to us in WGS84 - and I may have to update the data monthly - so I wanted to start this process off in a Data Interop SpatialETL tool right off the bat. In the first steps, I have to create the lines in WGS84 since that is what I am given - unless I am mistaken. I'll get into reprojecting it later. Thanks again! --Adam

‎01-28-2021

@BruceHarold wrote: If you have AGL heights then you'll need a ground surface for any analysis. Sorry for having to ask this @BruceHarold... Would "analysis" include creating these lines - like I am doing right now? If so - what Transformer would I be using and where would I be inserting it? Before the VertexCreators and somehow use a value from it in an Arithmetic Editor for Z... OR Am I writing the Z directly from the AGL that I have - and it will appear correctly above a ground surface in any analysis I want to do with it in the future? Sorry - I am very new to 3D as well as Data Interop.... EDIT - and as a note, I am simply trying to get these lines out of a CSV right now. I have to begin with the Coordinate System given to me to get anywhere.... --Adam

‎01-28-2021

@DanPatterson - Thank you for the education. - I got that part, as @BruceHarold mentioned above. I am trying to complete this task in a SpatialETL tool within Pro's Data Interoperability Extension - not as a one-off tool run.

‎01-28-2021

@BruceHarold - I have Meters Above Ground Level. I may have to add something that gives me the elevation at the points? OR am I getting too deep into my thinking? Would the recorded height be correct above any elevation surface that I would be using?

‎01-28-2021

Hi Everyone, I have a CSV file of microwave paths. Each record has two sets of X, Y and Z to make a line. Z comes in either feet or meters. X and Y are WGS84 - which i defined in the CSV Reader. So far, I think I have figured out how to make just the 2D lines. Use two VertexCreator transformers together, first one configured with the "From" X, Y - and the second with the "To" X, Y. I use the Add Point Mode to step from the first VertexCreator making the original point and then ADDING the next POINT to make a line with the second VertexCreator. In both of those VertexCreators, would I have to do a conversion of either Meters or Feet to Degrees for the Z value since I have defined WGS84 in the reader? Thanks, --Adam

‎01-25-2021

Thank you @BruceHarold ! I am finding that using FME for the first months is like when I started to use tools in ArcGIS Desktop. I know what I want to do - but what does Esri call it??? 🤣 Still strange why the reader is interpreting a field instead of just giving me a value.

‎01-25-2021

After spending a few days with Customer Service, we have found that there is a bug (BUG-000136812) in my specific situation. I will explain: My Portal WebAdaptor within IIS is set up with IWA (Windows Authentication) enabled (using Active Directory for accounts and login) AND Anonymous Authentication DISABLED to utilize Single Sign-On. My customers are not prompted for login. They are authenticated with the credentials they used to log into their machine/domain on our intranet. Workarounds: Enabling Anonymous Authentication on the Portal WebAdaptor. This is not a solution for me as I want my customers to have the Single Sign-On experience. Not use the Tools - FME Options - Web Connections for the Portal Connection. Alternatively: Manually set up the connection in a Writer (or Reader), using Kerbos Authentication. (I have not tried this.) Manually set up the connection in a Writer (or Reader), using NTLM Authentication. This has worked for me. The BUG has already been given a status of Not in Current Production Plan since it is an, "Authentication limitation from a third party component."

‎01-22-2021

Hi, I have been working on a tool to pull an MS Access query and transform it into a Portal Feature Service. Had it working for a week, but now it does not work anymore. There is one specific problem... There are 20 fields that contain a simple 1 or 0 in the Access db. When I export to CSV, all of the data in those fields is either a 1 or a 0 for every record. My Portal Feature Service is ready for those values in each of those integer fields with a domain (1=True, 0=False) . When I first made my Workbench Tool, it worked. I had an Access Reader, VertexCreator, CoordinateSystemSetter, Reprojector, and the Portal Feature Service Writer. Now, for some reason, all of my 1 values are writing as -1 (negative one). I have no idea why. When I look at a table, I see "No" or "-1" now. The 0 (zero) is coming out right, but the 1 is being changed to a -1. I have been tearing this tool apart, building new ones, to no avail. I have found that the field type of all of these 1/0 fields coming out of the MS Access Reader are defined as "[yesno]". When inspecting the data of the reader and each of the Transformers, I see values of "Yes" and "No" for each. Seeing that the 0 is obviously making it into my Feature Service correctly, I thought that I could just open up the writer and in the Value entry for every one of these fields - and use the Arithmetic Editor and say [fieldname]*-1. Hey, 0*-1=0 (no change) and -1*-1=1 (yay, positive one). BUT alas, it said that I had a string calculation error - can't math "No"*-1. So - how is the No being converted to a 0 and the Yes being converted to a -1. (I am seriously confused now...) So I found the AttributeValueMapper and, in one field, mapped "Yes" to 1 and "No" to 0. Ran the tool, and it worked. Well - now I have to format an AttributeValueMapper for another 19 fields???? EDIT - Back in the office, trying to string a number of the AttributeValueMappers together and find that I cannot configure the newly changed value to map to the original field in the next AttributeValueMapper. Can't attach the "_looked_up" field to the correct field in the next one. red represents field I want to pass from first AttributeValueMapper to the next. Can I just use the same field name in the Destination Attribute to string them together? This does not seem right. What am I missing? Thanks, --Adam

‎12-10-2020

I am making a Spatial ETL tool in Pro with the Data Interoperability extension. Sorry for my confusion. Do I still go to their support page?

‎12-10-2020

i'm using FME via Pro.... Same thing?

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by AdamRepsher

Re: Creating Microwave Paths with Z Values

Re: Creating Microwave Paths with Z Values

Re: Creating Microwave Paths with Z Values

Re: Creating Microwave Paths with Z Values

Creating Microwave Paths with Z Values

Re: Value changing

Re: Unauthorized - FME Web Connection Failure

Value changing

Re: Unauthorized - FME Web Connection Failure

Re: Unauthorized - FME Web Connection Failure

GeoMentors