Difference between revisions of "GEPS 006: Better Place handling"
m (B) |
(→Motivation) |
||
| Line 9: | Line 9: | ||
Time and again users pose questions on improving the place structure of GRAMPS. This GEPS is about defining a new improved way of handling place, keeping backward compatibility with GEDCOM/present GRAMPS. | Time and again users pose questions on improving the place structure of GRAMPS. This GEPS is about defining a new improved way of handling place, keeping backward compatibility with GEDCOM/present GRAMPS. | ||
| − | Many things are also not well designed, in that GRAMPS allows the user to do as he likes, without guiding the user to a good way of storing place data. | + | Many things are also not well designed, in that GRAMPS allows the user to do as he likes, without guiding the user to a good way of storing place data. (this statement is disputed, see [[Talk:GEPS 006: Better Place handling|discussion]]) |
== Some ideas == | == Some ideas == | ||
Revision as of 22:46, 8 April 2010
Proposed changes for enhancing GRAMPS by updating the Place object:
- make places more manageable by introducing a hiearchy
- integration with online map tools
- good definition of place and address/residence event in GRAMPS
- alternative place with a date span? Define one ideal way of working with alternative place.
Motivation
Time and again users pose questions on improving the place structure of GRAMPS. This GEPS is about defining a new improved way of handling place, keeping backward compatibility with GEDCOM/present GRAMPS.
Many things are also not well designed, in that GRAMPS allows the user to do as he likes, without guiding the user to a good way of storing place data. (this statement is disputed, see discussion)
Some ideas
- Geonames
- Gedcom 5.5EL
- An internal place database
