TRIRIGA/MREF GIS Queries must Include GIS Latitude and Longitude and these must be labeled “Latitude” and “Longtitude.”
This is a quick note in case anyone is struggling with the same problem I encountered caused today.
Here’s the scenario.
- You’ve got a GIS portal section in TRIRIGA/MREF.
- You’ve created the GIS Map record that powers the section.
- You’ve set up the extent, configured your basemap(s), connected to one or more data sources for layers.
- You’ve created a “GIS Query” record to display TRIRIGA data on the map.
For most of you, it probably just works. Congratulations! If you’re a grug brain like me, though, read on.
No matter what you do, the map doesn’t work! It’s so broken, in fact, that the portal is unstable and your browser reports that the page is unresponsive.
If that’s you, what now?
The TRIRIGA documentation says it plainly enough: “Queries must include display columns that are labeled Longitude and Latitude. The Latitude and Longitude fields pinpoint the item on the map.”
After spending a couple hours today troubleshooting a GIS query, let me make it even more plain.
- Make sure your query includes the Location Business Object and (of course) the correct association string.
- Add the triGisLatitude and triGisLongitude fields from the Location BO to the query.
- Label these fields Latitude and Longitude. This step is important! The fields are called “GIS Latitude” and “GIS Longitude” on the BO, and that won’t work.
Save the query, reload the portal, and voila!
Now I must confess what I did. Learn from grug.
grug see GIS query has longitude and latitude but TRIRIGA locations have no latitude and longitude data
this bad — it mean no TRIRIGA points on map
grug see GIS layer from ESRI includes ID
grug think user need way to open TRIRIGA record when they see something interesting on map
grug see “Show Table” on map viewer and see that records can be opened from the table
grug get idea
maybe user click on “Show Table,” find what they need with ID, and open record that way
this not great, but only option
grug change query to show data shown on GIS layer
grug think user no longer need latitude and longitude on query because these always blank
grug delete latitude and longitude from query because efficiency good
now portal no work and browser mad at grug when page load
grug try fix many ways until stop and eat lunch
maybe read documentation will help, grug think, but it only help a little
after few more tries, grug find answer and then write answer here
If this helped you, hello from the past! If you’re inclined, leave me a comment.
C.B. Crenshaw 