Originally Posted by nohal
do you think anybody could use anything else than vi? Like emacs? Those people would have to be insane
I've been a vi/vim user for almost 20 years now. Never really got emacs (I honestly tried
Thanks for the sample and description, it looks very usable. Do you have any ambitions to aim at non-point objects in the future as well? Will be ugly in the GPX extensions, but doable it is...
I considered other types of geometry. Like you said, GPX does not lend itself very conveniently to lines and polygons, though I think there may be solutions (pretend lines are tracks or routes?) Perhaps by then compatibility won't matter that much.
Personally, I think the scope of this format at least for now is POI and they are points by definition. Going into geometry we are entering less of "information exchange" and more of "chart" territory, and there are better ways to convey chart-like data than XML. The hard part with geometries is drawing them in a way that makes sense. Simply slapping polygons in order they appear in the file will likely not look anything like what user wants to see. So if this thing goes the way of charts, schema would have to become quite a bit more complex to handle visualization issues beyond "what icon to pick" etc.
In any case, I think data format should "grow organically". If there will be sufficient amount of data out there, and that data needs other geometries - I think the solution will reveal itself based on practical needs
If you decide to work with this - let me know, I'd certainly like to keep things compatible. There is a bit more to format than readme describes:
1. Updates - in the most basic case a new data entry from the same source with the same ID replaces the old one, but see below. Same goes for removing entries.
2. In addition to main body of data, there are "records" - basically sub-sets of data within main data record
. They have their own ID separate from that of the main entry. They exist for two reasons:
- Updates - you can update records of a given entry independently of the entire record
. I.e. you can update portions of data without touching the whole, and vice versa, you can update main record without touching sub records. This is useful where data is mapped from combined sources (like database tables or whatever), and you map one set to main body of POI, another to a specific record etc.
- Repeating fields. You can have multiple records in the main entry with the same fields. Visually I am mapping these to multiple data "groups" on the same page (like, for example, reviews
for a business - each review is a record). They don't have to be visualized the same way of course, but the purpose is to convey repeated information for a single
I think that about covers it - and if you are interested, I'll document these items too.