Thanks for the update! Glad TS was able to figure this out and it's working now. Well done. ... View more

Yes, request body looks good. Keep us posted how you go. Curious what's missing here. Thanks, Falko ... View more

Well, you did all the hard work - I'm just leaving some comments 🙂   Question. I just had another look at your data column description above - in particular table MAPSCSTM.SCOTTISH_LA1. I do not see a column named SEGMENT in there. Can you confirm it's there? At the very minimum you need ID, IDNAME, SEGMENT, X & Y columns.    In VA - can you also add a filter to reduce data to one region only? It sometimes helps to narrow down an issue. I have seen instances - nothing would render, just because there was one region which had invalid polygon data and confused the system. Worth a try - just looking at one for testing purposes.   Also let's validate whether expected ID variables are passed thru to the server. Can you open the browser developer tools (typically just by pressing F12 in Chrome/Edge). By default that window will be docked next to the browser window - if you undock and open in a new dialog - it will give you more room to see content. In the developer tools open the 'Network' tab and enter 'geoMapService' in the top left 'filter' input field. This will reduce the noise and only show requests to that one service. Every time you open a region map (even when sample data is shown) - a new request is send to retrieve the polygons. Now, if you select a request entry it will show you things like 'Headers' and 'Response' information. In 'Headers' - validate the query string parameters and make sure ID's are passed in as expected. No leading/ending spaces - upper/lowercase etc? Also validate the table name and library information. What is the return HTTP status code of such request (it should be 200) and do you see any response data at all?   Chances are, response data is empty given your description and it will be a little difficult to debug this here further without seeing any log files. If that is the case - we may need to get TechSupport involved so you can share log entries and they can help you enabling logs temporarily for debugging purposes.    However, it feels like you have everything in place - and it may just turn out to be one minor last tweak required here. ... View more

Nice work @Nigel_Pain - I feel like we are getting close 😎.   Given that data point overlays (bubble/scatter) are working indicates that you have correct entries in the CENTLOOKUP table along with correct X/Y values for the coordinates. Now, for regional overlays the actual polygon data is retrieved by referencing the table as specified in the MAPNAME column in CENTLOOKUP. If that fails (and you can double check any potential errors in the underlying workspace server log file) - it typically means that Visual Analytics can't find the related table (correct name?). In many cases it may just be a missing library definition during runtime - so first I would check whether you have correctly done step #2 in the instructions? In particular whether you have added the library to the appserver_autoexec_usermods.sas file and restarted the object spawner service?   If that library is there and table exists within that library and is correctly referenced in the CENTLOOKUP table - check the underlying workspace server log files and see whether you can see any other messages related to that. If you find something not making sense there - just post it here and I have a look...   Thanks, Falko ... View more

Well, typically you can determine the coordinate space by looking at your original Esri shape files. One of the files has the extension .PRJ and you can just open using a text editor. Then use information to find related proj.4 or EPSG code via https://epsg.io or https://spatialreference.org. Once done use a command such as (here an example converting Canada's UTM projection) :     proc gproject latlon project=proj4 from="+proj=utm +datum=NAD27 +units=m +no_defs +zone=11" to="EPSG:4326" data=myorigshp out=myprjshp; id REGION_ID_COL; run;     ..to convert values from your original projection into WGS. Note, that both from/to parameters support both the proj.4 syntax or EPSG codes.   Now, if you don't have the original shape file anymore or it doesn't have a .prj file - things get a little more complicated ;_) and it may involve a bit try and error approach. Looking at your first example line above - you stated that one coordinate pair for Clackmannanshire is:   Clackmannanshire 0 298892.30 694533.90 Using sites such as http://projfinder.com and entering both values as well as navigate the right hand map to exactly the location of Clackmannanshire shows a potential hit for EPSG:27700. Have you tried that?   In regards to your question and confusion about two different pairs of coordinates in MAPSGFK.VAEUROPE1. Note, that files in MAPSGFK are the original (unchanged) map data as provided by GfK. SAS Visual Analytics references only the LAT/LONG columns in these tables but not the X/Y. The latter represent the coordinates as projected by the Albers projection and aren't used in VA. So when you create your custom shape data set - it doesn't really matter what you populate in X/Y as long as LAT/LONG carry correct WGS84 representation of your values.   Hope this helps! Falko ... View more

Nice work. Getting thru the code examples is quite a bit of effort so good to see you actually have the new provider showing up in the UI. Looking at the data - it seems the registration went ok. I noticed the X/Y values in table SCOTTISH_LA1 (and assuming the resulting entries in the CENTLOOKUP table) are not using projection WGS84 (or EPSG:4326). Note, that VA 7.x does not support any other coordinate space (support for custom projection have been added to VA 8.x) and as such you will need to convert to EPSG:4326 before. SAS ships method proc gproject (doc: https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.5&docsetId=grmapref&docsetTarget=p17iukb090f5yvn1rmptbpg7xlnb.htm&locale=en) and conversion is usually pretty straight forward assuming you know the projection your data is in. So it may just be that the registration went all well - but the latitude/longitude values aren't in the range the system expects it. WGS84 has a range from -90..90 (lat) and -180..180 (lng). Hope this helps. Falko ... View more

Hey @Nigel_Pain - sorry I was somehow under the impression you would use current production version with VA on Viya. Well, in VA 7.x - things are a little more complicated unfortunately. Especially geographical support for custom polygons and centroids along with better Esri integration is something which got massively improved in VA 8.x.   However - we do have instructions on how to do this in VA 7.x as well. Please check out https://go.documentation.sas.com/?docsetId=vaag&docsetTarget=n09tvhnyrosr8mn1nmw7u3akrb1e.htm&docsetVersion=7.5&locale=en. There is a bit of SAS code involved so hopefully not too difficult. Essentially you will update the underlying lookup tables VA uses and merges in your custom polygon data. If all goes well - the 'Country or Region' drop down list will have your new entry populated.   In regards to your question around separating business from shape data. After the steps above you will have the shape data in a different table (the internal VA lookup tables). Once done - only an ID column ('GB-XXXXXX') is required in your business data. That is the very same column you will convert to a geographic item in VA. Once it's a geo column - you can use it in any geo visualization and combine with other business values to color regions or size bubbles.   Obviously let me know how you go.   Thanks, Falko ... View more

Hi! SAS Visual Analytics ships with boundary data for country and first administrative level (e.g. states or sub-divisions). You can find out expected mapping values by visiting https://support.sas.com/rnd/datavisualization/vageo/85/va85lookupvalues.html .   Now, Scottish local authorities are administrative level 2 I believe (correct me here of course) - and as such would require custom boundary data to be imported. You can follow guides such as https://blogs.sas.com/content/sgf/2019/03/27/creating-custom-region-maps-with-visual-analytics/ or of course check out related VA documentation how to do that. If you have an Esri shapefiles - you could also use the provided %shpimprt macro to import the data into SAS. Often boundary data is provided free of charge and many government agencies around the world provide data as part of their open-data strategy.   Once you have imported the boundary data and defined your geographic item based on a custom geographic provider - the mapping should work.   Hope this helps. Falko ... View more