MapQuest tile source lost

I expected this to happen at some point; for now, ownMapp is broken until the tile source is updated.

Modernization of MapQuest results in changes to direct tile access | MapQuest Dev Blog
On Monday, July 11, 2016, our direct tile access to MapQuest legacy maps will be discontinued. After Monday, July 11, 2016, we’ll require those using our direct tiles access to sign up for a plan on the Developer Network....
ownMapp v1.2.2 release as a new member of Hubzilla Plugins

Hubzilla Plugins v0.3.0
hubzilla-plugins - A collection of plugins for Hubzilla

ownMapp has been updated for compatibility with the upcoming release of Hubzilla v1.5. The MinVersion for the plugin has been increased to v1.4.2, which is not yet in the stable master branch but will be soon.

The ownMapp plugin repo has also been migrated to the collection of plugins in the hubzilla-plugins repo. We will be coordinating to update the relevant plugin repo links.
ownMapp v1.2.0

1.2.0 · Tags · zot / ownmapp

This release of ownMapp updates to be compatible with Hubzilla v1.1.2. The update is not backwards compatible with previous versions of Hubzilla.

The page_end hook function was dropped, because it was loading ownMapp JavaScript for all Hubzilla pages. Now this code should only be loaded for the ownMapp plugin. The map and control panel interface was also improved.
Andrew Manning
1.2.1 · Tags · zot / ownmapp

Fixed bug in event marker scanner that loaded events with invalid format locations. Added get_version function.
ownMapp git repo on GitHub too

For convenience, I renamed the original ownMapp repo on GitHub and replaced it with the current code. I recognize that not everyone has a GitLab account or the desire to use that service.

However, I do encourage people to consider using GitLab when possible because it is an excellent open source platform.

ownmapp - This is a plugin for Hubzilla that provides a map interface to track and share locations and an API for other location services.
Semantic Versioning

I started using semantic versioning. Here, then, is version 1.1.0, in which I add a plugin admin setting that can prevent the ownMapp database tables from being deleted if the plugin is uninstalled/disabled.

The next thing to do is the public API documentation:

Software using Semantic Versioning MUST declare a public API. This API could be declared in the code itself or exist strictly in documentation. However it is done, it should be precise and comprehensive.

But... but...

If even the tiniest backwards incompatible changes to the public API require a major version bump, won't I end up at version 42.0.0 very rapidly?

This is a question of responsible development and foresight. Incompatible changes should not be introduced lightly to software that has a lot of dependent code. The cost that must be incurred to upgrade can be significant. Having to bump major versions to release incompatible changes means you'll think through the impact of your changes, and evaluate the cost/benefit ratio involved.

Documenting the entire public API is too much work!

It is your responsibility as a professional developer to properly document software that is intended for use by others. Managing software complexity is a hugely important part of keeping a project efficient, and that's hard to do if nobody knows how to use your software, or what methods are safe to call. In the long run, Semantic Versioning, and the insistence on a well defined public API can keep everyone and everything running smoothly.
Static marker import from file

Static marker import works. URL is map/import. (2a0985e8) | Commits | zot / ownmapp | GitLab

Static markers can be imported (/map/import) from a file that was exported using the new markers export tool (/map/export/markers). The import is rudimentary at the moment, but at least you don't have to lose your markers if you migrate your channel to a new hub or make a new channel.

The next step is to create an option and mechanism to synchronize the map data with channel clones.
Maptime meeting

I attended my first Maptime meeting recently, and it was a wonderful experience. It was a project night, meaning everyone who attended introduced themselves and the project they are working on, and anyone interested could discuss it with them. I learned a lot about the tools available for OpenStreetMap data analysis and editing, as well as some interesting things people are doing with JavaScript libraries like D3.

I met several other open source enthusiasts. My demonstration of Hubzilla and ownMapp were well received and stoked a lot of interest in the projects!

This looks interesting. Might be useful for ownMapp at some point.

Advanced geospatial analysis for browsers and node Modular, simple-to-understand JavaScript functions that speak GeoJSON Takes advantage of the newest algorithms and doesn't require you to send data to a server Turf is a collection of small modules. You can require just what you use with browserify...
Added static marker export API map/export/markers (a163c308) | Commits | zot / ownmapp | GitLab

I'm beginning to add data export API functions. The first added today is the static marker export as a JSON formatted file.
New plugin settings

ownMapp now features some user settings, including the options to enable automatic tracking when the map loads and auto-saving of location data when tracking is active.

Haakon Meland Eriksen
Suppose I have my own map server, what do I need to do to make it work with ownMapp?
I have not yet explored the different ways to source the map tiles in OpenLayers. It is definitely a long term goal to host the map data. Perhaps you can specify a custom URL using the TileJSON source? Let us know what you discover if you research this.
ownMapp project page powered by Comanche (sort of)

I'm trying to follow Sean's lead and convert the ownMapp project page (currently still under development) into a Comanche-powered page. So far it's looking okay (aside from a lack of actual informative content) but I'm kind of hacking it together still, because I'm just shoving tons of CSS and JavaScript into blocks at the beginning and end of the layout. Also, all my images are being hosted on the channel cloud files.

Git repo relocation

The official git repository for the ownMapp project has migrated to
Updated for new repo URL. (2abb303a) | Commits | zot / ownmapp | GitLab

The repo hosted on GitHub for the standalone web app was also updated to direct people to the new development:
Update · anaqreon/ownMapp@3092de0
Haakon Meland Eriksen
I just put in Github and not Gitlab, reminder to fix deploy script.
Would it be useful to allow photo attachments to markers?
The official Git repository has moved to See the project webpage for details.
Events control panel

Added a control panel for #events to allow event marker centering. More events features to come, including links to the full event info page and options to hide the display of past events.

Added events control panel with event marker centering (775f6da4) | Commits | zot / ownmapp | GitLab