-
byJust a small update today β posts made with micropub respect the published datetime and I'm saving /showing syndication urls. I still need a proper interface for both of these in the admin. This is what syndication links will look like in a post.
Syndication links now appear in the post meta -
byWith support for locations finished, I was able to add support for checkins in a couple of hours this morning. You can only post a checkin via micropub, but you can edit them like any other post locally.
There's three remaining "tidbits" to be completed before I can mark location/checkin support is complete:Β use the sent published date time in the micropub request as the posts' published datetime, store/display the syndication urls in the post meta, and confirm microformat my location data. This is what they look like β checkin is from January 2nd :-)An example checkin post with a photo -
byWorking a bit on how to integrate location information into a post. Right now I've got the location name appearing in the byline. Some day, I imagine this will be a link to search page that'll show you all posts within a given radius of that area.
Initially I had planned to have the map display on the right hand side of the post, in the "meta" column. But that felt like it's separate from the post. Moving down into the footer and increasing it's size a bit has helped it feel a bit more "at home".Integrating location into detail page -
bySorted how locations will display on a post publicly today. I really like the automatic zoom as your mouse gets closer to the center.
Zoom animation -
Checkin to γ«γ»γγγγ³ι£γγ³ εΌ₯ηε°εΊ
-
Checkin to Starbucks
by in Kanagawa, Japan -
byManaged to get reverse geocoding (looking up the address from for a given coordinate) working when you click the map. I've also hooked up the remove location button to...remove the location.
The address updating when the point moves.
There's two last tweaks I need to make:Β 1) I'd like a reset button to reset your location form to it's initial state; 2) The address form is going to be hidden entirely and the values will be displayed as a single line of text below the map to emphasize that the address is "just meta". -
byMapping is coming along nicely. Today I got markers to move by clicking the map, serializing changes to geo-json for saving, and integrated leaflet-geosearch.Β
Next I'd like to automatically fill in the address when available, but in order to do so, I must first normalize the Nominatim addressdetail response to match up with my fields.A look at moving and searching for locations -
byΒ After making it so I can update my location for an entry, I started to integrate Leaflet, rather than use the default GeoDjango OSM widget. It's my first time working with Leaflet, so it's a bit slow going.
I've managed to get basic display of the map working as well as clicking to move the point. I think if I can get the point to be powered by some GeoJSON in a hidden textarea, I should be able to once again set and update locations on entries.Leaflet in Tanzawa -
byI got locations saving to notes properly. Next up allowing you to update locations when editing an entry. When saving I initially ran into the following error:
spatalite no such function: lwgeom_version
The issue was that Django's PointField default projection is 4326, which is used for spherical references e.g. Google Earth. However, I'm displaying a flat service (an OSM Map), which uses a different projection 3857.Β I fixed this by changing my database to match my most common display.from django.contrib.gis.db import models as geo_models ... point = geo_models.PointField(geography=True, srid=3857)