Can't find "boundaries" menu in Microstrategy Workstation for ESRI maps - reporting

I have a dataset which corresponds to COVID cases in Argentina (every row is a case). One of the attributes is the province (geography) but the problem is that some argentinian provinces like "San Juan" also exists in other countries (Puerto Rico). Therefore, when I try to configure a map (ESRI or MapBox) it points out to Puerto Rico, not Argentina.
I wanted to try changing the type of boundaries in Workstation but I can't find where is located this option in the menu. It is supposed to be located in Format/Layers/Boundaries, but it's not there.
My Workstation version is 11.3.0730.00693

Related

Swapping rows and columns in a matrix in Power BI

I want to analyse the sales of a certain company in Power Bi. I have a customer dataset with nine columns (gender, city, age range, hair colour etc.) and one million records. Now I want to put those columns in a matrix. For instance:
Rows: Gender
Columns: Age Range (<16, 17-20, 21-25 etc.)
Values: Number of Sales
I present this dashboard towards some people and I want to 'play' with the data. What happens if I change the rows to 'hair colour' for instance. Is there a way to do this without using bookmarks? In one sentence: swapping rows and columns of a matrix while you present the dashboard and cannot use the option 'Fields'? Or at least point me in the right direction? It would really help me. Thanks in advance!
Unfortunately, the quickest way to do this is using the Fields pane. The only other option that is available would be Bookmarks, but I guess you have already tried that. I guess you are an option similar to the one available in "Pivot Charts" where you can "Switch Rows/Columns" with the click of a button. That option is not available in Power BI at this point, as far as I know.

How to use dates and numbers separately with LUIS.ai?

I'm testing LUIS.ai and I'm following the introduction that I saw on Youtube (https://www.youtube.com/watch?v=jWeLajon9M8), but I'm doing it in French because I need it. So I'm writing some utterances for an intent but I have a problem with prebuilt entities "Date" and "Number".
Indeed when I want it to detect a date, I'm using the prebuilt entity "Date" on the suitable pattern, but the problem is that every number and date are automatically detected as dates, and I don't find how to remove the date entity from the pattern it is directly applied to. And if I completely delete the date entity but bring the prebuilt number entity, every number are detected as numbers, but I can't bring back the date entity in the same time because the date entity will remove the number entity and force itself on numbers.
For example : I have the utterance "je voudrais réserver un billet d'avion pour paris pour le 30 mars" which means "I would like to book a flight to Paris on the 30th of March". Here I can select "Paris" and tell that it is associated to a "Destination" entity that i created, but if I select "30 mars" (30h of March) and add the prebuilt entity date, it will detect it as a date (this one is fine), but it will also automaticcaly detect "un" ("1" in French) as a date, and I can't do anything about it, I can't remove it.
Is there a way to solve this problem ? Because of course I don't want numbers to be detected as dates and vice versa.
This is a UI issue more than anything and not likely one to change.
You can't change detection of pre-built entities (like number or dateTimeV2). So, clicking on a detected pre-built entity won't really help.
However, LUIS returns all detected entities.
From the Test panel:
In the JSON:
Assuming you're using this in a bot of some kind, just have your bot detect whether or not an entity is present on a recognized result.

Columnar report in Tableau

I'm new to Tableau. I'm using Tableau Desktop Professional 10.0.15. I need to write a very simple report that does not use any visualization.
Here's a example of the layout (the numbers are made up):
Web Site 1 North America Europe
Total Hits 3,523,483 3,523,483
Sessions 1,248,234 1,248,234
Unique Visitors 1,809,392 1,809,392
New Visitors 383,932 383,932
% new 10.9% 10.9%
Avg Page Views per user 1.9 1.9
Web Site 2 North America Europe
Total Hits 3,523,483 3,523,483
Sessions 1,248,234 1,248,234
Unique Visitors 1,809,392 1,809,392
New Visitors 383,932 383,932
% new 10.9% 10.9%
Avg Page Views per user 1.9 1.9
The users want the measures to be in one column, but they're not the same measures. Some measures need to be formatted as percentages. The average should have 1 decimal place. I have a feeling it's not possible to format the same measure differently in Tableau. Ideally, there would be something like a banded report where I could stack the measures on top of each other. But, I don't see a way to do that in Tableau. I could create a table in my database and put the measures in the same field and add the formatting in the database (which feels wrong), but it would have to be text (to have '%'). But, Tableau won't treat a text field as a measure. Also, it seems like if you don't add a measure, Tableau will insert a fake measure and put 'Abc' as the value (at least, I think that's why I'm getting these 'Abc' columns in my reports that I didn't add and that aren't in my data).
It seems like Tableau wants you to do something like this:
Unfortunately, this is not what my users want. Any suggestions?
In Tableau it's possible to put many measures in a single column using the measure names in rows.
To do this, add to filters shelf the dimension called Measures Names (the last one). Select all the Measures you'd like to show (Hits, Sessions, Visitors, Views, etc.). Then, drag this dimension to the rows shelft. Next, drag the measure called Measures Values (the last one too) to the marks shelf, specifically in the text box. You can also add other dimension to rows shelft (like website) to the left of Measures Names. This will show a table similar to your requirement.
By default, the Measure Values are SUM of each measure. Just right click on them and select the aggregation you need (AVG, COUNT or other).
Finally, you can format each measure as you want, right click a measure value, and select Format...

I need an XPATH to extract data from www.gsmarena.com

I am doing a research about how mobile phones evolved over years so I need to create a database with specifications of as many phones is possible. I am trying to scrap data from GSM Arena website.
Example page: http://www.gsmarena.com/samsung_galaxy_note7-8082.php
I am using XPATH that contains the label that precedes each value, example //tr[contains (.,"Sensors")]/td[2]
But there are some values, last one in category, with no preceding label.
How do I pick this info:
Non-removable Li-Po 3500 mAh battery
or this ino:
Fast battery charging
Qi wireless charging (market dependent)
ANT+ support
S-Voice natural language commands and dictation
MP4/DivX/XviD/WMV/H.265 player
MP3/WAV/WMA/eAAC+/FLAC player
Photo/video editor
Document editor
Do note that different phones have different number of rows on page, so using [number] in XPATH would pick different info from
http://www.gsmarena.com/samsung_galaxy_note7-8082.php - need to pick 5th row of features
http://www.gsmarena.com/samsung_sgh_600-49.php - need to pick 8th row of features
To select rows without label in Battery section you have to use this xpath:
//tbody[.//th[contains(.,'Battery')]]//td[#class="ttl" and not(*)]/following-sibling::td
To select info from features use this
//tbody[.//th[contains(.,'Features')]]//td[#class="ttl" and not(*)]/following-sibling::td
To select Camera features
//tbody[.//th[contains(.,'Camera')]]//td[#class="ttl" and contains(.,'Features')]/following-sibling::td
To select Loudspeaker in Sound Category
//tbody[.//th[contains(.,'Sound')]]//td[#class="ttl" and contains(.,'Loudspeaker')]/following-sibling::td

Faceting by geolocation in Elasticsearch (clustering)

I have a project that enables users to search for POIs using Elasticsearch, and they can filter by a number of different attributes, including location. I'd like to add faceting to all of the filters, most of which are categorical variables for which faceting is perfect. However, I also want users to be able to facet by location/city/metro area. Each location is currently a lat/long pair.
From my research, it seems that the best approach is to use k-means clustering of the lat/long pairs to get the most common groupings of locations for faceting. Once I have those groupings, I would want to provide the most commonly recognizable name for the area (e.g., even if "Brooklyn" was the center of a cluster, I'd want to provide the name "New York City").
(a) Can geo-clustering (k-means, or any other way) be done in Elasticsearch to allow faceting by location? If so, how? If not, can this be done in Postgres instead?
(b) How can I make sure that I'm providing the most widely recognizable political name for any given region returned by the clustering?
Given Lat/Long (or address) as input, you can use the Google Maps Geocoding API to retrieve (and index) specific hierarchically-scoped labels for:
country
administrative_area_level_1 (state: in the US)
administrative_area_level_2 (county: in the US)
sublocality_level_1 (borough: in NYC)
administrative_area_level_3 (city: in the US)
locality (neighborhood: in the US)
If you're building out a Yelp or AirBnB-like search interface with a zoom-map component, you can choose which location facet to display based some diversity criteria:
e.g. request all 6 term facets, but only display the one with the appropriate selection diversity (say 2-10 terms) ... for example, if your zoom level (and bounding box) includes Brooklyn, Manhattan and Staten Island, then you'll see the following:
country (United States) ... ignore, too broad
administrative_area_level_1 (New York) ... ignore, too broad
administrative_area_level_2 (Kings County, New York County, Richmond County) ... ignore (just in the case of NYC where sublocality_level_1 is more commonly used)
sublocality_level_1: (Brooklyn, Manhattan, Staten Island) ... appropriately specific, show this!
administrative_area_level_3 (New York City) ... ignore, too broad
locality (<100s of neighborhoods>) ... ignore, too narrow

Resources