|
Any wisdom about collecting practical Lexicon applications/use cases? (for Geo & beyond)
|
|
3
|
55
|
December 4, 2025
|
|
Bonfire Geo (place) implementation
|
|
0
|
12
|
November 7, 2025
|
|
ATGeo WG: more geometry types
|
|
1
|
34
|
October 22, 2025
|
|
Initial draft "proposal" for an ATGeo location record (lexicon)
|
|
7
|
51
|
October 16, 2025
|
|
ATProto Location Data Store: A Source-Aware, Federated Approach to Location Data
|
|
5
|
51
|
October 15, 2025
|
|
ATGeo WG: October 2025 meeting
|
|
0
|
16
|
October 6, 2025
|
|
ATGeo WG: Next meeting 25 Sep 2025 1900 UTC
|
|
5
|
42
|
September 29, 2025
|
|
Prototypes – go-whosonfirst-spatial-atproto
|
|
2
|
22
|
September 27, 2025
|
|
Prototypes - whosonfirst-external-duckdb
|
|
2
|
16
|
September 27, 2025
|
|
What is the Difference Between a “Federated Location Data Store” and a “Gazetteer”?
|
|
5
|
45
|
September 2, 2025
|
|
Location Data Providers and ATProto Development Patterns
|
|
8
|
38
|
September 2, 2025
|
|
Formalization Meeting: ATgeo Working Group
|
|
6
|
51
|
August 30, 2025
|
|
Licensing Considerations for Location Data
|
|
7
|
23
|
August 29, 2025
|
|
Broadly speaking, the applications of location data in ATProto
|
|
3
|
26
|
August 22, 2025
|
|
ATGeo WG: How do we represent place names?
|
|
5
|
25
|
August 16, 2025
|
|
ATGeo WG: How should we refer to place objects from off-protocol reference datasets?
|
|
3
|
30
|
August 16, 2025
|
|
ATGeo WG: What to do with reference place objects that have extra attribute data?
|
|
0
|
10
|
August 13, 2025
|
|
ATGeo WG: Documentation for existing Lexicons
|
|
2
|
23
|
August 10, 2025
|
|
ATGeo WG: Designing for interoperability with a common data model for places
|
|
5
|
47
|
August 7, 2025
|
|
ATgeo WG: Next Steps for Garganorn and Geographic Data in ATProtocol
|
|
7
|
61
|
August 7, 2025
|
|
Some ideas for a checkin record, need input!
|
|
18
|
61
|
June 29, 2025
|