OSM / Tickets Integration

[Chuck Killian]

Eric,

I have created a stand-alone instance of Open Street Maps will capabilities that I need for what I do.

Different grids

Address lookup

Bounded areas

Measurement tools and such

I'd like to discuss how to integrate it into Tickets.

I have the latest version of tickets running. I know there is guidance for setting up connections to map sources but I find them pretty obtuse.

Thanks!

Chuck...

Chuck Killian

WB6YOK

ARRL Life Member

801.791.0760

[Eric Osterberg]

And have you reviewed the youtube video dedicated to this subject? Try starting here: https://youtu.be/FOpZlZ9on00?t=152

Share with me how you created an "Open Street Maps Server"?

Is this a tile server? Or something else?

Here's an answer from Google Gemini. I asked it what someone might mean when they say they have a local OSM server.

---

When someone mentions setting up a local "OpenStreetMap Server," they usually mean one of three distinct services (or a bundle of them):

1. Raster Tile Server (Standard Map Display)

• What it is: A web service serving pre-rendered .png map images via the standard XYZ tile format (e.g., http://<server-ip>:<port>/tile/{z}/{x}/{y}.png or /{z}/{x}/{y}.png).
  
  
• Common stacks: Docker containers running overv/openstreetmap-tile-server, Renderd + mod_tile with Mapnik and PostGIS, or lightweight MBTiles/TileServer GL containers.
  
  
• TicketsCAD integration: This is the primary map layer Leaflet consumes. In TicketsCAD v4, this replaces the default public OSM tile endpoint ([https://tile.openstreetmap.org/](https://tile.openstreetmap.org/){z}/{x}/{y}.png).
  
  

2. Nominatim Geocoding Server (Address Search / Reverse Geocoding)

• What it is: The search engine for OSM data. It converts street addresses to lat/long coordinates and vice versa (returning JSON from endpoints like http://<server-ip>:<port>/search?format=json&q=...).
  
  
• Common stacks: mediagis/nominatim Docker containers or native Nominatim on PostgreSQL/PostGIS.
  
  
• TicketsCAD integration: v4 uses Nominatim for address auto-complete and incident location lookups. Setting up a local tile server alone will not handle offline address searching—they need a local Nominatim instance if they operate completely air-gapped.
  
  

3. Routing Engine (Optional)

• What it is: Turn-by-turn or shortest-path calculation APIs (such as OSRM, Valhalla, or GraphHopper).
  
  
• TicketsCAD integration: Generally secondary, used only if route lines or drive-time estimates are being calculated locally.
  
  

Questions to Clarify With Them

• Which endpoint formats are exposed? Ask for their base URL scheme (e.g., [http://192.168.1.50:8080/tile/](http://192.168.1.50:8080/tile/){z}/{x}/{y}.png for tiles, or [http://192.168.1.50:8080/search](http://192.168.1.50:8080/search) for geocoding).
  
  
• Are they using standard Slippy Map (XYZ) raster tiles or Vector tiles? TicketsCAD/Leaflet uses raster tiles by default. If they generated vector .pbf tiles, they will need a style renderer like TileServer GL to serve raster tiles.
  
  
• Is their deployment air-gapped? If they are running offline, confirm whether they also deployed a local Nominatim instance to avoid address lookup timeouts.

--
You received this message because you are subscribed to the Google Groups "Open Source CAD" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-source-c...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/emad3af0e4-6fa2-4102-878e-9118565c240f%40xmission.com.