LDSTechForumProjects

Talk:Geo code

(Redirected from Talk:GEO Codes)

I've finally finished cleaning up all the text written in first-person. Hopefully someone can review and make sure I didn't unintentionally change the meaning of something important. Lindsayre 16:20, 27 March 2009 (UTC)

Field length question

Are Stake and Ward GEO Codes up to eight characters long EACH or in TOTAL?

This implies eight total: Option 3 (WW##SS##)

CONVENTION: An eight-character Geo code where the ward uses the first four characters and the stake uses the final four characters. Rontilby 02:16, 21 April 2009 (UTC)

The limit is eight characters total. The stake and wards have to decide how to share the eight characters. Lindsayre 04:46, 21 April 2009 (UTC)
Just to clarify, the ward code is 8 characters, and the stake code is 8 characters. The stake and the ward don't have to share portions of those 8 characters unless they want to. It's certainly possible for the ward GEO code to be 8 characters long and the stake GEO code to be an entirely different 8 characters long. I'm not sure what the motivation would be for the option 3 scenario described in the article (which does specify a ward-stake sharing of the 8 characters in one or both of the GEO codes), but that is only one way of doing things.
Generally it makes sense for the stake to depend on the wards to create the ward GEO code and then make adjustments to the stake GEO code for stake purposes. But there's nothing stopping the stake from having an entirely different approach to using the 8-character stake GEO code. The main purpose for stake GEO codes is for ward and stake boundary adjustments, and the needs of the stake may be quite different from the wards because of this. -- Aebrown 10:57, 21 April 2009 (UTC)

Proper term?

This question or concern has been resolved.

MLS seems to be somewhat confused as to exactly what to call these things. In many places, they are called "Geo Codes" (such as the Stake MLS menu item "Household Geo Codes"). But does it use a capital G and C just because MLS uses title case for all menu items? That theory is supported by the MLS help file, which seems to be pretty consistent in just referring to "geo codes" (except, of course, when referring to a menu item which is of course in title case). But then in MLS, when you pop up the dialog to change a geo code, in all three places it refers to a "Stake GEO Code", and a couple of those are in places that could have been in all lower case. However, that is the only place I can find that uses the term "GEO" in all caps. The [1]  lesson always uses "geo code".

So I have to think that the proper term is simply "geo code", and that it is sometimes capitalized, but it should not ever be "GEO Code" (and that "GEO Code" appearing in one MLS dialog box is simply a mistake). As we are cleaning up case issues in the wiki, we might as well do that one right. -- Aebrown 04:23, 16 June 2009 (UTC)

Given that Lindsayre renamed the article to be Geo codes and fixed up several usages to be "geo codes," and I just adjusted the article title to the singular Geo code fixed up the rest of the usages that I could find to be "geo code," I think this issue has been resolved. -- Aebrown 18:18, 24 June 2009 (UTC)

Census Bureau Tract Numbers

If I'm reading the maps correctly on the Census Bureau website, tract numbers are (ignoring the decimal) six digits long (e.g. 1131.01) and each tract is then sub-divided into smaller areas that are assigned an additional four digit number (3030). Given that MLS geo codes are limited to eight characters, what is the proposed method to translate ten digit tract codes into MLS geo codes? Are you assuming low-density of members and only using the six digit code? Lindsayre 17:30, 2 September 2009 (UTC)

Suggestions

1. Move all the purposes of Geo codes to the top. Until you have a purpose, deciding on a coding method will be difficult.

2. Discuss how Geo code reporting works. You need to understand this before deciding on a convention. The only way I know of is to use custom reports. Since it gives you a "begins with", it might be wise to come up with a system that defines a large area and then sub-parts of that area. For example Map Page/Map square. That way you can create a report based on just map pages and ignore the individual squares. However, if there are more then 9 pages in the map book, be sure to use two digit map page numbers, so your report for page 1 doesn't have pages 10 and 11 mixed in.

3. Re-label the "options" as "examples". To call them options is to suggest that one must choose one of them. I realize the text specifically says "use what works for you" but to call them examples reinforces that.

Example 6 (US National Grid or Military Grid Reference System)

It appears to me that the suggestion to use the US National Grid System doesn't accomplish the goals of the Geo code as it is used in MLS. Although there are certainly merits to the suggestion for determining the location of a household, that's not what Geo codes are for. They are used for grouping households. Since this proposal would end up with a unique Geo code for each household, there would be no grouping at all. Thus it is totally unsuitable for boundary proposals, which depend on multiple households (usually at least a dozen or so) being grouped into a single Geo code.

It's unfortunate that the term "Geo code" as used in MLS is so close to the term "geocoding" which refers to determining the geographical position of a building or some other location based on its address. So the confusion is understandable. However, since this proposal doesn't fit the purpose of MLS Geo codes, I will be removing it (unless a discussion ensues here on this page that can explain how this proposal could work). -- Aebrown (talk) 13:43, 23 March 2013 (MDT)

This page was last modified on 23 March 2013, at 12:43.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.