1,057
edits
Changes
→Good definition of place and address/residence event in Gramps
* For UK data, an extra Locality field between City and Street would be useful.
* For Dutch data, an extra Municipality field between County and City would be useful. (Feature Request 4231)
* Japanese use block names, instead of streetnamesstreet names: [http://en.wikipedia.org/wiki/Japanese_addressing_system]
We could re-define each field for each country, or we could try to keep each field maintaining similar data. I think that I prefer adding a couple of extra fields. This is less complex than a list structure with definable number of tiers (less complex to program, but also less complex to use by the user)
{| {{Prettytable}}
|-
! Existing !! New structure!! General Name!! USA !! UK England !! France !! Netherlands !! Germany !! China
|-
| State || Tier 1 || Region || State || Not Used|| Region || Not Used || Province || Province
|-
| County || Tier 2 || District || County || County || Department|| Province || District || County
|-
| City || Tier 3 || City/Municipality || City || City || City || Municipality/City || City || City
|-
| / || Tier 4 || Locality || Locality || Locality|| Locality || City/community/hamlet || Locality || Locality
|-
| Street || Tier 5 || Street || Street || Street || Street || Street || Street || Street
|-
|}
Definitions:
* ''' Tier 1 & 2''': Between a country an the smallest administrative section, we allow for two levels.* '''Tier 3 ''': level of division of a country with a mayor.
* ''' Tier 4 ''': The locality people identify themself with. Can be a hamlet, the city itself, a borough, ...
We would need a country table. This would hold the field definitions for each country including the field names, 'not used' flags, and which fields should be used in the place tree view.
country
County
ZIP Localicty Locality - City
street
: for Belgium this format would be
street
: with a format field and people seeing this format, they will understand how they are supposed to enter the place information (note that if Locality equals city it obviously must not be repeated.
Comment (NH)
* Wales [http://en.wikipedia.org/wiki/Wales] is a country and I would expect it to appear in the list of countries, along with England, France, USA etc... I would like to keep things simple and to enter an English place: select "England" from countries, select a county from a list of English counties (or enter it directly) and then enter a city and fields below where applicable. I accept that the British Isles maybe a complicated place and this may need further discussion.
* Your example of Clairemont is exactly what I intended the Locality field for. Its use is not limited to the UK.
This data could then be used to dynamically create fields in the place editor, place filter and place tree view.
'''Questions and Design Decisions'''
* Do we need 2 or 3 tiers between the level with a mayor and the country? We only take 2 tiers. Most countries have more than 2 tiers, but they have little importance for the inhabitants or genealogy. What about Feature Request 4231?* Many countries have different sublevels sub-levels depending on the country. Yes, but Gramps is not a place storing application. In Countries like China you have province or autonomous region or .. as Tier 1. We can only provide one label, the users must himself understand that a locality in an autonomous region should put the name of the region in the Tier 1 (Labeled province) field. Or we could make the label read "Province/Region" if appropriate.
=== Define one ideal way of working with alternative place ===