Muhammad I.

I've built production web GIS since 2017, including a national disaster-monitoring platform that serves live satellite imagery. I build the map, the PostGIS database behind it and the pipelines that feed it. I also turn messy PDFs, supplier quotes and invoices into data you can check. Every value keeps the line it came from. Totals and units get checked. Anything that doesn't add up waits for a person. PROBLEMS I SOLVE - We have the data but no usable web map." Interactive 2D and 3D web maps with search, filters and layers, on PostGIS and GeoServer (Leaflet, OpenLayers, Mapbox/MapLibre, Cesium). - Our GeoTIFFs and shapefiles are too big to put online." I'll build a pipeline that checks, reprojects and converts them (Cloud Optimized GeoTIFF) and serves fast raster and vector tiles. - Our field teams still collect data on paper." Web and Android survey apps that sync geotagged records and large uploads into PostGIS. - Someone retypes PDFs into Excel all day." Extraction with a review step, so nothing doubtful reaches your system. It can run on your own server if your documents can't leave the building. - We need the whole app, not just the map." The dashboard, admin panel, API and deployment around it, built with Next.js, Python/FastAPI or Node, and shipped with Docker. WHAT I'VE BUILT - Lead web GIS engineer in the public sector: imagery map services, spatial databases, and training non-technical staff to run them. These systems are restricted. I can't name or link them, but I can walk you through them on a call. - 3D yacht-berth map on open data (live demo in my portfolio): a 60 m yacht at true scale, placed along a real dock. - Field survey platform: API, PostgreSQL/PostGIS, a React web app and an Android app, with automated deployment. - Tiling engine: raw rasters and vectors in, map-ready XYZ and vector tiles out, run by a background job queue. - Document pipeline tested on 316 public RFQ documents, 53 of them checked by hand: 98% right on "is this file relevant?", and 83% of the values found and correct before review. The other 17% is why a person reviews before export. Good fit: web map apps, PostGIS databases and spatial data pipelines, tile services, field data collection, and document workflows that need a review step. Send me a sample of your data or documents and one sentence on the result you need. I'll reply with how I'd approach it, where the risk is, and a first milestone.