Panorama 5m FME Male/SMA Male Antenna Cable
$22.99
Mfg # C23FP-5SP
CDW # 5083987
| UNSPSC 26121606
Know your gear
The Panorama Cable is designed for use with various Panorama devices. It comes with a FME male connector and a SMA male connector for efficient connectivity. This cable features a length of 5m for convenient usage.
Add to Compare
Enhance your purchase
Panorama 5m FME Male/SMA Male Antenna Cable is rated
4.70 out of
5 by
3.
Rated 5 out of
5 by
reviewer2626457 from
Intuitive with great integrations and excellent spatial features
What is our primary use case?
Primary use cases include: creating automatic data flow processes, enabling users to self-serve their data needs, and handling real-time events. It is a fault-tolerant, scalable multi-tier solution, so it has backup facilities. One can use a multi-server setup with a database. We can download data, start processes, update databases, send messages, tweets, push notifications, and almost everything in a few clicks. With spatial data, it has almost no competitors.
How has it helped my organization?
FME handles all ETL processes, refreshes data, and produces reports and dashboards.
Automated data enrichment and analysis using the setups we use are great for just doing the jobs by hand.
We easily share data and workspaces among users in a secure setup with managed authorizations, connected to Active Directory.
There is even a hosted solution, where one does not have to worry about having the appropriate server environment. All that is required is selecting a platform version, data storage region, performance type, and need for data space and ignite!
What is most valuable?
All spatial features are unrivaled, and the possibility to execute them based on a scheduled trigger, manual, e-mail, Websocket, tweet, file/directory change or virtually any trigger is most valuable.
The integration between FME Flow and FME Form is super as is its integration with scripting like Python is superb.
It is a really intuitive product; just type anything in the canvas and methods for processing pop up. Data is processed intelligently, though for optimal dataflow some human thinking has to be done.
What needs improvement?
Improvements could be made to mapping presentations. Though there are functions available for this, it is a complex and broad area that is not covered to the fullest extent. There is a presentation module, however, it is in no way a real GIS.
For now, there is the FME Forms product to enter detailed data mapping setups, which is a great tool. However, having an online medium for this would be great. In a future version, it would be great to have a website where you can log in and create your workspace to do the detailed data processing and publish it to the FME Flow environment where it can be used to participate in the general data processing setups.
For how long have I used the solution?
I've been using FME Flow, a.k.a. FME Server, now for 15 years.
What do I think about the stability of the solution?
I never got a blue page, however, that might be on my side.
What do I think about the scalability of the solution?
Performance is where you put the computational power. Do not drag large datasets over the internet if you just need the total number of addresses in a country.
Which solution did I use previously and why did I switch?
I did some work with Azure Functions, Databricks, and AWS Web Services. It is just for historical and pricing reasons that I did not switch to AWS or Azure platforms.
What's my experience with pricing, setup cost, and licensing?
FME is the nicer and cheaper platform that supports all the functions of larger platforms.
Which other solutions did I evaluate?
I did not evaluate other options. I rolled in and fell in love with the platform.
Which deployment model are you using for this solution?
Private Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-09-28T00:00:00-04:00
Rated 5 out of
5 by
Alan Bloor from
Great for handling large volumes of data, but it is priced a bit high
What is our primary use case?
I use two versions currently. The latest version that's just come out and the 2022 versions.
Currently, I'm using the solution to pull APC data using the data collection. I've got to transform the data massively to make it usable, so I use FME for huge amounts of transformation and to put it into ArcGIS Enterprise. FME is a ZTL as well, specifically the "L" bit. I also use FME for a lot of analysis where we want it quick and efficient on big datasets that ArcGIS Pro is unrealistic to do on.
I also use FME, where if somebody sends me a spreadsheet where, for example, we would need to get everything in capital letters, it's quicker for me to capitalize everything in FME Workbench than it is in Excel.
I can use FME for just about everything, from logging processes to looking at file structures, what's changed in file structures, what people are doing, or what they've updated. It's not just need-to-know. It's a massive piece of software that's also coded in Python. What FME can't do, I then write in Python.
I can make FME pull in ArcPy, which means that for every single thing that ArcGIS Pro can do, I can make FME. It's much bigger than the box.
What is most valuable?
When I do coding, I think about every single function. Some of these functions can be very elementary, like doing a substring or some capitalization. But FME removes all that coding because it's a transformer, so the time to develop an application to get to a point where you're producing results is decreased massively. It used to take weeks and months to develop software, and now I can use something like FME, and within one day, we get results. We can look at and validate data. We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else.
What needs improvement?
The one thing that always appears in the community is the ability to make really easy loops to loop through data efficiently. That needs to be added at some point. There must be a technical or commercial reason why it has not been done in FME yet, but many people ask for it, and it just doesn't appear. We can do it, but we have to create a child workbench to do it.
For how long have I used the solution?
I've used FME for more than five years.
What do I think about the stability of the solution?
I've used the 2022 and 2023 versions because of the application's stability, not the tools. What FME has done is they've bought out 2023 and update the backend code for the interface, and it's crap. The update was more about making the presentation pretty, similar to what they did with Office or ArcMap to ArcGIS Pro. I use 2022 when I want the interface to remain stable over a long period and 2023 when I want to see the updates and see if anything could have been changed.
The stability with the 2022 version is really good, and I rate it an eight out of ten. The stability with the 2023 version is probably a five out of ten. The stability depends on the version used.
What do I think about the scalability of the solution?
FME's scalability is fantastic. I rate it a ten out of ten. It's one of the most useful pieces of software I've ever encountered in my entire life.
More than ten users use it in my organization.
How was the initial setup?
FME workbench is dead easy to set up. It cannot be easier. Double-click on something and go, "Next, next, next." And then it's done.
Licensing is so straightforward if you've got a trial license or pay for it. You just type it in, and it authenticates on the server.
FME server, on the other hand, comes in two types: FME Cloud, with FME server inside, or FME server, which is on-premises. They are straightforward, provided you've got an IT department to set up the servers correctly in the first place.
FME Workbench took three minutes to deploy. FME server took a morning. FME Cloud is all automated. We just need to sign up, type in our details, and add a credit card, and It builds the server for us. The whole process takes under one hour.
What was our ROI?
We have seen an ROI, but it doesn't justify the price.
What's my experience with pricing, setup cost, and licensing?
The pricing is really bad. Last year, they rebranded the whole pricing structure. It used to be moderately priced at about £400 per user per year. Now they've changed the whole thing, and it's expensive, at ten times the price. The pricing is based on your company size, turnover, and all these different things to do with the company.
I had a conversation in London. I spoke to an FME guy from Canada at a conference and said it was horrendous. FME Server used to cost £10,000; now it can cost over £100,000. It's worth the money, but the rebrand is just killing them.
What other advice do I have?
I rate FME a seven out of ten because of the price.
The number of types of data you can save and read is growing massively. Similarly, the solution is improving at working with APIs, downloading data from remote sources much more efficiently. There are more transformers, but these are aimed at data types that don't apply to me.
Before choosing FME, immediately look into licensing and costs before you go down the road of trials and becoming dependent on the trial. When you finish that trial, you'll find yourself semi-dependent on software. Get the costs first because it's a shock.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-11-13T00:00:00-05:00
Rated 5 out of
5 by
reviewer1381977 from
Easy to debug, helpful graphical user interface, and useful assessing of processed data
What is our primary use case?
We use FME in geographical data analysis where a lot of sources or processes are involved.
What is most valuable?
The most valuable feature of FME is the graphical user interface. There is nothing better. It is very easy to debug because you can see all steps where there are failures. Overall the software is easy to optimize a process.
There's a map in the graphical user interface that helps in assessing whether you are processing data correctly in the geographical transformations.
What needs improvement?
FME can improve the geographical transformation. I've had some problems with the geographical transformations, but it's probably mostly because I'm not the most skilled geographer in-house. The solution requires some in-depth knowledge to perform some functions.
In the next release, it would be useful to have recommendations on how and how not to use the different functions. It would be helpful because this is a tool we only use once in a while and you have to wrap your mind around this tool quickly it can be difficult.
For how long have I used the solution?
I have been using FME for proximately two years.
What do I think about the stability of the solution?
FME is a highly stable solution.
What do I think about the scalability of the solution?
We are using FME for batch processes. We have not fully tested the capabilities, but for our usage, it has scaled well.
How are customer service and support?
The support from FME was very good. The support we received was personalized.
I rate the support from FME a five out of five.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have used ArcGIS Pro and FME is a bit easier to use. ArcGIS Pro takes a lot more experience and expertise to use and we still use it for more complex data processing tasks.
How was the initial setup?
The initial setup of FME is not for beginners. The installation of the license server locally can be a challenge. However, fortunately, it's very similar to the on-premise installation of license servers from ArcGIS Pro which we have used.
The full process of implementing FME took a couple of days because we had to involve the national IT unit.
I rate the initial setup of FME a five out of ten.
What about the implementation team?
FME can be managed by one person. I was an IT manager handling the maintenance in my company.
What's my experience with pricing, setup cost, and licensing?
We used the standard licensing for our use of FME. The cost was approximately €15,000 annually. We always welcome less expensive solutions, if the solution could be less expensive it would be helpful.
What other advice do I have?
I would recommend the desktop version of FME. The company is trying to sell it as a server version with automatically processing capabilities, but it's only buying one shared license for batch processing purposes. That's cost-effective. I don't think we will be able to raise the money for a desktop version. The data we are using it for would have to be very important.
I rate FME a nine out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-08-16T00:00:00-04:00